
From vesely@tana.it  Wed Jun  1 03:10:48 2011
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 75C8AE073F for <ietf@ietfa.amsl.com>; Wed,  1 Jun 2011 03:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.542
X-Spam-Level: 
X-Spam-Status: No, score=-5.542 tagged_above=-999 required=5 tests=[AWL=-0.823, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id onvEY60pmYc3 for <ietf@ietfa.amsl.com>; Wed,  1 Jun 2011 03:10:46 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 6A766E069E for <ietf@ietf.org>; Wed,  1 Jun 2011 03:10:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1306923041; bh=4xLQkWrOpuFAl8B7wwifeT9dQ51BziQpligx2OtZwt4=; l=7729; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=QunJDEU5ZGc6t072ylBrSPTBhjJhb6DvKSnf3ePYPu36xITixIYaMt+mrc7wnEUSH c1gNgUpVp3R5/qgCDvVRS3U/f5AiP95CkaoP+8BtWk7uIbym7Lgb5aLr+1LVxOnfoz QJn406qA0znINlEO7+rq9SjZKvFxwVj+MuVf/Gz0=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Wed, 01 Jun 2011 12:10:41 +0200 id 00000000005DC039.000000004DE61021.00003CCF
Message-ID: <4DE61020.2040401@tana.it>
Date: Wed, 01 Jun 2011 12:10:40 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call:	<draft-housley-two-maturity-levels-06.txt> (Reducing the	Standards Track to Two Maturity Levels) to BCP
References: <20110505161306.3291.13078.idtracker@ietfa.amsl.com> <24D7252BC7EC8D2A1BDAE9D4@PST.JCK.COM>
In-Reply-To: <24D7252BC7EC8D2A1BDAE9D4@PST.JCK.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 10:10:48 -0000

For an outsider's feedback about John's comments (1), (4), and (5):

On 31/May/11 18:23, John C Klensin wrote:
> This proposal is problematic in several ways.  The first is
> obviously the most important, but the others suggest changes
> that might be useful whether or not that main provision is
> adopted.
> 
> (1) Excessively-high requirements for Proposed Standard and
> dropping the three-level model.
> 
> 	The document asserts, I believe correctly, that one of the
> 	problems with the IETF Standards Process is that the
> 	relatively low bar established for Proposed Standards in
> 	RFC 2026 has evolved into a very high bar and that we
> 	should return to that lower requirement level.  Yet it
> 	effectively proposed to solve that problem by reducing the
> 	number of steps in the standards process to two.  No
> 	evidence has been offered that whether or not the standards
> 	process is two levels or three has anything to do with
> 	difficulties completing Proposed Standards or getting them
> 	to a satisfactory level of completeness and correctness.
> 	The logic on that subject in the document appears to me to
> 	quite similar to a physician saying "We agree there is a
> 	problem with your hand.  We don't know how to treat it
> 	either surgically or medically, but we should do something,
> 	so let's amputate your foot".  That really makes no sense
> 	and is probably bad for the patient (only probably... one
> 	really never knows).
> 
> 	In addition, draft-housley-two-maturity-levels-06 does not
> 	discuss any mechanism for getting from the current
> 	as-practiced requirements for Proposed Standard back to the
> 	requirements of RFC 2026, a schedule for doing so, nor
> 	whether it is necessary to warn readers about the level of
> 	scrutiny applied (it may not be, but there has been little
> 	or no discussion of that subject in the IETF and there is
> 	no such discussion in the document).  If this were a
> 	technical specification, unless there were an expectation
> 	that a transition will occur immediately and by magic, that
> 	omission would be a "known defect".
> 
> 	Suggestion: The level of completeness and quality required
> 	for a Proposed Standard, at least insofar as those
> 	requirements exceed the requirements in RFC 2026, are
> 	entirely in the hands of the IESG, relevant WGs, and the
> 	Last Call process.  Whether those requirements can be
> 	reduced to the level required by 2026 has nothing to do
> 	with this document because there is no change to the 2026
> 	requirements.

While those considerations are entirely self-evident, I omit John's
suggestions (i), (ii), and (iv) as they address an apparently
different problem.  In facts, on the requirements for Proposed
Standard, the I-D says that "they remain exactly as specified in RFC
2026", which seems to mean that the I-D is not attempting to alter
their formal status in any way.

I agree that the transition described in Section 5 is somewhat abrupt.
 It seems to me it would be smoother and more flexible to allow the
new two-step ladder to coexist with the current three-step one, at
least temporarily.  That is to say, use "add to" rather than "replace"
or "change" in the RFC Editor notes, and alter the last sentence in
section 2 to read

   Minor revisions and the removal of unused features are expected,
   but a significant revision may require that the specification
   accumulate more experience at either Proposed Standard or Draft
   Standard before progressing.

In John's word:

>         (iii) The above implies that different areas, and
> 			perhaps even different WGs within an area, will end
> 			up with different practical requirements based, at
> 			least in part, on their perception of the risks
> 			implied by a less comprehensive document.  I see
> 			that as an advantage and recognition of reality,
> 			not a problem. 


> (4) Discussion of the STD document series in Section 6.
> 
> 	It has been pointed out several times, in recent months to
> 	suppress discussion of proposals that might be alternates
> 	to some or all of this one, that there are many issues with
> 	how the IETF develops, approves, documents, and manages
> 	standards that are not addressed in this specification and
> 	that the community cannot reasonable expect to address all
> 	at the same time.  The question of what should be done
> 	about the STD numbers is just one entry on this very long
> 	list.  Examination of other IETF procedural RFCs indicates
> 	that we rarely, if ever, include a discussion of a single
> 	option that we have decided to _not_ pursue (even if only
> 	in the near term).  The only apparent justification for
> 	including Section 6 in this draft is that there was a
> 	specific proposal in an earlier version, a proposal that,
> 	as the draft indicates, did not get community consensus.
> 	The section should be dropped from this document before
> 	publication.  If the community wants to have a series
> 	discussion of STD numbers, I suggest that
> 	draft-klensin-std-numbers might be one contribution to that
> 	discussion.

+1, different documents for different problems.

> (5) Patents
> 
>     The specification says (last bullet in Section 2): 
> 
>     > * If patented or otherwise controlled technology is
> 	>   required for implementation, the separate
> 	>   implementations must also have resulted from separate
> 	>   exercise of the licensing process.  
> 
> 	While this text is copied from 2026, things have changed
> 	and the requirement has been interpreted very loosely,
> 	particularly to leave interpretation of "required" in the
> 	hands of the implementers.
> 
> 	If it is repeated in a spec that is approved now and that
> 	claims to reset and clarify Draft Standard requirements, it
> 	can easily be read as a requirement that the community has
> 	to somehow evaluate whether claimed controlled technology
> 	is actually "required for implementation".  That may be
> 	obvious in some cases; it may be highly controversial and
> 	dependent of validity of patent claims (something that can
> 	normally be resolved only by the courts) in others.  The
> 	IETF has been repeatedly advised, both by legal counsel and
> 	by various incarnations of IPR WGs, to avoid straying into
> 	the territory in which it takes a position on whether an
> 	IPR claim is valid.  Consider a scenario in which some
> 	company, say ChuckCo, decides that an IETF Internet
> 	Standard for Alice's proposal would put them at a
> 	competitive disadvantage.  It is merely necessary for
> 	ChuckCo to file an IPR claim against the technology in
> 	Alice's spec, even a obviously spurious one, assert a
> 	completely irrational and punitive licensing model that
> 	cannot be exercised in a reasonable way, and then sit back
> 	and watch the IETF paralyze itself over this provision as
> 	written.
> 
> 	Suggestion: I believe that advice of Counsel should be
> 	sought about this language and, if feasible, alternate
> 	language produced that either turns the requirement into an
> 	"if feasible" request or that places the responsibility for
> 	evaluating whether the claims are applicable on the
> 	implementers and not on the IETF or IESG.

I suggest that any IPR notices be referenced from RFCs, somewhere
among other boilerplate in the front matter.  If at all possible,
purely defensive patents, for which clearly worded statements grant
unencumbered use of the relevant technology, should enjoy a
distinguished wording that quickly conveys such condition.  No
separate exercise of the licensing process seems to be necessary for
such cases.  On the opposite, I see no reasons for standardizing
technologies that are known to require payed licenses, unless (part
of) that money goes to the IETF.

jm2c

From Ed.Lewis@neustar.biz  Wed Jun  1 08:04:13 2011
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A137E06D9; Wed,  1 Jun 2011 08:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.456
X-Spam-Level: 
X-Spam-Status: No, score=-106.456 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b3HZ+IsSbfLr; Wed,  1 Jun 2011 08:04:12 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 68F09E06FC; Wed,  1 Jun 2011 08:04:12 -0700 (PDT)
Received: from Work-Laptop-2.local (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p51F49BX051218; Wed, 1 Jun 2011 11:04:10 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.204.168] by Work-Laptop-2.local (PGP Universal service); Wed, 01 Jun 2011 11:04:10 -0400
X-PGP-Universal: processed; by Work-Laptop-2.local on Wed, 01 Jun 2011 11:04:10 -0400
Mime-Version: 1.0
Message-Id: <a06240802ca0bff6fff57@[10.31.204.168]>
In-Reply-To: <20110526152257.21795.30012.idtracker@ietfa.amsl.com>
References: <20110526152257.21795.30012.idtracker@ietfa.amsl.com>
Date: Wed, 1 Jun 2011 11:03:57 -0400
To: <ietf@ietf.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt>  (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: The IESG <iesg-secretary@ietf.org>, ed.lewis@neustar.biz, 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: Wed, 01 Jun 2011 15:04:13 -0000

At 8:22 -0700 5/26/11, The IESG wrote:
>The IESG has received a request from the DNS Extensions WG (dnsext) to
>consider the following document:
>- 'Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA
>    Registry'
>   <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> as a Proposed Standard

As someone that would implement against this document, I find its 
role confusing.

The title is
#   Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA
#                                Registry

Is this title meant to tell me that this is defining or redefining 
the DNSKEY Algorithm Registry run by IANA?  The "Applicability" part 
is a little confusing.

I mention this because of the following text in the Introduction:

# This document replaces the original list with a new table that includes the
# current compliance status for certain algorithms.
#
# This compliance status indication is only to be considered for
# implementation, not deployment or operations.  Operators are free to
# deploy any digital signature algorithm available in implementations
# or algorithms chosen by local security policies.  This status is to
# measure compliance to this RFC only.

The first sentence seems to be refining the registry.  Then there are 
words saying that this document relates only to code development and 
not use.  The final sentence mentions "compliance to this RFC" and 
this is where I lose it.

I am all for a document to define a registry.  And in my experience, 
a registry is supposed to map objects to entities (in this case 
DNSKEY algorithms to values in a protocol field) in a fairly neutral 
way.

I am all for a document to define an operational profile, requiring 
certain choices to be made to be conformant to some standard of 
service delivery.  I would like to be able to advertise that "we 
conform with RFC wxyz" and have that say we operate with certain 
algorithms.

But I don't think it is correct to do both in the same document. 
This gets very confusing when trying to deal with RFPs (Request for 
Propsals and the like) that list RFCs that should be complied with. 
One issue is the conflict between the neutrality of a registry's 
function and the advocacy of a profile document.

I fail to see the rationale that all implementations must support 
specific algorithms.  (Interoperability doesn't need that.)  I 
understand that if the topic is "general purpose implementations" 
there are a common set of algorithms such implementations should 
support.  There are, however, turnkey DNS deployments in which these 
algorithms may not make sense.  Any implementation is free to ignore 
an algorithm or to treat responses as "bad" if it wants to.

A strong tenet of the DNSSEC policy is that "local policy" is the 
trump card in all security decisions.  The cache that is being 
protected gets to choose it's own policy.  By creating a registry 
that commands what is implemented and not implemented, there's a 
conflict with "local policy".  I don't mean that the implementation 
of the cache is restricted, but the authority and other middle DNS 
servers are restricted.

My recommendation is to turn this document into something called a 
"Public Internet General Purpose DNSKEY ALgorithm Profile", make it a 
BCP (that can be updated) and let it summarily list the algorithms 
that should or shouldn't be included.  Leave these designations out 
of the registry (table) and don't have this document try to change 
the registry.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis             
NeuStar                    You can leave a voice message at +1-571-434-5468

Now, don't say I'm always complaining.
Wait, that's a complaint, isn't it?

From lorenzo@google.com  Tue May 31 09:52:55 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 801B3E0829 for <ietf@ietfa.amsl.com>; Tue, 31 May 2011 09:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bn8VGT5wBp22 for <ietf@ietfa.amsl.com>; Tue, 31 May 2011 09:52:55 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id BB4E1E083B for <ietf@ietf.org>; Tue, 31 May 2011 09:52:51 -0700 (PDT)
Received: from hpaq12.eem.corp.google.com (hpaq12.eem.corp.google.com [172.25.149.12]) by smtp-out.google.com with ESMTP id p4VGqop8032494 for <ietf@ietf.org>; Tue, 31 May 2011 09:52:50 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1306860770; bh=FHJFYtd0YIhp+q1VU7ptc1HbeEk=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=hZUWWOHByBomA8TwGjEJytE6zo5hQe5EUu0PD6MAB2qwqcpSgNtyUT6qyFOaavpdh C5SoH2uGpiqlUvYQ13pSQ==
Received: from yie12 (yie12.prod.google.com [10.243.66.12]) by hpaq12.eem.corp.google.com with ESMTP id p4VGpGB7025578 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Tue, 31 May 2011 09:52:49 -0700
Received: by yie12 with SMTP id 12so2855951yie.27 for <ietf@ietf.org>; Tue, 31 May 2011 09:52:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=J9EVmdnRsMC9NjMrwJDjm7zZgMxbVn78n3r5YdWfj+E=; b=kVyMQYKwIvnD9V8gVA7kMYOdricoy0o7Yg9rS6iL7xJY0UsUVubO5X8ZetYAX1STQg IdrSM/Z0pHhbETJXggzw==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=iJX0AL3K7Hb6QipvsOW/5XPqP6b7hYD2IjK3pgWBva+06bsbUkE9pOWIrEY51EAOtD Fo+ZAigSo6vvyrpMyPxw==
Received: by 10.151.24.10 with SMTP id b10mr5120949ybj.93.1306860768479; Tue, 31 May 2011 09:52:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.101.5 with HTTP; Tue, 31 May 2011 09:52:28 -0700 (PDT)
In-Reply-To: <CA0A60E8.28C51%jason_livingood@cable.comcast.com>
References: <BANLkTi=s_WHKnGzf=azS41m9tvnR4FJ16DevD4jOqwEwf09iJQ@mail.gmail.com> <CA0A60E8.28C51%jason_livingood@cable.comcast.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 31 May 2011 09:52:28 -0700
Message-ID: <BANLkTikLUf5f372cqyPX0VJGXf9x3HRJfg@mail.gmail.com>
Subject: Re: [v6ops] Review of: draft-ietf-v6ops-v6-aaaa-whitelisting-implications-03 *(formal for apps area)*
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
Content-Type: multipart/alternative; boundary=000e0cd23ef6e048bc04a4953bcf
X-System-Of-Record: true
X-Mailman-Approved-At: Wed, 01 Jun 2011 09:59:07 -0700
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, Apps Review <apps-review@ietf.org>, IETF Discussion <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2011 16:52:55 -0000

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

On Tue, May 31, 2011 at 6:17 AM, Livingood, Jason <
Jason_Livingood@cable.comcast.com> wrote:

>   While you have not contributed text per se (by sending it directly), I
> try to be a good listener and items you and other Googlers have raised have
> been included in the document around motivations and so on. Even new
> Sections 3.2 and 3.2 were added based on listening to you and/or your
> colleagues talk about the issue (and some direct conversations a couple of
> weeks ago).
>

Sure - anything said at the IETF and on mailing lists is subject to the note
well. But I wouldn't want to be seen as having contributed to the document.

Regards,
Lorenzo

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

<div class=3D"gmail_quote">On Tue, May 31, 2011 at 6:17 AM, Livingood, Jaso=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:Jason_Livingood@cable.comcast.com=
">Jason_Livingood@cable.comcast.com</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex;">





<div style=3D"word-wrap:break-word;color:rgb(0, 0, 0);font-size:16px;font-f=
amily:Calibri, sans-serif"><div class=3D"im">
<div>
<div>
<div>While you have not contributed text per se (by sending it directly), I=
 try to be a good listener and items you and other Googlers have raised hav=
e been included in the document around motivations and so on. Even new Sect=
ions 3.2 and 3.2 were added based
 on listening to you and/or your colleagues talk about the issue (and some =
direct conversations a couple of weeks ago).=A0</div></div></div></div></di=
v></blockquote><div><br></div><meta http-equiv=3D"content-type" content=3D"=
text/html; charset=3Dutf-8"><div>

Sure - anything said at the IETF and on mailing lists is subject to the not=
e well. But I wouldn&#39;t want to be seen as having contributed to the doc=
ument.</div><div><br></div><div>Regards,</div><div>Lorenzo</div></div>


--000e0cd23ef6e048bc04a4953bcf--

From ajs@anvilwalrusden.com  Wed Jun  1 10:52:44 2011
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 A58D5E078F; Wed,  1 Jun 2011 10:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level: 
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=0.091,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JfZfUEcQLcaC; Wed,  1 Jun 2011 10:52:43 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 09733E0860; Wed,  1 Jun 2011 10:52:19 -0700 (PDT)
Received: from shinkuro.com (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 520561ECB422; Wed,  1 Jun 2011 17:52:18 +0000 (UTC)
Date: Wed, 1 Jun 2011 13:52:17 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org, dnsext@ietf.org
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
Message-ID: <20110601175216.GX26780@shinkuro.com>
References: <20110526152257.21795.30012.idtracker@ietfa.amsl.com> <a06240802ca0bff6fff57@10.31.204.168> <BANLkTimpGsRXuHi2zuuJKrZi1Ypcic5Xkw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BANLkTimpGsRXuHi2zuuJKrZi1Ypcic5Xkw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 17:52:44 -0000

On Wed, Jun 01, 2011 at 01:18:11PM -0400, Scott Rose wrote:
> > The title is
> > #   Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA
> > #                                Registry
> >
> > Is this title meant to tell me that this is defining or redefining the
> > DNSKEY Algorithm Registry run by IANA?  The "Applicability" part is a little
> > confusing.
> >
> 
> Technically redefining if you want to split hairs.

We could remove the "Applicability Statement" in the title, if that would help.  Ed?

> Our main reason for replacing the registry table with a doc containing a new
> table was that not all implementors may be good at sorting through the IETF
> archives looking for every DNSSEC related RFC and BCP.  Have a simple table
> at a well known repository will hopefully reduce that document hunt.

I think this is the key point, and I want to make it more strongly
than Scott does: we already tried that.  

We have some documents that say which algorithms are mandatory to
implement.  Other RFCs have defined algorithms but were silent on
whether something needed to be implemented -- quite correctly, since
it is meaningless for a document to define what MUST be done for
anything other than conformance with it.  Finally, the DNS world has a
long history of requirements littered throughout various RFCs, but
without a codex that would allow you to find all the RFCs you need to
read to understand what you ought to do for your particular
implementation.

We received feedback at a meeting (in Maastricht, I think, and from
Steve Kent, I think) that the DNSEXT WG should pick some algorithms
and make it clear that those are the ones everyone ought to be able to
use, if they want to be interoperable with everyone else.  We were
also advised to make clear the one(s) we believe to be "up next", on
the grounds that implementers and deployers can be ready.

So, the goal here is threefold: (1) to collect all those MUSTs and
MUST NOTs into one RFC: anything not defined in that RFC as required
is completely optional; (2) to provide a single place where
implementers can find out where that advice is located; (3) to make
sure that we don't somehow end up with conflicting advice.

The list of requirements in this draft satisfies (1).  One conforms to
an RFC, and if it is published as an RFC then this document is the one
to which one should refer in RFPs and so on, assuming one wants this
sort of general-purpose conformance.  (If you only wanted GOST, for
instance, you wouldn't require conformance to this document.  That's
just a different decision.)

Now, of course, (2) could be solved in more than one way.  We could
put up http://tools.ietf.org/wg/dnsext/guide-to-the-perplexed and
include a link to this document (if it becomes an RFC).  But that
would not solve (3).

(3) is the real reason to use the registry for this.  Registries are
not just there to have a single convenient place to look everything
up.  They also exist because they prevent collisions and so on.  Only
one entry can be in the registry for code point _n_.  The "conformance
to RFC TBD1" column is yet anothe such condition: only RFC TBD1 is
allowed to add things to that column.  So if anything comes along and
tries to add things to that column, we know we have a failure, and the
registry entry doesn't get created until the problem is solved.

In this way, the draft is using the registry exactly as it was
intended: it is a control point that makes sure a given assignment
happens in a co-ordinated way.  In this case, the assignment is "DNS
community current best advice about what will be maximally
interoperable."  It's not a blessing; it's just another entry that
ensures co-ordination on the Internet in a way that ensures
interoperability is maximized.

Best,

A (document shepherd)

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From shanna@juniper.net  Wed Jun  1 11:16:08 2011
Return-Path: <shanna@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA8C130019; Wed,  1 Jun 2011 11:16:08 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wtzT3GvZjxUu; Wed,  1 Jun 2011 11:16:07 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id 4DA9513000B; Wed,  1 Jun 2011 11:15:57 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKTeaB3M4VN40gRIuNMaxAOQeXj9LBkRTp@postini.com; Wed, 01 Jun 2011 11:16:02 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 1 Jun 2011 11:15:18 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Wed, 1 Jun 2011 14:15:17 -0400
From: Stephen Hanna <shanna@juniper.net>
To: "secdir@ietf.org" <secdir@ietf.org>, "draft-ietf-dnsext-rfc2672bis-dname@tools.ietf.org" <draft-ietf-dnsext-rfc2672bis-dname@tools.ietf.org>
Date: Wed, 1 Jun 2011 14:15:15 -0400
Subject: secdir review of draft-ietf-dnsext-rfc2672bis-dname-22.txt
Thread-Topic: secdir review of draft-ietf-dnsext-rfc2672bis-dname-22.txt
Thread-Index: Acwgh9s80YeQfWrkRySR5CC9/YhwJg==
Message-ID: <AC6674AB7BC78549BB231821ABF7A9AEB57B40575D@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 01 Jun 2011 18:16:08 -0000

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 intends to replace RFC 2672, the definition of DNAME
redirection in the DNS. DNAME is a DNS resource record type that
(in layman's terms) indicates that all domain names ending in a
specified suffix should be redirected to domain names where the
suffix is replaced by a specified value. For example, all names
that end with example.com should be remapped to example.net.

The document is quite thorough, apparently because the DNAME RR
has been used for many years and a great deal of real-world
experience has been gained. That's definitely a good thing!

>From a security perspective, this document includes a more
thorough analysis of security considerations than the original
RFC 2672. It also includes a more thorough discussion of DNSSEC
interactions than the earlier document.

I do not see any security issues that are not well covered in
this document. While I don't think this document will close any
major security issues, it includes some helpful guidance. So
I recommend that this document advance to RFC status.

Thanks,

Steve


From Ed.Lewis@neustar.biz  Wed Jun  1 12:28:56 2011
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CFA0130052; Wed,  1 Jun 2011 12:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.495
X-Spam-Level: 
X-Spam-Status: No, score=-106.495 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wUgGZg2Qcub8; Wed,  1 Jun 2011 12:28:55 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 86DF9E0833; Wed,  1 Jun 2011 12:28:53 -0700 (PDT)
Received: from Work-Laptop-2.local (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p51JSoTU053111; Wed, 1 Jun 2011 15:28:50 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.204.168] by Work-Laptop-2.local (PGP Universal service); Wed, 01 Jun 2011 15:28:52 -0400
X-PGP-Universal: processed; by Work-Laptop-2.local on Wed, 01 Jun 2011 15:28:52 -0400
Mime-Version: 1.0
Message-Id: <a06240801ca0c41897e0b@[10.31.204.168]>
In-Reply-To: <BANLkTimpGsRXuHi2zuuJKrZi1Ypcic5Xkw@mail.gmail.com>
References: <20110526152257.21795.30012.idtracker@ietfa.amsl.com> <a06240802ca0bff6fff57@10.31.204.168> <BANLkTimpGsRXuHi2zuuJKrZi1Ypcic5Xkw@mail.gmail.com>
Date: Wed, 1 Jun 2011 15:28:46 -0400
To: <scott.rose@nist.gov>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt>  (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA  Registry) to Proposed Standard
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: dnsext@ietf.org, Edward Lewis <Ed.Lewis@neustar.biz>, 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: Wed, 01 Jun 2011 19:28:56 -0000

At 13:18 -0400 6/1/11, Scott Rose wrote:

>This doc doesn't change that at all.  You can still implement whatever
>you want, just not claim conformance to this doc.

If that's the case, then there should be no IANA changes from this document.

>Our main reason for replacing the registry table with a doc containing a
>new table was that not all implementors may be good at sorting through
>the IETF archives looking for every DNSSEC related RFC and BCP.  Have a
>simple table at a well known repository will hopefully reduce that
>document hunt.

I think there's a misunderstanding about the role of a registry table 
and a profile when it comes to conformance.  E.g., look at the DNS 
registry of RR type codes.  Implementations would support a type by 
using the directions in the documents indicated in the last column. 
This does not indicate whether the type is a good idea to support or 
not, just indicates the definition.

There is no list of types that "are actually in use."  That would be 
nice to have.  If this document is trying to fill that role, then 
fine, but don't change the underlying registry table.

As far as "Applicability Statement" in the title, which Olafur notes 
is defined in RFC 2026 (an unreferenced document, need to add that 
then), then make this document an applicability statement and not a 
change to a registry.


-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

Now, don't say I'm always complaining.
Wait, that's a complaint, isn't it?

From Ed.Lewis@neustar.biz  Wed Jun  1 12:45:56 2011
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC43C130070; Wed,  1 Jun 2011 12:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.503
X-Spam-Level: 
X-Spam-Status: No, score=-106.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sy4oHCULL-aE; Wed,  1 Jun 2011 12:45:56 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 317A7130048; Wed,  1 Jun 2011 12:45:56 -0700 (PDT)
Received: from Work-Laptop-2.local (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p51Jjokm053229; Wed, 1 Jun 2011 15:45:51 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.204.168] by Work-Laptop-2.local (PGP Universal service); Wed, 01 Jun 2011 15:45:52 -0400
X-PGP-Universal: processed; by Work-Laptop-2.local on Wed, 01 Jun 2011 15:45:52 -0400
Mime-Version: 1.0
Message-Id: <a06240802ca0c457b6ab4@[10.31.204.168]>
In-Reply-To: <20110601175216.GX26780@shinkuro.com>
References: <20110526152257.21795.30012.idtracker@ietfa.amsl.com> <a06240802ca0bff6fff57@10.31.204.168> <BANLkTimpGsRXuHi2zuuJKrZi1Ypcic5Xkw@mail.gmail.com> <20110601175216.GX26780@shinkuro.com>
Date: Wed, 1 Jun 2011 15:45:48 -0400
To: Andrew Sullivan <ajs@anvilwalrusden.com>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: [dnsext] Last Call:  <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement:  DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: ietf@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: Wed, 01 Jun 2011 19:45:57 -0000

At 13:52 -0400 6/1/11, Andrew Sullivan wrote:

>We could remove the "Applicability Statement" in the title, if that would
>help.  Ed?

I think the issue is where to put what conventional wisdom considers 
the current algorithms to use.  No matter how much I think about it, 
I think putting this in a registry is a mistake.

The problem is that a registry is a current state of affairs.  It is 
not versionable.  I don't say my implementation is compliant with the 
IANA registry of 1999.  If I did, there's no way to check that. 
However, I can say my implementation is compliant (as in built to the 
contents of) RFC 2065.  'Course, RFC 2065 is obsolete, but my code 
may not have been changed.  If I re-implement to meet RFC 2535 and 
then later to RFC 4033-4035, you can verify this via the history of 
documents.  The types in the IANA registry show the current 
definitions, but the RFCs keep the history.

>We received feedback at a meeting (in Maastricht, I think, and from
>Steve Kent, I think) that the DNSEXT WG should pick some algorithms
>and make it clear that those are the ones everyone ought to be able to
>use, if they want to be interoperable with everyone else.  We were
>also advised to make clear the one(s) we believe to be "up next", on
>the grounds that implementers and deployers can be ready.

Then just issue a document called "DNSEXT's Preferred Algorithms 
2011" and make it an RFC.  This way, in 10 years, we can sit back and 
laugh at what was fashionable back in the day.

>So, the goal here is threefold: (1) to collect all those MUSTs and
>MUST NOTs into one RFC: anything not defined in that RFC as required
>is completely optional; (2) to provide a single place where
>implementers can find out where that advice is located; (3) to make
>sure that we don't somehow end up with conflicting advice.

That would be nice, I just think a registry is the wrong place to put 
that - because registries change and old (deployed) implementations 
don't.

>In this way, the draft is using the registry exactly as it was
>intended: it is a control point that makes sure a given assignment
>happens in a co-ordinated way.  In this case, the assignment is "DNS
>community current best advice about what will be maximally
>interoperable."  It's not a blessing; it's just another entry that
>ensures co-ordination on the Internet in a way that ensures
>interoperability is maximized.

But the "current best advice" changes.  And old versions of software don't.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

Now, don't say I'm always complaining.
Wait, that's a complaint, isn't it?

From ajs@anvilwalrusden.com  Wed Jun  1 13:34:27 2011
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 4EDD1E0976; Wed,  1 Jun 2011 13:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level: 
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ojG5hfZgGvuX; Wed,  1 Jun 2011 13:34:26 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id B0CD2E0977; Wed,  1 Jun 2011 13:33:58 -0700 (PDT)
Received: from shinkuro.com (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id C241A1ECB422; Wed,  1 Jun 2011 20:33:56 +0000 (UTC)
Date: Wed, 1 Jun 2011 16:33:55 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org, dnsext@ietf.org
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
Message-ID: <20110601203355.GB26780@shinkuro.com>
References: <20110526152257.21795.30012.idtracker@ietfa.amsl.com> <a06240802ca0bff6fff57@10.31.204.168> <BANLkTimpGsRXuHi2zuuJKrZi1Ypcic5Xkw@mail.gmail.com> <20110601175216.GX26780@shinkuro.com> <a06240802ca0c457b6ab4@[10.31.204.168]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a06240802ca0c457b6ab4@[10.31.204.168]>
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, 01 Jun 2011 20:34:27 -0000

On Wed, Jun 01, 2011 at 03:45:48PM -0400, Edward Lewis wrote:

> >So, the goal here is threefold: (1) to collect all those MUSTs and
> >MUST NOTs into one RFC: anything not defined in that RFC as required
> >is completely optional; (2) to provide a single place where
> >implementers can find out where that advice is located; (3) to make
> >sure that we don't somehow end up with conflicting advice.
> 
> That would be nice, I just think a registry is the wrong place to
> put that - because registries change and old (deployed)
> implementations don't.

> >In this way, the draft is using the registry exactly as it was
> >intended: it is a control point that makes sure a given assignment
> >happens in a co-ordinated way.  In this case, the assignment is "DNS
> >community current best advice about what will be maximally
> >interoperable."  It's not a blessing; it's just another entry that
> >ensures co-ordination on the Internet in a way that ensures
> >interoperability is maximized.
> 
> But the "current best advice" changes.  And old versions of software don't.

Right.  And the RFC to which those old versions of software conforms
doesn't change either.

You cannot claim conformance to the registry, because registries are
not an archival series and because they do change.  We agree on that.
But you don't seem to think that the registry of RRTYPE code points
changing is a bad idea, even though early software didn't have the
RRTYPE for DNAME or DNSKEY.  In the same way, the registry of these
algorithm types might change, and it wouldn't matter.  But nobody is
allowed to put _anything_ into that "Compliance to RFC TBD1" column.
If the WG wants in future to make some shiny new algorithm
"RECOMMENDED TO IMPLEMENT" according to the latest guidance, and wants
that to be reflected in a registry somewhere, then the answer is to
write a new document that obsoletes the draft we're talking about, and
completely replace the typecode registry again, with the new values
(presumably, a new column, called "Compliance to RFC TBD2", and
dropping the analagous column from the current version).

I believe that nothing anywhere in the document suggests that one
ought to guage conformance of software against the registry, and if
you think it says that somewhere, I'd like a pointer to where.  It
would need to be fixed if it said that, but as far as I can tell it
does not.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From rsf@ns.live555.com  Wed Jun  1 14:59:21 2011
Return-Path: <rsf@ns.live555.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A312E08E8 for <ietf@ietfa.amsl.com>; Wed,  1 Jun 2011 14:59: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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZOcePxS90G8 for <ietf@ietfa.amsl.com>; Wed,  1 Jun 2011 14:59:20 -0700 (PDT)
Received: from ns.live555.com (ns.live555.com [4.79.217.242]) by ietfa.amsl.com (Postfix) with ESMTP id 98C24E08A2 for <ietf@ietf.org>; Wed,  1 Jun 2011 14:59:20 -0700 (PDT)
Received: from ns.live555.com (localhost.live555.com [127.0.0.1]) by ns.live555.com (8.14.4/8.14.4) with ESMTP id p51Lw9FN000129 for <ietf@ietf.org>; Wed, 1 Jun 2011 14:58:09 -0700 (PDT) (envelope-from rsf@ns.live555.com)
Received: (from rsf@localhost) by ns.live555.com (8.14.4/8.14.4/Submit) id p51Lw9bA000118; Wed, 1 Jun 2011 14:58:09 -0700 (PDT) (envelope-from rsf)
Mime-Version: 1.0
Message-Id: <f06240801ca0c65310a3e@[66.80.62.44]>
Date: Wed, 1 Jun 2011 14:59:02 -0700
To: ietf@ietf.org
From: Ross Finlayson <finlayson@live555.com>
Subject: Problems with online booking for the Hotel Delta Quebec?
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, 01 Jun 2011 21:59:21 -0000

Is anyone else having problems booking a room at the Hotel Delta 
Quebec (the second-listed IETF-81 hotel; the IETF-rate rooms at the 
Hilton Quebec (the first-listed hotel) appear to have already sold 
out)?  Whenever I try, I get all the way to the "Complete Booking" 
phase, but then end up with an error page

	"Oops! Terribly Sorry
	We are currently experiencing difficulties."

Has anyone succeeded in booking a room at the Delta online, or do we 
need to resort to using telephony?

	Ross.

From johnl@iecc.com  Wed Jun  1 15:21:57 2011
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 CAC36E0713 for <ietf@ietfa.amsl.com>; Wed,  1 Jun 2011 15:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.272
X-Spam-Level: 
X-Spam-Status: No, score=-109.272 tagged_above=-999 required=5 tests=[AWL=1.927, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lp0hMrD0wwIR for <ietf@ietfa.amsl.com>; Wed,  1 Jun 2011 15:21:57 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id DC29EE06D1 for <ietf@ietf.org>; Wed,  1 Jun 2011 15:21:56 -0700 (PDT)
Received: (qmail 70806 invoked from network); 1 Jun 2011 22:21:55 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 1 Jun 2011 22:21:55 -0000
Date: 1 Jun 2011 22:21:33 -0000
Message-ID: <20110601222133.4773.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Problems with online booking for the Hotel Delta Quebec?
In-Reply-To: <f06240801ca0c65310a3e@[66.80.62.44]>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 22:21:57 -0000

>Has anyone succeeded in booking a room at the Delta online, or do we 
>need to resort to using telephony?

I did, a couple of weeks ago.

R's,
John

From Ed.Lewis@neustar.biz  Thu Jun  2 05:53:03 2011
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5686EE0915; Thu,  2 Jun 2011 05:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.511
X-Spam-Level: 
X-Spam-Status: No, score=-106.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mnBJjCF+EC9a; Thu,  2 Jun 2011 05:53:02 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 50C44E09B8; Thu,  2 Jun 2011 05:52:59 -0700 (PDT)
Received: from Work-Laptop-2.local (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p52CqtQ6059180; Thu, 2 Jun 2011 08:52:56 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.204.168] by Work-Laptop-2.local (PGP Universal service); Thu, 02 Jun 2011 08:52:56 -0400
X-PGP-Universal: processed; by Work-Laptop-2.local on Thu, 02 Jun 2011 08:52:56 -0400
Mime-Version: 1.0
Message-Id: <a06240800ca0d30bcc18c@[10.31.204.168]>
In-Reply-To: <20110601203355.GB26780@shinkuro.com>
References: <20110526152257.21795.30012.idtracker@ietfa.amsl.com> <a06240802ca0bff6fff57@10.31.204.168> <BANLkTimpGsRXuHi2zuuJKrZi1Ypcic5Xkw@mail.gmail.com> <20110601175216.GX26780@shinkuro.com> <a06240802ca0c457b6ab4@[10.31.204.168]> <20110601203355.GB26780@shinkuro.com>
Date: Thu, 2 Jun 2011 08:51:48 -0400
To: Andrew Sullivan <ajs@anvilwalrusden.com>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: [dnsext] Last Call:  <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability  Statement: 	DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed 	Standard
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: ietf@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: Thu, 02 Jun 2011 12:53:03 -0000

At 16:33 -0400 6/1/11, Andrew Sullivan wrote:

>I believe that nothing anywhere in the document suggests that one
>ought to guage conformance of software against the registry, and if
>you think it says that somewhere, I'd like a pointer to where.  It
>would need to be fixed if it said that, but as far as I can tell it
>does not.

I believe the opposite.

 From the abstract:

    This status is to measure compliance to this RFC
    only.  This document replaces that registry table with a new IANA
    registry table for Domain Name System Security (DNSSEC) Algorithm
    Numbers that lists (or assigns) each algorithm's status based on the
    current reference.

Seeing these two sentences alone tells me that this document is 
setting up a registry and is setting up something to be compliant to 
the registry.

Bolstering my confusion is comments from the editor/Scott in a recent 
message (granted this is not in the draft):

"This doc doesn't change that at all.  You can still implement 
whatever you want, just not claim conformance to this doc."

Is the document an applicability statement to which software can 
conform, or is it a definition of a registry?

Jumping backwards in your message:

>You cannot claim conformance to the registry, because registries are
>not an archival series and because they do change.  We agree on that.
>But you don't seem to think that the registry of RRTYPE code points
>changing is a bad idea, even though early software didn't have the
>RRTYPE for DNAME or DNSKEY.  In the same way, the registry of these

Why did you use the word "but" in there?  I can't make sense out of 
that paragraph, especially the second sentence.

Change happens, and the registry has to keep up to be relevant.  A 
software version is written to a static set of requirements (like an 
RFC).  Software (referring to the process of producing a series of 
versions) can be said to be compliant to a registry in the sense that 
the latest version reflects what is in a registry.

That might give a hint of why I find this draft's mission confusing. 
And why I really think it is a bad idea to codify recommendations to 
implement in a registry, which is what I read in this document.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis             
NeuStar                    You can leave a voice message at +1-571-434-5468

Now, don't say I'm always complaining.
Wait, that's a complaint, isn't it?

From housley@vigilsec.com  Thu Jun  2 07:06:43 2011
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 C09D6E0786 for <ietf@ietfa.amsl.com>; Thu,  2 Jun 2011 07:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.485
X-Spam-Level: 
X-Spam-Status: No, score=-102.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SJkW2e3HCc8x for <ietf@ietfa.amsl.com>; Thu,  2 Jun 2011 07:06:43 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 2E5D7E06C2 for <ietf@ietf.org>; Thu,  2 Jun 2011 07:06:43 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 100DFF24013 for <ietf@ietf.org>; Thu,  2 Jun 2011 10:07:11 -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 ASKRDz2J0+OU for <ietf@ietf.org>; Thu,  2 Jun 2011 10:06:32 -0400 (EDT)
Received: from [172.21.129.48] (unknown [63.164.30.129]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 0D907F240A1 for <ietf@ietf.org>; Thu,  2 Jun 2011 10:07:10 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Concerns about the recent IPR Statement from Alcatel Lucent Related to RFC 6073
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <EC39C3A2-888B-4A62-952F-39712562D263@ietf.org>
Date: Thu, 2 Jun 2011 10:06:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E0A4D735-0E49-471F-843E-0314AD69F2C6@vigilsec.com>
References: <20110531163726.28776.73969.idtracker@ietfa.amsl.com> <EC39C3A2-888B-4A62-952F-39712562D263@ietf.org>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 14:06:43 -0000

I do not find any IPR disclosures against draft-ietf-pwe3-segmented-pw, =
the Internet-Draft that became RFC 6073.  As a result, I am very =
concerned by the extremely late notice of patents by Alcatel Lucent, =
especially since RFC 6073 and the patent have a common author.  This =
fact makes it very clear that Alcatel Lucent was aware of the work that =
produced RFC 6073. This is clearly a breach of IETF IPR policy as =
described in BCP 79.

Yesterday, I wrote to Alcatel Lucent about their recent IPR statement, =
and asked them to consider a revised IPR disclosure to correct this =
situation.

I received a response today.  Alcatel Lucent confirmed that they take =
their standards obligations very seriously.  They are investigating the =
situation, and they promised to respond to my message soon.  I will =
report further when I receive that response.

Russ


On May 31, 2011, at 12:37 PM, IETF Secretariat wrote:

> Dear Mustapha Aissaoui, Florin Balus, Matthew Bocci, Michael Duckett, =
Luca Martini, Chris Metz, Thomas Nadeau:
>=20
> An IPR disclosure that pertains to your RFC entitled "Segmented =
Pseudowire"
> (RFC6073) was submitted to the IETF Secretariat on 2011-05-26 and has=20=

> been posted on the "IETF Page of Intellectual Property Rights =
Disclosures"
> (https://datatracker.ietf.org/ipr/1566/). The title of the IPR=20
> disclosure is "Alcatel Lucent's Statement of IPR Related to RFC=20
> 6073."");
>=20
> The IETF Secretariat


From scottr.nist@gmail.com  Wed Jun  1 10:18:14 2011
Return-Path: <scottr.nist@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66F53E089F; Wed,  1 Jun 2011 10:18: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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pab5zx+yBw4g; Wed,  1 Jun 2011 10:18:13 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3E2D1E0824; Wed,  1 Jun 2011 10:18:12 -0700 (PDT)
Received: by wyb29 with SMTP id 29so12546wyb.31 for <multiple recipients>; Wed, 01 Jun 2011 10:18:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=deIb7UMYJfsnovlSnRYKrfcK9XuYFZp3t74rd0jmJuE=; b=j9gIatn7k9bl3qncQ/KqbiLgDt7UCGJEi1r5jBLdRaSESgo5RWAVVl3ki7P0Jk2PpV CLMd5zrUXroOKozb1P06YdXOc6ELxg/h0P52ASWaEh7cisLPpsJoGZ77XyGTrOGpOws/ Inv+2IrDYBQEvRYjLe813JsgTCFrrTFkf1Xmg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=wyFu9JtIUq9McZr5bFHrxBP4Y9fqK7WiRYzeLq4fUt7BBD8Qg0cz3dKItMUKY8uOYA QcqBFkJmCA0NS1v8RBVeNngX3Wq3hpIsLQLnd0VAxqEex8Bf6abE+Ssyx1V07YBQthjt SEgJ5bbyffIEj2zInaQIY5eq7RLdQtKje0lGY=
MIME-Version: 1.0
Received: by 10.216.145.206 with SMTP id p56mr5040350wej.80.1306948691337; Wed, 01 Jun 2011 10:18:11 -0700 (PDT)
Received: by 10.216.87.21 with HTTP; Wed, 1 Jun 2011 10:18:11 -0700 (PDT)
In-Reply-To: <a06240802ca0bff6fff57@10.31.204.168>
References: <20110526152257.21795.30012.idtracker@ietfa.amsl.com> <a06240802ca0bff6fff57@10.31.204.168>
Date: Wed, 1 Jun 2011 13:18:11 -0400
Message-ID: <BANLkTimpGsRXuHi2zuuJKrZi1Ypcic5Xkw@mail.gmail.com>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
From: Scott Rose <scottr.nist@gmail.com>
To: Edward Lewis <Ed.Lewis@neustar.biz>
Content-Type: multipart/alternative; boundary=0016e6de04447ca19704a4a9b4a2
X-Mailman-Approved-At: Thu, 02 Jun 2011 08:25:03 -0700
Cc: The IESG <iesg-secretary@ietf.org>, ietf@ietf.org, dnsext@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: scott.rose@nist.gov
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 17:18:14 -0000

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

On Wed, Jun 1, 2011 at 11:03 AM, Edward Lewis <Ed.Lewis@neustar.biz> wrote:

> At 8:22 -0700 5/26/11, The IESG wrote:
>
>> The IESG has received a request from the DNS Extensions WG (dnsext) to
>> consider the following document:
>> - 'Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA
>>   Registry'
>>  <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> as a Proposed Standard
>>
>
> As someone that would implement against this document, I find its role
> confusing.
>
> The title is
> #   Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA
> #                                Registry
>
> Is this title meant to tell me that this is defining or redefining the
> DNSKEY Algorithm Registry run by IANA?  The "Applicability" part is a little
> confusing.
>

Technically redefining if you want to split hairs.


>
> I mention this because of the following text in the Introduction:
>
> # This document replaces the original list with a new table that includes
> the
> # current compliance status for certain algorithms.
> #
> # This compliance status indication is only to be considered for
> # implementation, not deployment or operations.  Operators are free to
> # deploy any digital signature algorithm available in implementations
> # or algorithms chosen by local security policies.  This status is to
>
> # measure compliance to this RFC only.
>
> The first sentence seems to be refining the registry.  Then there are words
> saying that this document relates only to code development and not use.  The
> final sentence mentions "compliance to this RFC" and this is where I lose
> it.
>
> I am all for a document to define a registry.  And in my experience, a
> registry is supposed to map objects to entities (in this case DNSKEY
> algorithms to values in a protocol field) in a fairly neutral way.
>
> I am all for a document to define an operational profile, requiring certain
> choices to be made to be conformant to some standard of service delivery.  I
> would like to be able to advertise that "we conform with RFC wxyz" and have
> that say we operate with certain algorithms.
>
> But I don't think it is correct to do both in the same document. This gets
> very confusing when trying to deal with RFPs (Request for Propsals and the
> like) that list RFCs that should be complied with. One issue is the conflict
> between the neutrality of a registry's function and the advocacy of a
> profile document.
>
> I fail to see the rationale that all implementations must support specific
> algorithms.  (Interoperability doesn't need that.)  I understand that if the
> topic is "general purpose implementations" there are a common set of
> algorithms such implementations should support.  There are, however, turnkey
> DNS deployments in which these algorithms may not make sense.  Any
> implementation is free to ignore an algorithm or to treat responses as "bad"
> if it wants to.
>
> This doc doesn't change that at all.  You can still implement whatever you
want, just not claim conformance to this doc.


> A strong tenet of the DNSSEC policy is that "local policy" is the trump
> card in all security decisions.  The cache that is being protected gets to
> choose it's own policy.  By creating a registry that commands what is
> implemented and not implemented, there's a conflict with "local policy".  I
> don't mean that the implementation of the cache is restricted, but the
> authority and other middle DNS servers are restricted.
>
> Local policy is already restricted by implementations.  This doc really
doesn't change that - it only really reflects the current state of crypto in
DNSSEC.  Something that has been more oral history than written down.



> My recommendation is to turn this document into something called a "Public
> Internet General Purpose DNSKEY ALgorithm Profile", make it a BCP (that can
> be updated) and let it summarily list the algorithms that should or
> shouldn't be included.  Leave these designations out of the registry (table)
> and don't have this document try to change the registry.
>
>
Our main reason for replacing the registry table with a doc containing a new
table was that not all implementors may be good at sorting through the IETF
archives looking for every DNSSEC related RFC and BCP.  Have a simple table
at a well known repository will hopefully reduce that document hunt.


Scott



> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Edward Lewis             NeuStar                    You can leave a voice
> message at +1-571-434-5468
>
> Now, don't say I'm always complaining.
> Wait, that's a complaint, isn't it?
>
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext
>

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

<br><br><div class=3D"gmail_quote">On Wed, Jun 1, 2011 at 11:03 AM, Edward =
Lewis <span dir=3D"ltr">&lt;<a href=3D"mailto:Ed.Lewis@neustar.biz">Ed.Lewi=
s@neustar.biz</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">At 8:22 -0700 5/26/11, The IESG wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IESG has received a request from the DNS Extensions WG (dnsext) to<br>
consider the following document:<br>
- &#39;Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA=
<br>
 =A0 Registry&#39;<br>
 =A0&lt;draft-ietf-dnsext-dnssec-registry-fixes-08.txt&gt; as a Proposed St=
andard<br>
</blockquote>
<br></div>
As someone that would implement against this document, I find its role conf=
using.<br>
<br>
The title is<br>
# =A0 Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA<=
br>
# =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Registry<b=
r>
<br>
Is this title meant to tell me that this is defining or redefining the DNSK=
EY Algorithm Registry run by IANA? =A0The &quot;Applicability&quot; part is=
 a little confusing.<br></blockquote><div><br></div><div>Technically redefi=
ning if you want to split hairs.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;">
<br>
I mention this because of the following text in the Introduction:<br>
<br>
# This document replaces the original list with a new table that includes t=
he<br>
# current compliance status for certain algorithms.<br>
#<br>
# This compliance status indication is only to be considered for<br>
# implementation, not deployment or operations. =A0Operators are free to<br=
>
# deploy any digital signature algorithm available in implementations<br>
# or algorithms chosen by local security policies. =A0This status is to<div=
 class=3D"im"><br>
# measure compliance to this RFC only.<br>
<br></div>
The first sentence seems to be refining the registry. =A0Then there are wor=
ds saying that this document relates only to code development and not use. =
=A0The final sentence mentions &quot;compliance to this RFC&quot; and this =
is where I lose it.<br>

<br>
I am all for a document to define a registry. =A0And in my experience, a re=
gistry is supposed to map objects to entities (in this case DNSKEY algorith=
ms to values in a protocol field) in a fairly neutral way.<br>
<br>
I am all for a document to define an operational profile, requiring certain=
 choices to be made to be conformant to some standard of service delivery. =
=A0I would like to be able to advertise that &quot;we conform with RFC wxyz=
&quot; and have that say we operate with certain algorithms.<br>

<br>
But I don&#39;t think it is correct to do both in the same document. This g=
ets very confusing when trying to deal with RFPs (Request for Propsals and =
the like) that list RFCs that should be complied with. One issue is the con=
flict between the neutrality of a registry&#39;s function and the advocacy =
of a profile document.<br>

<br>
I fail to see the rationale that all implementations must support specific =
algorithms. =A0(Interoperability doesn&#39;t need that.) =A0I understand th=
at if the topic is &quot;general purpose implementations&quot; there are a =
common set of algorithms such implementations should support. =A0There are,=
 however, turnkey DNS deployments in which these algorithms may not make se=
nse. =A0Any implementation is free to ignore an algorithm or to treat respo=
nses as &quot;bad&quot; if it wants to.<br>

<br></blockquote><div>This doc doesn&#39;t change that at all. =A0You can s=
till implement whatever you want, just not claim conformance to this doc. =
=A0</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

A strong tenet of the DNSSEC policy is that &quot;local policy&quot; is the=
 trump card in all security decisions. =A0The cache that is being protected=
 gets to choose it&#39;s own policy. =A0By creating a registry that command=
s what is implemented and not implemented, there&#39;s a conflict with &quo=
t;local policy&quot;. =A0I don&#39;t mean that the implementation of the ca=
che is restricted, but the authority and other middle DNS servers are restr=
icted.<br>

<br></blockquote><div>Local policy is already restricted by implementations=
. =A0This doc really doesn&#39;t change that - it only really reflects the =
current state of crypto in DNSSEC. =A0Something that has been more oral his=
tory than written down. =A0 =A0</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
My recommendation is to turn this document into something called a &quot;Pu=
blic Internet General Purpose DNSKEY ALgorithm Profile&quot;, make it a BCP=
 (that can be updated) and let it summarily list the algorithms that should=
 or shouldn&#39;t be included. =A0Leave these designations out of the regis=
try (table) and don&#39;t have this document try to change the registry.<br=
>
<font color=3D"#888888">
<br></font></blockquote><div><br></div><div>Our main reason for replacing t=
he registry table with a doc containing a new table was that not all implem=
entors may be good at sorting through the IETF archives looking for every D=
NSSEC related RFC and BCP. =A0Have a simple table at a well known repositor=
y will hopefully reduce that document hunt.</div>
<div><br></div><div><br></div><div>Scott</div><div><br></div><div>=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><font color=3D"#888888">
-- <br>
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=
=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-<br>
Edward Lewis =A0 =A0 =A0 =A0 =A0 =A0 NeuStar =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0You can leave a voice message at <a href=3D"tel:%2B1-571-434-546=
8" value=3D"+15714345468" target=3D"_blank">+1-571-434-5468</a><br>
<br>
Now, don&#39;t say I&#39;m always complaining.<br>
Wait, that&#39;s a complaint, isn&#39;t it?</font><div><div></div><div clas=
s=3D"h5"><br>
_______________________________________________<br>
dnsext mailing list<br>
<a href=3D"mailto:dnsext@ietf.org" target=3D"_blank">dnsext@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsext" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/dnsext</a><br>
</div></div></blockquote></div><br>

--0016e6de04447ca19704a4a9b4a2--

From violeta.cakulev@alcatel-lucent.com  Wed Jun  1 13:04:44 2011
Return-Path: <violeta.cakulev@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DB3BE085D; Wed,  1 Jun 2011 13:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XG9Gx6o1OkHx; Wed,  1 Jun 2011 13:04:43 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id EF2A5E085C; Wed,  1 Jun 2011 13:04:42 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id p51K4d3J021833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 1 Jun 2011 15:04:40 -0500 (CDT)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p51K4cvD008021 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 1 Jun 2011 15:04:38 -0500
Received: from USNAVSXCHMBSA3.ndc.alcatel-lucent.com ([135.3.39.124]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Wed, 1 Jun 2011 15:04:38 -0500
From: "Cakulev, Violeta (Violeta)" <violeta.cakulev@alcatel-lucent.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 1 Jun 2011 15:04:37 -0500
Subject: RE: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
Thread-Topic: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
Thread-Index: AcwYsMo/0HGmfSXETjK9JZiEqS4i5AH5KH8A
Message-ID: <AAE76B481E7A0E4C96610790A852B9A625099F98E2@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
References: <20110520135022.1622.22713.idtracker@ietfa.amsl.com> <4DD9581C.3070900@gmail.com>
In-Reply-To: <4DD9581C.3070900@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
X-Mailman-Approved-At: Thu, 02 Jun 2011 08:25:03 -0700
Cc: IPsecme WG <ipsec@ietf.org>, "draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org>, "dime@ietf.org" <dime@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 20:04:44 -0000

Hi Yaron,
Thanks for the comments.
Please see inline [VC].

-Violeta

-----Original Message-----
From: ipsec-bounces@ietf.org [mailto:ipsec-bounces@ietf.org] On Behalf Of Y=
aron Sheffer
Sent: Sunday, May 22, 2011 2:38 PM
To: ietf@ietf.org
Cc: IPsecme WG; draft-ietf-dime-ikev2-psk-diameter@tools.ietf.og; dime@ietf=
.org
Subject: Re: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt>=
 (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to D=
iameter Server Interaction) to Proposed Standard

Hi,

Having read this document only now, I think there's a number of serious iss=
ues with it. This document was sent to the ipsec mailing list a while ago b=
ut unfortunately got no review.

Summary:
1. I think the wrong architectural choice was made, in preferring PSK over =
EAP authentication.
2. There is not enough detail in the document to result in interoperable im=
plementations.
[VC] Please see responses to detailed comments.

Detailed comments:
* The appropriate ref for IKEv2 is RFC 5996. This was actually noted in the=
 shepherd review back in March.
[VC] This is fixed in v7.


* The document notes that EAP is one of the authentication modes supported =
by IKEv2. EAP is designed for interaction with backend AAA servers, and is =
quite capable of performing shared-secret authentication, using a variety o=
f EAP methods (and see also RFC 5998, on IKEv2 mutual auth with EAP). Yet t=
he document does not explain why EAP is not used, instead preferring the IK=
E PSK authentication method.
[VC] Diameter application for Diameter client to server communication for I=
KEv2 with EAP has been specified in RFC 5778. However, there is no Diameter=
 application specified for IKE PSK authentication method. This is stated in=
 the draft both in Abstract and Introduction. The draft does not recommend =
one or the other, it is simply specifying what is not specified. It is up t=
o a specific use case to decide what to use. For example 3GPP2 decided to u=
se IKEv2 PSK (in 2 of its specifications), and that is what triggered this =
effort in IETF.


* 4.1: how can the incoming SPI be used to identify the peer?
[VC] As stated in Section 4.1 IDi payload is extracted from the IKE_AUTH me=
ssage and this payload 'MUST contain an identity that is meaningful
   for the Diameter infrastructure, such as a Network Access Identifier (NA=
I), since it is used by the IKEv2 Server to populate the User-Name
   AVP in the Diameter message'. SPI is not used to identify the peer.


* Packing additional semantics into SPI may conflict with elements of the I=
Psec architecture (see for example Sec. 9.3 of draft-ietf-ipsecme-failure-d=
etection-08).
[VC] Agreed.


* 4.1, 2nd paragraph: generation of the PSK is central to this solution, so=
 it cannot be "outside the scope" of the document. There is no way to inter=
operate otherwise.
[VC] This draft focuses on IKEv2 server, as a Diameter client, to the Diame=
ter server communication for IKEv2 with pre-
   shared secret based authentication, and specifies Diameter application f=
or this communication. It is left to specifications that make use of this D=
iameter application to specify where the PSK comes from and how it is gener=
ated. As mentioned above, there are two 3GPP2 specs that make use of this D=
iameter application and both of those specs specify generation of the PSK.


* Moreover, if a single client is expected to sometimes use EAP and sometim=
es PSK, there must be a way to notify it which one to use.
[VC] This is not the assumption. Again this draft specifies Diameter applic=
ation for Diameter client to the Diameter server communication for IKEv2 wi=
th PSK. IKEv2 server knows whether EAP or PSK is used.


* How does key-lifetime relate to the lifetime of the IKE SA?
[VC] This should be the same as in RFC 5996, how pre-shared secret lifetime=
 relates to the lifetime of the IKE SA. This draft should not make any chan=
ges.


* Sec. 10 refers to the PSK as a "session key" which is incorrect, as PSK i=
s only used for authentication and does not encrypt anything.
[VC] Good point. It is changed to PSK in v7.


* The same paragraph is very vague about the security properties of PSK.
RFC 5996 takes PSK much more seriously, e.g. "When using pre-shared keys, a=
 critical consideration is how to assure the randomness of these secrets." =
Again, I believe the document should specify how the PSK is derived.
[VC] I absolutely agree that derivation of PSK is critical. However, as sta=
ted above, this draft specifies Diameter application only. Therefore, secur=
ity consideration section cannot include much more details on derivation of=
 PSK as it is specified elsewhere.


* Why "if nonces are included" where the document says that they *must* be =
included (in the AVP occurrence table).
[VC] Good point. This is removed in v7.


Thanks,
Yaron

On 05/20/2011 04:50 PM, The IESG wrote:
> The IESG has received a request from the Diameter Maintenance and
> Extensions WG (dime) to consider the following document:
> - 'Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server
>     to Diameter Server Interaction'
>    <draft-ietf-dime-ikev2-psk-diameter-06.txt>  as a 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 2011-06-03. 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 Internet Key Exchange protocol version 2 (IKEv2) is a component
>     of the IPsec architecture and is used to perform mutual
>     authentication as well as to establish and to maintain IPsec security
>     associations (SAs) between the respective parties.  IKEv2 supports
>     several different authentication mechanisms, such as the Extensible
>     Authentication Protocol (EAP), certificates, and pre-shared secrets.
>
>     With [RFC5778] the Diameter interworking for Mobile IPv6 between the
>     Home Agent, as a Diameter client, and the Diameter server has been
>     specified.  However, that specification focused on the usage of EAP
>     and did not include support for pre-shared secret based
>     authentication available with IKEv2.  This document specifies IKEv2
>     server, as a Diameter client, to the Diameter server communication
>     for IKEv2 with pre-shared secret based authentication.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec

From stbryant@cisco.com  Thu Jun  2 11:22:29 2011
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 F2282E07FC; Thu,  2 Jun 2011 11:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.416
X-Spam-Level: 
X-Spam-Status: No, score=-110.416 tagged_above=-999 required=5 tests=[AWL=0.183, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rjGt9VJFQFWN; Thu,  2 Jun 2011 11:22:28 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id CE57BE06FB; Thu,  2 Jun 2011 11:22:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=1805; q=dns/txt; s=iport; t=1307038948; x=1308248548; h=message-id:date:from:reply-to:mime-version:to:cc:subject: content-transfer-encoding; bh=UAHhCyYgkahbcZx5/TJeO83SjqJXmSQRTiAo5L1F2zY=; b=mHyfIXe9I6yGbD967MNR3HtfIl7DoudEZgXKPahY3f6ujMudGtbZRdlt G+7b7oQ95Q6+4MBTWzafu49/pKLYx1irGB6EFZS6L7+iEEV22myFZh8J8 ftdjYbhhMwhlKqz5tjw/lbvXjPEWA2bbJi5JWvNbw+CHWICssZTrKlOQN 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAIDU502Q/khR/2dsb2JhbABThEmhcXerWoJ6DwGJfZBagSuDbIEKBJBnjzE
X-IronPort-AV: E=Sophos;i="4.65,310,1304294400"; d="scan'208";a="33471952"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 02 Jun 2011 18:22:27 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p52IMQiA026184; Thu, 2 Jun 2011 18:22:26 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p52IMOW16407; Thu, 2 Jun 2011 19:22:25 +0100 (BST)
Message-ID: <4DE7D4EF.6050208@cisco.com>
Date: Thu, 02 Jun 2011 19:22:39 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Proposed text for IESG Processing of RFC Errata concerning RFC Metadata
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "iesg@ietf.org" <iesg@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: Thu, 02 Jun 2011 18:22:29 -0000

The IESG is considering making this statement on the
processing of RFC Errata concerning RFC Metadata.

We would appreciate community feedback.

Please can we have feedback by Thursday 9th June.

Thanks

Stewart

======


Draft text for IESG Statement on RFC Metadata

Date: xx-xxx-xxxx

This IESG statement describes the manner in which the IESG will
process RFC Errata concerning RFC Metadata [RFC5741]. Metadata
is used, for example, in the compilation of the RFC Index.

The Area Director responsible for processing the RFC erratum will review 
the RFC and document history recorded in various IETF archives such as 
the datatracker. Where the error is major, for example
an error in the document track, the Area Director SHOULD
reject the erratum, and initiate the publication of a replacement
RFC.

Where

- The error is minor, for example where there is a minor
error in the list of updated RFCs, and
- The intent of the IETF community as determined from the RFC and the 
records is clear, and
- The RFC has been processed correctly in all other regards,
the Area Director MAY accept the erratum. The Area Director MAY consult 
with the IESG in making this determination.

If the above minor error conditions are met, but the Area Director 
responsible for processing the metadata is of the view that the best 
interests of the community are served by holding the RFC erratum for 
document update, or rejecting the erratum and initiating the
publication of a replacement RFC they MAY process the RFC erratum 
accordingly.

Where there is doubt as to the intent of the IETF community or where the 
RFC has not been processed in accordance with the rules governing the 
proposed change to the RFC metadata, the RFC erratum MUST be rejected.

======


From Ed.Lewis@neustar.biz  Thu Jun  2 11:34:39 2011
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3577FE07E6; Thu,  2 Jun 2011 11:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.527
X-Spam-Level: 
X-Spam-Status: No, score=-106.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u7rzOP6OZCoc; Thu,  2 Jun 2011 11:34:38 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id E5146E06FB; Thu,  2 Jun 2011 11:34:37 -0700 (PDT)
Received: from Work-Laptop-2.local (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id p52IYWf3061792; Thu, 2 Jun 2011 14:34:32 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.204.168] by Work-Laptop-2.local (PGP Universal service); Thu, 02 Jun 2011 14:34:33 -0400
X-PGP-Universal: processed; by Work-Laptop-2.local on Thu, 02 Jun 2011 14:34:33 -0400
Mime-Version: 1.0
Message-Id: <a06240804ca0d8646edd1@[10.31.204.168]>
In-Reply-To: <BANLkTi=bxAXrAvz9GNDVrPfQW_acD-UGJw@mail.gmail.com>
References: <20110526152257.21795.30012.idtracker@ietfa.amsl.com> <a06240802ca0bff6fff57@10.31.204.168> <BANLkTimpGsRXuHi2zuuJKrZi1Ypcic5Xkw@mail.gmail.com> <20110601175216.GX26780@shinkuro.com> <a06240802ca0c457b6ab4@10.31.204.168> <20110601203355.GB26780@shinkuro.com> <a06240800ca0d30bcc18c@10.31.204.168> <BANLkTi=bxAXrAvz9GNDVrPfQW_acD-UGJw@mail.gmail.com>
Date: Thu, 2 Jun 2011 14:31:55 -0400
To: <scott.rose@nist.gov>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: [dnsext] Last Call:  <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement:  DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.68 on 10.20.30.4
Cc: Scott Rose <scottr.nist@gmail.com>, ed.lewis@neustar.biz, ietf@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: Thu, 02 Jun 2011 18:34:39 -0000

At 14:10 -0400 6/2/11, Scott Rose wrote:

>Then perhaps a wording change?  It seems that it is confusion over the
>language rather than the purpose.

A wording change is probably needed, but I can't suggest one because 
I can't determine what the goal is from what's currently written.  I 
know that sounds like a cheap shot, but I'm definitely not getting 
something here.

E.g., I'm assuming the document is suggesting that the IANA registry 
have the new column and that is my main complaint.  (That it 
shouldn't.)  If the matrix with the compliance column only appears in 
the document, while the IANA registry omits the column, I have no 
complaint.  Perhaps IANA lists the document as a reference at the end 
of the matrix, but the registry contents itself doesn't hold 
"recommendations."

Does that make sense?
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

Now, don't say I'm always complaining.
Wait, that's a complaint, isn't it?

From turners@ieca.com  Thu Jun  2 12:17:32 2011
Return-Path: <turners@ieca.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB6C2E07B3 for <ietf@ietfa.amsl.com>; Thu,  2 Jun 2011 12:17:32 -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, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RW5GdLgxMKzJ for <ietf@ietfa.amsl.com>; Thu,  2 Jun 2011 12:17:32 -0700 (PDT)
Received: from nm12.access.bullet.mail.sp2.yahoo.com (nm12.access.bullet.mail.sp2.yahoo.com [98.139.44.139]) by ietfa.amsl.com (Postfix) with SMTP id 519B0E06BC for <ietf@ietf.org>; Thu,  2 Jun 2011 12:17:32 -0700 (PDT)
Received: from [98.139.44.103] by nm12.access.bullet.mail.sp2.yahoo.com with NNFMP; 02 Jun 2011 19:17:32 -0000
Received: from [98.139.44.70] by tm8.access.bullet.mail.sp2.yahoo.com with NNFMP; 02 Jun 2011 19:17:32 -0000
Received: from [127.0.0.1] by omp1007.access.mail.sp2.yahoo.com with NNFMP; 02 Jun 2011 19:17:32 -0000
X-Yahoo-Newman-Id: 266706.20900.bm@omp1007.access.mail.sp2.yahoo.com
Received: (qmail 30473 invoked from network); 2 Jun 2011 19:17:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1307042252; bh=sdlY71uJpEYkWgPxzkVlLy6xVdWC3v2iNDTk3WFyG1Q=; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:Content-Type:Content-Transfer-Encoding; b=wDgI3FfaccaQD1zFJ+ys5NF1rAjqrwH/VaT+RK8CJ2cE/o/PWRqL58NPGc3e3HyEcWOz2KhneTzMe+NOp7CF6304sLJWfrVF4n/1FfFUNY5/AMhJfewz+RsoG1ASw6FfoYsnkYJtemXOZ5RkSH0AIivl91f0srjudjb+LR4oFds=
Received: from thunderfish.local (turners@96.241.3.222 with plain) by smtp115.biz.mail.sp1.yahoo.com with SMTP; 02 Jun 2011 12:17:31 -0700 PDT
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
X-YMail-OSG: 8CIhDRoVM1n6Sb1eYDzwHICuzoPQpMFvIXxkwMZlDwXVDBG 1oFjAJpKKYzahUbp6WGp2DxiTRAkF_gmpdXS9FHWkwyDJv07xUGbMhwQb_mg LHnuIzNY6T0G_ubs.dJOc4S3whvuJ0lALxpJcr8_mM4OIQ7CfiZCMcJ3k7eu ZDwsCwYCBt6e24zqib2BL8tyRCft5fy8VHRghiv0SaCc2rlHF2CV3XG5Ukf2 Fkf4xHy9hJenyL47Vt6zj3J6uDDVxInC3dq2V5U9_1vRjwqJj2u2pjM9zsBn BKTKB3zzhMqC9OfY1K15QwWg6eNX6L6G_ZqAG9.BKi16AofN97gG1qR_BnMF 0SwvjEFp8Oq8nASc_HNJDxOSfv_f7UjWeN4Ttp6EjI_k-
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4DE7E1CA.9010309@ieca.com>
Date: Thu, 02 Jun 2011 15:17:30 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Proposed text for IESG Handling of Historic Status
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 02 Jun 2011 19:17:33 -0000

The IESG is considering making this statement on the IESG Handling of 
Historic status.

We would appreciate community feedback.

Please can we have feedback by Thursday 9th June.

Thanks

spt

<statement begins>

RFC 2026 states the following:

A specification that has been superseded by a more recent specification 
or is for any other reason considered to be obsolete is assigned to the 
"Historic" level.

In practice, the Historic status is not automatically assigned to RFCs 
that have been "obsoleted".  That is, when an RFC that contains the 
"Obsoletes: RFC XXXX" header is published the RFC editor does not 
automatically apply the Historic status to the XXXX RFC.  Note that in 
some situations this is perfectly acceptable because multiple versions 
of an Internet Standard are permitted to "honor the installed base," as 
per RFC 2026.

If authors wish to change the status of RFCs that are in the obsoletes 
header to Historic, then the authors must include an explicit statement 
for the RFC editor to do so; preferably in the abstract and 
introduction.  Further, when an AD sponsors a draft that includes the 
obsoletes header, then the AD should ask the authors whether the authors 
intended to move the RFC(s) listed in the obsoletes header to Historic 
status.

If an author wishes to publish a document directly to Historic status 
the preferred approach is to publish an I-D with the "Intended Status: 
Historic" in the header.

Moving a document to Historic status means that the document is "not 
[an] Internet Standards in any sense," as per RFC 2026.

</statement ends>

From hartmans@mit.edu  Thu Jun  2 12:47:24 2011
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 727D4E0865; Thu,  2 Jun 2011 12:47:24 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4p4rK6NiDsdk; Thu,  2 Jun 2011 12:47:24 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 25122E07CA; Thu,  2 Jun 2011 12:47:20 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (fq-guest-wireless-pittnet-94-214.net.pitt.edu [150.212.94.214]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id EF90420424; Thu,  2 Jun 2011 15:42:59 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 469F3454B; Thu,  2 Jun 2011 15:47:20 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Sean Turner <turners@ieca.com>
Subject: Re: Proposed text for IESG Handling of Historic Status
References: <4DE7E1CA.9010309@ieca.com>
Date: Thu, 02 Jun 2011 15:47:20 -0400
In-Reply-To: <4DE7E1CA.9010309@ieca.com> (Sean Turner's message of "Thu, 02 Jun 2011 15:17:30 -0400")
Message-ID: <tslmxi0583b.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@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: Thu, 02 Jun 2011 19:47:24 -0000

I'd prefer that we not clutter abstracts with instructions to the RFC
editor and prefer that the IESG only recommend such statements in the
introduction.
I'm OK with whatever here though: the IESG should go do something
intelligent in this space.

From john-ietf@jck.com  Thu Jun  2 13:04:43 2011
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 AAB28E06D7; Thu,  2 Jun 2011 13:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.518
X-Spam-Level: 
X-Spam-Status: No, score=-102.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qZvYQvfH7SNc; Thu,  2 Jun 2011 13:04:43 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 65FD5E081D; Thu,  2 Jun 2011 13:04:29 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QSE84-000BWd-7X; Thu, 02 Jun 2011 16:04:28 -0400
Date: Thu, 02 Jun 2011 16:04:27 -0400
From: John C Klensin <john-ietf@jck.com>
To: Sean Turner <turners@ieca.com>, ietf@ietf.org
Subject: Re: Proposed text for IESG Handling of Historic Status
Message-ID: <BC28F00B6ADCA73F54E8AF4C@PST.JCK.COM>
In-Reply-To: <4DE7E1CA.9010309@ieca.com>
References: <4DE7E1CA.9010309@ieca.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: 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: Thu, 02 Jun 2011 20:04:43 -0000

Sean,

Seems fine to me but, like Sam, I'd prefer to not clutter
abstracts  For a specification RFC that is rendered Historic by
a new specification, the combination of an "Obsoletes" header
and a note in the Introduction ought to be sufficient.

While the IESG is considering this, I would encourage you to
also consider the model used to make a specification that is
simply and obviously obsolete (and in A/S terms "not
recommended") Historic without having to have an I-D written and
processed into RFC via the same process used to create Standards
Track documents.  In the cases in which we want to move a
specification to Historic because it is a bad idea, having an
RFC to explain why it was a bad idea seems appropriate.  But for
the "no one cares about it any more" cases, it seems like a
lighter-weight procedure, such as a Last Call on the question
"does anyone believe that our impression that no one cares is
incorrect?"  might be in order (and much closer to the procedure
that was used when (and before) 2026 was adopted.

best,
    john


--On Thursday, June 02, 2011 15:17 -0400 Sean Turner
<turners@ieca.com> wrote:

> The IESG is considering making this statement on the IESG
> Handling of Historic status.
> 
> We would appreciate community feedback.
> 
> Please can we have feedback by Thursday 9th June.
> 
> Thanks
> 
> spt
> 
> <statement begins>
> 
> RFC 2026 states the following:
> 
> A specification that has been superseded by a more recent
> specification or is for any other reason considered to be
> obsolete is assigned to the "Historic" level.
> 
> In practice, the Historic status is not automatically assigned
> to RFCs that have been "obsoleted".  That is, when an RFC that
> contains the "Obsoletes: RFC XXXX" header is published the RFC
> editor does not automatically apply the Historic status to the
> XXXX RFC.  Note that in some situations this is perfectly
> acceptable because multiple versions of an Internet Standard
> are permitted to "honor the installed base," as per RFC 2026.
> 
> If authors wish to change the status of RFCs that are in the
> obsoletes header to Historic, then the authors must include an
> explicit statement for the RFC editor to do so; preferably in
> the abstract and introduction.  Further, when an AD sponsors a
> draft that includes the obsoletes header, then the AD should
> ask the authors whether the authors intended to move the
> RFC(s) listed in the obsoletes header to Historic status.
> 
> If an author wishes to publish a document directly to Historic
> status the preferred approach is to publish an I-D with the
> "Intended Status: Historic" in the header.
> 
> Moving a document to Historic status means that the document
> is "not [an] Internet Standards in any sense," as per RFC 2026.
> 
> </statement ends>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf





From msk@cloudmark.com  Thu Jun  2 13:14:47 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E4A3E06D7; Thu,  2 Jun 2011 13:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.61
X-Spam-Level: 
X-Spam-Status: No, score=-104.61 tagged_above=-999 required=5 tests=[AWL=-1.011, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QD8P8opwKl0T; Thu,  2 Jun 2011 13:14:46 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 2F2A0E081D; Thu,  2 Jun 2011 13:14:46 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Thu, 2 Jun 2011 13:14:46 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
Date: Thu, 2 Jun 2011 13:14:45 -0700
Subject: RE: Proposed text for IESG Handling of Historic Status
Thread-Topic: Proposed text for IESG Handling of Historic Status
Thread-Index: AcwhXfxqq8aNPVmnS9GjaEhZQ9aU/QAA6wQA
Message-ID: <F5833273385BB34F99288B3648C4F06F134C919364@EXCH-C2.corp.cloudmark.com>
References: <4DE7E1CA.9010309@ieca.com> <tslmxi0583b.fsf@mit.edu>
In-Reply-To: <tslmxi0583b.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2011 20:14:47 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
am Hartman
> Sent: Thursday, June 02, 2011 12:47 PM
> To: Sean Turner
> Cc: ietf@ietf.org; The IESG
> Subject: Re: Proposed text for IESG Handling of Historic Status
>=20
> I'd prefer that we not clutter abstracts with instructions to the RFC
> editor and prefer that the IESG only recommend such statements in the
> introduction.
>=20
> I'm OK with whatever here though: the IESG should go do something
> intelligent in this space.

+1

-MSK

From scott.brim@gmail.com  Thu Jun  2 14:45:58 2011
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 52980E08EE; Thu,  2 Jun 2011 14:45:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.59
X-Spam-Level: 
X-Spam-Status: No, score=-103.59 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S+-+-25Gckhj; Thu,  2 Jun 2011 14:45:57 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id B220EE0833; Thu,  2 Jun 2011 14:45:57 -0700 (PDT)
Received: by iyn15 with SMTP id 15so1353850iyn.31 for <multiple recipients>; Thu, 02 Jun 2011 14:45:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=09slVoxKTXa1dKdKRHjvGvq2wpDMtkzbu9fX5AzgQ+c=; b=RDkBtTnTSL16nDQL6QteVg9+2Lq7V7ZkzY49bAbqyii1dElklYCH5khx8nMND3OKy0 o25hcvDrpfB18IMajfVrxSRJw6+zWar7yEwR4ivmKLjf1cINjk3ak/5gcuNtq7UYlXET o+tFBsEdUH6DyR2ydA85zjJbbVzkBlxAoRsDs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=IzONrOrkuV7M2yVhiwsctLbwtAdL4uwGDR/e7hCure7uUhpvmYsSgAmDeCS+8LVCTB v4+uKKs0kZ9GELTpoqTwhSACB2zdHoOMMwcp/nmCHVAlkk6xD6nwky23DaVLx+dUQWfk Sm9kNgWA4xtYaTnjXMOYoB4Lw43fv3pD2qxLg=
MIME-Version: 1.0
Received: by 10.231.1.14 with SMTP id 14mr1521675ibd.13.1307051157022; Thu, 02 Jun 2011 14:45:57 -0700 (PDT)
Received: by 10.231.19.130 with HTTP; Thu, 2 Jun 2011 14:45:56 -0700 (PDT)
Received: by 10.231.19.130 with HTTP; Thu, 2 Jun 2011 14:45:56 -0700 (PDT)
In-Reply-To: <BC28F00B6ADCA73F54E8AF4C@PST.JCK.COM>
References: <4DE7E1CA.9010309@ieca.com> <BC28F00B6ADCA73F54E8AF4C@PST.JCK.COM>
Date: Thu, 2 Jun 2011 17:45:56 -0400
Message-ID: <BANLkTikfhMWuLweofTfjncNY6s_cFZ6VRQ@mail.gmail.com>
Subject: Re: Proposed text for IESG Handling of Historic Status
From: Scott Brim <scott.brim@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001517741a9eeae8e504a4c18f0a
Cc: The IESG <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, 02 Jun 2011 21:45:58 -0000

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

On Jun 2, 2011 4:05 PM, "John C Klensin" <john-ietf@jck.com> wrote:
> While the IESG is considering this, I would encourage you to
> also consider the model used to make a specification that is
> simply and obviously obsolete (and in A/S terms "not
> recommended") Historic without having to have an I-D written and
> processed into RFC via the same process used to create Standards
> Track documents.  In the cases in which we want to move a
> specification to Historic because it is a bad idea, having an
> RFC to explain why it was a bad idea seems appropriate.  But for
> the "no one cares about it any more" cases, it seems like a
> lighter-weight procedure, such as a Last Call on the question
> "does anyone believe that our impression that no one cares is
> incorrect?"  might be in order (and much closer to the procedure
> that was used when (and before) 2026 was adopted.

Agree, but producing such a "no one cares anymore" RFC and getting it
through the process should be lightweight enough already. It should slide
right through. I hope we don't need yet another special process because our
normal process is too heavy.

Scott

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

<p><br>
On Jun 2, 2011 4:05 PM, &quot;John C Klensin&quot; &lt;<a href=3D"mailto:jo=
hn-ietf@jck.com">john-ietf@jck.com</a>&gt; wrote:<br>
&gt; While the IESG is considering this, I would encourage you to<br>
&gt; also consider the model used to make a specification that is<br>
&gt; simply and obviously obsolete (and in A/S terms &quot;not<br>
&gt; recommended&quot;) Historic without having to have an I-D written and<=
br>
&gt; processed into RFC via the same process used to create Standards<br>
&gt; Track documents. =A0In the cases in which we want to move a<br>
&gt; specification to Historic because it is a bad idea, having an<br>
&gt; RFC to explain why it was a bad idea seems appropriate. =A0But for<br>
&gt; the &quot;no one cares about it any more&quot; cases, it seems like a<=
br>
&gt; lighter-weight procedure, such as a Last Call on the question<br>
&gt; &quot;does anyone believe that our impression that no one cares is<br>
&gt; incorrect?&quot; =A0might be in order (and much closer to the procedur=
e<br>
&gt; that was used when (and before) 2026 was adopted.</p>
<p>Agree, but producing such a &quot;no one cares anymore&quot; RFC and get=
ting it through the process should be lightweight enough already. It should=
 slide right through. I hope we don&#39;t need yet another special process =
because our normal process is too heavy. </p>

<p>Scott </p>

--001517741a9eeae8e504a4c18f0a--

From presnick@qualcomm.com  Thu Jun  2 15:52:58 2011
Return-Path: <presnick@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 BE454E08E7; Thu,  2 Jun 2011 15:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.573
X-Spam-Level: 
X-Spam-Status: No, score=-106.573 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xhGY0Rn8+aiF; Thu,  2 Jun 2011 15:52:57 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id C8E78E0879; Thu,  2 Jun 2011 15:52:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1307055177; x=1338591177; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: x-originating-ip; z=Message-ID:=20<4DE813E5.1040904@qualcomm.com>|Date:=20Th u,=202=20Jun=202011=2017:51:17=20-0500|From:=20Pete=20Res nick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Scott=20Brim=20<scott.brim@gma il.com>|CC:=20John=20C=20Klensin=20<john-ietf@jck.com>, =20The=20IESG=20<iesg@ietf.org>,=0D=0A=09<ietf@ietf.org> |Subject:=20Re:=20Proposed=20text=20for=20IESG=20Handling =20of=20Historic=20Status|References:=20<4DE7E1CA.9010309 @ieca.com>=20<BC28F00B6ADCA73F54E8AF4C@PST.JCK.COM>=20<BA NLkTikfhMWuLweofTfjncNY6s_cFZ6VRQ@mail.gmail.com> |In-Reply-To:=20<BANLkTikfhMWuLweofTfjncNY6s_cFZ6VRQ@mail .gmail.com>|Content-Type:=20multipart/alternative=3B=0D =0A=09boundary=3D"------------070401040401040604070300" |X-Originating-IP:=20[172.30.48.1]; bh=vNLVgJCE3NupWFRAhIcZWpq2pX4Urm7nfL2dF/vwLiY=; b=pjcBWtJZAvhnAI0g8DcjTwxWPWrunB+cVQdSVolY/rd/118o1OwzBXax ZJuPQeST2xTLocbbefYj3yI0omWhz+WY2k321kHIPXBRF6MC0DOo/GSR2 QTb/TeGeIELlSPQOTA/PPoTVqVvjR5prm7xXdmuPn2Aot9+dRWqcCcOmG M=;
X-IronPort-AV: E=McAfee;i="5400,1158,6365"; a="95242876"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine01.qualcomm.com with ESMTP; 02 Jun 2011 15:52:57 -0700
X-IronPort-AV: E=Sophos;i="4.65,309,1304319600";  d="scan'208,217";a="142348729"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 02 Jun 2011 15:52:56 -0700
Received: from Macintosh-4.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 2 Jun 2011 15:51:24 -0700
Message-ID: <4DE813E5.1040904@qualcomm.com>
Date: Thu, 2 Jun 2011 17:51:17 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Proposed text for IESG Handling of Historic Status
References: <4DE7E1CA.9010309@ieca.com> <BC28F00B6ADCA73F54E8AF4C@PST.JCK.COM> <BANLkTikfhMWuLweofTfjncNY6s_cFZ6VRQ@mail.gmail.com>
In-Reply-To: <BANLkTikfhMWuLweofTfjncNY6s_cFZ6VRQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070401040401040604070300"
X-Originating-IP: [172.30.48.1]
Cc: John C Klensin <john-ietf@jck.com>, The IESG <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, 02 Jun 2011 22:52:58 -0000

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

On 6/2/11 4:45 PM, Scott Brim wrote:
>
> On Jun 2, 2011 4:05 PM, "John C Klensin" <john-ietf@jck.com 
> <mailto:john-ietf@jck.com>> wrote:
> >But for the "no one cares about it any more" cases, it seems like a
> > lighter-weight procedure, such as a Last Call on the question
> > "does anyone believe that our impression that no one cares is
> > incorrect?"  might be in order (and much closer to the procedure
> > that was used when (and before) 2026 was adopted.
>
> Agree, but producing such a "no one cares anymore" RFC and getting it 
> through the process should be lightweight enough already. It should 
> slide right through. I hope we don't need yet another special process 
> because our normal process is too heavy.
>

I have no strong opinion on what exactly we should do on this point, but 
the IESG can already do exactly what John wants with no change to 
process. (See the end of 2026 sec. 6.2.) We would just have to decide to 
do it.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


--------------070401040401040604070300
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 6/2/11 4:45 PM, Scott Brim wrote:
<blockquote
 cite="mid:BANLkTikfhMWuLweofTfjncNY6s_cFZ6VRQ@mail.gmail.com"
 type="cite">
  <p>On Jun 2, 2011 4:05 PM, "John C Klensin" &lt;<a
 moz-do-not-send="true" href="mailto:john-ietf@jck.com">john-ietf@jck.com</a>&gt;
wrote:<br>
&gt;But for the "no one cares about it any more" cases, it seems like a<br>
&gt; lighter-weight procedure, such as a Last Call on the question<br>
&gt; "does anyone believe that our impression that no one cares is<br>
&gt; incorrect?" &nbsp;might be in order (and much closer to the procedure<br>
&gt; that was used when (and before) 2026 was adopted.</p>
  <p>Agree, but producing such a "no one cares anymore" RFC and getting
it through the process should be lightweight enough already. It should
slide right through. I hope we don't need yet another special process
because our normal process is too heavy. </p>
</blockquote>
<br>
I have no strong opinion on what exactly we should do on this point,
but the IESG can already do exactly what John wants with no change to
process. (See the end of 2026 sec. 6.2.) We would just have to decide
to do it.<br>
<br>
pr<br>
<pre class="moz-signature" cols="72">-- 
Pete Resnick <a class="moz-txt-link-rfc2396E" href="http://www.qualcomm.com/~presnick/">&lt;http://www.qualcomm.com/~presnick/&gt;</a>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102</pre>
</body>
</html>

--------------070401040401040604070300--

From sm@resistor.net  Thu Jun  2 19:43:10 2011
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 EA58CE06D7; Thu,  2 Jun 2011 19:43: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KcDLSC+OD1Ry; Thu,  2 Jun 2011 19:43: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 6D098E06A0; Thu,  2 Jun 2011 19:43:08 -0700 (PDT)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p532gicG005451;  Thu, 2 Jun 2011 19:42:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1307068984; bh=mEEKlXMMmueV7YkrN5HSdD1ts6FWbLfnTlJYKoKAdXo=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=x2qa4JzDRCXMyWyV9joKza/s7cjc8aIme2LptsoWzyvaeqrYESD/Qsz1DaFsdrnmb kVqgwfq3TZ3uGNEK0UEx5ZFJHFPCR8s0O+vxVxXFR3rWmW46ycRmfhlUG66dSzw/XA pqb7ib0DWKpziO6/ZguHb2hPz+TEZlUo7NE3ko8k=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1307068984; bh=mEEKlXMMmueV7YkrN5HSdD1ts6FWbLfnTlJYKoKAdXo=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=QtjAu/Y0ezK9sPnXYddeapwg/ljJsk0OMpa13+sQO0domYnApm4dHF5L/khLLvYzn qCTUxvz/JWwTVe4CZ48nUTNzuAs1YD97/0vQZf0wdxNp45D3fIkfQXRu618Em66JMp ajFozPYExCVzRkMik8pL9ASnZfIw2di+xOtbgMXM=
Message-Id: <6.2.5.6.2.20110602192735.07e0cc70@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 02 Jun 2011 19:33:31 -0700
To: John C Klensin <john-ietf@jck.com>, Sean Turner <turners@ieca.com>, ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Proposed text for IESG Handling of Historic Status
In-Reply-To: <BC28F00B6ADCA73F54E8AF4C@PST.JCK.COM>
References: <4DE7E1CA.9010309@ieca.com> <BC28F00B6ADCA73F54E8AF4C@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Fri, 03 Jun 2011 02:43:11 -0000

At 01:04 PM 6/2/2011, John C Klensin wrote:
>While the IESG is considering this, I would encourage you to
>also consider the model used to make a specification that is
>simply and obviously obsolete (and in A/S terms "not
>recommended") Historic without having to have an I-D written and
>processed into RFC via the same process used to create Standards
>Track documents.  In the cases in which we want to move a
>specification to Historic because it is a bad idea, having an
>RFC to explain why it was a bad idea seems appropriate.  But for
>the "no one cares about it any more" cases, it seems like a
>lighter-weight procedure, such as a Last Call on the question
>"does anyone believe that our impression that no one cares is
>incorrect?"  might be in order (and much closer to the procedure
>that was used when (and before) 2026 was adopted.

Agreed.  It's easier to do a Last Call.  If anyone objects, go 
through I-D path to explain why the RFC should be reclassified.

Regards,
-sm 


From john-ietf@jck.com  Thu Jun  2 20:05:22 2011
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 24395E088B; Thu,  2 Jun 2011 20:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id erSVAH9Hy8di; Thu,  2 Jun 2011 20:05:21 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 3D924E06D7; Thu,  2 Jun 2011 20:05:21 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QSKhJ-000JGk-SO; Thu, 02 Jun 2011 23:05:18 -0400
Date: Thu, 02 Jun 2011 23:05:17 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qualcomm.com>, Scott Brim <scott.brim@gmail.com>
Subject: Re: Proposed text for IESG Handling of Historic Status
Message-ID: <1F69FC6C0DEF58B9E8CB8B6C@PST.JCK.COM>
In-Reply-To: <4DE813E5.1040904@qualcomm.com>
References: <4DE7E1CA.9010309@ieca.com> <BC28F00B6ADCA73F54E8AF4C@PST.JCK.COM> <BANLkTikfhMWuLweofTfjncNY6s_cFZ6VRQ@mail.gmail.com> <4DE813E5.1040904@qualcomm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: The IESG <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: Fri, 03 Jun 2011 03:05:22 -0000

--On Thursday, June 02, 2011 17:51 -0500 Pete Resnick
<presnick@qualcomm.com> wrote:

>> Agree, but producing such a "no one cares anymore" RFC and
>> getting it  through the process should be lightweight enough
>> already. It should  slide right through.

For better or worse, I don't believe that has been the
experience in recent years.

>> I hope we don't need
>> yet another special process  because our normal process is
>> too heavy.

> I have no strong opinion on what exactly we should do on this
> point, but the IESG can already do exactly what John wants
> with no change to process. (See the end of 2026 sec. 6.2.) We
> would just have to decide to do it.

My point exactly.

      john





From narten@us.ibm.com  Thu Jun  2 22:03:39 2011
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 E383CE06A7 for <ietf@ietfa.amsl.com>; Thu,  2 Jun 2011 22:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.216
X-Spam-Level: 
X-Spam-Status: No, score=-106.216 tagged_above=-999 required=5 tests=[AWL=0.383, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ppXLEH960iF for <ietf@ietfa.amsl.com>; Thu,  2 Jun 2011 22:03:39 -0700 (PDT)
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.143]) by ietfa.amsl.com (Postfix) with ESMTP id 4A453E06A2 for <ietf@ietf.org>; Thu,  2 Jun 2011 22:03:38 -0700 (PDT)
Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by e3.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p534UvbH031375 for <ietf@ietf.org>; Fri, 3 Jun 2011 00:30:57 -0400
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 p534r3o4950462 for <ietf@ietf.org>; Fri, 3 Jun 2011 00:53:13 -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 p534r3YC003798 for <ietf@ietf.org>; Fri, 3 Jun 2011 00:53:03 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.176.22]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p534r2RS003772 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 3 Jun 2011 00:53:03 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p534r2F9004248 for <ietf@ietf.org>; Fri, 3 Jun 2011 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p534r1FF004236 for ietf@ietf.org; Fri, 3 Jun 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201106030453.p534r1FF004236@rotala.raleigh.ibm.com>
Date: Fri, 03 Jun 2011 00:53:01 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 05:03:40 -0000

Total of 68 messages in the last 7 days.
 
script run at: Fri Jun  3 00:53:01 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 17.65% |   12 | 53.78% |   632993 | jason_livingood@cable.comcast.com
  8.82% |    6 |  4.38% |    51500 | presnick@qualcomm.com
  4.41% |    3 |  7.17% |    84413 | joelja@bogus.com
  7.35% |    5 |  2.69% |    31677 | ed.lewis@neustar.biz
  2.94% |    2 |  6.84% |    80456 | dhc@dcrocker.net
  5.88% |    4 |  2.21% |    25991 | ajs@anvilwalrusden.com
  5.88% |    4 |  2.20% |    25852 | john-ietf@jck.com
  4.41% |    3 |  2.10% |    24692 | simon@josefsson.org
  4.41% |    3 |  2.09% |    24563 | lorenzo@google.com
  2.94% |    2 |  1.07% |    12642 | stbryant@cisco.com
  2.94% |    2 |  0.95% |    11212 | sm@resistor.net
  2.94% |    2 |  0.85% |     9966 | michael.scharf@alcatel-lucent.com
  1.47% |    1 |  1.65% |    19458 | klensin@jck.com
  1.47% |    1 |  1.42% |    16681 | scottr.nist@gmail.com
  1.47% |    1 |  1.37% |    16121 | ron.even.tlv@gmail.com
  1.47% |    1 |  1.01% |    11865 | violeta.cakulev@alcatel-lucent.com
  1.47% |    1 |  1.01% |    11863 | vesely@tana.it
  1.47% |    1 |  0.65% |     7701 | pekkas@netcore.fi
  1.47% |    1 |  0.64% |     7578 | ssaxena@cisco.com
  1.47% |    1 |  0.64% |     7500 | scott.brim@gmail.com
  1.47% |    1 |  0.55% |     6525 | turners@ieca.com
  1.47% |    1 |  0.55% |     6498 | paul.hoffman@vpnc.org
  1.47% |    1 |  0.54% |     6385 | narten@us.ibm.com
  1.47% |    1 |  0.51% |     6033 | adrian@olddog.co.uk
  1.47% |    1 |  0.47% |     5515 | housley@vigilsec.com
  1.47% |    1 |  0.46% |     5425 | shanna@juniper.net
  1.47% |    1 |  0.44% |     5139 | dot@dotat.at
  1.47% |    1 |  0.42% |     4984 | gert@space.net
  1.47% |    1 |  0.35% |     4178 | msk@cloudmark.com
  1.47% |    1 |  0.34% |     4037 | hartmans-ietf@mit.edu
  1.47% |    1 |  0.34% |     3973 | finlayson@live555.com
  1.47% |    1 |  0.30% |     3571 | johnl@iecc.com
--------+------+--------+----------+------------------------
100.00% |   68 |100.00% |  1176987 | Total

From evnikita2@gmail.com  Thu Jun  2 23:49:26 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8C0EE0662; Thu,  2 Jun 2011 23:49:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.533
X-Spam-Level: 
X-Spam-Status: No, score=-3.533 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pw8M8BfDYVH0; Thu,  2 Jun 2011 23:49:26 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id A0845E0593; Thu,  2 Jun 2011 23:49:25 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1280247fxm.31 for <multiple recipients>; Thu, 02 Jun 2011 23:49:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+r26B/KVS/gKRQuxYg0UtPIqlUMKZF+Vlvv9dcLrYok=; b=GWMH8oBpVYXGPqZOCfzibhXuUs7YucnaMRxjEkZRkHWyfV2/iMwzAEEX9CdOSwsiNT 3pVp/YzJNdVxOAnB64MjzrodfERIhNBNF//7d1+EF/EkIeKyTkO9LCAxV7IDPuP/HLBO dZViuwqeImvFMOq25VtbZ+wkBNJ5PHNMMYNJ0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=IBWcQgnGRDAr22Zj4e7H7zcbqp1S9S+XjHPqHi4HbLGVBrDXKbVqmThcWkKg+jsP2H 1j3IjzBjhQW0bEeNn8TaSBnXNqe3KOWLD1MA53fUHXcLYIewS2Gw/00Hx1HmGKONTd4W ikikxxvp9PUhOoUYkC7rYD1QF8rwpSjMcb2Fo=
Received: by 10.223.98.141 with SMTP id q13mr1699321fan.96.1307083764785; Thu, 02 Jun 2011 23:49:24 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id l26sm396994fam.45.2011.06.02.23.49.22 (version=SSLv3 cipher=OTHER); Thu, 02 Jun 2011 23:49:23 -0700 (PDT)
Message-ID: <4DE88420.2070202@gmail.com>
Date: Fri, 03 Jun 2011 09:50:08 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Sean Turner <turners@ieca.com>
Subject: Re: Proposed text for IESG Handling of Historic Status
References: <4DE7E1CA.9010309@ieca.com>
In-Reply-To: <4DE7E1CA.9010309@ieca.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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: Fri, 03 Jun 2011 06:49:26 -0000

Hello,

The proposed statement is mostly fine.  But, since RFC 2026 gives very 
little information on some issues, I'd like you considered them in the 
statement.

First, for RFCs of what categories is it legitimate to move them to 
Historic.  Whether Experimental or Informational RFCs could be 
considered for such action?  As far as I understand RFC 2026, Historic 
can be assigned to Standards Track documents; however it won't be 
excessive to clarify this regulation in the IESG statement additionally.

I support the opinion that the information on what the particular RFC 
moves to Historic shouldn't go in the Abstract; the current practice is 
also the same (see eg. http://tools.ietf.org/html/rfc6265, end of 
Section 1).  Let's mention it is only put in the Introduction.

The proposed statement says almost nothing about how the RFC may be 
moved to Historic status without the necessity to publish a separate RFC 
for this purpose.  Here I agree with John Klensin.  Let's adopt 
something like proposed in 
http://tools.ietf.org/id/draft-ietf-newtrk-cruft-00.txt, but more 
lightweight.  What I mean is that the procedure should be:

(1) an individual or a group of individuals apply to the appropriate AD 
for moving some specification to Historic;

(2) AD asks Secretariat to issue a 2-to-4-week Last Call on 
reclassification;

(3) once community consensus is determined, AD brings the question to 
IESG's attention via putting it on agenda as "Management Issue";

(4) if IESG does not object, the announcement is sent to RFC Editor and 
copied to IETF Announce list containing request to change the particular 
RFC's status to Historic.

Such procedure seems lightweight enough not to create dozens of new RFCs 
reclassifying the old ones but have the appropriate community involvement.

Mykyta Yevstifeyev

02.06.2011 22:17, Sean Turner wrote:
> The IESG is considering making this statement on the IESG Handling of 
> Historic status.
>
> We would appreciate community feedback.
>
> Please can we have feedback by Thursday 9th June.
>
> Thanks
>
> spt
>
> <statement begins>
>
> RFC 2026 states the following:
>
> A specification that has been superseded by a more recent 
> specification or is for any other reason considered to be obsolete is 
> assigned to the "Historic" level.
>
> In practice, the Historic status is not automatically assigned to RFCs 
> that have been "obsoleted".  That is, when an RFC that contains the 
> "Obsoletes: RFC XXXX" header is published the RFC editor does not 
> automatically apply the Historic status to the XXXX RFC.  Note that in 
> some situations this is perfectly acceptable because multiple versions 
> of an Internet Standard are permitted to "honor the installed base," 
> as per RFC 2026.
>
> If authors wish to change the status of RFCs that are in the obsoletes 
> header to Historic, then the authors must include an explicit 
> statement for the RFC editor to do so; preferably in the abstract and 
> introduction.  Further, when an AD sponsors a draft that includes the 
> obsoletes header, then the AD should ask the authors whether the 
> authors intended to move the RFC(s) listed in the obsoletes header to 
> Historic status.
>
> If an author wishes to publish a document directly to Historic status 
> the preferred approach is to publish an I-D with the "Intended Status: 
> Historic" in the header.
>
> Moving a document to Historic status means that the document is "not 
> [an] Internet Standards in any sense," as per RFC 2026.
>
> </statement ends>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From scottr.nist@gmail.com  Thu Jun  2 11:10:32 2011
Return-Path: <scottr.nist@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD76E0709; Thu,  2 Jun 2011 11:10:32 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZvQxlpkTNBtx; Thu,  2 Jun 2011 11:10:30 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 70FF6E0819; Thu,  2 Jun 2011 11:10:30 -0700 (PDT)
Received: by wyb29 with SMTP id 29so951087wyb.31 for <multiple recipients>; Thu, 02 Jun 2011 11:10:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=VQGQXpyoJJX9eCoUTg5emD/ist+GnP+SJqXtRjywuiI=; b=HVfohr4/HoUc4VuZET83sZlZ+taPd8F7aL2CBjp3hCmwzaH26mNqSbZ8tORS/2NmfX 8KR6JzaBD1Ac5AwdTWfTQ0mDgdLkmyshsONAzbnsfMAuEHQjGgyk6PWjWbyiz1Am0ln8 +NGhBX7JZRLU2QFjFuYU3quDttrG3myJevXuk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=hTrd80cfvrPwwvhbdkPuUwdORaW8ZIpxka/wpM4FQIFKf8ZAXSnrF+LDRZSshq97Pq QS00JRvnBUZ5NkuWnRpr64GBTJM85o+i4RX0IflU3umMp96Rj8PKJAEU7ncRF4+qAZ9Y FTVYTVOcmjhqftWF/AF2EkSuIpWiYZp25jp7A=
MIME-Version: 1.0
Received: by 10.216.201.163 with SMTP id b35mr980035weo.80.1307038229487; Thu, 02 Jun 2011 11:10:29 -0700 (PDT)
Received: by 10.216.87.21 with HTTP; Thu, 2 Jun 2011 11:10:29 -0700 (PDT)
In-Reply-To: <a06240800ca0d30bcc18c@10.31.204.168>
References: <20110526152257.21795.30012.idtracker@ietfa.amsl.com> <a06240802ca0bff6fff57@10.31.204.168> <BANLkTimpGsRXuHi2zuuJKrZi1Ypcic5Xkw@mail.gmail.com> <20110601175216.GX26780@shinkuro.com> <a06240802ca0c457b6ab4@10.31.204.168> <20110601203355.GB26780@shinkuro.com> <a06240800ca0d30bcc18c@10.31.204.168>
Date: Thu, 2 Jun 2011 14:10:29 -0400
Message-ID: <BANLkTi=bxAXrAvz9GNDVrPfQW_acD-UGJw@mail.gmail.com>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-fixes-08.txt> (Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry) to Proposed Standard
From: Scott Rose <scottr.nist@gmail.com>
To: ietf@ietf.org, dnsext@ietf.org
Content-Type: multipart/alternative; boundary=0016e6db2a8f6061f604a4be8dac
X-Mailman-Approved-At: Fri, 03 Jun 2011 08:40:42 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: scott.rose@nist.gov
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 18:10:32 -0000

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

On Thu, Jun 2, 2011 at 8:51 AM, Edward Lewis <Ed.Lewis@neustar.biz> wrote:

> At 16:33 -0400 6/1/11, Andrew Sullivan wrote:
>
>  I believe that nothing anywhere in the document suggests that one
>> ought to guage conformance of software against the registry, and if
>> you think it says that somewhere, I'd like a pointer to where.  It
>> would need to be fixed if it said that, but as far as I can tell it
>> does not.
>>
>
> I believe the opposite.
>

Then perhaps a wording change?  It seems that it is confusion over the
language rather than the purpose.


 Scott

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

On Thu, Jun 2, 2011 at 8:51 AM, Edward Lewis <span dir=3D"ltr">&lt;<a href=
=3D"mailto:Ed.Lewis@neustar.biz">Ed.Lewis@neustar.biz</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">At 16:33 -0400 6/1/11, 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">
I believe that nothing anywhere in the document suggests that one<br>
ought to guage conformance of software against the registry, and if<br>
you think it says that somewhere, I&#39;d like a pointer to where. =A0It<br=
>
would need to be fixed if it said that, but as far as I can tell it<br>
does not.<br>
</blockquote>
<br></div></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I believe the opposite.<br></blockquote><div><br></div><div>Then perhaps a =
wording change? =A0It seems that it is confusion over the language rather t=
han the purpose.<br>

<div class=3D"im"><br>
<br>=A0Scott
</div><div class=3D"im"><br></div></div><br>

--0016e6db2a8f6061f604a4be8dac--

From lars.eggert@nokia.com  Fri Jun  3 03:36:51 2011
Return-Path: <lars.eggert@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 4B4E4E0720 for <ietf@ietfa.amsl.com>; Fri,  3 Jun 2011 03:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.138
X-Spam-Level: 
X-Spam-Status: No, score=-103.138 tagged_above=-999 required=5 tests=[AWL=0.461, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 69HNX-5hW8tJ for <ietf@ietfa.amsl.com>; Fri,  3 Jun 2011 03:36:50 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id B33B4E06B1 for <ietf@ietf.org>; Fri,  3 Jun 2011 03:36:50 -0700 (PDT)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p53AamPI003031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 3 Jun 2011 13:36:50 +0300
From: Lars Eggert <lars.eggert@nokia.com>
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.97 at fit.nokia.com
Content-Type: multipart/signed; boundary=Apple-Mail-97-225207219; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Applied Networking Research Prize awards for IETF-81
Date: Fri, 3 Jun 2011 13:36:45 +0300
Message-Id: <F9D7E51A-FDEF-4757-823D-C43E476E2841@nokia.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.fit.nokia.com); Fri, 03 Jun 2011 13:36:45 +0300 (EEST)
X-Nokia-AV: Clean
X-Mailman-Approved-At: Fri, 03 Jun 2011 08:40:42 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: anrp@isoc.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 10:36:51 -0000

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

Hi,

we are extremely pleased to report that for this very first award
of the Applied Networking Research Prize (ANRP), 24 nominations
were received. Each submission was reviewed by 2-4 members of the
selection committee according to a diverse set of criteria, including
scientific excellence and substance, timeliness, relevance, and
potential impact on the Internet.=20

Based on this review, two submissions were awarded an Applied
Networking Research Prize:

*** Mattia Rossi *** for his research into reducing BGP traffic:

  Geoff Huston, Mattia Rossi and Grenville Armitage. A Technique
  for Reducing BGP Update Announcements through Path Exploration
  Damping. IEEE Journal on Selected Areas in Communications (JSAC),
  Vol. 28, No. 8, pp. 1271=961286, October 2010.

*** Beichuan Zhang *** for his research into =93green=94 traffic =
engineering:

  Mingui Zhang, Cheng Yi, Bin Liu and Beichuan Zhang. GreenTE:
  Power-Aware Traffic Engineering. Proc. IEEE International Conference
  on Network Protocols (ICNP), pp. 21=9630, October 2010.

Both researchers have been invited to present their findings in the
IRTF Open Meeting during IETF-81, July 24-29, 2011 in Quebec City,
Canada. Join them there!

There will be a call for ANRP nominations this summer that will target
IETF-82 in Taipei, Taiwan in November 2011. For 2012, we are
considering to switch to a yearly nomination/award cycle, with a
call for nominations in late 2011 that will cover all three IETF
meetings planned for 2012. Read more about the ANRP at
http://irtf.org/anrp.

Please subscribe to the IRTF-Announce mailing list in order to
receive future calls for ANRP nominations and join ISOC to stay
informed of other networking research initiatives:

  http://irtf.org/mailman/listinfo/irtf-announce
  http://isoc.org/join

Regards,

Lars Eggert, IRTF Chair
Mat Ford, Internet Society
http://irtf.org/anrp

--=20

ANRP Selection Committee

Mark Allman, ICIR
Lou Berger, LabN
Ross Callon, Juniper
Lars Eggert, Nokia
Olivier Festor, INRIA
Mat Ford, ISOC
Andrei Gurtov, HIIT
Al Morton, AT&T
Bruce Nordman, LBL
J=F6rg Ott, Aalto University
Stefano Previdi, Cisco
Martin Stiemerling, NEC


--Apple-Mail-97-225207219
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMRjCCBVAw
ggQ4oAMCAQICEGxdPUZzCwUJ8KBiJwH+bYgwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMDEwMTUwMDAwMDBaFw0x
MTEwMTUyMzU5NTlaMIIBEzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9r
aWEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwolKEyOz/NQZJJlw0x9XBS9W
wCmabdY1fXpbWSdcaJiEWhQpRzSIC/pgIwCgaUW9g3JsWioXCawyjUVeg8xR42sR690f4z+OPAUm
3jokZxsuRaGX6fuPkPQomYAGz7htUHws/8FZIU+4dciETQf4vF5ptitJ+QZCVRCTLqisj6mG/kG4
65Op3G5/YZF9F/a390LdhuRP6vdY2Y+dqm8LDa0zmENPpoE98u1pIZGqCcnskN/nNBtEPd+a4lNh
ZSGnPuL4XCUSJYR9NB7FAYBvi5N7LSWHR3fspwa5EgpXynJcsLzaLA0iGfjFOBYFxul/07edmyw4
FIXuCIkaMDUfEwIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcX
ATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIF
oDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDov
L2luZGMxZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3Js
MA0GCSqGSIb3DQEBBQUAA4IBAQAlSTzUKqa3ZouKWFQfIJ+4l/KsztPnY4Onwzt8lqAmeiFPqOmf
kLTXbXDKtC6caFadNtyHpnsmQFFKXwhe5Z9/AaVSwryu6F9992DzYLp3j8PE0DSU0wmpUXUtp+rz
TFqJRkzB8RCBoq/TPBmkMPr68qB0TkU3dbYiVIvscOt1MRkdHiwG4wKQLyCf8XRRWqmMY6lbun7g
kiEWiris5StGKRvE5+e1SrcdnoZxIKQFF7Etr+4ftClrsDQWX9nRCEjYcmz4y/deq+HU8ylBaKZE
0ZJmcnYlAaD50OYWi0ckGDnKYyeMUEtCZJSV0otm2LqyIUAu9WPv/GNHt2ntjnUaMIIG7jCCBdag
AwIBAgIQcRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTow
OAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5
MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g
QXV0aG9yaXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBO
ZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t
L3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJp
U2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6Zvg
SU6Lb9UB0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHs
EnMhjfXcMM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO
4YM/d/mZ//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSy
riMGZSalJ1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCC
ArUwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20w
EgYDVR0TAQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUH
AgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWdu
LmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgw
VhYJaW1hZ2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDov
L2xvZ28udmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQ
cml2YXRlTGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYD
VR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4x
HzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlT
aWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENs
YXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaE
VIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlM
JBq6WaSHO3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKv
YLMVirOVnDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDR
yxTWcVibvtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy
+kgOZY5JyNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/
wYIxggSLMIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMu
MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2Ny
aWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJ
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDYwMzEwMzY0NVowIwYJKoZIhvcNAQkE
MRYEFMzB6qNP+Qiqg9btQIEzTP3vIeoJMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AGeXijaWx8H+lrtu6dWWpOwRySabRWryWNxHcD0I89eGwkKXsw1eeWRBCvs7cS6h5K3lTJ1KmOuh
ZO8Hbc1XmR2zCtm9MRyACl3c26Jh6lfXxCrA3rOR8W1+EjYa3ESxO6xBYY+raTfU3JGPjc84J+m8
WeSJLAPBtJP1il141kdED2SKfbnYIa1sVcHfGD4jvokAiuTNMM5BejujcER/TGXRKONK1+Pbf+vv
ExuuwjfMvvMUI+gqvkWCokWozSSHrbQAEK5VxQ2E+RrGDFxPjMyS+5Ks4aCAnRxaZ7/+wxU+k1I3
2baCNT66NUm1Xach7p5ouwuJK2CFzBC2yuo4/m4AAAAAAAA=

--Apple-Mail-97-225207219--

From johnl@iecc.com  Fri Jun  3 12:34:37 2011
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 523C0E078B for <ietf@ietfa.amsl.com>; Fri,  3 Jun 2011 12:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.37
X-Spam-Level: 
X-Spam-Status: No, score=-109.37 tagged_above=-999 required=5 tests=[AWL=1.829, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rQEJxdDUAS1N for <ietf@ietfa.amsl.com>; Fri,  3 Jun 2011 12:34:36 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id 1B299E067F for <ietf@ietf.org>; Fri,  3 Jun 2011 12:34:36 -0700 (PDT)
Received: (qmail 86059 invoked from network); 3 Jun 2011 19:34:34 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 3 Jun 2011 19:34:34 -0000
Date: 3 Jun 2011 19:34:12 -0000
Message-ID: <20110603193412.77778.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Second Last Call: <draft-ietf-dkim-mailinglists-11.txt> (DKIM And Mailing Lists) to BCP
In-Reply-To: <20110603191508.32738.46125.idtracker@ietfa.amsl.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 19:34:37 -0000

This problem with this document is that it does not, in fact, describe
Best Current Practices.

The description of the interaction between DKIM and mailing lists is
pretty good.  But of the advice it offers, only one item is in fact
done in production, signing outgoing mail, and everything else is
hypothetical.  We can have (and have had) arguments about whether it
would be a good idea to do what the rest of the advice says, but the
reality is that nobody knows, since we haven't tried it other than
perhaps in tiny experiments.

I'd suggest changing the category to Informational or perhaps
Experimental, after sending it back to the group and telling us to
distinguish between what's current practice and what isn't.

On the other hand, if it's OK for BCPs to consist of Our Unimplemented
Speculation, I have a variety of BCPs I'd like to send along.

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 yaronf.ietf@gmail.com  Fri Jun  3 13:32:08 2011
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 722B7E07BE; Fri,  3 Jun 2011 13:32:08 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i0Vy8MeZBvm9; Fri,  3 Jun 2011 13:32:07 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id B05A7E07AB; Fri,  3 Jun 2011 13:32:06 -0700 (PDT)
Received: by wyb29 with SMTP id 29so1954647wyb.31 for <multiple recipients>; Fri, 03 Jun 2011 13:32:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ys9/a6FOLVsH1YDb4viHsfWjgcRNUhxyv/K7HQA0Gek=; b=TK29CrE+wR2+npw9gG9QvbErnDgLbTgO/8v84HfOSKcG7hGB9BefqpmDljMDWmG2PV BaM9gkeokZPm+LLOoZeIZhC64svVkf4pJErJeBKMjzwyuH1W2FCWdHOglFyfxZRL6H9P NCZGvczViT8Vnd6gSa1Xemlm2jd+l7MEsBxUQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=pDFWUmDIrIKCLYM5iU0+qasB2IlJ7jjkz5H5kpHVOnOaf+4fHm2m5i+JRA+qZnnyPi FLnZDkVR3lRoOBkYrTTar1Gxp42lUtfC7YYI89kTI4+U4bbUbNpGwbf7Uwa8XzPr5vOH a3TiNIli5D7MhEzoxmRSPb5rHH4rOmhWtwr1M=
Received: by 10.227.132.210 with SMTP id c18mr2355829wbt.44.1307133125437; Fri, 03 Jun 2011 13:32:05 -0700 (PDT)
Received: from [10.0.0.2] (bzq-79-178-38-173.red.bezeqint.net [79.178.38.173]) by mx.google.com with ESMTPS id et5sm1267260wbb.33.2011.06.03.13.32.02 (version=SSLv3 cipher=OTHER); Fri, 03 Jun 2011 13:32:04 -0700 (PDT)
Message-ID: <4DE944C1.5020608@gmail.com>
Date: Fri, 03 Jun 2011 23:32:01 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: "Cakulev, Violeta (Violeta)" <violeta.cakulev@alcatel-lucent.com>
Subject: Re: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
References: <20110520135022.1622.22713.idtracker@ietfa.amsl.com> <4DD9581C.3070900@gmail.com> <AAE76B481E7A0E4C96610790A852B9A625099F98E2@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
In-Reply-To: <AAE76B481E7A0E4C96610790A852B9A625099F98E2@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IPsecme WG <ipsec@ietf.org>, "draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org>, "dime@ietf.org" <dime@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, 03 Jun 2011 20:32:08 -0000

Hi Violeta,

thanks for your response.

I understand now where you're coming from. But the next person to read 
the document might not have the authors so readily available :-) 
Implementors need to understand the motivation for this solution as well 
as the missing pieces.

So I would suggest that you add:
- A short paragraph in the Introduction putting this document in 
perspective and referencing (non-normative references of course) the 
3GGP2 documents.
- Another paragraph in the Security Considerations that says that 
generation/derivation of the PSK is security-critical, and provides the 
3GPP2 docs again as an example of a solution to this problem.

Regarding usage of the SPI, the document says: "Upon receiving the 
IKE_AUTH message from the IKEv2 Peer, the IKEv2 Server uses the 
information received in IDi *and the SPI* if available, to determine if 
it has the PSK for this IKEv2 Peer."This sounds to me as if the SPI is 
used as part of the PSK lookup operation. Maybe the SPI should not be 
mentioned in the above text.

Best regards,

     Yaron

On 06/01/2011 11:04 PM, Cakulev, Violeta (Violeta) wrote:
> Hi Yaron,
> Thanks for the comments.
> Please see inline [VC].
>
> -Violeta
>
> -----Original Message-----
> From: ipsec-bounces@ietf.org [mailto:ipsec-bounces@ietf.org] On Behalf Of Yaron Sheffer
> Sent: Sunday, May 22, 2011 2:38 PM
> To: ietf@ietf.org
> Cc: IPsecme WG; draft-ietf-dime-ikev2-psk-diameter@tools.ietf.og; dime@ietf.org
> Subject: Re: [IPsec] Last Call:<draft-ietf-dime-ikev2-psk-diameter-06.txt>  (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
>
> Hi,
>
> Having read this document only now, I think there's a number of serious issues with it. This document was sent to the ipsec mailing list a while ago but unfortunately got no review.
>
> Summary:
> 1. I think the wrong architectural choice was made, in preferring PSK over EAP authentication.
> 2. There is not enough detail in the document to result in interoperable implementations.
> [VC] Please see responses to detailed comments.
>
> Detailed comments:
> * The appropriate ref for IKEv2 is RFC 5996. This was actually noted in the shepherd review back in March.
> [VC] This is fixed in v7.
>
>
> * The document notes that EAP is one of the authentication modes supported by IKEv2. EAP is designed for interaction with backend AAA servers, and is quite capable of performing shared-secret authentication, using a variety of EAP methods (and see also RFC 5998, on IKEv2 mutual auth with EAP). Yet the document does not explain why EAP is not used, instead preferring the IKE PSK authentication method.
> [VC] Diameter application for Diameter client to server communication for IKEv2 with EAP has been specified in RFC 5778. However, there is no Diameter application specified for IKE PSK authentication method. This is stated in the draft both in Abstract and Introduction. The draft does not recommend one or the other, it is simply specifying what is not specified. It is up to a specific use case to decide what to use. For example 3GPP2 decided to use IKEv2 PSK (in 2 of its specifications), and that is what triggered this effort in IETF.
>
>
> * 4.1: how can the incoming SPI be used to identify the peer?
> [VC] As stated in Section 4.1 IDi payload is extracted from the IKE_AUTH message and this payload 'MUST contain an identity that is meaningful
>     for the Diameter infrastructure, such as a Network Access Identifier (NAI), since it is used by the IKEv2 Server to populate the User-Name
>     AVP in the Diameter message'. SPI is not used to identify the peer.
>
>
> * Packing additional semantics into SPI may conflict with elements of the IPsec architecture (see for example Sec. 9.3 of draft-ietf-ipsecme-failure-detection-08).
> [VC] Agreed.
>
>
> * 4.1, 2nd paragraph: generation of the PSK is central to this solution, so it cannot be "outside the scope" of the document. There is no way to interoperate otherwise.
> [VC] This draft focuses on IKEv2 server, as a Diameter client, to the Diameter server communication for IKEv2 with pre-
>     shared secret based authentication, and specifies Diameter application for this communication. It is left to specifications that make use of this Diameter application to specify where the PSK comes from and how it is generated. As mentioned above, there are two 3GPP2 specs that make use of this Diameter application and both of those specs specify generation of the PSK.
>
>
> * Moreover, if a single client is expected to sometimes use EAP and sometimes PSK, there must be a way to notify it which one to use.
> [VC] This is not the assumption. Again this draft specifies Diameter application for Diameter client to the Diameter server communication for IKEv2 with PSK. IKEv2 server knows whether EAP or PSK is used.
>
>
> * How does key-lifetime relate to the lifetime of the IKE SA?
> [VC] This should be the same as in RFC 5996, how pre-shared secret lifetime relates to the lifetime of the IKE SA. This draft should not make any changes.
>
>
> * Sec. 10 refers to the PSK as a "session key" which is incorrect, as PSK is only used for authentication and does not encrypt anything.
> [VC] Good point. It is changed to PSK in v7.
>
>
> * The same paragraph is very vague about the security properties of PSK.
> RFC 5996 takes PSK much more seriously, e.g. "When using pre-shared keys, a critical consideration is how to assure the randomness of these secrets." Again, I believe the document should specify how the PSK is derived.
> [VC] I absolutely agree that derivation of PSK is critical. However, as stated above, this draft specifies Diameter application only. Therefore, security consideration section cannot include much more details on derivation of PSK as it is specified elsewhere.
>
>
> * Why "if nonces are included" where the document says that they *must* be included (in the AVP occurrence table).
> [VC] Good point. This is removed in v7.
>
>
> Thanks,
> Yaron
>
> On 05/20/2011 04:50 PM, The IESG wrote:
>> The IESG has received a request from the Diameter Maintenance and
>> Extensions WG (dime) to consider the following document:
>> - 'Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server
>>      to Diameter Server Interaction'
>>     <draft-ietf-dime-ikev2-psk-diameter-06.txt>   as a 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 2011-06-03. 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 Internet Key Exchange protocol version 2 (IKEv2) is a component
>>      of the IPsec architecture and is used to perform mutual
>>      authentication as well as to establish and to maintain IPsec security
>>      associations (SAs) between the respective parties.  IKEv2 supports
>>      several different authentication mechanisms, such as the Extensible
>>      Authentication Protocol (EAP), certificates, and pre-shared secrets.
>>
>>      With [RFC5778] the Diameter interworking for Mobile IPv6 between the
>>      Home Agent, as a Diameter client, and the Diameter server has been
>>      specified.  However, that specification focused on the usage of EAP
>>      and did not include support for pre-shared secret based
>>      authentication available with IKEv2.  This document specifies IKEv2
>>      server, as a Diameter client, to the Diameter server communication
>>      for IKEv2 with pre-shared secret based authentication.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec

From msk@cloudmark.com  Fri Jun  3 14:24:46 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CF08E07D0 for <ietf@ietfa.amsl.com>; Fri,  3 Jun 2011 14:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.572
X-Spam-Level: 
X-Spam-Status: No, score=-104.572 tagged_above=-999 required=5 tests=[AWL=-0.973, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IOPD+hJf+3Zm for <ietf@ietfa.amsl.com>; Fri,  3 Jun 2011 14:24:45 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id E1D6AE07CA for <ietf@ietf.org>; Fri,  3 Jun 2011 14:24:45 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Fri, 3 Jun 2011 14:24:45 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 3 Jun 2011 14:24:44 -0700
Subject: RE: Second Last Call: <draft-ietf-dkim-mailinglists-11.txt> (DKIM And	Mailing Lists) to BCP
Thread-Topic: Second Last Call: <draft-ietf-dkim-mailinglists-11.txt> (DKIM And	Mailing Lists) to BCP
Thread-Index: AcwiJVKFO2ZLl8iNQTaWnKWqLKhtSQADzPbw
Message-ID: <F5833273385BB34F99288B3648C4F06F134C9193D4@EXCH-C2.corp.cloudmark.com>
References: <20110603191508.32738.46125.idtracker@ietfa.amsl.com> <20110603193412.77778.qmail@joyce.lan>
In-Reply-To: <20110603193412.77778.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 21:24:46 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of J=
ohn Levine
> Sent: Friday, June 03, 2011 12:34 PM
> To: ietf@ietf.org
> Subject: Re: Second Last Call: <draft-ietf-dkim-mailinglists-11.txt>
> (DKIM And Mailing Lists) to BCP
>=20
> This problem with this document is that it does not, in fact, describe
> Best Current Practices.

I think this objection has been noted.  This second last call is just to co=
ver the downref to the [EMAIL-ARCH] reference, since the first LC didn't ma=
ke explicit note of this.


From fernando.gont.netbook.win@gmail.com  Fri Jun  3 15:16:26 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C397E07FF; Fri,  3 Jun 2011 15:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.659
X-Spam-Level: 
X-Spam-Status: No, score=-2.659 tagged_above=-999 required=5 tests=[AWL=-0.690, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_PROLOSTOCK_SYM3=1.63]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wb0ykAyZwN2P; Fri,  3 Jun 2011 15:16:24 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 58E6FE07F5; Fri,  3 Jun 2011 15:16:24 -0700 (PDT)
Received: by yic13 with SMTP id 13so1221641yic.31 for <multiple recipients>; Fri, 03 Jun 2011 15:16:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:x-enigmail-version:content-type :content-transfer-encoding; bh=Sj4Vst+u1ZbwtKHVqJr82KaaGYTOx70sLtiL61tHnWA=; b=po9gsDAhSoCIBaZA3BCxp3QOyXAEi+gRUUVprl4EAmC/aqiXIbL9srMzf4dpHMtgrv 43hKzFDyoC6wLu4IJhN6UBl0Xs28yxvd0oSRHX6Rt0lcBRV0UgT+PJKD7GS+kwOhNj7S XrdFFxuAKpXsZEyl5CdO2d9gRYi6gxoHlreSw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :x-enigmail-version:content-type:content-transfer-encoding; b=LJgbVnQz95Ae3EOGATAJpTpwfmkgOPUc+vsP3va9O3W3973MJC3xTITiNEJAoehVup sGo3h3mbLjHcKjzVRkONV5ryU72Zh+A84WI9sck9MidWgj/HsostN3nby52Zu+njmFZK xghUX38sDavEqt34RMRUAfd/fgr/GY/cxSVqc=
Received: by 10.101.5.7 with SMTP id h7mr1816672ani.25.1307139383538; Fri, 03 Jun 2011 15:16:23 -0700 (PDT)
Received: from [192.168.123.100] ([190.48.193.117]) by mx.google.com with ESMTPS id b25sm1460806anb.20.2011.06.03.15.16.20 (version=SSLv3 cipher=OTHER); Fri, 03 Jun 2011 15:16:22 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4DE95D31.2030400@gont.com.ar>
Date: Fri, 03 Jun 2011 19:16:17 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: draft-ietf-behave-ftp64@tools.ietf.org
Subject: tsv-dir review of draft-ietf-behave-ftp64-10
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: tsv-area@ietf.org, "'ietf@ietf.org'" <ietf@ietf.org>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 22:16:26 -0000

Hello,

I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the
document's authors for their information and to allow them to address
any issues raised. The authors should consider this review together with
any other last-call comments they receive. Please always CC
tsv-dir@ietf.org if you reply to or forward this review.


SUMMARY
-------

This draft is on the right track but has open issues, described in the
review.


TECHNICAL
---------

* Section 1, page 3:
   In 5 cases, issuing the EPSV
   command to the server led to a significant delay, in 3 cases followed
   by a control channel reset.

Could you please clarify what was the cause of the delay? And, btw, have
you guys put the details of your results publicly available somewhere?


* Section 1, page 3-4:
   Clients that want to engage in more complex behavior, such as server-
   to-server transfers, may make an FTP application layer gateway (ALG)
   go into transparent mode by issuing AUTH or ALGS commands as
   explained in Section 5.

I thought server-to-server transfer had been banned for many years now
(it was exploited for address scan purposes). Am I missing something?


* Section 5:
   In the second case, an implementation MUST have the ability to track
   and update TCP sequence numbers when translating packets as well as
   the ability to break up packets into smaller packets after
[....]

What about the TCP URG flag and the Urgent Pointer? FTP is one of the
few legacy applications that make use of TCP's urgent mode. And while
use in new applications is deprecated, and TCP urgent mode itself is
unreliable (see RFC 6093), you should make an explicit decision about
what to do with TCP urgent mode when used for the FTP control channel.

When packets are translated individually, the ALG should update the
Urgent Pointer if/where necessary. If the ALG terminates the IPv6 TCP
session, there's the question of whether urgent mode should be "copied"
from the IPv6 session to the IPv4 session.


* Section 5.1, page 7:
For the time being, ALG implementations may employ
   one of the following strategies regarding LANG negotiation

Should you s/may/MAY/?


* Section 5.1, page 8:
   3.  Block LANG negotiation by translating the LANG command to a NOOP
       command, and translating the resulting 200 response into a
       response appropriate for unsupported commands, such as 500.  Text
       is sent in the default language.

I think you should mandate which exact code the 200 should be translated
to, rather than just provide an example.


EDITORIAL
---------

* Abstract, page 1

   The File Transfer Protocol (FTP) has a very long history, and despite
   the fact that today, other options exist to perform file transfers,
   FTP is still in common use.

Remove the comma between "today" and "others"


* Abstract, page 1

   translators
   are used to bridge that gap, FTP is made to work through these
   translators as best it can.

s/as best as it can/to the best possible extent/?


* Section 5.1 (page 7) and elsewhere:
   So the situation where the client and server try to
   negotiate a language that the ALG doesn't support can't be avoided.

Expand doesn't to "does not", "can't" to "cannot", etc.


* Section 5.1, page 8:
   Note that [RFC2640] section 3.1 specifies new handling for spaces and
   the CR character in path names.

Rephrase to "Note that Section 3.1 of [RFC2640]..."


* Section 11, page 12:
   ALGs MUST support the new ALGS (ALG status) command that allows
   command MUST be passed on to the server without modification, and the
   clients to query and set the ALG's status.

I had trouble parsing this sentence.


* Section 11, page 12:
   A client can use the ALGS command to request the ALG's status and to
   enable and disable EPSV to PASV and, if implemented, EPRT to PORT
   translation.

Please rephrase to "...disable EPSV to PASV translation and, if
implemented, EPRT to PORT translation".


Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From alexey.melnikov@isode.com  Sat Jun  4 13:13:38 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C526521F84EA; Sat,  4 Jun 2011 13:13:38 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n6+xuS-vQM3Q; Sat,  4 Jun 2011 13:13:38 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 0DC0F21F84E8; Sat,  4 Jun 2011 13:13:37 -0700 (PDT)
Received: from [188.28.114.130] (188.28.114.130.threembb.co.uk [188.28.114.130])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TeqR6wA-uWkF@rufus.isode.com>; Sat, 4 Jun 2011 21:13:34 +0100
Message-ID: <4DEA91C8.8080107@isode.com>
Date: Sat, 04 Jun 2011 21:12:56 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Proposed text for IESG Handling of Historic Status
References: <4DE7E1CA.9010309@ieca.com> <BC28F00B6ADCA73F54E8AF4C@PST.JCK.COM>
In-Reply-To: <BC28F00B6ADCA73F54E8AF4C@PST.JCK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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: Sat, 04 Jun 2011 20:13:38 -0000

John C Klensin wrote:

>Sean,
>
>Seems fine to me but, like Sam, I'd prefer to not clutter
>abstracts  For a specification RFC that is rendered Historic by
>a new specification, the combination of an "Obsoletes" header
>and a note in the Introduction ought to be sufficient.
>  
>
I don't mind having a note in the Abstract, if editors of a particular 
document want to make a possibly stronger (and easier to find) statement 
about moving something to Historic.

>While the IESG is considering this, I would encourage you to
>also consider the model used to make a specification that is
>simply and obviously obsolete (and in A/S terms "not
>recommended") Historic without having to have an I-D written and
>processed into RFC via the same process used to create Standards
>Track documents.  In the cases in which we want to move a
>specification to Historic because it is a bad idea, having an
>RFC to explain why it was a bad idea seems appropriate.  But for
>the "no one cares about it any more" cases, it seems like a
>lighter-weight procedure, such as a Last Call on the question
>"does anyone believe that our impression that no one cares is
>incorrect?"  might be in order (and much closer to the procedure
>that was used when (and before) 2026 was adopted.
>  
>
+1.


From alexey.melnikov@isode.com  Sat Jun  4 13:45:26 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F06C228008; Sat,  4 Jun 2011 13:45:26 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YPoSH6yOadw9; Sat,  4 Jun 2011 13:45:26 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id A9741228006; Sat,  4 Jun 2011 13:45:25 -0700 (PDT)
Received: from [188.28.114.130] (188.28.114.130.threembb.co.uk [188.28.114.130])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TeqZYQA-uV5U@rufus.isode.com>; Sat, 4 Jun 2011 21:45:24 +0100
Message-ID: <4DEA993F.4050008@isode.com>
Date: Sat, 04 Jun 2011 21:44:47 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: stbryant@cisco.com
Subject: Re: Proposed text for IESG Processing of RFC Errata concerning RFC Metadata
References: <4DE7D4EF.6050208@cisco.com>
In-Reply-To: <4DE7D4EF.6050208@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jun 2011 20:45:26 -0000

Hi Stewart,

Stewart Bryant wrote:

> The IESG is considering making this statement on the
> processing of RFC Errata concerning RFC Metadata.
>
> We would appreciate community feedback.
>
> Please can we have feedback by Thursday 9th June.
>
> Thanks
>
> Stewart
>
> ======
>
>
> Draft text for IESG Statement on RFC Metadata
>
> Date: xx-xxx-xxxx
>
> This IESG statement describes the manner in which the IESG will
> process RFC Errata concerning RFC Metadata [RFC5741]. Metadata
> is used, for example, in the compilation of the RFC Index.
>
> The Area Director responsible for processing the RFC erratum will 
> review the RFC and document history recorded in various IETF archives 
> such as the datatracker. Where the error is major, for example
> an error in the document track,

Maybe it is better to call this "Category" as in RFC 5741?

> the Area Director SHOULD
> reject the erratum, and initiate the publication of a replacement
> RFC.
>
> Where
>
> - The error is minor, for example where there is a minor
> error in the list of updated RFCs, and

Are "major" and "minor" errors fully defined above? I.e. "minor error" 
only covers errors in Updates and Obsoletes?

> - The intent of the IETF community as determined from the RFC and the 
> records is clear, and
> - The RFC has been processed correctly in all other regards,
> the Area Director MAY accept the erratum. The Area Director MAY 
> consult with the IESG in making this determination.
>
> If the above minor error conditions are met, but the Area Director 
> responsible for processing the metadata is of the view that the best 
> interests of the community are served by holding the RFC erratum for 
> document update, or rejecting the erratum and initiating the
> publication of a replacement RFC they MAY process the RFC erratum 
> accordingly.
>
> Where there is doubt as to the intent of the IETF community or where 
> the RFC has not been processed in accordance with the rules governing 
> the proposed change to the RFC metadata, the RFC erratum MUST be 
> rejected.

Some clarifications on the above questions would be useful, but I think 
overall this looks fine.


From alexey.melnikov@isode.com  Sat Jun  4 14:00:22 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08F9711E8071; Sat,  4 Jun 2011 14:00:22 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Ti9Lu7lCYjx; Sat,  4 Jun 2011 14:00:21 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id E2FEC22800C; Sat,  4 Jun 2011 14:00:19 -0700 (PDT)
Received: from [188.28.114.130] (188.28.114.130.threembb.co.uk [188.28.114.130])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Teqc3gA-uUx9@rufus.isode.com>; Sat, 4 Jun 2011 22:00:15 +0100
Message-ID: <4DEA9CBC.6080608@isode.com>
Date: Sat, 04 Jun 2011 21:59:40 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Proposed text for IESG Handling of Historic Status
References: <4DE7E1CA.9010309@ieca.com> <4DE88420.2070202@gmail.com>
In-Reply-To: <4DE88420.2070202@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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: Sat, 04 Jun 2011 21:00:22 -0000

Mykyta Yevstifeyev wrote:

> Hello,
>
> The proposed statement is mostly fine.  But, since RFC 2026 gives very 
> little information on some issues, I'd like you considered them in the 
> statement.
>
> First, for RFCs of what categories is it legitimate to move them to 
> Historic.  Whether Experimental or Informational RFCs could be 
> considered for such action?  As far as I understand RFC 2026, Historic 
> can be assigned to Standards Track documents; however it won't be 
> excessive to clarify this regulation in the IESG statement additionally.

My understanding is that any RFC can be moved to Historic. But if this 
is not clear from RFC 2026, maybe it is worth clarifying.

> I support the opinion that the information on what the particular RFC 
> moves to Historic shouldn't go in the Abstract; the current practice 
> is also the same (see eg. http://tools.ietf.org/html/rfc6265, end of 
> Section 1).  Let's mention it is only put in the Introduction.
>
> The proposed statement says almost nothing about how the RFC may be 
> moved to Historic status without the necessity to publish a separate 
> RFC for this purpose.  Here I agree with John Klensin.  Let's adopt 
> something like proposed in 
> http://tools.ietf.org/id/draft-ietf-newtrk-cruft-00.txt, but more 
> lightweight.  What I mean is that the procedure should be:
>
> (1) an individual or a group of individuals apply to the appropriate 
> AD for moving some specification to Historic;
>
> (2) AD asks Secretariat to issue a 2-to-4-week Last Call on 
> reclassification;
>
> (3) once community consensus is determined, AD brings the question to 
> IESG's attention via putting it on agenda as "Management Issue";

 From the pedantic deparment:

As a matter of clarification: it is already possible to move an RFC to 
Historic without new draft using the datatracker. The RFC is added to 
datatracker (just like a draft), etc. This is not going to be a 
management item, it would appear as a proper document on IESG agenda.

"Management items" are second class citizens during IESG telechats...

> (4) if IESG does not object, the announcement is sent to RFC Editor 
> and copied to IETF Announce list containing request to change the 
> particular RFC's status to Historic.
>
> Such procedure seems lightweight enough not to create dozens of new 
> RFCs reclassifying the old ones but have the appropriate community 
> involvement.



From evnikita2@gmail.com  Sat Jun  4 21:40:10 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1DE221F84A8; Sat,  4 Jun 2011 21:40:10 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOz8V1-f1GBF; Sat,  4 Jun 2011 21:40:10 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4800E21F8474; Sat,  4 Jun 2011 21:39:49 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2179754fxm.31 for <multiple recipients>; Sat, 04 Jun 2011 21:39:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=NlHLzVq/4ah/nxWsNVf8ApNDxRWdvgmAQXjyKt4BOb0=; b=GR7IDJD0jr7TB2/sjM5V0YAPnevwFuSa1N5pqA51t0NMLTzJZQF9niv5gj5jyJ3wtL eD0lzJ0FqI2datAqrAr1iq1En0jL9knK6Xk9CcBU5gmBdZJvdNi4QVAqI3FcfZLpdpwi bhVurS4YhwaYODj1fegTR5rOVAZfiFKcZQbu0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=ndD+2Laa1+4+PTdm9xdnW234x46D9P04/fZGmJltEmk2LYX8BscvjPdGbns5JePR/2 JT3MglsPmgossan2yF8i28g/Sl1mmNBXQyELZwO2TtM3LBVApfnl5yzy5m2VF4YbQxiX 6KxIuR3fE9VArInv2PPywpjQXw+D+TF17qmoY=
Received: by 10.223.14.139 with SMTP id g11mr1850342faa.103.1307248788380; Sat, 04 Jun 2011 21:39:48 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id a18sm933328fak.29.2011.06.04.21.39.46 (version=SSLv3 cipher=OTHER); Sat, 04 Jun 2011 21:39:47 -0700 (PDT)
Message-ID: <4DEB08BF.8000302@gmail.com>
Date: Sun, 05 Jun 2011 07:40:31 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Proposed text for IESG Handling of Historic Status
References: <4DE7E1CA.9010309@ieca.com> <4DE88420.2070202@gmail.com> <4DEA9CBC.6080608@isode.com>
In-Reply-To: <4DEA9CBC.6080608@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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: Sun, 05 Jun 2011 04:40:11 -0000

04.06.2011 23:59, Alexey Melnikov wrote:
> Mykyta Yevstifeyev wrote:
>
>> Hello,
>>
>> The proposed statement is mostly fine.  But, since RFC 2026 gives 
>> very little information on some issues, I'd like you considered them 
>> in the statement.
>>
>> First, for RFCs of what categories is it legitimate to move them to 
>> Historic.  Whether Experimental or Informational RFCs could be 
>> considered for such action?  As far as I understand RFC 2026, 
>> Historic can be assigned to Standards Track documents; however it 
>> won't be excessive to clarify this regulation in the IESG statement 
>> additionally.
>
> My understanding is that any RFC can be moved to Historic. But if this 
> is not clear from RFC 2026, maybe it is worth clarifying.
It isn't really clear from RFC 2026 - so let's mention this in the 
statement.
>
>> I support the opinion that the information on what the particular RFC 
>> moves to Historic shouldn't go in the Abstract; the current practice 
>> is also the same (see eg. http://tools.ietf.org/html/rfc6265, end of 
>> Section 1).  Let's mention it is only put in the Introduction.
>>
>> The proposed statement says almost nothing about how the RFC may be 
>> moved to Historic status without the necessity to publish a separate 
>> RFC for this purpose.  Here I agree with John Klensin.  Let's adopt 
>> something like proposed in 
>> http://tools.ietf.org/id/draft-ietf-newtrk-cruft-00.txt, but more 
>> lightweight.  What I mean is that the procedure should be:
>>
>> (1) an individual or a group of individuals apply to the appropriate 
>> AD for moving some specification to Historic;
>>
>> (2) AD asks Secretariat to issue a 2-to-4-week Last Call on 
>> reclassification;
>>
>> (3) once community consensus is determined, AD brings the question to 
>> IESG's attention via putting it on agenda as "Management Issue";
>
> From the pedantic deparment:
>
> As a matter of clarification: it is already possible to move an RFC to 
> Historic without new draft using the datatracker. The RFC is added to 
> datatracker (just like a draft), etc. This is not going to be a 
> management item, it would appear as a proper document on IESG agenda.
This is possible as well and even more preferable.  I surely don't know, 
but I haven't seen any RFCs moved to Historic in this way, but I agree 
this way is good.

So, I'd like to make the following corrections to my proposal:

(1) the reclassification issue should firstly be discussed in the 
appropriate WG (or on the appropriate mailing list);

(2) once a rough consensus is achieved, an individual or a group of 
individuals apply to the appropriate AD for moving some RFC to Historic;

(3) upon ensuring the adequate pre-IESG community involvement, the AD 
adds the RFC in the Datatracker with the Interned Status "Historic" and 
requests the Secretariat to issue a 2-to-4-week Last Call on 
reclassification;

(4) once community consensus is determined, AD brings the question to 
IESG's attention by issuing a ballot and putting the issue on the IESG 
agenda;

(5) as soon as IESG approve the reclassification, the announcement is 
sent to RFC Editor and copied to IETF Announce list containing request 
to change the particular RFC's status to Historic.

Here the new (1) was missing from the old one; other changes incorporate 
Alexey's comment.

All the best,
Mykyta Yevstifeyev
>
> "Management items" are second class citizens during IESG telechats...
>
>> (4) if IESG does not object, the announcement is sent to RFC Editor 
>> and copied to IETF Announce list containing request to change the 
>> particular RFC's status to Historic.
>>
>> Such procedure seems lightweight enough not to create dozens of new 
>> RFCs reclassifying the old ones but have the appropriate community 
>> involvement.
>
>
>


From msk@cloudmark.com  Sat Jun  4 23:39:22 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A83DD11E808C; Sat,  4 Jun 2011 23:39:22 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u4ul9rwng1WW; Sat,  4 Jun 2011 23:39:22 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 45BB011E8072; Sat,  4 Jun 2011 23:39:22 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Sat, 4 Jun 2011 23:39:22 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
Date: Sat, 4 Jun 2011 23:39:21 -0700
Subject: RE: Proposed text for IESG Handling of Historic Status
Thread-Topic: Proposed text for IESG Handling of Historic Status
Thread-Index: Acwi+nfQ1DtD9YEBQQSHI1xi4qeydQAUKcYQ
Message-ID: <F5833273385BB34F99288B3648C4F06F134C9193ED@EXCH-C2.corp.cloudmark.com>
References: <4DE7E1CA.9010309@ieca.com> <4DE88420.2070202@gmail.com> <4DEA9CBC.6080608@isode.com>
In-Reply-To: <4DEA9CBC.6080608@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Jun 2011 06:39:22 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of A=
lexey Melnikov
> Sent: Saturday, June 04, 2011 2:00 PM
> To: Mykyta Yevstifeyev
> Cc: ietf@ietf.org; The IESG
> Subject: Re: Proposed text for IESG Handling of Historic Status
>=20
> > First, for RFCs of what categories is it legitimate to move them to
> > Historic.  Whether Experimental or Informational RFCs could be
> > considered for such action?  As far as I understand RFC 2026, Historic
> > can be assigned to Standards Track documents; however it won't be
> > excessive to clarify this regulation in the IESG statement additionally=
.
>=20
> My understanding is that any RFC can be moved to Historic. But if this
> is not clear from RFC 2026, maybe it is worth clarifying.

If 2026 doesn't limit what types of RFCs can become Historic, then I presum=
e any of them can.  I'm not sure we need to make that explicit.


From alexey.melnikov@isode.com  Sun Jun  5 10:51:46 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F76221F8485; Sun,  5 Jun 2011 10:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.559
X-Spam-Level: 
X-Spam-Status: No, score=-101.559 tagged_above=-999 required=5 tests=[AWL=1.040, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fKqt+EN+GNjr; Sun,  5 Jun 2011 10:51:45 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id B6A3721F8484; Sun,  5 Jun 2011 10:51:45 -0700 (PDT)
Received: from [188.28.247.216] (188.28.247.216.threembb.co.uk [188.28.247.216])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TevCKwA-ucTe@rufus.isode.com>; Sun, 5 Jun 2011 18:51:42 +0100
Message-ID: <4DEBC218.2020707@isode.com>
Date: Sun, 05 Jun 2011 18:51:20 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-06.txt>  (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110505161306.3291.13078.idtracker@ietfa.amsl.com> <4DE42639.5060604@qualcomm.com>
In-Reply-To: <4DE42639.5060604@qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Jun 2011 17:51:46 -0000

Pete Resnick wrote:
 [...]

> Section 2.2
> (a) Specifically, merge Draft Standard into Internet Standard
> (b) Combine criteria from Draft Standard and Standard
>     (i) Significant number of implementations with successful 
> operational experience
>     (ii) No unresolved errata causing interoperational problems
>     (iii) No unused features, except allow unused features that do not 
> greatly increase implementation complexity
>     (iv) Independent patent/licensing for implementations
> (c) Remove overt requirement for documentation of interoperability 
> testing

 [...]

> 2.2(b)(i) - This is the current requirement for Internet Standard. I'm 
> fine with that remaining, but object to the removal of any notion of 
> interoperability. If this were changed to "A significant number of 
> interoperable implementations...", I would have no objection.

+1.

> 2.2(b)(iii) - I would prefer that this be amended to "All unused 
> 'MUST' requirements will be changed to 'SHOULD' requirements." If 
> deployment is interoperable and a feature is unused, it means that the 
> feature was not actually REQUIRED for interoperability. I object to 
> this as it stands.

-1.
If for a protocol X nobody implemented MUST implement security 
mechanism, I don't think I would like it to be downgraded to a SHOULD. 
At least not without a good explanation.


From krishnabirth@gmail.com  Sun Jun  5 12:40:46 2011
Return-Path: <krishnabirth@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FA1921F8447 for <ietf@ietfa.amsl.com>; Sun,  5 Jun 2011 12:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level: 
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vAGOtuLwhOD2 for <ietf@ietfa.amsl.com>; Sun,  5 Jun 2011 12:40:45 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id D1B0D21F8445 for <ietf@ietf.org>; Sun,  5 Jun 2011 12:40:45 -0700 (PDT)
Received: by yxm34 with SMTP id 34so202236yxm.31 for <ietf@ietf.org>; Sun, 05 Jun 2011 12:40:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=k2Mr1ABk3z/sPCuIuf1Bom/X4gf3pbWuf/Ipo3IFuoo=; b=xq36HifyN/lDHqQ2v0Ot7ERiNgCRmlYlHlSi9vCFwSWjHU6Lfn2A372j5QJr8WPqKZ K4QPqKZJBwtt8Qo3hH7+yH8jllfDGlWta7Iczn2l2UWgWLi31KM2BM28/pXiTQkM/8TC +tSxHZNL+vIi7l1jp2/eXJUv8DlvqWzH5Ysek=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=IMWjL8YlUZTmrlnP3+xIPFY39y+5jKg28bcRbMui3umczUJjEVN6pzvRjD4BmQuTDV yp50AVlGWCFhY04vVGWlbe3+IHUdfkGA34DDpJ+wqP5wS0NuT3Hp4gLfuLt403cIkNlH e73UCLOdf0VU8yU/vvxePRS0mQx2t/UYqO8oA=
MIME-Version: 1.0
Received: by 10.236.28.167 with SMTP id g27mr4783909yha.145.1307302845255; Sun, 05 Jun 2011 12:40:45 -0700 (PDT)
Received: by 10.236.125.234 with HTTP; Sun, 5 Jun 2011 12:40:45 -0700 (PDT)
Date: Sun, 5 Jun 2011 19:40:45 +0000
Message-ID: <BANLkTi=JkcP3+3w3cbKvbJ3UNLHOJ=mTSA@mail.gmail.com>
Subject: Could you build a linux distro?
From: Krishna Birth <krishnabirth@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=00151773e410b48f1b04a4fc2901
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 19:40:46 -0000

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

I want a linux distro. Could you tweek an existing distro e.g. Ubunto or
Fedora?

Please tell me if I wanted a logo installed, put fonts, remove other fonts
at console/terminal, verbose, gui, apps and perhaps put a keyboard app,
startup browser with specific website, what would you charge for live or
install distro and also for regular maintenance?


Best,


Meeku

--00151773e410b48f1b04a4fc2901
Content-Type: text/html; charset=ISO-8859-1

I want a linux distro.  Could you tweek an existing distro e.g. Ubunto or Fedora?<br>
<br>
Please tell me if I wanted a logo installed, put fonts, remove other
fonts at console/terminal, verbose, gui, apps and perhaps put a
keyboard app, startup browser with specific website, what would you
charge for live or install distro and also for regular maintenance?<br>
<br>
<br>
Best,<br>
<br>
<br>
Meeku

--00151773e410b48f1b04a4fc2901--

From krishnabirth@gmail.com  Sun Jun  5 15:43:02 2011
Return-Path: <krishnabirth@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D965228011 for <ietf@ietfa.amsl.com>; Sun,  5 Jun 2011 15:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[AWL=-0.088, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_OBFU_ONLINE=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tU0kJSVXBulT for <ietf@ietfa.amsl.com>; Sun,  5 Jun 2011 15:43:01 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 34576228010 for <ietf@ietf.org>; Sun,  5 Jun 2011 15:43:01 -0700 (PDT)
Received: by ywp31 with SMTP id 31so1769555ywp.31 for <ietf@ietf.org>; Sun, 05 Jun 2011 15:43:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=uIAnRT8kDbqPys1DWavblOwKU8YuTLTSjKCMKZgwz7w=; b=L3dOZr/iFN0oYme1Y4PnWg9euOQlkCLiYmdhV53S75SrN9xojPdBg4MQDxYQ8fH8o2 VJlSHKkrIagLARncS37opAFf9Vty1UAtREMrLKBa831WdH5Y4N4SH5k7zHkWVZ12gDrd EFJVZx77dPuqouaP0d95VUw+azxxcDKUZz01k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=QjT3B15AvvacZCLLSSwCl4EBUn4sexwdW8EB1d3LOj461/apvzmhu4p0GsUekRZ8Dr r3E2DIXlM3Bz2CXS4YeniUlfKdvzfc/4784/TS2z0w+uqHWmqOd5aF3ahwTDs+egwPTj hlqyHptSzoEmVCzDqBQldOeahR0SelAEJ52Ao=
MIME-Version: 1.0
Received: by 10.236.32.2 with SMTP id n2mr5445456yha.279.1307313779802; Sun, 05 Jun 2011 15:42:59 -0700 (PDT)
Received: by 10.236.125.234 with HTTP; Sun, 5 Jun 2011 15:42:59 -0700 (PDT)
In-Reply-To: <BANLkTi=JkcP3+3w3cbKvbJ3UNLHOJ=mTSA@mail.gmail.com>
References: <BANLkTi=JkcP3+3w3cbKvbJ3UNLHOJ=mTSA@mail.gmail.com>
Date: Sun, 5 Jun 2011 22:42:59 +0000
Message-ID: <BANLkTik8USXS13xksZxeh1Tb9HSn+DjBuw@mail.gmail.com>
Subject: Re: Could you build a linux distro?
From: Krishna Birth <krishnabirth@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=windows-1252
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: Sun, 05 Jun 2011 22:43:02 -0000

On Sun, Jun 5, 2011 at 7:40 PM, Krishna Birth <krishnabirth@gmail.com> wrot=
e:
> I want a linux distro. Could you tweek an existing distro e.g. Ubunto or
> Fedora?
>
> Please tell me if I wanted a logo installed, put fonts, remove other font=
s
> at console/terminal, verbose, gui, apps and perhaps put a keyboard app,
> startup browser with specific website, what would you charge for live or
> install distro and also for regular maintenance?
>
>
> Best,
>
>
> Meeku


Press Release

=93onlliinnee=94 is meant to be an opensource foss operating system.  It
is meant to be free os and a linux based distro.  What is meant to be
different and planned about onlliinnee is:  only unique fonts,
software, development, a specific website home page on the browser,
startup screen connects to video website/s,  related with model
railroad / railway, diecasting and =91automation over internet protocol=92
(AOIP) especially Rail Model AOIP (RMAOIP)  and is for Srila
Prabhupada: the always on eternal spiritual initiating and education
guru. Regarding any questions about this, send message to:
identi.ca/onlliinnee (after joining identi.ca)

www.onlliinnee.net

copyright 2011 onlliinnee.  all rights reserved worldwide.

From yoshifumi.nishida@gmail.com  Mon Jun  6 01:39:05 2011
Return-Path: <yoshifumi.nishida@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C52711E80BC; Mon,  6 Jun 2011 01:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C6+aNkRH6Ibb; Mon,  6 Jun 2011 01:39:05 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id D1DE911E808F; Mon,  6 Jun 2011 01:39:04 -0700 (PDT)
Received: by iyn15 with SMTP id 15so4400843iyn.31 for <multiple recipients>; Mon, 06 Jun 2011 01:39:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=yg30WmXAtc9+spwokUbuzGDPjz6Om1LJ7fxt1P+eD1s=; b=T1qlq/9ppw9xgI1BoBHhEEPDX9hISJysSOPqfIulc/lbyJ5fEZJHB5iASW+FlbWpoQ QgOtGqgCee3QbrIi7c03wpSTrb8B9Ui4BrkHGXK/uhe6fUsnK+VE93PqS82pnIUcFviL n2kl4Un5owH3puXvD1ZWLsdE02eMB03tsojiU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=D1Ik3373YJTkpLlv1ZMEmHU+5quqCo0A3CwcvbOubvhj3/vFip3R6wDyVlj55ofp0j Bxsy7IuDuPLMMTErKMilEliVomG4Q1meHBMKIuif6RJjx+CH2rHBeWnsknRnthmrJZ7+ tdYfqnT+k2PC/r4jI7lY4nbB2gBgzP+1ctuXM=
MIME-Version: 1.0
Received: by 10.231.41.69 with SMTP id n5mr8061345ibe.83.1307349544026; Mon, 06 Jun 2011 01:39:04 -0700 (PDT)
Sender: yoshifumi.nishida@gmail.com
Received: by 10.231.251.198 with HTTP; Mon, 6 Jun 2011 01:39:03 -0700 (PDT)
Date: Mon, 6 Jun 2011 01:39:03 -0700
X-Google-Sender-Auth: EtyFQS4kk1w-pxOTWAVGNLSOG6o
Message-ID: <BANLkTikc0e=j2_t91gu8=EOQB1VkRTDOSw@mail.gmail.com>
Subject: TSVDIR Review for draft-ohba-pana-relay-03
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Transport Directorate <tsv-dir@ietf.org>, draft-ohba-pana-relay@tools.ietf.org, 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, 06 Jun 2011 08:39:05 -0000

Hello,
I've reviewed this document as part of the transport area
directorate's ongoing effort to review key IETF documents. These
comments were written primarily for the transport area directors, but
are copied to the document's authors for their information and to
allow them to address any issues raised. The authors should consider
this review together with any other last-call comments they
receive. Please always CC tsv-dir@ietf.org if you reply to or forward
this review.

Summary:

This draft specifies protocol for PANA Relay Element that can relay
messages between a PaC and a PAA where they cannot reach each other.
The proposed function is simple and straightforward and useful.
I couldn't find any transport related issues in the draft.


Minor comments:

Please consider clarifying the following points.

1)  I think clarifying communication model of this proposal will be
helpful for readers.
     It seems to me that a PRE should communicate only one PAA. But, can a PAA
     communicate multiple PREs?

2)  The draft seems to presume PRE to be a multi-homed node. But, is
this mandatory
      requirement? Is it possible to use single-homed node as a PRE?

3)  Is it possible to place a PRE behind NAT? Is there any concern for this?

4)  How p2 (PRE-assigned UDP port number) is determined? Is it possible to use
     ephemeral port? If so, the protocol will need to be robust
against PRE rebooting.
     Similarly, can we use dhcp-ed address for IP2b?

Regards,
--
Yoshifumi Nishida
nishida@sfc.wide.ad.jp

From dlb@interlinux.org.uk  Mon Jun  6 02:41:37 2011
Return-Path: <dlb@interlinux.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 8605411E80E8 for <ietf@ietfa.amsl.com>; Mon,  6 Jun 2011 02:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.108
X-Spam-Level: *
X-Spam-Status: No, score=1.108 tagged_above=-999 required=5 tests=[AWL=1.665,  BAYES_05=-1.11, HELO_MISMATCH_COM=0.553]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LGEqv96POL-u for <ietf@ietfa.amsl.com>; Mon,  6 Jun 2011 02:41:37 -0700 (PDT)
Received: from mail.blacknight.com (pemlinmail01.blacknight.ie [81.17.254.10]) by ietfa.amsl.com (Postfix) with ESMTP id E0BF811E808C for <ietf@ietf.org>; Mon,  6 Jun 2011 02:41:36 -0700 (PDT)
Received: (qmail 23831 invoked from network); 6 Jun 2011 09:41:33 -0000
Received: from unknown (HELO ?192.168.1.101?) ([92.27.49.44]) by 81.17.254.9 with SMTP; 6 Jun 2011 09:41:33 -0000
Subject: Individual submission rationale - draft-brasher-ltasp-05
From: Damian L Brasher <dlb@interlinux.org.uk>
To: ietf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Organization: Interlinux Engineering Foundation
Date: Mon, 06 Jun 2011 10:41:32 +0100
Message-ID: <1307353292.10910.1.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) 
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dlb@interlinux.org.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2011 09:42:41 -0000

Hello

This draft has been written to provide a reference. The open source
production implementation itself is strong in delivery and in principle.
A significant portion of this draft covers areas not normally covered by
IETF. 

Perhaps there is a small chance another vendor may want to write an
implementation or implement some components or interface. But, even in
this event, I believe an individual submission will suffice.

If a WG is interested and would like to contribute I'll re-consider.
Also, this is my first contribution.

Abstract

   Long-term archiving storage fundamentally begins with archive data
   Accumulation, then Geo-duplication and then Management.  Using
   A->G->M, LTASP has been created to solve mid-range and below, long-
   term archiving requirements of the small-medium enterprise.  Where
   tape has been deployed in the past, LTASP now offers an alternative
   solution designed to be more robust and manageable in the long term
   than network attached storage devices or simple disk storage alone.

http://tools.ietf.org/html/draft-brasher-ltasp-05

http://uk.linkedin.com/in/dbrasher

http://interlinux.org.uk

Best Regards

Damian L Brasher




From iljitsch@muada.com  Mon Jun  6 02:44:11 2011
Return-Path: <iljitsch@muada.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2B9311E80E8; Mon,  6 Jun 2011 02:44:11 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XwveGvSTRq3C; Mon,  6 Jun 2011 02:44:11 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id DDF0711E808C; Mon,  6 Jun 2011 02:44:10 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p569iv1P000634 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 Jun 2011 11:44:58 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: tsv-dir review of draft-ietf-behave-ftp64-10
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <4DE95D31.2030400@gont.com.ar>
Date: Mon, 6 Jun 2011 11:44:03 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <28164FBC-556D-45BF-B924-A0645621B423@muada.com>
References: <4DE95D31.2030400@gont.com.ar>
To: Fernando Gont <fernando@gont.com.ar>
X-Mailer: Apple Mail (2.1084)
Cc: draft-ietf-behave-ftp64@tools.ietf.org, tsv-area@ietf.org, "'ietf@ietf.org'" <ietf@ietf.org>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2011 09:44:11 -0000

Thanks everyone for the comments. I'll look into the other technical =
comments later this week, but there's one I can respond to right now:


On 4 jun 2011, at 0:16, Fernando Gont wrote:

> * Section 1, page 3:
>   In 5 cases, issuing the EPSV
>   command to the server led to a significant delay, in 3 cases =
followed
>   by a control channel reset.

> Could you please clarify what was the cause of the delay?

These tests were towards FTP servers found around the internet, so we =
were unable to determine what exactly those servers were doing, other =
than what we observed remotely.

We speculate that this is the result of a firewall placed in front of =
the FTP server that monitors the control channel and opens ports based =
on the PASV or PORT commands, but the firewall doesn't support EPSV so =
no port is opened and the data channel can never be established.

I can put this discussion in the draft. (I seem to remember it was in an =
earlier version.)=

From yoshihiro.ohba@toshiba.co.jp  Mon Jun  6 05:59:31 2011
Return-Path: <yoshihiro.ohba@toshiba.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 54FCE11E8142; Mon,  6 Jun 2011 05:59:31 -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.400,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hOi2eCGAk5n5; Mon,  6 Jun 2011 05:59:30 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id F06B711E8143; Mon,  6 Jun 2011 05:59:25 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id p56CxNpV004913; Mon, 6 Jun 2011 21:59:23 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id p56CxNuD021414; Mon, 6 Jun 2011 21:59:23 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id XAA21413; Mon, 6 Jun 2011 21:59:23 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id p56CxM0H004235; Mon, 6 Jun 2011 21:59:22 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id p56CxMKV017637; Mon, 6 Jun 2011 21:59:22 +0900 (JST)
Received: from [133.199.75.87] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0LMD006XUDEUE690@mail.po.toshiba.co.jp>; Mon, 06 Jun 2011 21:59:22 +0900 (JST)
Date: Mon, 06 Jun 2011 21:59:16 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
Subject: Re: TSVDIR Review for draft-ohba-pana-relay-03
In-reply-to: <BANLkTikc0e=j2_t91gu8=EOQB1VkRTDOSw@mail.gmail.com>
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Message-id: <4DECCF24.4010902@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-2022-JP
Content-transfer-encoding: 7bit
References: <BANLkTikc0e=j2_t91gu8=EOQB1VkRTDOSw@mail.gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
Cc: draft-ohba-pana-relay@tools.ietf.org, ietf@ietf.org, Transport Directorate <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2011 12:59:31 -0000

Nishida-san,

Thank you very much for reviewing the draft.

Please see my comments below.

(2011/06/06 17:39), Yoshifumi Nishida wrote:
> Hello,
> I've reviewed this document as part of the transport area
> directorate's ongoing effort to review key IETF documents. These
> comments were written primarily for the transport area directors, but
> are copied to the document's authors for their information and to
> allow them to address any issues raised. The authors should consider
> this review together with any other last-call comments they
> receive. Please always CC tsv-dir@ietf.org if you reply to or forward
> this review.
> 
> Summary:
> 
> This draft specifies protocol for PANA Relay Element that can relay
> messages between a PaC and a PAA where they cannot reach each other.
> The proposed function is simple and straightforward and useful.
> I couldn't find any transport related issues in the draft.
> 
> 
> Minor comments:
> 
> Please consider clarifying the following points.
> 
> 1)  I think clarifying communication model of this proposal will be
> helpful for readers.
>       It seems to me that a PRE should communicate only one PAA. But, can a PAA
>       communicate multiple PREs?

PANA allows multiple PAAs in an access network.  For example, RFC 5192
defines a DHCP option to carry a list of PAA addresses and a PaC will
choose one PAA to communicate with.  Similarly, there can be multiple
PAAs in an access network with PREs.  In this case, a PRE will choose
one PAA to communicate with for a given PaC.  Next, a PAA can
communicate with multiple PREs.  We can clarify these in the draft.

> 
> 2)  The draft seems to presume PRE to be a multi-homed node. But, is
> this mandatory
>        requirement? Is it possible to use single-homed node as a PRE?

You are right, PRE can be either single-homed or multi-homed.  In
fact, in ZigBee IP, each mesh router is a PRE having a single 802.15.4
radio interface.  We can clarify this in the draft as well.

> 
> 3)  Is it possible to place a PRE behind NAT? Is there any concern for this?
> 

There are two cases, (i) a NAT between a PaC and a PRE, and (ii) a
NAT between a PRE and a PAA.  I don't see a NAT issue specific to PANA
relay for both cases.

> 4)  How p2 (PRE-assigned UDP port number) is determined? Is it possible to use
>       ephemeral port? If so, the protocol will need to be robust
> against PRE rebooting.
>       Similarly, can we use dhcp-ed address for IP2b?

Yes, p2 can be ephemeral.  Since a PAA just uses the UDP and IP
headers received from the relay to generate UDP and IP headers of its
response PRY to the relay, I think the protocol is robust against PRE
rebooting.  For the same reason, use of DHCP-ed address for IP2b
works.  Even when IPsec is used between a PRE and a PAA, I think
DHCP-ed address for IP2b works as long as IKEv2 identity for the PRE
is not based on IP address.

Kind Regards,
Yoshihiro Ohba

> 
> Regards,
> --
> Yoshifumi Nishida
> nishida@sfc.wide.ad.jp
> 


From ben@nostrum.com  Fri Jun  3 13:09:54 2011
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 B147AE06BF; Fri,  3 Jun 2011 13:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.45
X-Spam-Level: 
X-Spam-Status: No, score=-101.45 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.3, SPF_PASS=-0.001,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v0QaP27myuny; Fri,  3 Jun 2011 13:09:53 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id D1E6DE07B3; Fri,  3 Jun 2011 13:09:52 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p53K9mLf021853 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 3 Jun 2011 15:09:50 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
Date: Fri, 3 Jun 2011 15:09:47 -0500
Message-Id: <5E434E92-2EB7-43B3-A29F-8410B1AC23AE@nostrum.com>
To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Mon, 06 Jun 2011 09:59:06 -0700
Cc: The 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 Jun 2011 20:09:54 -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-dime-ikev2-psk-diameter-07
Reviewer: Ben Campbell
Review Date: 2011-06-03
IETF LC End Date: 2011-06-03


Summary:

This draft is almost ready for publication as a proposed standard. I =
have a question concerning the procedure for generating PSKs, and a =
number of minor and editorial comments.


Major issues:

The draft says that the procedure that the HAAA follows to generate the =
PSK is out of scope. But doesn't the IKE2 initiator need to understand =
the procedure? If the procedure is not defined somewhere, how you =
achieve any degree of interoperability?


Minor issues:

-- section 4.1, 1st paragraph:"The IDi payload extracted from the =
IKE_AUTH message MUST contain an identity that is meaningful for the =
Diameter infrastructure, such as a Network Access Identifier (NAI), =
since it is used by the IKEv2 Server to populate the User-Name AVP in =
the Diameter message. "

Do you mean that as a normative MUST, or a statement of fact? If =
normative, isn't that a requirement on the initiator?

-- section 10:

The security considerations should describe the threat models. We're =
talking about requesting an authentication key from a third party, which =
is tricky from a security perspective. Does the PSK have greater =
security concerns than for Diameter AVPs in general? In particular, what =
are the consequences if the PSK is disclosed or tampered with?=20

-- section 10, 1st paragraph: "Furthermore, any agents that process =
IKEv2-PSK-Answer messages can see the contents of the Key AVP. For this =
reason, this specification strongly recommends avoiding Diameter agents =
when they cannot be trusted to keep the keys secret."

Should that be normative? Is there no way to protect the PSK AVP from =
diameter agents? E.g. can it be encrypted?

-- section 10, 2nd paragraph: "this specification also recommends the =
use of nonces included in IKEv2-PSK-Request."

Actually, the spec requires it using a normative SHALL.


Nits/editorial comments:

-- IDNits reports an out-of-date reference

-- Section 1, general:

It's probably worth elaborating that we are talking about a PSK used =
during the IKEv2 authentication process, which is distinct from any =
shared secrets negotiated by IKE for use in the resulting SA.

-- Section 1, paragraph 1, 1st sentence:

The use, and lack of, commas in this sentence is confusing. It's easy to =
parse as saying IKE2 is a protocol and a set of algorithms, when I think =
you meant to say that the resulting SA has a set of algorithms along =
with the shared secret.

-- section 4.1, 2nd paragraph: "message is routed to the IKEv2 Peer=92s =
HAAA."

What routes it? ( be careful not to let passive voice obscure =
responsibilities)

-- section 4.2, paragraph 1: "The HAAA may maintain state or may be =
stateless"

What kind of state? I assume from the following sentences you mean =
Diameter session state, but it should be explicit.

-- "indicated by presence or absence of the Auth-Session-State AVP."

In what message(s)?

-- section 4.2, paragraph 2:

This sentence is long and hard to parse. Can it be broken up?

-- section 5.1, last paragraph: "SHALL be used to identify the =
appropriate PSK."

Shall be used by what? (passive voice obscures responsibility)

-- 5.2, last paragraph: "associated key SHALL NOT be used if the =
lifetime has expired."

SHALL NOT be used by what?

-- section 8, first paragraph: "whether the AVP MAY be encrypted."

I don't see anything about encryption in the table.

-- section 8, AVP table:

Are all the Key* AVPs intended to have the same code? I assume not, but =
mixing in TBD with the various TBD* placeholders is confusing.

-- section 9:

Consider a note to the RFC editor to change all occurances of TBD(x) =
with the IANA assignment throughout the entire document. Since these are =
scattered throughout the doc, the intent may not be obvious to them.



From moore@network-heretics.com  Mon Jun  6 10:22:32 2011
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 8456F11E819F; Mon,  6 Jun 2011 10:22:32 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fzvtSnDlIN+j; Mon,  6 Jun 2011 10:22:31 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 2A18B11E8194; Mon,  6 Jun 2011 10:22:31 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 698E420C50; Mon,  6 Jun 2011 13:22:30 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute6.internal (MEProxy); Mon, 06 Jun 2011 13:22:30 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=ZFmALFB4p9jXUV17JlbFTbzclrc=; b=jsm9+KWO8zTnAOemjqWwiBAJjY7aEc6kujqGf4WjMul1ySfTBH9maVXHh9t98hfnKafexm7Wp+W7WN5AldwaA2vtKiUZMyd2AjLKTu2K0nTIt0YAN8r1CGO6v1Vw4WypJtoYvgmB8uVB8Nw2AL4RvbO3cAXKapCbZrp1QsISLiE=
X-Sasl-enc: qHLxH8LQL2luuSbwtLtjkKc57dcZ+ieQttjccTSICfag 1307380948
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 5F440441792; Mon,  6 Jun 2011 13:22:28 -0400 (EDT)
Subject: Re: Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-2-508749156
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110606162326.26262.53944.idtracker@ietfa.amsl.com>
Date: Mon, 6 Jun 2011 13:22:27 -0400
Message-Id: <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
Cc: v6ops@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2011 17:22:32 -0000

--Apple-Mail-2-508749156
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I strongly object to the proposed reclassification of these documents as =
Historic. =20

6to4 still has many valid use cases, and there is not a suitable =
replacement for it that has been deployed.  Until there is a suitable =
replacement, or until there is widespread ISP support for native IPv6, =
reclassification of this document to Historic is premature.  (6rd is not =
a suitable replacement for 6to4, as it is intended for very different =
use cases than 6to4.)

(It could be argued that reclassification of RFC 3068 (by itself) to =
Historic is appropriate, but that would require a separate document and =
last call.)

In addition, this document is misleading and perhaps even vituperative.  =
  For instance:

"There would appear to be no evidence of any substantial deployment of =
the variant of 6to4 described in [RFC3056]."

This statement is blatantly false. 6to4 is supported by every major =
desktop and server platfrom that is shipping today, and has been =
supported for several years.

"The IETF sees no evolutionary future for the mechanism and it is not =
recommended to include this mechanism in new implementations."

6to4 never was intended to have an "evolutionary future".  It was always =
intended as a near-term solution to allow consenting hosts and networks =
to interchange IPv6 traffic without prior support from the IPv4 networks =
that carry the traffic.   It is premature to recommend that 6to4 be =
removed from implementations.  We do not know how long it will take ISPs =
to universally deploy IPv6.  Until they do, there will be a need for =
individuals and enterprises using IPv6-based applications to be able to =
exchange IPv6 traffic with hosts that only have IPv4 connectivity. =20

All of the criticisms in section 3 have to do with the use of relays to =
exchange traffic between 6to4 and native IPv6.   In many cases the =
criticisms are overbroad.   Not all uses of 6to4 involve relays.  For =
some of those that do need to use relays, it is not necessarily the case =
that the relay is operated by an unknown third-party. =20

The fact that some firewalls block protocol 41 traffic causes problems =
for many tunneling solutions, not just 6to4; yet this document appears =
to recommend some tunneling solutions while trashing 6to4.

The recommendations to treat 6to4 as a service of last resort will do =
harm to users and applications using it.   A better recommendation is =
for hosts to disable 6to4 by default. =20

This document appears to make the mistake of assuming that the purpose =
of applications using IPv6 is to interoperate with the existing =
Internet.  I have maintained for many years that it is new applications, =
or existing applications that can't tolerate widespread deployment of =
IPv4 NAT, that will drive use of IPv6.   I therefore believe that it is =
inappropriate to judge 6to4 merely by how well it works in scenarios =
where it is being used to talk to applications that work well over IPv4 =
NAT such as HTTP.   The Internet is much more diverse than that, and =
will become even more diverse as IPv6 enjoys wider deployment.

It is also premature to remove references to 6to4 from RFC 5156bis, for =
IANA to mark the prefix and DNS zones as deprecated.  This will only =
cause confusion and difficulty for legitimate continued uses of 6to4.

Keith


On Jun 6, 2011, at 12:23 PM, The IESG wrote:

>=20
> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) =
to
>   Historic status'
>  <draft-ietf-v6ops-6to4-to-historic-04.txt> as an Informational RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-06-20. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   Experience with the "Connection of IPv6 Domains via IPv4 Clouds
>   (6to4)" IPv6 transitioning mechanism has shown that the mechanism is
>   unsuitable for widespread deployment and use in the Internet.  This
>   document requests that RFC3056 and the companion document "An =
Anycast
>   Prefix for 6to4 Relay Routers" RFC3068 are moved to historic status.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


--Apple-Mail-2-508749156
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I =
strongly object to the proposed reclassification of these documents as =
Historic. &nbsp;<div><br></div><div>6to4 still has many valid use cases, =
and there is not a suitable replacement for it that has been deployed. =
&nbsp;Until there is a suitable replacement, or until there is =
widespread ISP support for native IPv6, reclassification of this =
document to Historic is premature. &nbsp;(6rd is not a suitable =
replacement for 6to4, as it is intended for very different use cases =
than 6to4.)<div><div><br></div><div>(It could be argued that =
reclassification of RFC 3068 (by itself) to Historic is appropriate, but =
that would require a separate document and last =
call.)<div><br></div><div>In addition, this document is misleading and =
perhaps even vituperative. &nbsp; &nbsp;For =
instance:</div><div><br></div><div><meta charset=3D"utf-8"><span =
class=3D"Apple-style-span" style=3D"line-height: 16px; =
-webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: =
2px; "><pre style=3D"line-height: 1.2em; margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><font =
class=3D"Apple-style-span" face=3D"Helvetica" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"font-size: 12px;">"There would =
appear to be no evidence of any substantial deployment of the variant of =
6to4 described in [RFC3056]."</span></font></pre><pre =
style=3D"line-height: 1.2em; margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font class=3D"Apple-style-span" =
face=3D"Helvetica" size=3D"3"><span class=3D"Apple-style-span" =
style=3D"font-size: 12px;"><br></span></font></pre><pre =
style=3D"line-height: 1.2em; margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font class=3D"Apple-style-span" =
face=3D"Helvetica" size=3D"3"><span class=3D"Apple-style-span" =
style=3D"font-size: 12px;">This statement is blatantly false. 6to4 is =
supported by every major desktop and server platfrom that is shipping =
today, and has been supported for several =
years.</span></font></pre></span><div><br></div></div><div><meta =
charset=3D"utf-8"><span class=3D"Apple-style-span" style=3D"line-height: =
16px; -webkit-border-horizontal-spacing: 2px; =
-webkit-border-vertical-spacing: 2px; "><pre style=3D"line-height: =
1.2em; margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font class=3D"Apple-style-span" face=3D"Helvetica" =
size=3D"3"><span class=3D"Apple-style-span" style=3D"font-size: =
12px;">"The IETF sees no evolutionary future for the mechanism and it is =
not recommended to include this mechanism in new =
implementations."</span></font></pre></span><div><br></div></div><div>6to4=
 never was intended to have an "evolutionary future". &nbsp;It was =
always intended as a near-term solution to allow consenting hosts and =
networks to interchange IPv6 traffic without prior support from the IPv4 =
networks that carry the traffic. &nbsp; It is premature to recommend =
that 6to4 be removed from implementations. &nbsp;We do not know how long =
it will take ISPs to universally deploy IPv6. &nbsp;Until they do, there =
will be a need for individuals and enterprises using IPv6-based =
applications to be able to exchange IPv6 traffic with hosts that only =
have IPv4 connectivity. &nbsp;</div><div><br></div><div>All of the =
criticisms in section 3 have to do with the use of relays to exchange =
traffic between 6to4 and native IPv6. &nbsp; In many cases the =
criticisms are overbroad. &nbsp; Not all uses of 6to4 involve relays. =
&nbsp;For some of those that do need to use relays, it is not =
necessarily the case that the relay is operated by an unknown =
third-party. &nbsp;</div><div><br></div><div>The fact that some =
firewalls block protocol 41 traffic causes problems for many tunneling =
solutions, not just 6to4; yet this document appears to recommend some =
tunneling solutions while trashing 6to4.</div><div><br></div><div>The =
recommendations to treat 6to4 as a service of last resort will do harm =
to users and applications using it. &nbsp; A better recommendation is =
for hosts to disable 6to4 by default. =
&nbsp;</div><div><br></div><div>This document appears to make the =
mistake of assuming that the purpose of applications using IPv6 is to =
interoperate with the existing Internet. &nbsp;I have maintained for =
many years that it is new applications, or existing applications that =
can't tolerate widespread deployment of IPv4 NAT, that will drive use of =
IPv6. &nbsp; I therefore believe that it is inappropriate to judge 6to4 =
merely by how well it works in scenarios where it is being used to talk =
to applications that work well over IPv4 NAT such as HTTP. &nbsp; The =
Internet is much more diverse than that, and will become even more =
diverse as IPv6 enjoys wider deployment.</div><div><br></div><div>It is =
also premature to remove references to 6to4 from RFC 5156bis, for IANA =
to mark the prefix and DNS zones as deprecated. &nbsp;This will only =
cause confusion and difficulty for legitimate continued uses of =
6to4.</div><div><br></div><div>Keith</div><div><br></div><div><div><br><di=
v><div>On Jun 6, 2011, at 12:23 PM, The IESG wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><br>The=
 IESG has received a request from the IPv6 Operations WG (v6ops) =
to<br>consider the following document:<br>- 'Request to move Connection =
of IPv6 Domains via IPv4 Clouds (6to4) to<br> &nbsp;&nbsp;Historic =
status'<br> &nbsp;&lt;draft-ietf-v6ops-6to4-to-historic-04.txt&gt; as an =
Informational RFC<br><br>The IESG plans to make a decision in the next =
few weeks, and solicits<br>final comments on this action. Please send =
substantive comments to the<br><a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by =
2011-06-20. Exceptionally, comments may be<br>sent to <a =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, =
please retain the<br>beginning of the Subject line to allow automated =
sorting.<br><br>Abstract<br><br><br> &nbsp;&nbsp;Experience with the =
"Connection of IPv6 Domains via IPv4 Clouds<br> &nbsp;&nbsp;(6to4)" IPv6 =
transitioning mechanism has shown that the mechanism is<br> =
&nbsp;&nbsp;unsuitable for widespread deployment and use in the =
Internet. &nbsp;This<br> &nbsp;&nbsp;document requests that RFC3056 and =
the companion document "An Anycast<br> &nbsp;&nbsp;Prefix for 6to4 Relay =
Routers" RFC3068 are moved to historic status.<br><br><br><br><br>The =
file can be obtained via<br><a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/=
">http://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/</a><b=
r><br>IESG discussion can be tracked =
via<br>http://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/<=
br><br><br>No IPR declarations have been submitted directly on this =
I-D.<br><br><br>_______________________________________________<br>IETF-An=
nounce mailing =
list<br>IETF-Announce@ietf.org<br>https://www.ietf.org/mailman/listinfo/ie=
tf-announce<br></div></blockquote></div><br></div></div></div></div></div>=
</body></html>=

--Apple-Mail-2-508749156--

From mail@sabahattin-gucukoglu.com  Mon Jun  6 10:49:45 2011
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C15F21F843F for <ietf@ietfa.amsl.com>; Mon,  6 Jun 2011 10:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.962
X-Spam-Level: 
X-Spam-Status: No, score=0.962 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HOST_MISMATCH_COM=0.311, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sfwRelzc2zak for <ietf@ietfa.amsl.com>; Mon,  6 Jun 2011 10:49:44 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com (sgucukoglu-2-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:7ef::2]) by ietfa.amsl.com (Postfix) with ESMTP id 492CA11E808E for <ietf@ietf.org>; Mon,  6 Jun 2011 10:49:40 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:42974) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S35998> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Mon, 6 Jun 2011 18:49:39 +0100
Received: from [192.168.1.20] (cpc2-dals7-0-0-cust570.hari.cable.virginmedia.com [82.35.114.59]) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Mon, 06 Jun 2011 18:49:37 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
In-Reply-To: <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>
Date: Mon, 6 Jun 2011 18:49:33 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C071697-0C3F-4B24-A86C-FB6FDB80333B@sabahattin-gucukoglu.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-Delivery-Agent: TMDA/1.1.12-kg3 (Haumea)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1309974579.c0e0cf@sabahattin-gucukoglu.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2011 17:49:45 -0000

Nothing to say here that Keith hasn't already said in so many fine =
words.  In summary:

+-1.  Heck, no, -1000.  I especially dislike the registry changes; those =
are deeply, *deeply* irresponsible.

On 6 Jun 2011, at 18:22, Keith Moore wrote:
> I strongly object to the proposed reclassification of these documents =
as Historic. =20
>=20
> 6to4 still has many valid use cases, and there is not a suitable =
replacement for it that has been deployed.  Until there is a suitable =
replacement, or until there is widespread ISP support for native IPv6, =
reclassification of this document to Historic is premature.  (6rd is not =
a suitable replacement for 6to4, as it is intended for very different =
use cases than 6to4.)
>=20
> (It could be argued that reclassification of RFC 3068 (by itself) to =
Historic is appropriate, but that would require a separate document and =
last call.)
>=20
> In addition, this document is misleading and perhaps even =
vituperative.    For instance:
>=20
> "There would appear to be no evidence of any substantial deployment of =
the variant of 6to4 described in [RFC3056]."
>=20
> This statement is blatantly false. 6to4 is supported by every major =
desktop and server platfrom that is shipping today, and has been =
supported for several years.
>=20
> "The IETF sees no evolutionary future for the mechanism and it is not =
recommended to include this mechanism in new implementations."
>=20
> 6to4 never was intended to have an "evolutionary future".  It was =
always intended as a near-term solution to allow consenting hosts and =
networks to interchange IPv6 traffic without prior support from the IPv4 =
networks that carry the traffic.   It is premature to recommend that =
6to4 be removed from implementations.  We do not know how long it will =
take ISPs to universally deploy IPv6.  Until they do, there will be a =
need for individuals and enterprises using IPv6-based applications to be =
able to exchange IPv6 traffic with hosts that only have IPv4 =
connectivity. =20
>=20
> All of the criticisms in section 3 have to do with the use of relays =
to exchange traffic between 6to4 and native IPv6.   In many cases the =
criticisms are overbroad.   Not all uses of 6to4 involve relays.  For =
some of those that do need to use relays, it is not necessarily the case =
that the relay is operated by an unknown third-party. =20
>=20
> The fact that some firewalls block protocol 41 traffic causes problems =
for many tunneling solutions, not just 6to4; yet this document appears =
to recommend some tunneling solutions while trashing 6to4.
>=20
> The recommendations to treat 6to4 as a service of last resort will do =
harm to users and applications using it.   A better recommendation is =
for hosts to disable 6to4 by default. =20
>=20
> This document appears to make the mistake of assuming that the purpose =
of applications using IPv6 is to interoperate with the existing =
Internet.  I have maintained for many years that it is new applications, =
or existing applications that can't tolerate widespread deployment of =
IPv4 NAT, that will drive use of IPv6.   I therefore believe that it is =
inappropriate to judge 6to4 merely by how well it works in scenarios =
where it is being used to talk to applications that work well over IPv4 =
NAT such as HTTP.   The Internet is much more diverse than that, and =
will become even more diverse as IPv6 enjoys wider deployment.
>=20
> It is also premature to remove references to 6to4 from RFC 5156bis, =
for IANA to mark the prefix and DNS zones as deprecated.  This will only =
cause confusion and difficulty for legitimate continued uses of 6to4.
>=20
> Keith
>=20
>=20
> On Jun 6, 2011, at 12:23 PM, The IESG wrote:
>=20
>>=20
>> The IESG has received a request from the IPv6 Operations WG (v6ops) =
to
>> consider the following document:
>> - 'Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) =
to
>>  Historic status'
>> <draft-ietf-v6ops-6to4-to-historic-04.txt> as an Informational RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf@ietf.org mailing lists by 2011-06-20. Exceptionally, comments =
may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>  Experience with the "Connection of IPv6 Domains via IPv4 Clouds
>>  (6to4)" IPv6 transitioning mechanism has shown that the mechanism is
>>  unsuitable for widespread deployment and use in the Internet.  This
>>  document requests that RFC3056 and the companion document "An =
Anycast
>>  Prefix for 6to4 Relay Routers" RFC3068 are moved to historic status.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.

From bortzmeyer@nic.fr  Mon Jun  6 13:48:02 2011
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 6C1A921F84A1; Mon,  6 Jun 2011 13:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.249
X-Spam-Level: 
X-Spam-Status: No, score=-110.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vK0hAKmF7Z8L; Mon,  6 Jun 2011 13:48:01 -0700 (PDT)
Received: from mx2.nic.fr (mx2.nic.fr [IPv6:2001:660:3003:2::4:11]) by ietfa.amsl.com (Postfix) with ESMTP id B603621F849C; Mon,  6 Jun 2011 13:47:57 -0700 (PDT)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 7CAE21C0020; Mon,  6 Jun 2011 22:47:55 +0200 (CEST)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx2.nic.fr (Postfix) with ESMTP id 776BF1C001B; Mon,  6 Jun 2011 22:47:55 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.6.69]) by relay1.nic.fr (Postfix) with ESMTP id 6BB195680CA; Mon,  6 Jun 2011 22:47:55 +0200 (CEST)
Date: Mon, 6 Jun 2011 22:47:55 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: IETF Secretariat <ietf-secretariat@ietf.org>
Subject: Re: New Non-WG Mailing List: fun -- FUture home Networking (FUN)
Message-ID: <20110606204755.GA32176@nic.fr>
References: <20110606165456.74F4411E8179@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110606165456.74F4411E8179@ietfa.amsl.com>
X-Operating-System: Debian GNU/Linux 6.0.1
X-Kernel: Linux 2.6.32-5-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: Mark Townsley <townsley@cisco.com>, ietf@ietf.org, Ole Troan <ot@cisco.com>, fun@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 20:48:02 -0000

On Mon, Jun 06, 2011 at 09:54:56AM -0700,
 IETF Secretariat <ietf-secretariat@ietf.org> wrote 
 a message of 15 lines which said:

> Purpose: Mailing list for proposed working group on FUture home Networking (FUN)

And nothing more (same thing on the Web site). Could we ask for a
little bit more context when a new IETF list is created?

From cheshire@apple.com  Mon Jun  6 15:12:25 2011
Return-Path: <cheshire@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 969D011E80F9 for <ietf@ietfa.amsl.com>; Mon,  6 Jun 2011 15:12:25 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uets6jUN5izk for <ietf@ietfa.amsl.com>; Mon,  6 Jun 2011 15:12:24 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id B0DB811E8073 for <ietf@ietf.org>; Mon,  6 Jun 2011 15:12:24 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LME005DQ2X3UMC1@mail-out.apple.com> for ietf@ietf.org; Mon, 06 Jun 2011 15:12:00 -0700 (PDT)
X-AuditID: 1180711d-b7c70ae00000719a-6e-4ded50afc9d3
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id 94.12.29082.0B05DED4; Mon, 06 Jun 2011 15:12:00 -0700 (PDT)
Received: from [17.153.48.8] (unknown [17.153.48.8]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LME008TF2ZYMF30@koseret.apple.com> for ietf@ietf.org; Mon, 06 Jun 2011 15:11:59 -0700 (PDT)
From: Stuart Cheshire <cheshire@apple.com>
Subject: Subversion troubles?
Date: Mon, 06 Jun 2011 15:11:58 -0700
Message-id: <53ECDA9E-3B7B-48A3-BE6D-CEFBE86DE11F@apple.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-Brightmail-Tracker: AAAAAA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 22:12:25 -0000

I'm using svn 1.6.15 on Mac OS X 10.6.7.

It used to work fine for me, but recently it stopped working. I now get SSL errors, e.g.:

> % svn ls https://svn.tools.ietf.org/svn/wg/6lowpan
> svn: OPTIONS of 'https://svn.tools.ietf.org/svn/wg/6lowpan': SSL negotiation failed: SSL error code -1/1/336032856 (https://svn.tools.ietf.org)

If I do the insecure version using "http" instead of "https" then it works:

> % svn ls http://svn.tools.ietf.org/svn/wg/6lowpan
> 6lowpan-terminology.xml
> hc/
> nd/
> packets/
> routing-requirements/
> usecases/

Is anyone else seeing this problem?

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


From paul.hoffman@vpnc.org  Mon Jun  6 15:12:38 2011
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 D39E911E81D1; Mon,  6 Jun 2011 15:12:38 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QVfxiTZsQ7UQ; Mon,  6 Jun 2011 15:12: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 AAE1011E81D2; Mon,  6 Jun 2011 15:12:37 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p56MCVq1028807 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 Jun 2011 15:12:31 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com>
Date: Mon, 6 Jun 2011 15:12:32 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2011 22:12:39 -0000

On May 29, 2011, at 4:13 AM, Roni Even wrote:

> Major issues:
>=20
> 1.       I am not sure how the IANA consideration section is in-line =
with the IANA consideration section of RFC5892. Maybe some clarification =
text would be helpful.

We think that the IANA considerations here are, in fact, what RFC 5892 =
was designed for. That is, RFC 5892 says that the registry will be =
updated ("IANA has created a registry with the derived properties for =
the versions of Unicode released after (and including) version 5.2"), =
and this is such an update. Please let me know if that doesn't match =
your understanding.

> 2.       The IANA registry for derived property value has RFC 5892, =
does this draft want to change the reference, how will it be done.

Section 2 of the draft is pretty clear here: "No change to RFC 5892 is =
needed based on the changes made in Unicode 6.0".

>   I think that it relates also to the issue of whether this draft =
updates RFC 5892.

And here too.

--Paul Hoffman


From trejrco@gmail.com  Mon Jun  6 16:42:18 2011
Return-Path: <trejrco@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CDFF1F0C4D; Mon,  6 Jun 2011 16:42:18 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g0UMwWlKgcug; Mon,  6 Jun 2011 16:42:17 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8E3A61F0C46; Mon,  6 Jun 2011 16:42:09 -0700 (PDT)
Received: by yib18 with SMTP id 18so1064791yib.31 for <multiple recipients>; Mon, 06 Jun 2011 16:42:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=06DSOfowt/GAcRYT9//rw1jFOWmeUauVvPwM6w3IXA4=; b=pm/O8HrV7l/xfOjv9aypvrrEyCe1NgY8DF2WRldkn+aHOoK4oMMZUt+0jkie7g95yJ X40o9WvjQwtN88Gif4XgyaUj2FOPpBrCbCJMXYMefsX8fAejp0BNbFAEgHX/72DaTtE+ RnZ+VShi/b3EIcEFV/qiCM2kY7fx3OLx/w38E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; b=L90ruj0Q4f28hJwCNSH+55iTsxt94kHAeOtpUlUTX+DWQY0VrYvYZzslmSrhhgsPKA 2BAeW5PoCGtnIeLqoaYXiM+dkLiN/rH84Pgx7U6jCWpxiwqxmwuht29UmjAFv5mAFJpk 0JkcI83v4iw9p/Ii85qoX1sDP89eNH7CVle84=
Received: by 10.91.198.11 with SMTP id a11mr4827959agq.184.1307403729095; Mon, 06 Jun 2011 16:42:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.91.170.3 with HTTP; Mon, 6 Jun 2011 16:41:49 -0700 (PDT)
In-Reply-To: <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>
From: TJ <trejrco@gmail.com>
Date: Mon, 6 Jun 2011 19:41:49 -0400
Message-ID: <BANLkTikaGbFASQfisP5=H3yXKgDUpdKEqA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: ietf@ietf.org, v6ops@ietf.org, ietf-announce@ietf.org
Content-Type: multipart/alternative; boundary=0016367658a3d9cd5104a513a6e8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2011 23:42:18 -0000

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

On Mon, Jun 6, 2011 at 13:22, Keith Moore <moore@network-heretics.com>wrote:

> I strongly object to the proposed reclassification of these documents as
> Historic.
> *<snipped lots of great thoughts/comments, solely for brevity>*
>


Agreed that this is too harsh, too soon.  Fixing the broken implementations
is a better idea than trying to break the working ones.  And I am not just
saying this because I successfully use 6to4 on a fairly common basis ...


/TJ

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

<br><div class=3D"gmail_quote">On Mon, Jun 6, 2011 at 13:22, Keith Moore <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com">moore@net=
work-heretics.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style=3D"word-wrap:break-word">I strongly object to the proposed recla=
ssification of these documents as Historic. =A0<div><i>&lt;snipped lots of =
great thoughts/comments, solely for brevity&gt;</i></div></div></blockquote=
>

<div><br></div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quo=
te">Agreed that this is too harsh, too soon. =A0Fixing the broken implement=
ations is a better idea than trying to break the working ones. =A0And I am =
not just saying this because I=A0successfully=A0use 6to4 on a fairly common=
 basis ...</div>

<div class=3D"gmail_quote"><br></div><br clear=3D"all">/TJ<br><br><div>=A0<=
/div></div>

--0016367658a3d9cd5104a513a6e8--

From barryleiba.mailing.lists@gmail.com  Mon Jun  6 18:23:04 2011
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 5165311E8074; Mon,  6 Jun 2011 18:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QIhYhGpsJg4o; Mon,  6 Jun 2011 18:23:03 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id ED4F711E8070; Mon,  6 Jun 2011 18:23:02 -0700 (PDT)
Received: by gwb20 with SMTP id 20so2182712gwb.31 for <multiple recipients>; Mon, 06 Jun 2011 18:23:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=O0hFOXA2yw4a+wXa8PvSjimnpMQneRbbvFldfPZEvfA=; b=amOA0RdP0CQ+8cisaR9bbnWp2NvZUJ1LNswfaebDEWm48Mb/i3CRx/r6AYnv9L1Guw JXlcsDzn0ToM28nVCwnCD6eVR70csVrxi0BRp9tAURiIzD3jTnQg46rvyK6V4v+fXMzZ 7ZKVqIgPg7IbhQAx38bp5rJXmtQakAS3aW96E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=kiK/cJakL65+5pyZm+tFgabnOIoh4iYjzoaxSBODq4V/f0cs1riRSnQ04yf5JPWTOK i/HTzrASvSCAZ1otGOlNl4ofDtmT9WbD+xY7UafGE4Eoe6yX8khEocJoCJoygoVUNICX tN4XyeRS7pIFXtBHzO5gH1tF+3vgZfXvAFjYc=
MIME-Version: 1.0
Received: by 10.236.136.1 with SMTP id v1mr6631595yhi.261.1307409781995; Mon, 06 Jun 2011 18:23:01 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.125.15 with HTTP; Mon, 6 Jun 2011 18:23:01 -0700 (PDT)
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134C9193ED@EXCH-C2.corp.cloudmark.com>
References: <4DE7E1CA.9010309@ieca.com> <4DE88420.2070202@gmail.com> <4DEA9CBC.6080608@isode.com> <F5833273385BB34F99288B3648C4F06F134C9193ED@EXCH-C2.corp.cloudmark.com>
Date: Tue, 7 Jun 2011 01:23:01 +0000
X-Google-Sender-Auth: zDp0Y9Ct5wBumo7WAOnCUI5jdy4
Message-ID: <BANLkTimXFMHVPWBX2DGUF0cehPd6hyPqZw@mail.gmail.com>
Subject: Re: Proposed text for IESG Handling of Historic Status
From: Barry Leiba <barryleiba@computer.org>
To: "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@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: Tue, 07 Jun 2011 01:23:04 -0000

>> My understanding is that any RFC can be moved to Historic. But if this
>> is not clear from RFC 2026, maybe it is worth clarifying.
>
> If 2026 doesn't limit what types of RFCs can become Historic, then I pres=
ume
> any of them can. =A0I'm not sure we need to make that explicit.

I'm sure we don't.  There's no need to change anything in this regard.

Barry

From fred@cisco.com  Mon Jun  6 18:49:59 2011
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 C2E6721F8571; Mon,  6 Jun 2011 18:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.699
X-Spam-Level: 
X-Spam-Status: No, score=-110.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S0M5KcN-xlkn; Mon,  6 Jun 2011 18:49:59 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id 2FB8A21F8570; Mon,  6 Jun 2011 18:49:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2683; q=dns/txt; s=iport; t=1307411399; x=1308620999; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=/i10Rb/fdIvPRV6joze33219RcIf0bqMra03Jv+HlVw=; b=M88geYZWAWStHkr2n+ALvyiC58MUPxza3KIq4A0SOzjhf1SRuuwbLIGe ALKT/ey+oV9XXr7+0EWAjNTeG5mi9UjvsbS/JvZxdzrnH8mTab4TN88gb zSEjsTn3Dfwpov8mH6lTNGmUQAxL5F3c4NT/QX3W4+AyFC8PuX9BxvlPq 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHOD7U2rRDoH/2dsb2JhbABTphh3iHGie54ThiEEhnWKDoRMixY
X-IronPort-AV: E=Sophos;i="4.65,329,1304294400"; d="scan'208";a="709207742"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-6.cisco.com with ESMTP; 07 Jun 2011 01:49:58 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p571nrLX008605; Tue, 7 Jun 2011 01:49:58 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Mon, 06 Jun 2011 18:49:58 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Mon, 06 Jun 2011 18:49:58 -0700
Subject: Re: Proposed text for IESG Handling of Historic Status
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4DE7E1CA.9010309@ieca.com>
Date: Mon, 6 Jun 2011 18:49:43 -0700
Message-Id: <C761D66B-A348-4D2A-A352-8FE45B8A23CC@cisco.com>
References: <4DE7E1CA.9010309@ieca.com>
To: Sean Turner <turners@ieca.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: 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: Tue, 07 Jun 2011 01:49:59 -0000

I think that there are three sets of proposed state changes - what the =
author would like to do, what the working group if any agrees to do, and =
what the IESG wants to instruct the RFC Editor should ultimately be =
done. There is no reason they all have to be the same. For example, a =
document author might want to make a document a proposed standard, the =
working group decide it should be informational, and the IESG decide =
that at most it wants to make the document experimental - or make the =
document it obsoleted historic(al).

Rather than put more data into the Internet Draft, I would suggest =
putting the Working Group's view into the Shepherd's Report, and the =
IESG's view into the announcement and the note to the RFC Editor.


On Jun 2, 2011, at 12:17 PM, Sean Turner wrote:

> The IESG is considering making this statement on the IESG Handling of =
Historic status.
>=20
> We would appreciate community feedback.
>=20
> Please can we have feedback by Thursday 9th June.
>=20
> Thanks
>=20
> spt
>=20
> <statement begins>
>=20
> RFC 2026 states the following:
>=20
> A specification that has been superseded by a more recent =
specification or is for any other reason considered to be obsolete is =
assigned to the "Historic" level.
>=20
> In practice, the Historic status is not automatically assigned to RFCs =
that have been "obsoleted".  That is, when an RFC that contains the =
"Obsoletes: RFC XXXX" header is published the RFC editor does not =
automatically apply the Historic status to the XXXX RFC.  Note that in =
some situations this is perfectly acceptable because multiple versions =
of an Internet Standard are permitted to "honor the installed base," as =
per RFC 2026.
>=20
> If authors wish to change the status of RFCs that are in the obsoletes =
header to Historic, then the authors must include an explicit statement =
for the RFC editor to do so; preferably in the abstract and =
introduction.  Further, when an AD sponsors a draft that includes the =
obsoletes header, then the AD should ask the authors whether the authors =
intended to move the RFC(s) listed in the obsoletes header to Historic =
status.
>=20
> If an author wishes to publish a document directly to Historic status =
the preferred approach is to publish an I-D with the "Intended Status: =
Historic" in the header.
>=20
> Moving a document to Historic status means that the document is "not =
[an] Internet Standards in any sense," as per RFC 2026.
>=20
> </statement ends>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From john-ietf@jck.com  Mon Jun  6 19:16:39 2011
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 DAB0311E80A3; Mon,  6 Jun 2011 19:16: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tkgXf1RveRiT; Mon,  6 Jun 2011 19:16:38 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 1611C11E809F; Mon,  6 Jun 2011 19:16:38 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QTlqN-0004lV-UX; Mon, 06 Jun 2011 22:16:36 -0400
Date: Mon, 06 Jun 2011 22:16:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, IETF Secretariat <ietf-secretariat@ietf.org>
Subject: Re: New Non-WG Mailing List: fun -- FUture home Networking (FUN)
Message-ID: <6F2D64905D13DA87C2343EB7@PST.JCK.COM>
In-Reply-To: <20110606204755.GA32176@nic.fr>
References: <20110606165456.74F4411E8179@ietfa.amsl.com> <20110606204755.GA32176@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: Mark Townsley <townsley@cisco.com>, ietf@ietf.org, Ole Troan <ot@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: Tue, 07 Jun 2011 02:16:39 -0000

--On Monday, June 06, 2011 22:47 +0200 Stephane Bortzmeyer
<bortzmeyer@nic.fr> wrote:

> On Mon, Jun 06, 2011 at 09:54:56AM -0700,
>  IETF Secretariat <ietf-secretariat@ietf.org> wrote 
>  a message of 15 lines which said:
> 
>> Purpose: Mailing list for proposed working group on FUture
>> home Networking (FUN)
> 
> And nothing more (same thing on the Web site). Could we ask
> for a little bit more context when a new IETF list is created?

Stephane,

I think asking is perfectly reasonable.  But I also think we
should trust the ADs who need to agree to these things to
determine when the right point is reached to create a mailing
list for discussion.  I have no idea whether it is the case
here, but it is not at all hard for me to imagine circumstances
in which it would be appropriate to create and announce a
mailing list when there are few specifics beyond a very general
topic area.

Someone can always take the action to make a more comprehensive
announcement to the IETF list when things come together more.

    john






From barryleiba.mailing.lists@gmail.com  Mon Jun  6 21:56:42 2011
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 415B111E8070; Mon,  6 Jun 2011 21:56:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f8fSMLjWjVGC; Mon,  6 Jun 2011 21:56:41 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6AF3411E8082; Mon,  6 Jun 2011 21:56:41 -0700 (PDT)
Received: by yib18 with SMTP id 18so1190507yib.31 for <multiple recipients>; Mon, 06 Jun 2011 21:56:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=V9wqx81Tz0fR9dFjx3ObaZIYJdLyNRktq+r/+BHpI5U=; b=wdlvNBgRsiq47zWoQWLy/GmHvYpAjsbpipHUFlnHtutBZjycWQpmGc6iwh1l/+PkKA dn0d7BIm5t/W/KXt0fGJqDS4mIu4c8yYtXaQTrmGKsZ9pZJaL18YbvPBo9nW05cdTchr rEpOBjc+e99u10oABddRCswKS94klb4Af1dgU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Kd2kJF95iHj0rmn/6TJk4B6hmMOe80VqJcHmoXW2beLpnaEaIPmaGzn1EXQR9wbJiB Gt6huTGRrmuhvmS60nDYXW9SR4YJIa7YBL7evMcjFmSyikpdticmX11g18fe40RYpIYu COe70Hgc7nIeIZE3go5/7VSWXlTDifLiFYQ+Q=
MIME-Version: 1.0
Received: by 10.147.142.11 with SMTP id u11mr3131304yan.29.1307422600794; Mon, 06 Jun 2011 21:56:40 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.125.15 with HTTP; Mon, 6 Jun 2011 21:56:40 -0700 (PDT)
In-Reply-To: <6F2D64905D13DA87C2343EB7@PST.JCK.COM>
References: <20110606165456.74F4411E8179@ietfa.amsl.com> <20110606204755.GA32176@nic.fr> <6F2D64905D13DA87C2343EB7@PST.JCK.COM>
Date: Tue, 7 Jun 2011 04:56:40 +0000
X-Google-Sender-Auth: mGo2RKgKPWkztECJDMibsnuATGk
Message-ID: <BANLkTinr_HoZ2Xd=s3R0MRD4UzM2N1=pjQ@mail.gmail.com>
Subject: Re: New Non-WG Mailing List: fun -- FUture home Networking (FUN)
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org, 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, 07 Jun 2011 04:56:42 -0000

>>> Purpose: Mailing list for proposed working group on FUture
>>> home Networking (FUN)
>>
>> And nothing more (same thing on the Web site). Could we ask
>> for a little bit more context when a new IETF list is created?
>
> I think asking is perfectly reasonable. =A0But I also think we
> should trust the ADs who need to agree to these things to
> determine when the right point is reached to create a mailing
> list for discussion. =A0I have no idea whether it is the case
> here, but it is not at all hard for me to imagine circumstances
> in which it would be appropriate to create and announce a
> mailing list when there are few specifics beyond a very general
> topic area.

That may sometimes be true, but I don't think it's the typical case.
It's certainly not the case here, where there's a clear problem
statement, with a strawman proposal for what the working group will do
(even if it's not in charter form yet).  Something of that should have
been in the mailing list announcement.

We've seen quite a few non-WG mailing lists announced, where the title
of the list was all we got, and we'd have no idea whatsoever if we
wanted to subscribe to it.  Please, when we send out announcements,
let's include enough of a description -- even two or three paragraphs,
if that's what it takes -- so that we can understand what's meant to
be discussed, and so that we can know whether we want to subscribe.

The announcements for the obscurity-interest and paws lists are
examples of particularly good ones.  This one and the one for "weirds"
are particularly lacking.

Barry

From jari.arkko@piuha.net  Mon Jun  6 22:01:54 2011
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 8993421F84E8 for <ietf@ietfa.amsl.com>; Mon,  6 Jun 2011 22:01:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.068
X-Spam-Level: 
X-Spam-Status: No, score=-102.068 tagged_above=-999 required=5 tests=[AWL=-0.069, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GYDbyjHnIsrt for <ietf@ietfa.amsl.com>; Mon,  6 Jun 2011 22:01:53 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id C99AC21F84E6 for <ietf@ietf.org>; Mon,  6 Jun 2011 22:01:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id ECA0B2CC4B; Tue,  7 Jun 2011 08:01: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 lrgOTDA57qnK; Tue,  7 Jun 2011 08:01:49 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id CE5352CC3B; Tue,  7 Jun 2011 08:01:48 +0300 (EEST)
Message-ID: <4DEDB0BC.7040906@piuha.net>
Date: Tue, 07 Jun 2011 08:01:48 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>,  Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: New Non-WG Mailing List: fun -- FUture home Networking (FUN)
References: <20110606165456.74F4411E8179@ietfa.amsl.com>	<20110606204755.GA32176@nic.fr> <6F2D64905D13DA87C2343EB7@PST.JCK.COM>
In-Reply-To: <6F2D64905D13DA87C2343EB7@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 05:01:54 -0000

Stephane, John,

FUN is a new working group proposal, a variation of the HOMEGATE / 
HOMENET theme that we discussed some time ago but this time looking at 
it from a different angle. Roughly speaking, its about how to run IPv6 
in home networks, including some possibly missing protocol pieces.

The proposal has been under private discussion during the spring, and is 
now coming to a state where it can be brought for more public 
discussion. I have asked for comments from a few directorates etc last 
week, and was about to ask more publicly once I had the mailing list up 
and running :-)

The draft charter is below. Comments very much appreciated. Subscription 
to the list open.

FUture home Networks (FUN)
-------------------------

Current Status: Proposed
Last Edit: Friday, June 3rd, 2011

Chairs:
     TBD

 Internet Area Directors:
     Ralph Droms <rdroms.ietf@gmail.com>
     Jari Arkko <jari.arkko@piuha.net>

Internet Area Advisor:
     Jari Arkko <jari.arkko@piuha.net>

Routing Area Technical Advisor:
     TBD

Security Area Technical Advisor:
     TBD

Mailing Lists:
     General Discussion: fun@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/fun
     Archive:            http://www.ietf.org/mail-archive/web/fun

Description of Working Group:

This working group focuses on the evolving networking technology in
small networks such as those in homes. This evolution sets some
requirements on IETF protocols. An obvious trend for home networking
is the proliferation of networking technology in increasing number of
different devices, from home entertainment systems to appliances and
energy applications, just to name a few examples.  This leads to a
higher number of networked devices in each network.  However, some
more fundamental changes are occurring at the same time as well:

o  First, the link layer networking technology is become more
   heterogeneous, as networks are starting to employ, for instance,
   both traditional Ethernet technology and link layers designed for
   low-powered sensor networks.

o  Networks are also moving from a "one size fits all" model to
   dedicated segments for specific purposes. For instance, a common
   feature in high-end home routers in the ability to support both
   guest and private network segments. Similar needs for separation
   may occur in other cases, such as separating building control from
   the Internet access network. Typically, different subnets, routing
   and firewalls are used between the different segments.

o  Service providers are rolling out networks that support IPv6, and
   home gateway support for IPv6 is starting to appear. But for home
   networks, IPv6 is not just a new protocol, it also changes address
   allocation principles and allows end-to-end communication to the
   devices in the home.

o  End-to-end communication is both an opportunity and a problem, as it
   enables new applications but also exposes nodes in the internal
   networks to unwanted traffic from the Internet. Firewalls are in
   many cases needed to prevent exposure. However, this reduces the
   usefulness of end-to-end connectivity, as the firewall policy model
   is usually default deny, only allowing a small set of known
   protocols. In addition, consumer equipment typically reacts slowly
   if at all to changes in the typical Internet application, and it is
   likely that traffic for a popular application is not recognized by
   devices manufactured before that application was launched.

Future home networks need to provide the tools to handle these
situations in an easy manner. It is obvious that manual configuration
is rarely possible. For IPv4, NAT and private address based solutions
already provide limited solutions. The purpose of this working group
is to develop an architecture and necessary additional tools for IPv6,
to address the full scope of requirements:

o  prefix configuration for routers
o  managing routing (including turning it on by default)
o  name resolution
o  service discovery
o  perimeter security

Specifically, the group should produce an architecture document that
outlines how to construct home networks involving multiple routers and
subnets. This document is expected to apply the IPv6 addressing
architecture, prefix delegation, global and ULA addresses, source
address selection rules and other existing components of the IPv6
architecture.

In addition, the group will apply existing protocols to handle the
five requirements above. For prefix configuration, DHCPv6 PD is an
obvious candidate solution, possibly supplemented by some small
enhancements, such as new options. For automatic routing, it is
expected that existing routing protocols can be used as is, however, a
new mechanism may be needed in order to turn a selected protocol on.
For name resolution and service discovery, extensions are needed to
mDNS and DNS-SD to enable them to work across subnets.

For perimeter security, the group shall document the concept of
"advanced security" as a further development of "simple security" from
RFC 6092. The main goal of this work is to enable a default allow
security policy. This may be accomplished, for instance, through
driving security policy from an up-to-date database in the Internet or
using simple security along with firewall control protocols such as
PCP.

It is expected that the working group defines a set of protocol
specifications to accomplish the five requirements from
above. However, it is NOT in the scope of the working group to define
entirely new routing protocols or address allocation protocols. As
noted additional options or other small extensions may be necessary to
use the existing protocols in these new configuration tasks. The
working group shall also not make any changes to IPv6 protocols or
addressing architecture. Prefix configuration, routing, and security
related work shall not cause any changes that are visible to hosts.
There may be host visible changes in the work on naming and discovery
protocols, however. In its design, the working group shall also
consider security aspects and the impact on manageability.

The working group will liaise with the relevant IETF working groups
and other standards bodies. In particular, the group should work
closely with the V6OPS working group, review any use or extension of
DHCP with the DHC working group, and get feedback on DNS issues from
the DNSEXT and DNSOP working groups. If it turns out that additional
options are needed for a routing protocol, they will be developed in
the appropriate Routing Area working group, with the FUN working group
providing the architecture and requirements for such enhancements.

Milestones:

Oct 2011    First WG draft on the architecture
Dec 2011    First WG draft on prefix configuration
Dec 2011    First WG draft on routing
Jan 2011    First WG draft on name resolution
Feb 2011    First WG draft on service discovery
Feb 2011    First WG draft on perimeter security
Feb 2012    Submission of the architecture draft to the IESG as 
Informational RFC
Feb 2012    Start of routing related work in the relevant routing area 
working group, if needed
Mar 2012    Submission of the prefix configuration draft to the IESG as 
Standards Track RFC
Apr 2012    Submission of the routing draft to the IESG as Informational RFC
Jun 2012    Submission of the name resolution draft to the IESG as 
Standards Track RFC
Jun 2012    Submission of the service discovery draft to the IESG as 
Standards Track RFC
Aug 2012    Submission of the perimeter security draft to the IESG as 
Informational RFC


From tjc@ecs.soton.ac.uk  Tue Jun  7 00:14:48 2011
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 54F6C21F8461; Tue,  7 Jun 2011 00:14: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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ohu4u9hrJZzl; Tue,  7 Jun 2011 00:14:45 -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 918B521F845B; Tue,  7 Jun 2011 00:14:39 -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 p577EXtl024267;  Tue, 7 Jun 2011 08:14:33 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p577EXtl024267
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1307430873; bh=hnxWt52VfGHuyPUsHH3wgY7QVlM=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=QriKM1EjlaLV9H1yEBnVbbpn9lSkIpT9H6d5Xn3i1/DAt+Oa8SxHfqrXJCcfmELvB QWnTPBSx98JNFDKAmv7Zkao/Ku/bRAPPc3A0uLWGpoYVMCfR3DcOifVjGXW7WwHGBw Dx3fPcBOg0rzKO7bKvXHzGZ6WS7cnbHwmu/dXC9E=
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 id n568EX0035644059q0 ret-id none; Tue, 07 Jun 2011 08:14:33 +0100
Received: from [192.168.1.14] (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 p577DE3Y026437 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Jun 2011 08:13:15 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20110607063336.GO45955@Space.Net>
Date: Tue, 7 Jun 2011 08:13:14 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|c03704711a0f54e1e9000b2d94a04e2dn568EX03tjc|ecs.soton.ac.uk|4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <BANLkTikaGbFASQfisP5=H3yXKgDUpdKEqA@mail.gmail.com> <20110607063336.GO45955@Space.Net> <4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk>
To: "v6ops@ietf.org WG" <v6ops@ietf.org>, ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n568EX003564405900; tid=n568EX0035644059q0; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p577EXtl024267
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 07:14:48 -0000

On 7 Jun 2011, at 07:33, Gert Doering wrote:

>=20
> Do we really need to go through all this again?
>=20
> As long as there is no Internet Overlord that can command people to=20
> a) put up relays everywhere and b) ensure that these relays are =
working,
> 6to4 as a general mechanism for attachment to the IPv6 Internet is =
FAIL.
>=20
> If someone wants to use 6to4 to interconnect his machines over an IPv4
> infrastructure (=3D6to4 on both ends), nobody is taking this away.
>=20
> Gert Doering
>        -- NetMaster

Exactly.

Less than 1% of the IPv6 traffic reaching us is 6to4. And 6to4 in its =
6to4-to-native mode is proven to be highly unreliable. It seems highly =
preferable to have that 1% wait for native IPv6 to be available to them, =
rather than being used as a reason by the bigger content providers for =
holding back production deployment, which is what we all want to see.

It's time to remove the stabilisers on the IPv6 bicycle.

Tim


From ichiroumakino@gmail.com  Tue Jun  7 01:48:48 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5BAA1F0C35; Tue,  7 Jun 2011 01:48:48 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 645qfJMq2s6m; Tue,  7 Jun 2011 01:48:47 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0843F1F0C34; Tue,  7 Jun 2011 01:48:46 -0700 (PDT)
Received: by wyb29 with SMTP id 29so4024498wyb.31 for <multiple recipients>; Tue, 07 Jun 2011 01:48:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=SeRlIB/r8mp454KCGU8vdOzabz9UYzFOk8DW4GHxlJ0=; b=rWMzXzM7CKOYA7FX3/Mcg6DSQrjIfQwMmIRIzykfppIr9XxoXXbwrkNSu52MVB0lCM G3eUFsd2WkDodnbof3gptFcE38XUinX6H47MgYSphbt18S5vCynhHRseTO/PxPLDfchr 9aHm+hWCu1pv0XHHEFLEJszYG3lDgSfejicyM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=tWR4ZdvdMgo8QIvoimSA6myybSGlX1bHVTXRk1Sb7Wg6i2bnSp7Eg4gyFTu9KpUKk7 szNL5XvujIvBVmySIPMCNae1OJGz3UT7GA6T1Tkhasjpnn4nhKNPFZXoyTjvgu/VrlNV Pq/HLPR22Q5ZHKOybE3uGZiDr9SjQ6JvVF7Bc=
Received: by 10.227.160.140 with SMTP id n12mr5814286wbx.69.1307436526136; Tue, 07 Jun 2011 01:48:46 -0700 (PDT)
Received: from dhcp-osl-vl300-64-103-53-213.cisco.com (dhcp-osl-vl300-64-103-53-213.cisco.com [64.103.53.213]) by mx.google.com with ESMTPS id fl19sm1511630wbb.15.2011.06.07.01.48.44 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Jun 2011 01:48:45 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>
Date: Tue, 7 Jun 2011 10:48:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations Working Group <v6ops@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 Jun 2011 08:48:48 -0000

Keith,

I'm loathe to go through this discussion again. let me just respond to =
some of the points you make, and then agree that we disagree.

> I strongly object to the proposed reclassification of these documents =
as Historic. =20
>=20
> 6to4 still has many valid use cases, and there is not a suitable =
replacement for it that has been deployed.  Until there is a suitable =
replacement, or until there is widespread ISP support for native IPv6, =
reclassification of this document to Historic is premature.  (6rd is not =
a suitable replacement for 6to4, as it is intended for very different =
use cases than 6to4.)
>=20
> (It could be argued that reclassification of RFC 3068 (by itself) to =
Historic is appropriate, but that would require a separate document and =
last call.)
>=20
> In addition, this document is misleading and perhaps even =
vituperative.    For instance:
>=20
> "There would appear to be no evidence of any substantial deployment of =
the variant of 6to4 described in [RFC3056]."
> This statement is blatantly false. 6to4 is supported by every major =
desktop and server platfrom that is shipping today, and has been =
supported for several years.


incorrect. there is no evidence that the  _managed_ model of 6to4 =
described in rfc3056 has any deployment.
that's the model where relay operators advertise what parts of the 6to4 =
space they are routing. with BGP neighborships between managed and =
participating relays.

_deployment_ not _support_.

> "The IETF sees no evolutionary future for the mechanism and it is not =
recommended to include this mechanism in new implementations."
>=20
> 6to4 never was intended to have an "evolutionary future".  It was =
always intended as a near-term solution to allow consenting hosts and =
networks to interchange IPv6 traffic without prior support from the IPv4 =
networks that carry the traffic.   It is premature to recommend that =
6to4 be removed from implementations.  We do not know how long it will =
take ISPs to universally deploy IPv6.  Until they do, there will be a =
need for individuals and enterprises using IPv6-based applications to be =
able to exchange IPv6 traffic with hosts that only have IPv4 =
connectivity. =20
>=20
> All of the criticisms in section 3 have to do with the use of relays =
to exchange traffic between 6to4 and native IPv6.   In many cases the =
criticisms are overbroad.   Not all uses of 6to4 involve relays.  For =
some of those that do need to use relays, it is not necessarily the case =
that the relay is operated by an unknown third-party. =20
>=20
> The fact that some firewalls block protocol 41 traffic causes problems =
for many tunneling solutions, not just 6to4; yet this document appears =
to recommend some tunneling solutions while trashing 6to4.

it is the unmanaged aspect of 6to4 deployment that exhibits the most =
problems. a manually configured managed point to point tunnel may also =
be blocked in a firewall, but then the operator will have to sort that =
out. 6to4 has no operator.
Teredo is similar in many aspects to 6to4, but there is little evidence =
that it causes the same problems. largely because it is the choice of =
last resort in implementations and it hasn't/can't be enabled by default =
in CPEs.

> The recommendations to treat 6to4 as a service of last resort will do =
harm to users and applications using it.   A better recommendation is =
for hosts to disable 6to4 by default. =20
>=20
> This document appears to make the mistake of assuming that the purpose =
of applications using IPv6 is to interoperate with the existing =
Internet.  I have maintained for many years that it is new applications, =
or existing applications that can't tolerate widespread deployment of =
IPv4 NAT, that will drive use of IPv6.   I therefore believe that it is =
inappropriate to judge 6to4 merely by how well it works in scenarios =
where it is being used to talk to applications that work well over IPv4 =
NAT such as HTTP.   The Internet is much more diverse than that, and =
will become even more diverse as IPv6 enjoys wider deployment.

6to4 does not work through IPv4 NATs.

> It is also premature to remove references to 6to4 from RFC 5156bis, =
for IANA to mark the prefix and DNS zones as deprecated.  This will only =
cause confusion and difficulty for legitimate continued uses of 6to4.

the purpose of the text in the document is to ensure that the deprecated =
prefixes are not reused before 6to4 has been phased out.

cheers,
Ole=

From yoshifumi.nishida@gmail.com  Tue Jun  7 01:52:55 2011
Return-Path: <yoshifumi.nishida@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C945C21F85AE; Tue,  7 Jun 2011 01:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yXPehPTAvMWD; Tue,  7 Jun 2011 01:52:55 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1201021F85A6; Tue,  7 Jun 2011 01:52:54 -0700 (PDT)
Received: by iyn15 with SMTP id 15so5629103iyn.31 for <multiple recipients>; Tue, 07 Jun 2011 01:52:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=w4oZVbiFGfWyL02ME2/wFMpIu14ocEvq6CuYSbQODJA=; b=xANBI7PkezFBNFL6yMKqKJ+UlCCWOP+11TOQfPfaebXkdxHW17u/Aa7g43lU893aFX 7PT7PdsroLDSS8A/UYywn2yPh2NyM0k8gCdbe/3z5fBnhVBkzF3QtK+VCsHCq4ijju/X 5MAllX/yyUoSteR1MRDKgDHo4rrLCW+OCERFE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=ToNo+Nh+kBVBxHAdh8OnK0Z1mpvQyeWfJdz9tzl9EB5+HmMT45GeYqrhUEWEdiUEkQ 91KEotWV/h/K9MtgyiCzMycudxAU3EEtpOOyO/KRBES4CZAvaMKeTFWyjhAXhmWNO9zE K8DoaYUeavcmqJxZQukFjuXkqsVBkoKiKnKiI=
MIME-Version: 1.0
Received: by 10.231.60.73 with SMTP id o9mr1225708ibh.33.1307436774672; Tue, 07 Jun 2011 01:52:54 -0700 (PDT)
Sender: yoshifumi.nishida@gmail.com
Received: by 10.231.251.198 with HTTP; Tue, 7 Jun 2011 01:52:54 -0700 (PDT)
In-Reply-To: <4DECCF24.4010902@toshiba.co.jp>
References: <BANLkTikc0e=j2_t91gu8=EOQB1VkRTDOSw@mail.gmail.com> <4DECCF24.4010902@toshiba.co.jp>
Date: Tue, 7 Jun 2011 01:52:54 -0700
X-Google-Sender-Auth: hlsOjdIGIUdia-bJbPIWW7zbb7g
Message-ID: <BANLkTi=wYms4JzrJa1fpA_O+WHSoM5NnPA@mail.gmail.com>
Subject: Re: TSVDIR Review for draft-ohba-pana-relay-03
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: draft-ohba-pana-relay@tools.ietf.org, ietf@ietf.org, Transport Directorate <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 08:52:55 -0000

Hello Ohba-san,

Thank you so much for your quick response.
I agree with your comments and won't have further comments as long as
the doc is updated based on your response.

Regards,
--
Yoshifumi Nishida
nishida@sfc.wide.ad.jp

2011$BG/(B6$B7n(B6$BF|(B5:59 Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>:
> Nishida-san,
>
> Thank you very much for reviewing the draft.
>
> Please see my comments below.
>
> (2011/06/06 17:39), Yoshifumi Nishida wrote:
>> Hello,
>> I've reviewed this document as part of the transport area
>> directorate's ongoing effort to review key IETF documents. These
>> comments were written primarily for the transport area directors, but
>> are copied to the document's authors for their information and to
>> allow them to address any issues raised. The authors should consider
>> this review together with any other last-call comments they
>> receive. Please always CC tsv-dir@ietf.org if you reply to or forward
>> this review.
>>
>> Summary:
>>
>> This draft specifies protocol for PANA Relay Element that can relay
>> messages between a PaC and a PAA where they cannot reach each other.
>> The proposed function is simple and straightforward and useful.
>> I couldn't find any transport related issues in the draft.
>>
>>
>> Minor comments:
>>
>> Please consider clarifying the following points.
>>
>> 1)  I think clarifying communication model of this proposal will be
>> helpful for readers.
>>       It seems to me that a PRE should communicate only one PAA. But, can a PAA
>>       communicate multiple PREs?
>
> PANA allows multiple PAAs in an access network.  For example, RFC 5192
> defines a DHCP option to carry a list of PAA addresses and a PaC will
> choose one PAA to communicate with.  Similarly, there can be multiple
> PAAs in an access network with PREs.  In this case, a PRE will choose
> one PAA to communicate with for a given PaC.  Next, a PAA can
> communicate with multiple PREs.  We can clarify these in the draft.
>
>>
>> 2)  The draft seems to presume PRE to be a multi-homed node. But, is
>> this mandatory
>>        requirement? Is it possible to use single-homed node as a PRE?
>
> You are right, PRE can be either single-homed or multi-homed.  In
> fact, in ZigBee IP, each mesh router is a PRE having a single 802.15.4
> radio interface.  We can clarify this in the draft as well.
>
>>
>> 3)  Is it possible to place a PRE behind NAT? Is there any concern for this?
>>
>
> There are two cases, (i) a NAT between a PaC and a PRE, and (ii) a
> NAT between a PRE and a PAA.  I don't see a NAT issue specific to PANA
> relay for both cases.
>
>> 4)  How p2 (PRE-assigned UDP port number) is determined? Is it possible to use
>>       ephemeral port? If so, the protocol will need to be robust
>> against PRE rebooting.
>>       Similarly, can we use dhcp-ed address for IP2b?
>
> Yes, p2 can be ephemeral.  Since a PAA just uses the UDP and IP
> headers received from the relay to generate UDP and IP headers of its
> response PRY to the relay, I think the protocol is robust against PRE
> rebooting.  For the same reason, use of DHCP-ed address for IP2b
> works.  Even when IPsec is used between a PRE and a PAA, I think
> DHCP-ed address for IP2b works as long as IKEv2 identity for the PRE
> is not based on IP address.
>
> Kind Regards,
> Yoshihiro Ohba
>
>>
>> Regards,
>> --
>> Yoshifumi Nishida
>> nishida@sfc.wide.ad.jp
>>
>
>

From ron.even.tlv@gmail.com  Tue Jun  7 03:56:03 2011
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 96A3B21F84D5; Tue,  7 Jun 2011 03:56:03 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0UlywTFsUoQt; Tue,  7 Jun 2011 03:56:02 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 74E9721F84EB; Tue,  7 Jun 2011 03:56:02 -0700 (PDT)
Received: by qwc23 with SMTP id 23so3557767qwc.31 for <multiple recipients>; Tue, 07 Jun 2011 03:56:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=wiEO+dpxqKaqszSJC/01xghHneWE6gbWRUZf9yzB85U=; b=jxaVft1jReydb1peu3hXFS7I+MJJ6D6xzb/0au1bNutQT2qc3vpixfB1TBMrPVtZoL zfnR1AHpYwjBP21q/O3H0ysaF+H1kQRCmJoamWUULdlysoGbeRlwbIBNyGEr+Bt+wgbU EGK4Lyz3yvSaW+SnLQ5f738TQ47q222FDLKGI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=ECiq55to3FSAD47L/+8bsIYXS8i6O7UVV+mAekjhzUhfjW36AFN+zEQiKhvAMnsJQ2 LkOuozs9V1uUDNRG6srrZYHozRE+Yi3RiKSPl4RME20PMV/BRjoeRO7Rz+5R4dQGmilo DszAagpiGXwrSx0X9/ItkvIyUULCckNGo80+w=
Received: by 10.229.20.210 with SMTP id g18mr4296151qcb.115.1307444161674; Tue, 07 Jun 2011 03:56:01 -0700 (PDT)
Received: from YOUR6108 (user-0ccehtm.cable.mindspring.com [24.199.71.182]) by mx.google.com with ESMTPS id m16sm3497913qck.16.2011.06.07.03.55.59 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Jun 2011 03:55:59 -0700 (PDT)
From: "rontlv" <ron.even.tlv@gmail.com>
To: "'Paul Hoffman'" <paul.hoffman@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org>
In-Reply-To: <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org>
Subject: RE: Gen-ART LC review of draft-faltstrom-5892bis-04
Date: Tue, 7 Jun 2011 13:56:08 +0300
Message-ID: <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acwklte7796Bb4noSxWY8eQukloclgAaX0Mw
Content-Language: he
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 10:56:03 -0000

Hi Paul,

The IANA registry is in
http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml#idnabis-ta
bles-properties
I saw that in the beginning it has as reference RFC 5892 for the whole
table. Will it stay this way after the change proposed in this draft and
just the three individual values will change based on 1.1, 1.2 and 1.3? or
are there no changes in the IANA registry at all. This is unclear to me
according to the section 3 of your draft.

Section 5.1 of RFC5892 says "If non-backward-compatible changes or other
problems arise during the
   creation or designated expert review of the table of derived property
   values, they should be flagged for the IESG." . My question was if the
change is backward compatible. The 5892bis draft does not say it.

Thanks
Roni




> -----Original Message-----
> From: Paul Hoffman [mailto:paul.hoffman@vpnc.org]
> Sent: Tuesday, June 07, 2011 1:13 AM
> To: Roni Even
> Cc: draft-faltstrom-5892bis.all@tools.ietf.org; gen-art@ietf.org;
> 'IETF-Discussion list'
> Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
> 
> On May 29, 2011, at 4:13 AM, Roni Even wrote:
> 
> > Major issues:
> >
> > 1.       I am not sure how the IANA consideration section is in-line
> with the IANA consideration section of RFC5892. Maybe some
> clarification text would be helpful.
> 
> We think that the IANA considerations here are, in fact, what RFC 5892
> was designed for. That is, RFC 5892 says that the registry will be
> updated ("IANA has created a registry with the derived properties for
> the versions of Unicode released after (and including) version 5.2"),
> and this is such an update. Please let me know if that doesn't match
> your understanding.
> 
> > 2.       The IANA registry for derived property value has RFC 5892,
> does this draft want to change the reference, how will it be done.
> 
> Section 2 of the draft is pretty clear here: "No change to RFC 5892 is
> needed based on the changes made in Unicode 6.0".
> 
> >   I think that it relates also to the issue of whether this draft
> updates RFC 5892.
> 
> And here too.
> 
> --Paul Hoffman
> 
> 
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 6185 (20110606) __________
> 
> The message was checked by ESET NOD32 Antivirus.
> 
> http://www.eset.com
> 
 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6186 (20110607) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 


From trejrco@gmail.com  Tue Jun  7 04:33:31 2011
Return-Path: <trejrco@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADD1A21F84E2; Tue,  7 Jun 2011 04:33:31 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XEK1MAkVcp5Q; Tue,  7 Jun 2011 04:33:31 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id C9D6421F84DE; Tue,  7 Jun 2011 04:33:30 -0700 (PDT)
Received: by gyf3 with SMTP id 3so2569294gyf.31 for <multiple recipients>; Tue, 07 Jun 2011 04:33:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=hT6M2iUs77ri4r/e2jW5x2boadH11Z4hxL02gjAVz20=; b=whFjP933rrH5B9HYQFaXkQnNv7grc4s6liSGUM+Nhy2jddgtAyrMJSKu4QynBTGzAQ JnZNMLL5v4d02XT8N3KxRdYkWrIBmyOPNUJGQEWw/8P2g2kw7oYMnKFBaWxGHZbrbkBp 4V/tNpslQJm1Tyyk0JS7wEgbszjUECmEHhg30=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=A5EOhsF0l4j8jZIVsvdJPb+r5OMGj5EozZB6zjNzn00UE2w+f4/E2qOWG1MfE++CTv uFfc0+a8CA3vMjywfuY0QuLiJkKaNAQTA96UnO9c0DwAJ/wQI7rc501/ErXt/xJEq+6H xwn4rIYG4IBxRS6qNW3DgiYCRGclSnHOaklrI=
MIME-Version: 1.0
Received: by 10.91.195.5 with SMTP id x5mr2648775agp.103.1307446410048; Tue, 07 Jun 2011 04:33:30 -0700 (PDT)
Received: by 10.91.170.3 with HTTP; Tue, 7 Jun 2011 04:33:28 -0700 (PDT)
Received: by 10.91.170.3 with HTTP; Tue, 7 Jun 2011 04:33:28 -0700 (PDT)
In-Reply-To: <EMEW3|c03704711a0f54e1e9000b2d94a04e2dn568EX03tjc|ecs.soton.ac.uk|4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <BANLkTikaGbFASQfisP5=H3yXKgDUpdKEqA@mail.gmail.com> <4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk> <20110607063336.GO45955@Space.Net> <EMEW3|c03704711a0f54e1e9000b2d94a04e2dn568EX03tjc|ecs.soton.ac.uk|4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk>
Date: Tue, 7 Jun 2011 07:33:28 -0400
Message-ID: <BANLkTikC06JkjJufNTaDA6r5X=Qrs7ozyw@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
From: TJ <trejrco@gmail.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=00163676587dd576ad04a51d964a
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 11:33:31 -0000

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

> Less than 1% of the IPv6 traffic reaching us is 6to4.

Unless you provide IPv6 only sites, you should see very little ... that is
part of the point :).

<snip>

> It's time to remove the stabilisers on the IPv6 bicycle.

I agree, but get me native everywhere before taking away one connection
mechanism that does work.

Just my $.02,
/TJ ... ready for world IPv6 Day?

--00163676587dd576ad04a51d964a
Content-Type: text/html; charset=ISO-8859-1

<p><br>
&gt; Less than 1% of the IPv6 traffic reaching us is 6to4. </p>
<p>Unless you provide IPv6 only sites, you should see very little ... that is part of the point :).</p>
<p>&lt;snip&gt;</p>
<p>&gt; It&#39;s time to remove the stabilisers on the IPv6 bicycle.</p>
<p>I agree, but get me native everywhere before taking away one connection mechanism that does work.<br></p>
<p>Just my $.02,<br>
/TJ ... ready for world IPv6 Day? <br>
</p>

--00163676587dd576ad04a51d964a--

From trejrco@gmail.com  Tue Jun  7 06:35:23 2011
Return-Path: <trejrco@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BC0D21F84A6; Tue,  7 Jun 2011 06:35:23 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cj8xN+PO25OY; Tue,  7 Jun 2011 06:35:22 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5B94621F8492; Tue,  7 Jun 2011 06:35:22 -0700 (PDT)
Received: by yib18 with SMTP id 18so1473188yib.31 for <multiple recipients>; Tue, 07 Jun 2011 06:35:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=8aKWC7bSwg+hxOrMsCJARTOhVaEUfEPOpOJxsJ3EzjE=; b=x5z3KZuWiQC0ZQk2c2uaJpqJEG0572ovrXh5QxT3SZxxwh/kZDcmZ6rGNIhfpFB3eZ orXfgrwCFFi5G0pEqa8dFxSJTGHMIPP+6+MEjgDOqp9JFZXiAnswciTEejwRcl3j6WHN /bt/REWgHBP5+xpSi9QEU4a7Ack6sybWY+OLM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; b=HYVXAnCNKnWLVH1aNt03m9O6ILHFbsWqXHZKrGB10YpepcRB/iiQccHwX8SjLuPras +hRRDKr5Cv81PRCkYJEvI4o4Rh2OUm6rnBMHU2ZrGR+1H6fW+DizhgJM5ZVKzizT1B+P hLE1c741b61mTy5FKIDvcAHndiDAMsZlSPePA=
Received: by 10.90.61.8 with SMTP id j8mr5552420aga.76.1307453721613; Tue, 07 Jun 2011 06:35:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.91.170.3 with HTTP; Tue, 7 Jun 2011 06:34:59 -0700 (PDT)
In-Reply-To: <34E4F50CAFA10349A41E0756550084FB067B72F8@PRVPEXVS04.corp.twcable.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <BANLkTikaGbFASQfisP5=H3yXKgDUpdKEqA@mail.gmail.com> <4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk> <20110607063336.GO45955@Space.Net> <EMEW3|c03704711a0f54e1e9000b2d94a04e2dn568EX03tjc|ecs.soton.ac.uk|4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk> <BANLkTikC06JkjJufNTaDA6r5X=Qrs7ozyw@mail.gmail.com> <34E4F50CAFA10349A41E0756550084FB067B72F8@PRVPEXVS04.corp.twcable.com>
From: TJ <trejrco@gmail.com>
Date: Tue, 7 Jun 2011 09:34:59 -0400
Message-ID: <BANLkTikZJQHQnvbXhPJMGBOdzh8tvh0z5A@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: "George, Wesley" <wesley.george@twcable.com>, "v6ops@ietf.org WG" <v6ops@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=0016e68db78ca317bc04a51f4a26
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 13:35:23 -0000

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

On Tue, Jun 7, 2011 at 08:56, George, Wesley <wesley.george@twcable.com>wrote:

>
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of
> TJ
> Sent: Tuesday, June 07, 2011 7:33 AM
> To: Tim Chown
> Cc: v6ops@ietf.org WG; ietf@ietf.org
> Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to
> Historic status) to Informational RFC
>
> > It's time to remove the stabilisers on the IPv6 bicycle.
> I agree, but get me native everywhere before taking away one connection
> mechanism that does work.
>
>
> This takes nothing away. It's not as if the day that this draft gets
> published as an RFC, 6to4 stops working. IETF has moved other protocols to
> historical status before they were out of heavy use, with the expectation
> that it would take some time for the alternatives to be deployed and
> existing implementations to be retired. This is specifically why we resisted
> the idea of putting in a shutdown schedule or other flag day where the 6to4
> prefixes get null-routed, because it's likely to be different in each
> network and application.
>
> "In order to limit the impact of end-users, it is
>   recommended that operators retain their existing 6to4 relay routers
>   and follow the recommendations found in
>   [I-D.ietf-v6ops-6to4-advisory].  When traffic levels diminish, these
>   routers can be decommissioned."
>
> Wes George
>
>
I agree with the end goal here, but for a mechanism that relies on the good
will of others (relays) changing it to "historic" could have a more-abrupt
impact on those who use the mechanism than in other cases of similar
demotions.  That is my concern.

 /TJ

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

<br><div class=3D"gmail_quote">On Tue, Jun 7, 2011 at 08:56, George, Wesley=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:wesley.george@twcable.com">wesley.=
george@twcable.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"=
>

<br>
From: <a href=3D"mailto:v6ops-bounces@ietf.org">v6ops-bounces@ietf.org</a> =
[mailto:<a href=3D"mailto:v6ops-bounces@ietf.org">v6ops-bounces@ietf.org</a=
>] On Behalf Of TJ<br>
Sent: Tuesday, June 07, 2011 7:33 AM<br>
To: Tim Chown<br>
Cc: <a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a> WG; <a href=3D"mai=
lto:ietf@ietf.org">ietf@ietf.org</a><br>
Subject: Re: [v6ops] Last Call: &lt;draft-ietf-v6ops-6to4-to-historic-04.tx=
t&gt; (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to=
 Historic status) to Informational RFC<br>
<div class=3D"im"><br>
&gt; It&#39;s time to remove the stabilisers on the IPv6 bicycle.<br>
I agree, but get me native everywhere before taking away one connection mec=
hanism that does work.<br>
<br>
<br>
</div>This takes nothing away. It&#39;s not as if the day that this draft g=
ets published as an RFC, 6to4 stops working. IETF has moved other protocols=
 to historical status before they were out of heavy use, with the expectati=
on that it would take some time for the alternatives to be deployed and exi=
sting implementations to be retired. This is specifically why we resisted t=
he idea of putting in a shutdown schedule or other flag day where the 6to4 =
prefixes get null-routed, because it&#39;s likely to be different in each n=
etwork and application.<br>


<br>
&quot;In order to limit the impact of end-users, it is<br>
 =A0 recommended that operators retain their existing 6to4 relay routers<br=
>
 =A0 and follow the recommendations found in<br>
 =A0 [I-D.ietf-v6ops-6to4-advisory]. =A0When traffic levels diminish, these=
<br>
 =A0 routers can be decommissioned.&quot;<br>
<br>
Wes George<br><br></blockquote><div><br></div><div>I agree with the end goa=
l here, but for a mechanism that relies on the good will of others (relays)=
 changing it to &quot;historic&quot; could have a more-abrupt impact on tho=
se who use the mechanism than in other cases of similar demotions. =A0That =
is my concern.</div>

<div><br></div><div>=A0/TJ</div></div>

--0016e68db78ca317bc04a51f4a26--

From john-ietf@jck.com  Tue Jun  7 07:20:17 2011
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 33E7A11E812C; Tue,  7 Jun 2011 07:20: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PbcuRKpuIOiN; Tue,  7 Jun 2011 07:20:16 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 7041F11E8129; Tue,  7 Jun 2011 07:20:16 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QTx8V-000H4c-VT; Tue, 07 Jun 2011 10:20:04 -0400
Date: Tue, 07 Jun 2011 10:20:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: New Non-WG Mailing List: fun -- FUture home Networking (FUN)
Message-ID: <76C452C24ECA41ACBA28CC2E@PST.JCK.COM>
In-Reply-To: <BANLkTinr_HoZ2Xd=s3R0MRD4UzM2N1=pjQ@mail.gmail.com>
References: <20110606165456.74F4411E8179@ietfa.amsl.com> <20110606204755.GA32176@nic.fr> <6F2D64905D13DA87C2343EB7@PST.JCK.COM> <BANLkTinr_HoZ2Xd=s3R0MRD4UzM2N1=pjQ@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org, 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, 07 Jun 2011 14:20:17 -0000

--On Tuesday, June 07, 2011 04:56 +0000 Barry Leiba
<barryleiba@computer.org> wrote:

>... 
> We've seen quite a few non-WG mailing lists announced, where
> the title of the list was all we got, and we'd have no idea
> whatsoever if we wanted to subscribe to it.  Please, when we
> send out announcements, let's include enough of a description
> -- even two or three paragraphs, if that's what it takes -- so
> that we can understand what's meant to be discussed, and so
> that we can know whether we want to subscribe.

Agreed.  I certainly wasn't trying to suggest that
zero-information announcements were a good thing, only that we
shouldn't try to prohibit them if an AD believed that was the
right thing to do.

> The announcements for the obscurity-interest and paws lists are
> examples of particularly good ones.  This one and the one for
> "weirds" are particularly lacking.

Especially since it is now apparent that the relevant
information was readily available in both cases: See Jari's note
for this one; in the case of "weirds", three documents are now
in the I-D directory and there is apparently a plan to ask for a
BOF in Quebec.

     john
 





From moore@network-heretics.com  Tue Jun  7 08:21:22 2011
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 AB7F121F8494; Tue,  7 Jun 2011 08:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yv0YzwTTSUW1; Tue,  7 Jun 2011 08:21:16 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id A0AB121F848E; Tue,  7 Jun 2011 08:21:12 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id B586E20248; Tue,  7 Jun 2011 11:21:08 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 07 Jun 2011 11:21:08 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=rjU89i/thnBE82B8ACtt5TXATMc=; b=PHFgleuHen2/Ve8q8Z0JSLJfR/Z0j8h80xymlbyCi+6+RX03NzezonJUnlKaD+GDpBM0oSxC6xlHw5OgZWZlVGv6MFy/GhEYXE0R+rAgoVRzuiSMhGPx/LvUVs8YLMiUL/SgvQCSuP0XIO6mYsN2hZp1GO4JuW2wZN1S0OMWxC8=
X-Sasl-enc: 9eFlCh9xSSQp/+uqkgdBtildedmoAs0jqHjrap/d+jyj 1307460066
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 65FA3403D22; Tue,  7 Jun 2011 11:21:06 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-11-587867425
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com>
Date: Tue, 7 Jun 2011 11:21:05 -0400
Message-Id: <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com>
To: "George, Wesley" <wesley.george@twcable.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 15:21:22 -0000

--Apple-Mail-11-587867425
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 7, 2011, at 10:39 AM, George, Wesley wrote:

> At the risk of rehashing discussion from WGLC...
> Ole has addressed some of your points, I'll address a few others below =
inline.
>=20
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf =
Of Keith Moore
> Sent: Monday, June 06, 2011 1:22 PM
> To: ietf@ietf.org
> Cc: v6ops@ietf.org; IETF-Announce
> Subject: Re: [v6ops] Last Call: =
<draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection =
of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to =
Informational RFC
>=20
> 6to4 still has many valid use cases, and there is not a suitable =
replacement for it that has been deployed.  Until there is a suitable =
replacement, or until there is widespread ISP support for native IPv6, =
reclassification of this document to Historic is premature.  (6rd is not =
a suitable replacement for 6to4, as it is intended for very different =
use cases than 6to4.)
>=20
> WEG> Please substantiate these claims. What are the use cases, and why =
are there no other solutions for those specific use cases? What is =
considered "widespread ISP support for native IPV6"?

The best current use cases for 6to4 that I'm aware of are:

- Applications developers want to be forward thinking and develop IPv6 =
apps, but cannot get native IPv6 access.  6to4 allows them to develop =
those apps and test or use them in useful situations (i.e. outside of a =
lab) without having to configure a separate tunnel to every host =
involved.   Note that 6to4 is useful in this way even if all of the =
addresses used are 6to4 addresses, and the traffic therefore does not =
cross any relays between 6to4 and native IPv6.
- Enterprises have applications that need to be able to communicate with =
large numbers of hosts spread over a diverse area.  IPv6 is clearly the =
way that they want to go, but it's not widely available at present.  =
6to4 provides them with a means of routing traffic to their hosts in the =
interim until widespread support for IPv6 exists.
- Users (including enterprise users) who have small networks with IPv4 =
access (generally behind v4 NATs) can use 6to4 to allow them to remotely =
access individual hosts on those networks.  This can be done either with =
a NAT that also acts as a v6 router and supports 6to4 as an external =
connection, or by configuring the NAT to pass protocol 41 to a IPv6 =
router for the network, internal to the v4 NAT.

Widespread IPv6 support for native IPv6 would be when native IPv6 is =
available everywhere that IPv4 access is available, from at least one =
provider, with quality (connectivity, reliability, support) =
approximately as good as IPv4, and at a reasonable price.  In other =
words, you can't expect applications to rely on native IPv6 until it's =
reliably available everywhere that they need to use it.

> "The IETF sees no evolutionary future for the mechanism and it is not =
recommended to include this mechanism in new implementations."
>=20
> 6to4 never was intended to have an "evolutionary future".  It was =
always intended as a near-term solution to allow consenting hosts and =
networks to interchange IPv6 traffic without prior support from the IPv4 =
networks that carry the traffic.   It is premature to recommend that =
6to4 be removed from implementations.  We do not know how long it will =
take ISPs to universally deploy IPv6.  Until they do, there will be a =
need for individuals and enterprises using IPv6-based applications to be =
able to exchange IPv6 traffic with hosts that only have IPv4 =
connectivity.
>=20
> WEG> As was discussed in the WGLC for this document, enterprise =
applications will not realistically use 6to4 as a means to reach IPv6 =
for business critical applications. It's simply not reliable enough. =
It's also probably unlikely that those will go directly to IPv6-only vs =
using dual-stack to ease that transition. Individuals and Enterprises =
that use IPv6-only applications will need to make IPv6 service a =
non-negotiable requirement for their ISPs, networks, and devices rather =
than hoping that 6to4 works.

With respect, the v6ops working group is not in a good position to judge =
whether enterprise applications will use 6to4.   Operators rarely have a =
good understanding of what individual application users or developers =
need.  They tend to focus mostly on the applications that generate the =
most traffic,  or cause them particular amounts of trouble, or the ones =
that their biggest customers need.  Problem is, those aren't the only =
applications that are important.  Every application is important to its =
users, no matter how much or little traffic (or revenue) it generates.

6to4 is as reliable as IPv4 is, if it isn't asked to cross a relay =
router.  And there are valid reasons to use 6to4 even where IPv4 =
connectivity already exists.

Even in cases where 6to4 traffic must cross a relay router, sometimes =
it's the best solution available.  =20

> All of the criticisms in section 3 have to do with the use of relays =
to exchange traffic between 6to4 and native IPv6.   In many cases the =
criticisms are overbroad.   Not all uses of 6to4 involve relays.  For =
some of those that do need to use relays, it is not necessarily the case =
that the relay is operated by an unknown third-party.
>=20
> WEG> Again, please substantiate this with examples of implementations =
that are actively using non-relay 6to4. Also, the number of applications =
of 6to4 that can be guaranteed to avoid any unknown 3rd party relays is =
extremely limited due to the nature of anycast and 6to4's asymmetric =
routing. The protocol action requested in this draft in no way prevents =
one or more consenting networks from using 6to4 and continuing to run =
relays for their local traffic indefinitely - in fact, it even provides =
a reference to a document to show them how to make it work as well as =
possible. It is simply saying that it's not a good idea.

Application implementations shouldn't care whether they're using relay =
6to4, non-relay 6to4, or 6to4 at all.  Application implementations =
should at most care that they're using IPv6 rather than IPv4, and for =
some applications even this is not appropriate.

Application deployments might well need to care how well their =
underlying networks work.  Ideally, they shouldn't have to care, but =
that's the world we're currently living in.

The requested protocol action deprecates 6to4 and discourages its =
inclusion in future implementations.  That's harmful to applications and =
users for whom native IPv6 isn't available - which is to say, pretty =
much everyone at the moment.  When native IPv6 becomes widely available, =
it will then be appropriate to transition hosts and networks using 6to4 =
to native IPv6.  But even then, there will probably still be a need for =
host implementations=20

> The recommendations to treat 6to4 as a service of last resort will do =
harm to users and applications using it.   A better recommendation is =
for hosts to disable 6to4 by default.
>=20
> WEG> this seems to be to be splitting hairs. Please explain the =
distinction you're making here. Disable by default means never use. Use =
as last resort means use when no better IP connectivity is available.

I was interpreting "treat 6to4 as a service of last resort" as affecting =
the address and interface selection algorithm.   If 6to4 is enabled on a =
host or network, there are reasons to use 6to4 in preference to some =
other kinds of connectivity.    The question of whether to enable 6to4 =
should be separate from the question of "if 6to4 is enabled, what =
priority should it have in address selection?"

Keith

p.s. I'd support the writing of an applicability statement for 6to4 that =
recommends a narrowing of its applicability to specific use cases, and =
I'm even willing to help write it.   But moving it to Historic is going =
too far, and it sends the wrong message.   We need for 6to4 in our =
toolbox to enable enterprises and applications developers to be able to =
write and (tentatively, carefully) deploy applications that use IPv6.   =
We can't afford to wait until all ISPs support native v6 for people to =
start writing applications that use it. =20


--Apple-Mail-11-587867425
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 7, 2011, at 10:39 AM, George, Wesley wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>At =
the risk of rehashing discussion from WGLC...<br>Ole has addressed some =
of your points, I'll address a few others below inline.<br><br>From: <a =
href=3D"mailto:v6ops-bounces@ietf.org">v6ops-bounces@ietf.org</a> =
[mailto:v6ops-bounces@ietf.org] On Behalf Of Keith Moore<br>Sent: =
Monday, June 06, 2011 1:22 PM<br>To: <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>Cc: <a =
href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a>; =
IETF-Announce<br>Subject: Re: [v6ops] Last Call: =
&lt;draft-ietf-v6ops-6to4-to-historic-04.txt&gt; (Request to move =
Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to =
Informational RFC<br><br>6to4 still has many valid use cases, and there =
is not a suitable replacement for it that has been deployed. &nbsp;Until =
there is a suitable replacement, or until there is widespread ISP =
support for native IPv6, reclassification of this document to Historic =
is premature. &nbsp;(6rd is not a suitable replacement for 6to4, as it =
is intended for very different use cases than 6to4.)<br><br>WEG&gt; =
Please substantiate these claims. What are the use cases, and why are =
there no other solutions for those specific use cases? What is =
considered "widespread ISP support for native =
IPV6"?<br></div></blockquote><div><br></div><div>The best current use =
cases for 6to4 that I'm aware of are:</div><div><br></div><div>- =
Applications developers want to be forward thinking and develop IPv6 =
apps, but cannot get native IPv6 access. &nbsp;6to4 allows them to =
develop those apps and test or use them in useful situations (i.e. =
outside of a lab) without having to configure a separate tunnel to every =
host involved. &nbsp; Note that 6to4 is useful in this way even if all =
of the addresses used are 6to4 addresses, and the traffic therefore does =
not cross any relays between 6to4 and native IPv6.</div><div>- =
Enterprises have applications that need to be able to communicate with =
large numbers of hosts spread over a diverse area. &nbsp;IPv6 is clearly =
the way that they want to go, but it's not widely available at present. =
&nbsp;6to4 provides them with a means of routing traffic to their hosts =
in the interim until widespread support for IPv6 exists.</div><div>- =
Users (including enterprise users) who have small networks with IPv4 =
access (generally behind v4 NATs) can use 6to4 to allow them to remotely =
access individual hosts on those networks. &nbsp;This can be done either =
with a NAT that also acts as a v6 router and supports 6to4 as an =
external connection, or by configuring the NAT to pass protocol 41 to a =
IPv6 router for the network, internal to the v4 =
NAT.</div><div><br></div>Widespread IPv6 support for native IPv6 would =
be when native IPv6 is available everywhere that IPv4 access is =
available, from at least one provider, with quality (connectivity, =
reliability, support) approximately as good as IPv4, and at a reasonable =
price. &nbsp;In other words, you can't expect applications to rely on =
native IPv6 until it's reliably available everywhere that they need to =
use it.</div><div><br></div><div><blockquote type=3D"cite"><div>"The =
IETF sees no evolutionary future for the mechanism and it is not =
recommended to include this mechanism in new =
implementations."<br><br>6to4 never was intended to have an =
"evolutionary future". &nbsp;It was always intended as a near-term =
solution to allow consenting hosts and networks to interchange IPv6 =
traffic without prior support from the IPv4 networks that carry the =
traffic. &nbsp;&nbsp;It is premature to recommend that 6to4 be removed =
from implementations. &nbsp;We do not know how long it will take ISPs to =
universally deploy IPv6. &nbsp;Until they do, there will be a need for =
individuals and enterprises using IPv6-based applications to be able to =
exchange IPv6 traffic with hosts that only have IPv4 =
connectivity.<br><br>WEG&gt; As was discussed in the WGLC for this =
document, enterprise applications will not realistically use 6to4 as a =
means to reach IPv6 for business critical applications. It's simply not =
reliable enough. It's also probably unlikely that those will go directly =
to IPv6-only vs using dual-stack to ease that transition. Individuals =
and Enterprises that use IPv6-only applications will need to make IPv6 =
service a non-negotiable requirement for their ISPs, networks, and =
devices rather than hoping that 6to4 =
works.<br></div></blockquote><div><br></div>With respect, the v6ops =
working group is not in a good position to judge whether enterprise =
applications will use 6to4. &nbsp; Operators rarely have a good =
understanding of what individual application users or developers need. =
&nbsp;They tend to focus mostly on the applications that generate the =
most traffic, &nbsp;or cause them particular amounts of trouble, or the =
ones that their biggest customers need. &nbsp;Problem is, those aren't =
the only applications that are important. &nbsp;Every application is =
important to its users, no matter how much or little traffic (or =
revenue) it generates.</div><div><br></div><div>6to4 is as reliable as =
IPv4 is, if it isn't asked to cross a relay router. &nbsp;And there are =
valid reasons to use 6to4 even where IPv4 connectivity already =
exists.</div><div><br></div><div>Even in cases where 6to4 traffic must =
cross a relay router, sometimes it's the best solution available. =
&nbsp;&nbsp;</div><div><br><blockquote type=3D"cite"><div>All of the =
criticisms in section 3 have to do with the use of relays to exchange =
traffic between 6to4 and native IPv6. &nbsp;&nbsp;In many cases the =
criticisms are overbroad. &nbsp;&nbsp;Not all uses of 6to4 involve =
relays. &nbsp;For some of those that do need to use relays, it is not =
necessarily the case that the relay is operated by an unknown =
third-party.<br><br>WEG&gt; Again, please substantiate this with =
examples of implementations that are actively using non-relay 6to4. =
Also, the number of applications of 6to4 that can be guaranteed to avoid =
any unknown 3rd party relays is extremely limited due to the nature of =
anycast and 6to4's asymmetric routing. The protocol action requested in =
this draft in no way prevents one or more consenting networks from using =
6to4 and continuing to run relays for their local traffic indefinitely - =
in fact, it even provides a reference to a document to show them how to =
make it work as well as possible. It is simply saying that it's not a =
good idea.<br></div></blockquote><div><br></div>Application =
<i>implementations</i> shouldn't care whether they're using relay 6to4, =
non-relay 6to4, or 6to4 at all. &nbsp;Application implementations should =
at most care that they're using IPv6 rather than IPv4, and for some =
applications even this is not =
appropriate.</div><div><br></div><div>Application <i>deployments</i> =
might well need to care how well their underlying networks work. =
&nbsp;Ideally, they shouldn't have to care, but that's the world we're =
currently living in.</div><div><br></div><div>The requested protocol =
action deprecates 6to4 and discourages its inclusion in future =
implementations. &nbsp;That's harmful to applications and users for whom =
native IPv6 isn't available - which is to say, pretty much everyone at =
the moment. &nbsp;When native IPv6 becomes widely available, it will =
then be appropriate to transition hosts and networks using 6to4 to =
native IPv6. &nbsp;But even then, there will probably still be a need =
for host implementations&nbsp;</div><div><br><blockquote =
type=3D"cite"><div>The recommendations to treat 6to4 as a service of =
last resort will do harm to users and applications using it. =
&nbsp;&nbsp;A better recommendation is for hosts to disable 6to4 by =
default.<br><br>WEG&gt; this seems to be to be splitting hairs. Please =
explain the distinction you're making here. Disable by default means =
never use. Use as last resort means use when no better IP connectivity =
is available.</div></blockquote><div><br></div>I was interpreting "treat =
6to4 as a service of last resort" as affecting the address and interface =
selection algorithm. &nbsp; If 6to4 is enabled on a host or network, =
there are reasons to use 6to4 in preference to some other kinds of =
connectivity. &nbsp; &nbsp;The question of whether to enable 6to4 should =
be separate from the question of "if 6to4 is enabled, what priority =
should it have in address =
selection?"</div><div><br></div><div>Keith</div><div><br></div><div>p.s. =
I'd support the writing of an applicability statement for 6to4 that =
recommends a narrowing of its applicability to specific use cases, and =
I'm even willing to help write it. &nbsp; But moving it to Historic is =
going too far, and it sends the wrong message. &nbsp; We need for 6to4 =
in our toolbox to enable enterprises and applications developers to be =
able to write and (tentatively, carefully) deploy applications that use =
IPv6. &nbsp; We can't afford to wait until all ISPs support native v6 =
for people to start writing applications that use it. =
&nbsp;</div><div><br></div></body></html>=

--Apple-Mail-11-587867425--

From gert@space.net  Mon Jun  6 23:34:32 2011
Return-Path: <gert@space.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51CF221F85C6 for <ietf@ietfa.amsl.com>; Mon,  6 Jun 2011 23:34: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aKm90EG7Pohx for <ietf@ietfa.amsl.com>; Mon,  6 Jun 2011 23:34:31 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by ietfa.amsl.com (Postfix) with ESMTP id B23B721F85C9 for <ietf@ietf.org>; Mon,  6 Jun 2011 23:34:30 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 9DB8CF842D for <ietf@ietf.org>; Tue,  7 Jun 2011 08:34:27 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id A2EF3F8438 for <ietf@ietf.org>; Tue,  7 Jun 2011 08:33:36 +0200 (CEST)
Received: (qmail 63090 invoked by uid 1007); 7 Jun 2011 08:33:36 +0200
Date: Tue, 7 Jun 2011 08:33:36 +0200
From: Gert Doering <gert@space.net>
To: TJ <trejrco@gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Message-ID: <20110607063336.GO45955@Space.Net>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <BANLkTikaGbFASQfisP5=H3yXKgDUpdKEqA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BANLkTikaGbFASQfisP5=H3yXKgDUpdKEqA@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Tue, 07 Jun 2011 08:25:55 -0700
Cc: v6ops@ietf.org, ietf@ietf.org, ietf-announce@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 06:34:32 -0000

Hi,

On Mon, Jun 06, 2011 at 07:41:49PM -0400, TJ wrote:
> On Mon, Jun 6, 2011 at 13:22, Keith Moore <moore@network-heretics.com>wrote:
> 
> > I strongly object to the proposed reclassification of these documents as
> > Historic.
> > *<snipped lots of great thoughts/comments, solely for brevity>*
> 
> Agreed that this is too harsh, too soon.  Fixing the broken implementations
> is a better idea than trying to break the working ones.  And I am not just
> saying this because I successfully use 6to4 on a fairly common basis ...

Do we really need to go through all this again?

As long as there is no Internet Overlord that can command people to 
a) put up relays everywhere and b) ensure that these relays are working,
6to4 as a general mechanism for attachment to the IPv6 Internet is FAIL.

If someone wants to use 6to4 to interconnect his machines over an IPv4
infrastructure (=6to4 on both ends), nobody is taking this away.

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

From wesley.george@twcable.com  Tue Jun  7 05:56:31 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 127C911E8102; Tue,  7 Jun 2011 05:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.163
X-Spam-Level: 
X-Spam-Status: No, score=-0.163 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HVGXiwAdruyV; Tue,  7 Jun 2011 05:56:30 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 53C9211E80C0; Tue,  7 Jun 2011 05:56:30 -0700 (PDT)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.65,332,1304308800"; d="scan'208";a="221653942"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 07 Jun 2011 08:56:35 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.29]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Tue, 7 Jun 2011 08:56:29 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: "trejrco@gmail.com" <trejrco@gmail.com>
Date: Tue, 7 Jun 2011 08:56:27 -0400
Subject: RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Thread-Index: AcwlBs60NNUHtNEPRnGN4Wu0BHZ3iwACmjLQ
Message-ID: <34E4F50CAFA10349A41E0756550084FB067B72F8@PRVPEXVS04.corp.twcable.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <BANLkTikaGbFASQfisP5=H3yXKgDUpdKEqA@mail.gmail.com> <4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk> <20110607063336.GO45955@Space.Net> <EMEW3|c03704711a0f54e1e9000b2d94a04e2dn568EX03tjc|ecs.soton.ac.uk|4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk> <BANLkTikC06JkjJufNTaDA6r5X=Qrs7ozyw@mail.gmail.com>
In-Reply-To: <BANLkTikC06JkjJufNTaDA6r5X=Qrs7ozyw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 07 Jun 2011 08:25:55 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 12:56:31 -0000

From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of T=
J
Sent: Tuesday, June 07, 2011 7:33 AM
To: Tim Chown
Cc: v6ops@ietf.org WG; ietf@ietf.org
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> =
(Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Histo=
ric status) to Informational RFC

> It's time to remove the stabilisers on the IPv6 bicycle.
I agree, but get me native everywhere before taking away one connection mec=
hanism that does work.


This takes nothing away. It's not as if the day that this draft gets publis=
hed as an RFC, 6to4 stops working. IETF has moved other protocols to histor=
ical status before they were out of heavy use, with the expectation that it=
 would take some time for the alternatives to be deployed and existing impl=
ementations to be retired. This is specifically why we resisted the idea of=
 putting in a shutdown schedule or other flag day where the 6to4 prefixes g=
et null-routed, because it's likely to be different in each network and app=
lication.

"In order to limit the impact of end-users, it is
   recommended that operators retain their existing 6to4 relay routers
   and follow the recommendations found in
   [I-D.ietf-v6ops-6to4-advisory].  When traffic levels diminish, these
   routers can be decommissioned."

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From cb.list6@gmail.com  Tue Jun  7 06:58:39 2011
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 C7E4A11E808E; Tue,  7 Jun 2011 06:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.998
X-Spam-Level: 
X-Spam-Status: No, score=-2.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IeOl0B19OYcn; Tue,  7 Jun 2011 06:58:35 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD6A11E80F0; Tue,  7 Jun 2011 06:58:35 -0700 (PDT)
Received: by wwa36 with SMTP id 36so3340345wwa.13 for <multiple recipients>; Tue, 07 Jun 2011 06:58:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=FPmSggJEpIbFwoT8dpNTDDr8CGt1aAOy7G42OaPsIuw=; b=IYsl1TIwT6XPRc/K7ay6HY3TLEtbIERVIWXk9PzkDWs/7NMWjjmXmRVQT0OdRtAbvY 7EcQqEZ4CPNvobc0YVYKwKs3iarnRDMNHrZhaiyPWoHDM9mqPnIZN8OLVwXhy0qw30Mo l3e9Z2Z02voGd51hhqAEjJZi9uscE+QxrkPvk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=lbOn+W2cJXjr6QTjPMkfw0LDaHu+Zfch2bgBM99JXVrftcCzu/a/YNkZl2Tjv5hPyK 3k9HfLJaUjMVniZznhRDxk53HBUS4ILjbV0TA4NejLA/JvLiTWdopRR13M9TiFq/yUYQ mH+3CEbyL4RnfkdrekKnS0zqndi1H2Lq3mZAo=
MIME-Version: 1.0
Received: by 10.216.241.132 with SMTP id g4mr2041569wer.9.1307455114179; Tue, 07 Jun 2011 06:58:34 -0700 (PDT)
Received: by 10.216.179.199 with HTTP; Tue, 7 Jun 2011 06:58:34 -0700 (PDT)
Received: by 10.216.179.199 with HTTP; Tue, 7 Jun 2011 06:58:34 -0700 (PDT)
In-Reply-To: <EMEW3|c03704711a0f54e1e9000b2d94a04e2dn568EX03tjc|ecs.soton.ac.uk|4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <BANLkTikaGbFASQfisP5=H3yXKgDUpdKEqA@mail.gmail.com> <4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk> <20110607063336.GO45955@Space.Net> <EMEW3|c03704711a0f54e1e9000b2d94a04e2dn568EX03tjc|ecs.soton.ac.uk|4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk>
Date: Tue, 7 Jun 2011 06:58:34 -0700
Message-ID: <BANLkTin-UocNpgLc-EaGG4RZ17uL-X0frg@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
From: Cameron Byrne <cb.list6@gmail.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=e0cb4e43d1b9a3f4fb04a51f9d41
X-Mailman-Approved-At: Tue, 07 Jun 2011 08:25:55 -0700
Cc: "v6ops@ietf.org WG" <v6ops@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 Jun 2011 13:58:39 -0000

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

On Jun 7, 2011 12:16 AM, "Tim Chown" <tjc@ecs.soton.ac.uk> wrote:
>
>
> On 7 Jun 2011, at 07:33, Gert Doering wrote:
>
> >
> > Do we really need to go through all this again?
> >
> > As long as there is no Internet Overlord that can command people to
> > a) put up relays everywhere and b) ensure that these relays are working,
> > 6to4 as a general mechanism for attachment to the IPv6 Internet is FAIL.
> >
> > If someone wants to use 6to4 to interconnect his machines over an IPv4
> > infrastructure (=6to4 on both ends), nobody is taking this away.
> >
> > Gert Doering
> >        -- NetMaster
>
> Exactly.
>
> Less than 1% of the IPv6 traffic reaching us is 6to4. And 6to4 in its
6to4-to-native mode is proven to be highly unreliable. It seems highly
preferable to have that 1% wait for native IPv6 to be available to them,
rather than being used as a reason by the bigger content providers for
holding back production deployment, which is what we all want to see.
>
> It's time to remove the stabilisers on the IPv6 bicycle.
>

+1. Let's move on and not repeat this tired discussion.

Cb

> Tim
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

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

<p><br>
On Jun 7, 2011 12:16 AM, &quot;Tim Chown&quot; &lt;<a href=3D"mailto:tjc@ec=
s.soton.ac.uk">tjc@ecs.soton.ac.uk</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; On 7 Jun 2011, at 07:33, Gert Doering wrote:<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; Do we really need to go through all this again?<br>
&gt; &gt;<br>
&gt; &gt; As long as there is no Internet Overlord that can command people =
to<br>
&gt; &gt; a) put up relays everywhere and b) ensure that these relays are w=
orking,<br>
&gt; &gt; 6to4 as a general mechanism for attachment to the IPv6 Internet i=
s FAIL.<br>
&gt; &gt;<br>
&gt; &gt; If someone wants to use 6to4 to interconnect his machines over an=
 IPv4<br>
&gt; &gt; infrastructure (=3D6to4 on both ends), nobody is taking this away=
.<br>
&gt; &gt;<br>
&gt; &gt; Gert Doering<br>
&gt; &gt; =A0 =A0 =A0 =A0-- NetMaster<br>
&gt;<br>
&gt; Exactly.<br>
&gt;<br>
&gt; Less than 1% of the IPv6 traffic reaching us is 6to4. And 6to4 in its =
6to4-to-native mode is proven to be highly unreliable. It seems highly pref=
erable to have that 1% wait for native IPv6 to be available to them, rather=
 than being used as a reason by the bigger content providers for holding ba=
ck production deployment, which is what we all want to see.<br>

&gt;<br>
&gt; It&#39;s time to remove the stabilisers on the IPv6 bicycle.<br>
&gt;</p>
<p>+1. Let&#39;s move on and not repeat this tired discussion.=A0 </p>
<p>Cb<br></p>
<p>&gt; Tim<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; v6ops mailing list<br>
&gt; <a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops">https://www.ie=
tf.org/mailman/listinfo/v6ops</a><br>
</p>

--e0cb4e43d1b9a3f4fb04a51f9d41--

From wesley.george@twcable.com  Tue Jun  7 07:39:54 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CCD321F8446; Tue,  7 Jun 2011 07:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.313
X-Spam-Level: 
X-Spam-Status: No, score=-0.313 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hh7Tkj99sWIr; Tue,  7 Jun 2011 07:39:53 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 2D4BC21F8441; Tue,  7 Jun 2011 07:39:53 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.65,332,1304308800"; d="scan'208";a="235240644"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 07 Jun 2011 10:46:52 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.29]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Tue, 7 Jun 2011 10:39:52 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: Keith Moore <moore@network-heretics.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 7 Jun 2011 10:39:51 -0400
Subject: RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Thread-Index: Acwkbm4HzRgmGLCeQW6rooVHG8gmQQAo1VsQ
Message-ID: <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>
In-Reply-To: <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 07 Jun 2011 08:25:56 -0700
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 14:39:54 -0000

At the risk of rehashing discussion from WGLC...
Ole has addressed some of your points, I'll address a few others below inli=
ne.

From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of K=
eith Moore
Sent: Monday, June 06, 2011 1:22 PM
To: ietf@ietf.org
Cc: v6ops@ietf.org; IETF-Announce
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> =
(Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Histo=
ric status) to Informational RFC

6to4 still has many valid use cases, and there is not a suitable replacemen=
t for it that has been deployed.  Until there is a suitable replacement, or=
 until there is widespread ISP support for native IPv6, reclassification of=
 this document to Historic is premature.  (6rd is not a suitable replacemen=
t for 6to4, as it is intended for very different use cases than 6to4.)

WEG> Please substantiate these claims. What are the use cases, and why are =
there no other solutions for those specific use cases? What is considered "=
widespread ISP support for native IPV6"?

"The IETF sees no evolutionary future for the mechanism and it is not recom=
mended to include this mechanism in new implementations."

6to4 never was intended to have an "evolutionary future".  It was always in=
tended as a near-term solution to allow consenting hosts and networks to in=
terchange IPv6 traffic without prior support from the IPv4 networks that ca=
rry the traffic.   It is premature to recommend that 6to4 be removed from i=
mplementations.  We do not know how long it will take ISPs to universally d=
eploy IPv6.  Until they do, there will be a need for individuals and enterp=
rises using IPv6-based applications to be able to exchange IPv6 traffic wit=
h hosts that only have IPv4 connectivity.

WEG> As was discussed in the WGLC for this document, enterprise application=
s will not realistically use 6to4 as a means to reach IPv6 for business cri=
tical applications. It's simply not reliable enough. It's also probably unl=
ikely that those will go directly to IPv6-only vs using dual-stack to ease =
that transition. Individuals and Enterprises that use IPv6-only application=
s will need to make IPv6 service a non-negotiable requirement for their ISP=
s, networks, and devices rather than hoping that 6to4 works.

All of the criticisms in section 3 have to do with the use of relays to exc=
hange traffic between 6to4 and native IPv6.   In many cases the criticisms =
are overbroad.   Not all uses of 6to4 involve relays.  For some of those th=
at do need to use relays, it is not necessarily the case that the relay is =
operated by an unknown third-party.

WEG> Again, please substantiate this with examples of implementations that =
are actively using non-relay 6to4. Also, the number of applications of 6to4=
 that can be guaranteed to avoid any unknown 3rd party relays is extremely =
limited due to the nature of anycast and 6to4's asymmetric routing. The pro=
tocol action requested in this draft in no way prevents one or more consent=
ing networks from using 6to4 and continuing to run relays for their local t=
raffic indefinitely - in fact, it even provides a reference to a document t=
o show them how to make it work as well as possible. It is simply saying th=
at it's not a good idea.

The recommendations to treat 6to4 as a service of last resort will do harm =
to users and applications using it.   A better recommendation is for hosts =
to disable 6to4 by default.

WEG> this seems to be to be splitting hairs. Please explain the distinction=
 you're making here. Disable by default means never use. Use as last resort=
 means use when no better IP connectivity is available. I would think if yo=
u insist that 6to4 must stick around you'd prefer it to be enabled. I under=
stand that there are different values of "better" but if 6to4 works, this m=
eans that the host is not behind a NAT, and therefore by most definitions, =
its IPv4 connectivity would be better than 6to4. If it's behind an IPv4 NAT=
, and therefore IPv6 connectivity would be better (especially if there are =
one or more applications that work via IPv6 but not via IPv4 + NAT) then 6t=
o4 won't work in lieu of IPv6 connectivity anyway.

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From brian.e.carpenter@gmail.com  Tue Jun  7 08:45:23 2011
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 B891322800B; Tue,  7 Jun 2011 08:45:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.92
X-Spam-Level: 
X-Spam-Status: No, score=-102.92 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5skNXnit5OPk; Tue,  7 Jun 2011 08:45:23 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 25A1E228006; Tue,  7 Jun 2011 08:45:23 -0700 (PDT)
Received: by gyf3 with SMTP id 3so2752485gyf.31 for <multiple recipients>; Tue, 07 Jun 2011 08:45:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=unmanW0s+Sfwp/bghJyiKm36AQSpOs42IoxY2ehs1Yo=; b=smrxQcGj6OFFq5UU8Er6micnHZ34VkUtQ6/XbIB53Yoj447j1EtzxtS4XTIVddAFY5 FCbJx7W3F5L3VRbpaaEBIPF+I5wXJmY240j9rRuea7D/+oXSCAB9XVqIRrMHorxtBdgC TBecpFY8NOxlwhDQBdm4hXNM+is2AUmIJs0lo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=YbZQdHZx6tnHcm48mJKA1OueD2+6uWpFVNq/gBVyPT3Don69xf9VBG5mHd6ycUk+9M zcWgurjqUchZpZrngHWiknnmVGzK1ZYhawY/6FtX2OWLrgMB1Mv8B3R+ww8QJsUtWylP HMIxPfN2/hd4FXP0X8iJH9pYgHPVTgJumF40I=
Received: by 10.236.192.228 with SMTP id i64mr1135398yhn.111.1307461522680; Tue, 07 Jun 2011 08:45:22 -0700 (PDT)
Received: from [10.71.0.232] ([12.68.183.2]) by mx.google.com with ESMTPS id w70sm206025yhl.45.2011.06.07.08.45.06 (version=SSLv3 cipher=OTHER); Tue, 07 Jun 2011 08:45:21 -0700 (PDT)
Message-ID: <4DEE477C.9040709@gmail.com>
Date: Wed, 08 Jun 2011 03:45:00 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4 to	Historic status) to Informational RFC
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com>
In-Reply-To: <20110606162326.26262.53944.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 15:45:23 -0000

After a fair amount of thought, I have decided that I support
this document without reservation.

I support the recommendation that RFC 3056/3068 support should be off
by default in CPEs; the reasons for this are clear enough in my companion
draft. Specifically, I support the choice of "SHOULD NOT enable" (rather
than MUST NOT) because it leaves open the option for a CPE or host vendor to
enable RFC 3056/3068 by default if there is a sound reason to do so for a
specific product.

I support the recommendation to reclassify RFC 3056 as Historic,
because its time is past. The reason for inventing 6to4 in the
first place was for the benefit of customers whose ISPs could
not deploy IPv6. There is now no reason or excuse for a consumer
ISP to fail to deploy IPv6 for customers, so it is entirely
reasonable to consider the technique as Historic. This has no
impact on current successful use of 6to4 - the recommendation is
to retain existing relays "until traffic diminishes" and to follow
appropriate operational recommendations meanwhile. As my companion
draft indicates, relays advertising the 2002::/16 prefix are needed
as long as there is residual 6to4 traffic in the network.

Regards
   Brian Carpenter (co-author of RFC 3056)

From paul.hoffman@vpnc.org  Tue Jun  7 09:38:53 2011
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 1FF1711E807A; Tue,  7 Jun 2011 09:38:53 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53TZpTebZwSl; Tue,  7 Jun 2011 09:38:52 -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 E75A511E8193; Tue,  7 Jun 2011 09:38:51 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p57GcjUe094182 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Jun 2011 09:38:46 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>
Date: Tue, 7 Jun 2011 09:38:47 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <406033A9-BDB9-406C-84E9-194B1BF7B21C@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>
To: rontlv <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 16:38:53 -0000

On Jun 7, 2011, at 3:56 AM, rontlv wrote:

> The IANA registry is in
> =
http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml#idnabis-=
ta
> bles-properties
> I saw that in the beginning it has as reference RFC 5892 for the whole
> table. Will it stay this way after the change proposed in this draft =
and
> just the three individual values will change based on 1.1, 1.2 and =
1.3? or
> are there no changes in the IANA registry at all. This is unclear to =
me
> according to the section 3 of your draft.

The table will likely change, based on the input of the expert reviewer. =
I assume that a reference to this RFC-to-be would be added to the top of =
the table, next to "[RFC5892]". That is, this would be an additional =
reference, not a replacement. But that's up to IANA.

> Section 5.1 of RFC5892 says "If non-backward-compatible changes or =
other
> problems arise during the
>   creation or designated expert review of the table of derived =
property
>   values, they should be flagged for the IESG." . My question was if =
the
> change is backward compatible. The 5892bis draft does not say it.

The draft says:
   This imply the derived property value differs
   depending on whether the property definitions used are from Unicode
   5.2 or 6.0.
We intended that as "non-backwards-compatible"; we can change the =
wording to make that explicit.

--Paul Hoffman


From moore@network-heretics.com  Tue Jun  7 11:20:24 2011
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 C50B511E811F; Tue,  7 Jun 2011 11:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.151,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id desgCW1UYZfz; Tue,  7 Jun 2011 11:20:22 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id B0BE111E8092; Tue,  7 Jun 2011 11:20:22 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id BA96822433; Tue,  7 Jun 2011 14:20:21 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 07 Jun 2011 14:20:21 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=4+es+ZtqsvVOFTdqMrxSa9UGR6Q=; b=LVJQZhUQXQrvxUmiG7DGXWk1M6ig+IAnCtRtPGrTIT608XJHhTndVPGG7GtufhIdRdriSbQ98H0PdM8ZlgJQWekcMEraMwmx6fcvTSen2lgaIIMfK67wJntXMq6Jrwbdo1+yIJ+/VirK1N2Z0e+sxhFBPafpSa6CgN8DvJdUqds=
X-Sasl-enc: j9Esr1JWmM3TzQ9499QdhTMjuAxJaIFJrzjbWv5i/wjM 1307470820
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 35A644047D6; Tue,  7 Jun 2011 14:20:20 -0400 (EDT)
Subject: Re: Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org>
Date: Tue, 7 Jun 2011 14:20:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations Working Group <v6ops@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 Jun 2011 18:20:24 -0000

On Jun 7, 2011, at 4:48 AM, Ole Troan wrote:

> I'm loathe to go through this discussion again. let me just respond to =
some of the points you make, and then agree that we disagree.

I'm also loathe to go through the discussion again.  It shouldn't be =
necessary.  6to4 has long been useful, and continues to be useful, for =
some cases.  It's appropriate to document problems with 6to4, perhaps =
revise its applicability based on experience, and also to publish =
recommendations for how to manage 6to4 relays, and to urge removal of =
broken relays and/or filtering of their routing advertisements.   But =
deprecating it is entirely premature.  (When I recently asked local ISPs =
when they'll be offering IPv6 support, their answer was "what?". )

>> (It could be argued that reclassification of RFC 3068 (by itself) to =
Historic is appropriate, but that would require a separate document and =
last call.)
>>=20
>> In addition, this document is misleading and perhaps even =
vituperative.    For instance:
>>=20
>> "There would appear to be no evidence of any substantial deployment =
of the variant of 6to4 described in [RFC3056]."
>> This statement is blatantly false. 6to4 is supported by every major =
desktop and server platfrom that is shipping today, and has been =
supported for several years.
>=20
> incorrect. there is no evidence that the  _managed_ model of 6to4 =
described in rfc3056 has any deployment.
> that's the model where relay operators advertise what parts of the =
6to4 space they are routing. with BGP neighborships between managed and =
participating relays.
>=20
> _deployment_ not _support_.

The recommendations of the proposal are overkill anyway.  But assuming =
there's some merit in writing an applicability statement for 6to4 (and I =
think there might be), this text should be clearer and more balanced.

And I'm not sure where you get the idea that RFC 3056 recommends that =
relay operators advertise what parts of the 6to4 space they are routing. =
 3056 doesn't say anything about BGP advertisements for IPv4, as 3056 =
assumes there will be a manually configured relay router.   As for =
advertisement of IPv6 prefixes, the idea has always been that we didn't =
want to incorporate the v4 routing table into v6, so 3056 specifically =
says that the only prefix advertised in BGP should be 2002::/16.  =
(Obviously no such prefix should be advertised if the router isn't =
willing and able to route to the entire 2002::/16 space, i.e. arbitrary =
addresses on the public IPv4 network.)

>> "The IETF sees no evolutionary future for the mechanism and it is not =
recommended to include this mechanism in new implementations."
>>=20
>> 6to4 never was intended to have an "evolutionary future".  It was =
always intended as a near-term solution to allow consenting hosts and =
networks to interchange IPv6 traffic without prior support from the IPv4 =
networks that carry the traffic.   It is premature to recommend that =
6to4 be removed from implementations.  We do not know how long it will =
take ISPs to universally deploy IPv6.  Until they do, there will be a =
need for individuals and enterprises using IPv6-based applications to be =
able to exchange IPv6 traffic with hosts that only have IPv4 =
connectivity. =20
>>=20
>> All of the criticisms in section 3 have to do with the use of relays =
to exchange traffic between 6to4 and native IPv6.   In many cases the =
criticisms are overbroad.   Not all uses of 6to4 involve relays.  For =
some of those that do need to use relays, it is not necessarily the case =
that the relay is operated by an unknown third-party. =20
>>=20
>> The fact that some firewalls block protocol 41 traffic causes =
problems for many tunneling solutions, not just 6to4; yet this document =
appears to recommend some tunneling solutions while trashing 6to4.
>=20
> it is the unmanaged aspect of 6to4 deployment that exhibits the most =
problems. a manually configured managed point to point tunnel may also =
be blocked in a firewall, but then the operator will have to sort that =
out. 6to4 has no operator.

Indeed, that is one of its main virtues.  6to4 decouples application =
deployment of v6 from network deployment of v6, and helps reduce the =
"chicken or egg" problem.

(At least, that's the intent.  Reality is that 6to4 does have some =
impact on the network, at least where relay routers that publicly =
advertise prefixes through BGP are concerned.  But 6to4 is useful - =
admittedly in corner cases - even without relay routers.)

> Teredo is similar in many aspects to 6to4, but there is little =
evidence that it causes the same problems. largely because it is the =
choice of last resort in implementations and it hasn't/can't be enabled =
by default in CPEs.

Bogus argument.  Teredo has a different set of problems than 6to4 - =
higher overhead, not as scalable, dependent on a single provider for =
relays, not as widely deployed in hosts, etc.  If you're seeing fewer =
problems with Teredo, it's because it's not used as much as 6to4 is (in =
part because it has more problems) - not because there are fewer =
problems with it overall.   In other words, you're blaming 6to4 for its =
relative success.

I think it's fair to say that 6to4 didn't anticipate the degree to which =
relay routers and their BGP advertisements need to be monitored, and it =
failed to make recommendations for this.  But the same is true for IP.  =
When you get a BGP advertisement for a prefix that goes to a router that =
drops the packets, you have to deal with it.  When you get a BGP =
advertisement for a 6to4 router that isn't working properly, you have to =
deal with that too.  The 6to4 relay problem may appear worse than the =
normal bogus route advertisement case because all of the 6to4 related =
bogus BGP advertisements are for the same two address prefixes (one IPv4 =
and one IPv6).  But from where I sit, I can't tell that it's a worse =
problem overall.

>> The recommendations to treat 6to4 as a service of last resort will do =
harm to users and applications using it.   A better recommendation is =
for hosts to disable 6to4 by default. =20
>>=20
>> This document appears to make the mistake of assuming that the =
purpose of applications using IPv6 is to interoperate with the existing =
Internet.  I have maintained for many years that it is new applications, =
or existing applications that can't tolerate widespread deployment of =
IPv4 NAT, that will drive use of IPv6.   I therefore believe that it is =
inappropriate to judge 6to4 merely by how well it works in scenarios =
where it is being used to talk to applications that work well over IPv4 =
NAT such as HTTP.   The Internet is much more diverse than that, and =
will become even more diverse as IPv6 enjoys wider deployment.
>=20
> 6to4 does not work through IPv4 NATs.

6to4 can work through IPv4 NATs.  Some NATs support 6to4 (and act as =
NATs for v4, routers for v6).  Other NATs can be manually configured to =
pass protocol 41, and to have that traffic handled internally to the =
interior network.

Admittedly, 6to4 does not work though LSN.   I see that as a bug in LSN, =
if it doesn't provide a well-defined way for customers to get equivalent =
functionality to 6to4.  =20

>> It is also premature to remove references to 6to4 from RFC 5156bis, =
for IANA to mark the prefix and DNS zones as deprecated.  This will only =
cause confusion and difficulty for legitimate continued uses of 6to4.
>=20
> the purpose of the text in the document is to ensure that the =
deprecated prefixes are not reused before 6to4 has been phased out.

Just leave the allocation as-is until it really is time to deprecate =
6to4.  Frankly I don't expect that to happen for another 5-10 years, but =
I'd love to be surprised at the rapid acceleration in native IPv6 =
deployment.

Keith


From mrex@sap.com  Tue Jun  7 11:50:19 2011
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 3A46411E808A; Tue,  7 Jun 2011 11:50:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.424
X-Spam-Level: 
X-Spam-Status: No, score=-8.424 tagged_above=-999 required=5 tests=[AWL=1.825,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uabB+UQ56xy8; Tue,  7 Jun 2011 11:50:17 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF6A11E807A; Tue,  7 Jun 2011 11:50:17 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p57IoE4R017314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Jun 2011 20:50:14 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201106071850.p57IoDhb011453@fs4113.wdf.sap.corp>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
To: wesley.george@twcable.com (George Wesley)
Date: Tue, 7 Jun 2011 20:50:13 +0200 (MEST)
In-Reply-To: <34E4F50CAFA10349A41E0756550084FB067B72F8@PRVPEXVS04.corp.twcable.com> from "George, Wesley" at Jun 7, 11 08:56:27 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: v6ops@ietf.org, 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: Tue, 07 Jun 2011 18:50:19 -0000

George, Wesley wrote:
> 
> > It's time to remove the stabilisers on the IPv6 bicycle.
> 
> This takes nothing away. It's not as if the day that this draft gets
> published as an RFC, 6to4 stops working.


In my personal perception, the "historic" status used to be a technical
characterization to indicate that 

  (1) a protocol or technology has been fully replaced by some newer
      protocol and there is no reason to continue using the original
      technology anymore because the successor can be used in each
      of the original usage scenarios today

  (2) the protocol/technology has been largely put out of use, and its
      active use has dropped to marginal levels (like less than 1% of the
      original active use)

Personally, I have never conciously used anything related to IPv6 so
far, so for me it is difficult to comment, but what has been said
looks to me that neither (1) nor (2) apply to 6to4.

The user base seems to have always been small, and most of the users
of 6to4 simply did _not_ have an alternative -- and its current
users still do _not_ have an alternative today.

Classification of 6to4 as historic is appropriate use of the IETF process,
because it would be a political, but not an accurate technical statement.


-Martin

From ron.even.tlv@gmail.com  Tue Jun  7 12:30:45 2011
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 D3EF011E8226; Tue,  7 Jun 2011 12:30:45 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LrcUYX503Q1J; Tue,  7 Jun 2011 12:30:45 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 218C311E821F; Tue,  7 Jun 2011 12:30:44 -0700 (PDT)
Received: by vws12 with SMTP id 12so4897833vws.31 for <multiple recipients>; Tue, 07 Jun 2011 12:30:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=T9qDryzpUn7FCWEm53zONvJ4XGkui3huVr8hLvnDEm4=; b=qqxpj9Llfi0NUc3CbS2Myc/XKC+oVZ4l9FSWlaIGNGjHf6aUFIvKE9QzycBkW8AZGq mRQGv858rZQUNJpigaU16kirgSKfMQvRczXId1VIHbQTKKUlJSK3UVeNhD/pVfBUY/kZ OMEDi+w5tGAv/VxNq829XphewosSE60ivPbD0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=GW9+371tquc6xl4UpP61y4yWfH0oCc6H1bUhVWdoaLtXwB+fwsHjR6qm61iP3TePHi 7YmOh9Uyvvh16CMLUZaKB4NkvHRUYmnsshrvSxdKHpdjUal9rHq4JWX2/DWIRE7DRo34 dQIv3vEqKJ4NbtArmMd5I2bIDNyk2fqK69bWs=
Received: by 10.52.175.129 with SMTP id ca1mr184559vdc.168.1307475042749; Tue, 07 Jun 2011 12:30:42 -0700 (PDT)
Received: from YOUR6108 (user-0ccehtm.cable.mindspring.com [24.199.71.182]) by mx.google.com with ESMTPS id cf7sm223129vdb.14.2011.06.07.12.30.41 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Jun 2011 12:30:41 -0700 (PDT)
From: "rontlv" <ron.even.tlv@gmail.com>
To: "'Paul Hoffman'" <paul.hoffman@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <406033A9-BDB9-406C-84E9-194B1BF7B21C@vpnc.org>
In-Reply-To: <406033A9-BDB9-406C-84E9-194B1BF7B21C@vpnc.org>
Subject: RE: Gen-ART LC review of draft-faltstrom-5892bis-04
Date: Tue, 7 Jun 2011 22:30:40 +0300
Message-ID: <4dee7c61.a75b340a.22ed.1857@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwlMWG4EDYJW5yAR9WCStSlitXx4AAF7Gow
Content-Language: he
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 19:30:46 -0000

Hi Paul,
My understanding that the new value does not replace the current one since
5892bis is not updating rfc5892. So should the IANA registry reflect that
you are not replacing the current value or is my understanding wrong
Roni Even

> -----Original Message-----
> From: Paul Hoffman [mailto:paul.hoffman@vpnc.org]
> Sent: Tuesday, June 07, 2011 7:39 PM
> To: rontlv
> Cc: draft-faltstrom-5892bis.all@tools.ietf.org; gen-art@ietf.org;
> 'IETF-Discussion list'
> Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
> 
> On Jun 7, 2011, at 3:56 AM, rontlv wrote:
> 
> > The IANA registry is in
> > http://www.iana.org/assignments/idnabis-tables/idnabis-
> tables.xml#idnabis-ta
> > bles-properties
> > I saw that in the beginning it has as reference RFC 5892 for the
> whole
> > table. Will it stay this way after the change proposed in this draft
> and
> > just the three individual values will change based on 1.1, 1.2 and
> 1.3? or
> > are there no changes in the IANA registry at all. This is unclear to
> me
> > according to the section 3 of your draft.
> 
> The table will likely change, based on the input of the expert
> reviewer. I assume that a reference to this RFC-to-be would be added to
> the top of the table, next to "[RFC5892]". That is, this would be an
> additional reference, not a replacement. But that's up to IANA.
> 
> > Section 5.1 of RFC5892 says "If non-backward-compatible changes or
> other
> > problems arise during the
> >   creation or designated expert review of the table of derived
> property
> >   values, they should be flagged for the IESG." . My question was if
> the
> > change is backward compatible. The 5892bis draft does not say it.
> 
> The draft says:
>    This imply the derived property value differs
>    depending on whether the property definitions used are from Unicode
>    5.2 or 6.0.
> We intended that as "non-backwards-compatible"; we can change the
> wording to make that explicit.
> 
> --Paul Hoffman
> 
> 
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 6186 (20110607) __________
> 
> The message was checked by ESET NOD32 Antivirus.
> 
> http://www.eset.com
> 
 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6188 (20110607) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 


From rdroms.ietf@gmail.com  Tue Jun  7 13:27:57 2011
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 3790511E8131 for <ietf@ietfa.amsl.com>; Tue,  7 Jun 2011 13:27:57 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2vbX-W3Zcb4G for <ietf@ietfa.amsl.com>; Tue,  7 Jun 2011 13:27:56 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 627FE228005 for <ietf@ietf.org>; Tue,  7 Jun 2011 13:27:56 -0700 (PDT)
Received: by pwi5 with SMTP id 5so60379pwi.31 for <ietf@ietf.org>; Tue, 07 Jun 2011 13:27:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=rzDwq3yva0XBU0+OJfAPEDO0H0iFcR0vzgv1hpiUiY0=; b=HlHOxiNyQNajLMIbWikv/hvR9tZxC+7oL2Oq0Y562NA0rUEi3ncKJCaXAHxI1pS6DV mcS0wHMS6dWeX1gALpmN0bKakYqfp3ewPv1uFqExsKC5aSFJD4xKlTbLT/5zq1xtlFL3 pccVa0F1ZxasrcX7ZEDxOkkIdel6l7btx8v6Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=nEPrJsYHt7LGOB6JiRadtftHkt11UyL/o78QLUMXrxgyms62SFfNVxGrLw15RtO71A yyOFlckbfMai92Y1kiMiyibW4f4pCuXZgx/rPlovbo1dU256qlSPguXQu3IUIR23eYRz yZ59h8rGAAhwDOh/oSM2qn3+uKoNdUm5N8dUE=
Received: by 10.68.20.106 with SMTP id m10mr422233pbe.137.1307478475651; Tue, 07 Jun 2011 13:27:55 -0700 (PDT)
Received: from [10.21.108.214] (128-107-239-233.cisco.com [128.107.239.233]) by mx.google.com with ESMTPS id y2sm365936pbi.51.2011.06.07.13.27.52 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Jun 2011 13:27:54 -0700 (PDT)
From: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Liaison and request for review of ITU-T document
Date: Wed, 8 Jun 2011 04:27:46 +0800
Message-Id: <666AC2E8-ECF9-4C64-98B3-839315ED56C3@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 20:27:57 -0000

The IETF has recently received a liaison from ITU-T Q5/SG-11 regarding a =
Draft Recommendation.  That liaison is available as =
https://datatracker.ietf.org/liaison/1054/.  The official liaison is =
available at =
https://datatracker.ietf.org/documents/LIAISON/file1232.pdf.

The liaison asks for IETF review of Draft Recommendation "Signalling =
protocols and procedures relating to Flow State Aware QoS control in a =
bounded sub-network of a NGN", which is available at =
https://datatracker.ietf.org/documents/LIAISON/file1231.pdf.  This note =
opens an IETF comment period on the document, ending midnight, anywhere =
on earth, 2011/7/5.  After the comment period, a summary will be =
prepared and returned in a liaison to ITU-T Q5/SG-11.

Of specific interest to the IETF are any ways in which the "signalling =
protocols and procedures" defined in the Draft Recommendation might =
interact with existing IETF Internet protocols.  We are especially =
interested in potential adverse interactions or interference with IETF =
Internet protocols.  The technical merits of the "signalling protocols =
and procedures" defined in the Draft Recommendation are of interest =
inasmuch as the IETF community might provide technical advice and =
recommendations to improve the Draft Recommendation itself.

Please respond with any comments on the Draft Recommendation to =
ietf@ietf.org.  Thanks in advance for your review of the Draft =
Recommendation.

- Ralph Droms, Internet Area Director
  for the IESG



From paul.hoffman@vpnc.org  Tue Jun  7 14:43:55 2011
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 3D87C11E819F; Tue,  7 Jun 2011 14:43:55 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pZaeGIemDXVW; Tue,  7 Jun 2011 14:43:54 -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 3A58E11E8071; Tue,  7 Jun 2011 14:43:53 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p57LhjP3013927 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Jun 2011 14:43:45 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>
Date: Tue, 7 Jun 2011 14:43:46 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>
To: rontlv <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 21:43:55 -0000

On Jun 7, 2011, at 3:56 AM, rontlv wrote:

> The IANA registry is in
> =
http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml#idnabis-=
ta
> bles-properties
> I saw that in the beginning it has as reference RFC 5892 for the whole
> table. Will it stay this way after the change proposed in this draft =
and
> just the three individual values will change based on 1.1, 1.2 and =
1.3? or
> are there no changes in the IANA registry at all. This is unclear to =
me
> according to the section 3 of your draft.
>=20
> Section 5.1 of RFC5892 says "If non-backward-compatible changes or =
other
> problems arise during the
>   creation or designated expert review of the table of derived =
property
>   values, they should be flagged for the IESG." . My question was if =
the
> change is backward compatible. The 5892bis draft does not say it.

Ah, very good catch! My earlier comment about us listing this new RFC in =
the registry is, in fact, wrong.

When we wrote RFC 5892, we said:
   IANA has created a registry with the derived properties for the
   versions of Unicode released after (and including) version 5.2. =20
That's one registry that has the properties for most current version of =
Unicode at any given time. Thus, the registry would be updated *even if* =
we didn't publish 5892bis. We are not updating either 5892, nor the =
registry, by publishing 5892bis. We are simply giving IETF consensus =
advice about what we think the expert reviewer who updates the registry =
should consider.

Our IANA considerations in 5892bis are:
   IANA is to update the derived property value registry according to
   RFC 5892 and property values as defined in The Unicode Standard
   version 6.0.
That might sound like they are initiating the registry update, but they =
really aren't: the update was already specified in 5892. We can change =
the IANA considerations to reflect that:
   IANA will update the derived property value registry according to
   RFC 5892 and property values as defined in The Unicode Standard
   version 6.0, regardless of the content of this RFC.

--Paul Hoffman


From moore@network-heretics.com  Tue Jun  7 15:47:57 2011
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 92AAF11E8164; Tue,  7 Jun 2011 15:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.023
X-Spam-Level: 
X-Spam-Status: No, score=-2.023 tagged_above=-999 required=5 tests=[AWL=-1.425, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_210=0.6, J_CHICKENPOX_23=0.6, J_CHICKENPOX_24=0.6, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PyfQFubrFV0U; Tue,  7 Jun 2011 15:47:55 -0700 (PDT)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id AC97F11E8147; Tue,  7 Jun 2011 15:47:54 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id A4A602180D; Tue,  7 Jun 2011 18:47:52 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Tue, 07 Jun 2011 18:47:52 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=AvcFsQEIYTvtiOXvUyZMPUB4EBU=; b=WHbz8rQ+7q/dn1++t4ULD7ZgB/Ibb2mhoFFRw2+JGFp3+km7sr7J/vFeNee51FgRoU+PTAkJx5lwfSAz/C7RVVXD5eVrvLPFOUbF389lCeoNkMCE2TC4nOnQabSlv7XT1zh2E2PlXOxmFv+OqSKNpQ2ayMGy+etD1qxQ0gu8hS8=
X-Sasl-enc: e21TgKuK6l1kfvpjHTpeV5FqP2Mgn0J2hQQLLlXBL2Es 1307486868
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 0FDF044320A; Tue,  7 Jun 2011 18:47:47 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-18-614669036
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com>
Date: Tue, 7 Jun 2011 18:47:47 -0400
Message-Id: <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com>
To: "George, Wesley" <wesley.george@twcable.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 22:47:57 -0000

--Apple-Mail-18-614669036
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jun 7, 2011, at 5:27 PM, George, Wesley wrote:

>=20
> From: Keith Moore [mailto:moore@network-heretics.com]
> Sent: Tuesday, June 07, 2011 11:21 AM
> To: George, Wesley
> Cc: ietf@ietf.org; v6ops@ietf.org
> Subject: Re: [v6ops] Last Call: =
<draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection =
of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to =
Informational RFC
>=20
> WEG> Please substantiate these claims. What are the use cases, and why =
are there no other solutions for those specific use cases? What is =
considered "widespread ISP support for native IPV6"?
>=20
> KM>The best current use cases for 6to4 that I'm aware of are:
>=20
> KM>- Applications developers want to be forward thinking and develop =
IPv6 apps, but cannot get native IPv6 access.  6to4 allows them to =
develop those apps and test or use them in useful situations (i.e. =
outside of a lab) without having to configure a separate tunnel to every =
host involved.   Note that 6to4 is useful in this way even if all of the =
addresses used are 6to4 addresses, and the traffic therefore does not =
cross any relays between 6to4 and native IPv6.
>=20
> WEG> Exactly my point. this is a valid use case, but 6to4 is by no =
means the only way to solve it. Application developers are welcome to =
set up an IPv6 network to test their apps against.

Why are you trying to make life harder for developers of IPv6 =
applications?  There's no reason at all that an application developer =
should have to set up a special-purpose network just to test an IPv6 =
application.=20

> That doesn't require IPv6 connectivity to the outside world.

Realistic testing of applications needs to be done on real networks, or =
a least an approximation to real networks.  Testing IPv6 using 6to4 over =
public IPv4 obviously isn't perfect, but it's a hell of a lot more =
realistic than setting up a lab network and confining one's testing to =
that.

> If you have more than one of any modern computer on your LAN and you =
turn the right knobs, they can all talk to each other via IPv6 =
independent of any external IPv6 connectivity. You seem to want to draw =
this distinction between IPv6 between two hosts using 6to4 since that =
"works" and using 6to4 as a means to connect to the IPv6 Internet via =
relays, but then you conflate them by repeatedly complaining about lack =
of IPv6 service available from most ISPs and presenting 6to4 as a =
solution.

I've been using 6to4 on a regular, often daily, basis since the late =
1990s.   6to4 has allowed me to develop IPv6 applications and test them =
on real networks, and deploy them in limited circumstances.  6to4 has =
also allowed me to remotely access computers on my SOHO networks, using =
any application protocol that I chose to do so, with out-of-the-box =
hardware and software, without any application-specific proxies, and =
generally without any application-specific configuration.  None of these =
scenarios required a relay router.  All of them were, and continue to =
be, useful.

Yes, I've experienced on many occasions that using 6to4 to access =
dual-stack web servers doesn't always work so well.  Sometimes it picks =
a suboptimal path because the relay router isn't convenient.  Sometimes =
the v6 path doesn't work at all and the application has to time out and =
retry using v4.   But this never really bothered me much, because my =
purpose in using 6to4 wasn't to try to access services that I could get =
to via IPv4 anyway.  And neither, I suggest, is that a reasonable metric =
for evaluating 6to4 or any other IPv6 transition mechanism.   The metric =
for evaluating an IPv6 transition mechanism should be based on its =
effectiveness in accessing services that are IPv6 only.  =20

And sure, 6to4 is a sort of last resort for those services, except maybe =
for the other transition mechanisms that are worse: Teredo is often =
worse, configured tunnels are often worse, for all of the obvious =
reasons.  If your ISP offers you native IPv6 access you should probably =
use that instead, even if internally they use 6rd or some other =
tunneling scheme.  There's definitely benefit to having professional =
management and support (such as it is) for your IPv6 connectivity. =20

Yet, time and time again the argument gets made that 6to4 gets in the =
way of trying to access such services.  6to4 by itself is not the =
problem.  The problem is address selection rules that favor v6 over v4.  =
If the service is supported under v4, if it works fine through any NATs =
in the signal path, the application should probably use v4 to talk to =
that service.  And if the service is v6-only, and 6to4 is the best way =
of getting there that's available, you might as well try to use it.

> Further, I don't buy the "separate tunnel to every host..." thing. =
Tunneled IPv6 connectivity is widely available. All any developer needs =
to do if they can't get Native IPv6 and a tunneled application is deemed =
good enough for their testing purposes is connect both ends of their =
testing environment to their choice of tunnel broker, and through the =
magic of the internet, they're all connected to one another.

You seem to have this fixed idea of how applications should be tested =
and used, that is inconsistent with my experience.  "Both" ends of their =
testing environment?  What gives you the idea that there are only two =
ends?   Distributed development projects are quite commonplace, and can =
involve hundreds or even thousands of people, each at different sites.   =
Nor is there necessarily some sort of central network that everything =
connects to.  Nor should there be.=20

> KM> - Enterprises have applications that need to be able to =
communicate with large numbers of hosts spread over a diverse area.  =
IPv6 is clearly the way that they want to go, but it's not widely =
available at present.  6to4 provides them with a means of routing =
traffic to their hosts in the interim until widespread support for IPv6 =
exists.
>=20
> WEG> So do IPv6IP or GRE tunnels. Been using one at home for 3+ years =
now. And honestly, if this type of application is going to be =
enterprise-class, it needs to be in conjunction with ISP deployment of =
IPv6, not in spite of it.

What you're saying is that applications developers shouldn't bother with =
actually trying to use IPv6 until the ISPs get their act together and =
deploy it.  Well guess what?  The ISPs have let us down.  We've been =
waiting for 15 years for the ISPs to roll out IPv6, and for most of =
those 15 years they were all telling us that there were no applications =
for it.  Now the ISPs are scrambling to get IPv6 into their networks, =
and they want to sabotage the IPv6 mechanisms that we have in place even =
before they are actually offering product.

> KM> - Users (including enterprise users) who have small networks with =
IPv4 access (generally behind v4 NATs) can use 6to4 to allow them to =
remotely access individual hosts on those networks.  This can be done =
either with a NAT that also acts as a v6 router and supports 6to4 as an =
external connection, or by configuring the NAT to pass protocol 41 to a =
IPv6 router for the network, internal to the v4 NAT.
>=20
> WEG> Until CGN becomes common, in which case 6to4 doesn't work again. =
Also, that same NAT + v6 router combination could just as easily manage =
a static tunnel.

You're missing something.   I can connect directly from my mobile laptop =
to a machine in my home network using 6to4.  I didn't have to set up any =
static tunnel for either one.  Sure, I could do that, I could get =
tunnels from HE or some other source and route through them.  Why should =
I bother?  Why do I want to make my IPv6 traffic take any longer a route =
than necessary?  You've argued against 6to4 with relay routers because =
it's routing can be suboptimal, but the same is true of any other =
tunneling scheme.

> KM>Widespread IPv6 support for native IPv6 would be when native IPv6 =
is available everywhere that IPv4 access is available, from at least one =
provider, with quality (connectivity, reliability, support) =
approximately as good as IPv4, and at a reasonable price.  In other =
words, you can't expect applications to rely on native IPv6 until it's =
reliably available everywhere that they need to use it.
>=20
> WEG> So Widespread IPv6 has to have reliability and support equivalent =
to IPv4, yet you're saying that you can expect applications to rely on =
6to4 in the meantime despite evidence that it's unreliable, and the =
virtual guarantee that it won't be supported by the upstream ISP?

There's no such virtual guarantee.  =20

> And you and I disagree about the definition of widespread. I do not =
think that widespread means "every small ISP in every corner of the =
world supports it ubiquitously and at every price point." I think it =
means "it's available for a majority (>50%) of Internet service =
customers."

We can disagree about the meaning of the word "widespread", but the =
practical fact is that you can't expect people to give up something that =
works for them until you can provide them something that works better =
for them.  "Available to 50% of Internet service customers" is =
equivalent to a very small percent probability of native connectivity =
being able to replace 6to4 connectivity in a scenario where 6to4 is =
currently working.  And the more hosts involved, the smaller that =
probability is.=20

> WEG> As was discussed in the WGLC for this document, enterprise =
applications will not realistically use 6to4 as a means to reach IPv6 =
for business critical applications. It's simply not reliable enough. =
It's also probably unlikely that those will go directly to IPv6-only vs =
using dual-stack to ease that transition. Individuals and Enterprises =
that use IPv6-only applications will need to make IPv6 service a =
non-negotiable requirement for their ISPs, networks, and devices rather =
than hoping that 6to4 works.
>=20
> KM> With respect, the v6ops working group is not in a good position to =
judge whether enterprise applications will use 6to4.   Operators rarely =
have a good understanding of what individual application users or =
developers need.  They tend to focus mostly on the applications that =
generate the most traffic,  or cause them particular amounts of trouble, =
or the ones that their biggest customers need.  Problem is, those aren't =
the only applications that are important.  Every application is =
important to its users, no matter how much or little traffic (or =
revenue) it generates.
>=20
> WEG> I'm not going to touch the "operators don't know what they're =
talking about" part of your comment, except to note that it's a gross =
generalization that won't help your argument, and wonder how you are =
uniquely qualified to know better than the rest of us...

Seems to me it's the v6ops people who are making the gross =
generalizations.  I'm mostly pointing out exceptions to those gross =
generalizations that have been made here and in v6ops. =20

> I am simply saying that I do not for a second believe that those same =
applications that are so important to that user community are at the =
same time unimportant enough that they're the sacrificial lamb that has =
to go IPv6-only when the majority of that user community, no matter how =
small, doesn't have native IPv6 access yet.

You have absolutely no idea which applications will be important to the =
user community tomorrow.   Who knows what will be the next netflix, =
twitter, facebook, youtube, ... ?   The Internet is successful not =
because it supports some small number of apps that operators think are a =
good idea; it's successful because it (at least as originally =
architected) can support a wide range of apps without operators having =
to bless them.=20

> This is the essence of the IPv6 content vs access chicken/egg problem, =
and 6to4 absolutely will not break the impasse. 6to4 breakage is the =
most common thing that content providers cite as reasons why they don't =
just go dual-stack. Why would an enterprise application be any =
different?

It doesn't really matter much whether "content-providers" (as in web =
site providers) go "dual stack" now.  Sure, they need to be gearing up =
for it, making sure that they understand it, making sure that their =
networks support it.  (Or maybe they'll just install v6-to-v4 proxies at =
their borders so that they can keep providing good customer service in =
the face of LSN-induced brain damage on the public v4 network.)   But =
assuming their applications work through LSN, they're going to keep =
supporting v4 for a long time anyway, because that's the established =
base of interoperability for their products and services.   Existing =
"content providers" are not going to drive adoption of IPv6.   They're =
going to follow it.  Web and email will be the last applications to =
migrate.  New content might appear on v6, and that might drive adoption. =
 But to the extent that it drives adoption, it probably won't be from =
the currently established players that already have plenty of v4 =
addresses and infrastructure.  It will be from new things that take =
advantage of the niches created by IPv6 that didn't exist before.

> KM> 6to4 is as reliable as IPv4 is, if it isn't asked to cross a relay =
router.
> WEG> perhaps (with the exception of MTU issues that plague any =
tunneled protocol), but you continue to not provide any examples of this =
being used anywhere, in the face of significant evidence that 6to4 is =
horribly unreliable *with* a relay. So this gets filed in the same place =
as my 100% secure file server which happens to be unplugged from power =
and network and encased in 10ft of concrete. Theoretically perfect, but =
otherwise practically useless.

What is "anywhere" to you?  You seem to have a content-centric view of =
the Internet.  I do not.   Meanwhile, you persist in saying that =
something that I've used regularly for more than 10 years, to do useful =
work, isn't being used anywhere.   I keep seeing figures that 6to4 =
comprises 40-some-odd percent of IPv6 traffic, while native IPv6 is =
around 10 percent.  By your logic, native v6 should be deprecated =
because it doesn't work reliably and it's not being used anywhere.

> KM> And there are valid reasons to use 6to4 even where IPv4 =
connectivity already exists.
> WEG> One would hope you wouldn't be trying to use 6to4 where IPv4 =
connectivity *doesn't* exist.

Right, but the point is that there are valid use cases for 6to4 even =
where you have IPv4 connectivity for part or even all of the network =
that you're using.

> KM>Even in cases where 6to4 traffic must cross a relay router, =
sometimes it's the best solution available.
> WEG> Perhaps, but again, we're talking about such a small percentage =
of the time that the cure ends up being worse than the disease. I love =
orphans and lost causes as much as the next guy, but really...

The disease is the current IPv4 network with NATs and LSNs and a paucity =
of address space.  6to4 is like a drug that can let some valuable v6 =
applications grow (even if a bit stunted) and survive until there's once =
again a network that will support them.  Sure, there are some side =
effects and contraindications.  But it's useful when used with awareness =
of its limitations.  You're arguing that it should be discouraged =
because it causes some problems.  Indeed it does.  But LSN also causes =
problems, and is a bigger dead-end than 6to4, and it's full steam ahead =
with that.  At least 6to4 is designed to ease transition to a saner =
world, which is a lot more than I can say for LSN.

> KM>All of the criticisms in section 3 have to do with the use of =
relays to exchange traffic between 6to4 and native IPv6.   In many cases =
the criticisms are overbroad.   Not all uses of 6to4 involve relays.  =
For some of those that do need to use relays, it is not necessarily the =
case that the relay is operated by an unknown third-party.
>=20
> WEG> Again, please substantiate this with examples of implementations =
that are actively using non-relay 6to4.  Also, the number of =
applications of 6to4 that can be guaranteed to avoid any unknown 3rd =
party relays is extremely limited due to the nature of anycast and =
6to4's asymmetric routing.  The protocol action requested in this draft =
in no way prevents one or more consenting networks from using 6to4 and =
continuing to run relays for their local traffic indefinitely - in fact, =
it even provides a reference to a document to show them how to make it =
work as well as possible. It is simply saying that it's not a good idea.

>=20
> KM> Application implementations shouldn't care whether they're using =
relay 6to4, non-relay 6to4, or 6to4 at all.  Application implementations =
should at most care that they're using IPv6 rather than IPv4, and for =
some applications even this is not appropriate.
> Application deployments might well need to care how well their =
underlying networks work.  Ideally, they shouldn't have to care, but =
that's the world we're currently living in.
>=20
> WEG> First, you're hair-splitting between implementation and =
deployment. However you want to call it, I'm referring to "situations" =
where 6to4 is in use without relays and is performing reliably on a =
business-critical use to justify your assertion that we shouldn't toss =
out this part of 6to4 along with the anycast/relay part because it's =
still so useful.

You're attacking 6to4 on the basis of irrelevancies.  As for =
business-critical, that's up to the business using it to determine =
whether it works well enough for their purposes.  There are a lot of =
technically dubious practices used in business critical applications and =
networks.

> WEG> I agree that properly written applications are IP =
version-agnostic. There is only a question of whether they work through =
one or more layers of IPv4 NAT, or they don't. If they don't, then the =
solution is IPv6. If IPv6 isn't available, you have many major content =
providers saying that they absolutely don't see 6to4 as an acceptable =
substitute, meaning that your supposed application of 6to4 as a fix for =
this problem is so niche as to be harmful rather than helpful.

The notion that "properly written applications are IP version-agnostice" =
is naive and overbroad.  IPv6 works differently enough from IPv4 that =
many applications cannot treat them the same.   Simple client-server =
apps, perhaps, can ignore their differences, but that's just a corner =
case.  =20

I have no doubt that many of those "major content providers" are correct =
when they don't see 6to4 as an acceptable substitute for them.  But the =
Internet doesn't exist just to support "major content providers".  So =
stop trying to sabotage something that works well enough for other =
users.

> Why are we having a World IPv6 Day? In part to shake loose the broken =
6to4 users that may not even know that 6to4 is enabled/broken so that =
content providers can be more confident that they can dual-stack their =
websites without risk of significant user impact due to breakage.

I'm looking forward to World IPv6 Day, and what will be learned from it. =
  But again, how well 6to4 works with "major content providers" is =
irrelevant.

> KM> The requested protocol action deprecates 6to4 and discourages its =
inclusion in future implementations.  That's harmful to applications and =
users for whom native IPv6 isn't available - which is to say, pretty =
much everyone at the moment.  When native IPv6 becomes widely available, =
it will then be appropriate to transition hosts and networks using 6to4 =
to native IPv6.  But even then, there will probably still be a need for =
host implementations
>=20
> WEG> Well, it'd be more harmful if there weren't alternatives.

There aren't any good ones.  Teredo and configured tunnels are worse in =
many ways; though they each have their use cases.  =20

> Also, assuming that the protocol is declared historical, we're now in =
a footrace between ISPs deploying IPv6 and equipment vendors removing =
support for 6to4 (or rolling out new products that don't support it in =
the first place). I think you're oversensationalizing both the impact of =
this draft and the lack of IPv6, given that nearly all major ISPs in the =
commercial space are currently offering or have a timeline to offer =
Native IPv6, and a large amount of the ISPs in the residential space =
have a timeline for deployment, many have already started trials.
> Finally, we're having problems with equipment that doesn't support =
IPv6 at all. 6to4 is not high on the priority list to implement compared =
with a functional IPv6 stack, meaning that on new gear, it likely won't =
get implemented until it's no longer necessary.

Gear that doesn't support IPv6 by now is pretty odd gear.     But I'm =
not going to tell you not to use it.  I'm just saying, if you want odd =
gear to work for you in your own specific use cases, don't try to =
sabotage other odd things that work for other people in their specific =
use cases.

Keith


--Apple-Mail-18-614669036
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jun 7, 2011, at 5:27 PM, George, Wesley =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div><br>From: Keith Moore =
[mailto:moore@network-heretics.com]<br>Sent: Tuesday, June 07, 2011 =
11:21 AM<br>To: George, Wesley<br>Cc: <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>Subject: Re: =
[v6ops] Last Call: &lt;draft-ietf-v6ops-6to4-to-historic-04.txt&gt; =
(Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to =
Historic status) to Informational RFC<br><br>WEG&gt; Please substantiate =
these claims. What are the use cases, and why are there no other =
solutions for those specific use cases? What is considered "widespread =
ISP support for native IPV6"?<br><br>KM&gt;The best current use cases =
for 6to4 that I'm aware of are:<br><br>KM&gt;- Applications developers =
want to be forward thinking and develop IPv6 apps, but cannot get native =
IPv6 access. &nbsp;6to4 allows them to develop those apps and test or =
use them in useful situations (i.e. outside of a lab) without having to =
configure a separate tunnel to every host involved. &nbsp;&nbsp;Note =
that 6to4 is useful in this way even if all of the addresses used are =
6to4 addresses, and the traffic therefore does not cross any relays =
between 6to4 and native IPv6.<br><br>WEG&gt; Exactly my point. this is a =
valid use case, but 6to4 is by no means the only way to solve it. =
Application developers are welcome to set up an IPv6 network to test =
their apps against. </div></blockquote><div><br></div>Why are you trying =
to make life harder for developers of IPv6 applications? &nbsp;There's =
no reason at all that an application developer should have to set up a =
special-purpose network just to test an IPv6 =
application.&nbsp;</div><div><br><blockquote type=3D"cite"><div>That =
doesn't require IPv6 connectivity to the outside world. =
</div></blockquote><div><br></div>Realistic testing of applications =
needs to be done on real networks, or a least an approximation to real =
networks. &nbsp;Testing IPv6 using 6to4 over public IPv4 obviously isn't =
perfect, but it's a hell of a lot more realistic than setting up a lab =
network and confining one's testing to =
that.</div><div><br></div><div><blockquote type=3D"cite"><div>If you =
have more than one of any modern computer on your LAN and you turn the =
right knobs, they can all talk to each other via IPv6 independent of any =
external IPv6 connectivity. You seem to want to draw this distinction =
between IPv6 between two hosts using 6to4 since that "works" and using =
6to4 as a means to connect to the IPv6 Internet via relays, but then you =
conflate them by repeatedly complaining about lack of IPv6 service =
available from most ISPs and presenting 6to4 as a =
solution.<br></div></blockquote><div><br></div><div>I've been using 6to4 =
on a regular, often daily, basis since the late 1990s. &nbsp; 6to4 has =
allowed me to develop IPv6 applications and test them on real networks, =
and deploy them in limited circumstances. &nbsp;6to4 has also allowed me =
to remotely access computers on my SOHO networks, using any application =
protocol that I chose to do so, with out-of-the-box hardware and =
software, without any application-specific proxies, and generally =
without any application-specific configuration. &nbsp;None of these =
scenarios required a relay router. &nbsp;All of them were, and continue =
to be, useful.</div><div><br></div><div>Yes, I've experienced on many =
occasions that using 6to4 to access dual-stack web servers doesn't =
always work so well. &nbsp;Sometimes it picks a suboptimal path because =
the relay router isn't convenient. &nbsp;Sometimes the v6 path doesn't =
work at all and the application has to time out and retry using v4. =
&nbsp; But this never really bothered me much, because <i>my purpose in =
using 6to4 wasn't to try to access services that I could get to via IPv4 =
anyway. &nbsp;</i>And neither, I suggest, is that a reasonable metric =
for evaluating 6to4 or any other IPv6 transition mechanism. &nbsp; The =
metric for evaluating an IPv6 transition mechanism should be based on =
its effectiveness in accessing services that are IPv6 only. =
&nbsp;&nbsp;</div><div><br></div><div>And sure, 6to4 is a sort of last =
resort for those services, except maybe for the other transition =
mechanisms that are worse: Teredo is often worse, configured tunnels are =
often worse, for all of the obvious reasons. &nbsp;If your ISP offers =
you native IPv6 access you should probably use that instead, even if =
internally they use 6rd or some other tunneling scheme. &nbsp;There's =
definitely benefit to having professional management and support (such =
as it is) for your IPv6 connectivity. =
&nbsp;</div><div><br></div><div>Yet, time and time again the argument =
gets made that 6to4 gets in the way of trying to access such services. =
&nbsp;6to4 by itself is not the problem. &nbsp;The problem is address =
selection rules that favor v6 over v4. &nbsp;If the service is supported =
under v4, if it works fine through any NATs in the signal path, the =
application should probably use v4 to talk to that service. &nbsp;And if =
the service is v6-only, and 6to4 is the best way of getting there that's =
available, you might as well try to use =
it.</div><div><br></div><blockquote type=3D"cite"><div>Further, I don't =
buy the "separate tunnel to every host..." thing. Tunneled IPv6 =
connectivity is widely available. All any developer needs to do if they =
can't get Native IPv6 and a tunneled application is deemed good enough =
for their testing purposes is connect both ends of their testing =
environment to their choice of tunnel broker, and through the magic of =
the internet, they're all connected to one =
another.<br></div></blockquote><div><br></div>You seem to have this =
fixed idea of how applications should be tested and used, that is =
inconsistent with my experience. &nbsp;"Both" ends of their testing =
environment? &nbsp;What gives you the idea that there are only two ends? =
&nbsp; Distributed development projects are quite commonplace, and can =
involve hundreds or even thousands of people, each at different sites. =
&nbsp; Nor is there necessarily some sort of central network that =
everything connects to. &nbsp;Nor should there =
be.&nbsp;</div><div><br><blockquote type=3D"cite"><div>KM&gt; - =
Enterprises have applications that need to be able to communicate with =
large numbers of hosts spread over a diverse area. &nbsp;IPv6 is clearly =
the way that they want to go, but it's not widely available at present. =
&nbsp;6to4 provides them with a means of routing traffic to their hosts =
in the interim until widespread support for IPv6 exists.<br><br>WEG&gt; =
So do IPv6IP or GRE tunnels. Been using one at home for 3+ years now. =
And honestly, if this type of application is going to be =
enterprise-class, it needs to be in conjunction with ISP deployment of =
IPv6, not in spite of it.<br></div></blockquote><div><br></div><div>What =
you're saying is that applications developers shouldn't bother with =
actually trying to use IPv6 until the ISPs get their act together and =
deploy it. &nbsp;Well guess what? &nbsp;The ISPs have let us down. =
&nbsp;We've been waiting for 15 years for the ISPs to roll out IPv6, and =
for most of those 15 years they were all telling us that there were no =
applications for it. &nbsp;Now the ISPs are scrambling to get IPv6 into =
their networks, and they want to sabotage the IPv6 mechanisms that we =
have in place even before they are actually offering =
product.</div><div><br></div><blockquote type=3D"cite"><div>KM&gt; - =
Users (including enterprise users) who have small networks with IPv4 =
access (generally behind v4 NATs) can use 6to4 to allow them to remotely =
access individual hosts on those networks. &nbsp;This can be done either =
with a NAT that also acts as a v6 router and supports 6to4 as an =
external connection, or by configuring the NAT to pass protocol 41 to a =
IPv6 router for the network, internal to the v4 NAT.<br><br>WEG&gt; =
Until CGN becomes common, in which case 6to4 doesn't work again. Also, =
that same NAT + v6 router combination could just as easily manage a =
static tunnel.<br></div></blockquote><div><br></div>You're missing =
something. &nbsp; I can connect directly from my mobile laptop to a =
machine in my home network using 6to4. &nbsp;I didn't have to set up any =
static tunnel for either one. &nbsp;Sure, I could do that, I could get =
tunnels from HE or some other source and route through them. &nbsp;Why =
should I bother? &nbsp;Why do I want to make my IPv6 traffic take any =
longer a route than necessary? &nbsp;You've argued against 6to4 with =
relay routers because it's routing can be suboptimal, but the same is =
true of any other tunneling scheme.</div><div><br><blockquote =
type=3D"cite"><div>KM&gt;Widespread IPv6 support for native IPv6 would =
be when native IPv6 is available everywhere that IPv4 access is =
available, from at least one provider, with quality (connectivity, =
reliability, support) approximately as good as IPv4, and at a reasonable =
price. &nbsp;In other words, you can't expect applications to rely on =
native IPv6 until it's reliably available everywhere that they need to =
use it.<br><br>WEG&gt; So Widespread IPv6 has to have reliability and =
support equivalent to IPv4, yet you're saying that you can expect =
applications to rely on 6to4 in the meantime despite evidence that it's =
unreliable, and the virtual guarantee that it won't be supported by the =
upstream ISP?<br></div></blockquote><div><br></div>There's no such =
virtual guarantee. &nbsp;&nbsp;</div><div><br><blockquote =
type=3D"cite"><div>And you and I disagree about the definition of =
widespread. I do not think that widespread means "every small ISP in =
every corner of the world supports it ubiquitously and at every price =
point." I think it means "it's available for a majority (&gt;50%) of =
Internet service customers."<br></div></blockquote><div><br></div>We can =
disagree about the meaning of the word "widespread", but the practical =
fact is that you can't expect people to give up something that works for =
them until you can provide them something that works better <i>for them. =
&nbsp;"<span class=3D"Apple-style-span" style=3D"font-style: =
normal;">Available to 50% of Internet service customers" is equivalent =
to a very small percent probability of native connectivity being able to =
replace 6to4 connectivity in a scenario where 6to4 is currently working. =
&nbsp;And the more hosts involved, the smaller that probability =
is.&nbsp;</span></i></div><div><br><blockquote type=3D"cite"><div>WEG&gt; =
As was discussed in the WGLC for this document, enterprise applications =
will not realistically use 6to4 as a means to reach IPv6 for business =
critical applications. It's simply not reliable enough. It's also =
probably unlikely that those will go directly to IPv6-only vs using =
dual-stack to ease that transition. Individuals and Enterprises that use =
IPv6-only applications will need to make IPv6 service a non-negotiable =
requirement for their ISPs, networks, and devices rather than hoping =
that 6to4 works.<br><br>KM&gt; With respect, the v6ops working group is =
not in a good position to judge whether enterprise applications will use =
6to4. &nbsp;&nbsp;Operators rarely have a good understanding of what =
individual application users or developers need. &nbsp;They tend to =
focus mostly on the applications that generate the most traffic, =
&nbsp;or cause them particular amounts of trouble, or the ones that =
their biggest customers need. &nbsp;Problem is, those aren't the only =
applications that are important. &nbsp;Every application is important to =
its users, no matter how much or little traffic (or revenue) it =
generates.<br><br>WEG&gt; I'm not going to touch the "operators don't =
know what they're talking about" part of your comment, except to note =
that it's a gross generalization that won't help your argument, and =
wonder how you are uniquely qualified to know better than the rest of =
us...</div></blockquote><div><br></div><div>Seems to me it's the v6ops =
people who are making the gross generalizations. &nbsp;I'm mostly =
pointing out exceptions to those gross generalizations that have been =
made here and in v6ops. &nbsp;</div><div><br></div><blockquote =
type=3D"cite"><div> I am simply saying that I do not for a second =
believe that those same applications that are so important to that user =
community are at the same time unimportant enough that they're the =
sacrificial lamb that has to go IPv6-only when the majority of that user =
community, no matter how small, doesn't have native IPv6 access yet. =
</div></blockquote><div><br></div><div>You have absolutely no idea which =
applications will be important to the user community tomorrow. &nbsp; =
Who knows what will be the next netflix, twitter, facebook, youtube, ... =
? &nbsp; The Internet is successful not because it supports some small =
number of apps that operators think are a good idea; it's successful =
because it (at least as originally architected) can support a wide range =
of apps <i>without</i> operators having to bless =
them.&nbsp;</div><br><blockquote type=3D"cite"><div>This is the essence =
of the IPv6 content vs access chicken/egg problem, and 6to4 absolutely =
will not break the impasse. 6to4 breakage is the most common thing that =
content providers cite as reasons why they don't just go dual-stack. Why =
would an enterprise application be any =
different?<br></div></blockquote><div><br></div>It doesn't really matter =
much whether "content-providers" (as in web site providers) go "dual =
stack" now. &nbsp;Sure, they need to be gearing up for it, making sure =
that they understand it, making sure that their networks support it. =
&nbsp;(Or maybe they'll just install v6-to-v4 proxies at their borders =
so that they can keep providing good customer service in the face of =
LSN-induced brain damage on the public v4 network.) &nbsp; But assuming =
their applications work through LSN, they're going to keep supporting v4 =
for a long time anyway, because that's the established base of =
interoperability for their products and services. &nbsp; Existing =
"content providers" are not going to drive adoption of IPv6. &nbsp; =
They're going to follow it. &nbsp;Web and email will be the last =
applications to migrate. &nbsp;New content might appear on v6, and that =
might drive adoption. &nbsp;But to the extent that it drives adoption, =
it probably won't be from the currently established players that already =
have plenty of v4 addresses and infrastructure. &nbsp;It will be from =
new things that take advantage of the niches created by IPv6 that didn't =
exist before.</div><div><br><blockquote type=3D"cite"><div>KM&gt; 6to4 =
is as reliable as IPv4 is, if it isn't asked to cross a relay =
router.<br>WEG&gt; perhaps (with the exception of MTU issues that plague =
any tunneled protocol), but you continue to not provide any examples of =
this being used anywhere, in the face of significant evidence that 6to4 =
is horribly unreliable *with* a relay. So this gets filed in the same =
place as my 100% secure file server which happens to be unplugged from =
power and network and encased in 10ft of concrete. Theoretically =
perfect, but otherwise practically =
useless.<br></div></blockquote><div><br></div><div>What is "anywhere" to =
you? &nbsp;You seem to have a content-centric view of the Internet. =
&nbsp;I do not. &nbsp; Meanwhile, you persist in saying that something =
that I've used regularly for more than 10 years, to do useful work, =
isn't being used anywhere. &nbsp; I keep seeing figures that 6to4 =
comprises 40-some-odd percent of IPv6 traffic, while native IPv6 is =
around 10 percent. &nbsp;By your logic, native v6 should be deprecated =
because it doesn't work reliably and it's not being used =
anywhere.</div><div><br></div><blockquote type=3D"cite"><div>KM&gt; And =
there are valid reasons to use 6to4 even where IPv4 connectivity already =
exists.<br>WEG&gt; One would hope you wouldn't be trying to use 6to4 =
where IPv4 connectivity *doesn't* =
exist.<br></div></blockquote><div><br></div><div>Right, but the point is =
that there are valid use cases for 6to4 even where you have IPv4 =
connectivity for part or even all of the network that you're =
using.</div></div><div><br><blockquote type=3D"cite"><div>KM&gt;Even in =
cases where 6to4 traffic must cross a relay router, sometimes it's the =
best solution available.<br>WEG&gt; Perhaps, but again, we're talking =
about such a small percentage of the time that the cure ends up being =
worse than the disease. I love orphans and lost causes as much as the =
next guy, but really...<br></div></blockquote><div><br></div>The disease =
is the current IPv4 network with NATs and LSNs and a paucity of address =
space. &nbsp;6to4 is like a drug that can let some valuable v6 =
applications grow (even if a bit stunted) and survive until there's once =
again a network that will support them. &nbsp;Sure, there are some side =
effects and contraindications. &nbsp;But it's useful when used with =
awareness of its limitations. &nbsp;You're arguing that it should be =
discouraged because it causes some problems. &nbsp;Indeed it does. =
&nbsp;But LSN also causes problems, and is a bigger dead-end than 6to4, =
and it's full steam ahead with that. &nbsp;At least 6to4 is designed to =
ease transition to a saner world, which is a lot more than I can say for =
LSN.</div><div><br><blockquote type=3D"cite"><div>KM&gt;All of the =
criticisms in section 3 have to do with the use of relays to exchange =
traffic between 6to4 and native IPv6. &nbsp;&nbsp;In many cases the =
criticisms are overbroad. &nbsp;&nbsp;Not all uses of 6to4 involve =
relays. &nbsp;For some of those that do need to use relays, it is not =
necessarily the case that the relay is operated by an unknown =
third-party.<br><br>WEG&gt; Again, please substantiate this with =
examples of implementations that are actively using non-relay 6to4. =
&nbsp;Also, the number of applications of 6to4 that can be guaranteed to =
avoid any unknown 3rd party relays is extremely limited due to the =
nature of anycast and 6to4's asymmetric routing. &nbsp;The protocol =
action requested in this draft in no way prevents one or more consenting =
networks from using 6to4 and continuing to run relays for their local =
traffic indefinitely - in fact, it even provides a reference to a =
document to show them how to make it work as well as possible. It is =
simply saying that it's not a good =
idea.</div></blockquote></div><div><blockquote =
type=3D"cite"><div><br>KM&gt; Application implementations shouldn't care =
whether they're using relay 6to4, non-relay 6to4, or 6to4 at all. =
&nbsp;Application implementations should at most care that they're using =
IPv6 rather than IPv4, and for some applications even this is not =
appropriate.<br>Application deployments might well need to care how well =
their underlying networks work. &nbsp;Ideally, they shouldn't have to =
care, but that's the world we're currently living in.<br><br>WEG&gt; =
First, you're hair-splitting between implementation and deployment. =
However you want to call it, I'm referring to "situations" where 6to4 is =
in use without relays and is performing reliably on a business-critical =
use to justify your assertion that we shouldn't toss out this part of =
6to4 along with the anycast/relay part because it's still so =
useful.<br></div></blockquote><div><br></div>You're attacking 6to4 on =
the basis of irrelevancies. &nbsp;As for business-critical, that's up to =
the business using it to determine whether it works well enough for =
their purposes. &nbsp;There are a lot of technically dubious practices =
used in business critical applications and =
networks.</div><div><br><blockquote type=3D"cite"><div>WEG&gt; I agree =
that properly written applications are IP version-agnostic. There is =
only a question of whether they work through one or more layers of IPv4 =
NAT, or they don't. If they don't, then the solution is IPv6. If IPv6 =
isn't available, you have many major content providers saying that they =
absolutely don't see 6to4 as an acceptable substitute, meaning that your =
supposed application of 6to4 as a fix for this problem is so niche as to =
be harmful rather than helpful. =
</div></blockquote><div><br></div><div>The notion that "properly written =
applications are IP version-agnostice" is naive and overbroad. =
&nbsp;IPv6 works differently enough from IPv4 that many applications =
cannot treat them the same. &nbsp; Simple client-server apps, perhaps, =
can ignore their differences, but that's just a corner case. =
&nbsp;&nbsp;</div><div><br></div><div>I have no doubt that many of those =
"major content providers" are correct when they don't see 6to4 as an =
acceptable substitute for them. &nbsp;But the Internet doesn't exist =
just to support "major content providers". &nbsp;So stop trying to =
sabotage something that works well enough for other =
users.</div><br><blockquote type=3D"cite"><div>Why are we having a World =
IPv6 Day? In part to shake loose the broken 6to4 users that may not even =
know that 6to4 is enabled/broken so that content providers can be more =
confident that they can dual-stack their websites without risk of =
significant user impact due to =
breakage.<br></div></blockquote><div><br></div><div>I'm looking forward =
to World IPv6 Day, and what will be learned from it. &nbsp; But again, =
how well 6to4 works with "major content providers" is =
irrelevant.</div><br><blockquote type=3D"cite"><div>KM&gt; The requested =
protocol action deprecates 6to4 and discourages its inclusion in future =
implementations. &nbsp;That's harmful to applications and users for whom =
native IPv6 isn't available - which is to say, pretty much everyone at =
the moment. &nbsp;When native IPv6 becomes widely available, it will =
then be appropriate to transition hosts and networks using 6to4 to =
native IPv6. &nbsp;But even then, there will probably still be a need =
for host implementations<br><br>WEG&gt; Well, it'd be more harmful if =
there weren't alternatives. </div></blockquote><div><br></div><div>There =
aren't any good ones. &nbsp;Teredo and configured tunnels are worse in =
many ways; though they each have their use cases. =
&nbsp;&nbsp;</div><br><blockquote type=3D"cite"><div>Also, assuming that =
the protocol is declared historical, we're now in a footrace between =
ISPs deploying IPv6 and equipment vendors removing support for 6to4 (or =
rolling out new products that don't support it in the first place). I =
think you're oversensationalizing both the impact of this draft and the =
lack of IPv6, given that nearly all major ISPs in the commercial space =
are currently offering or have a timeline to offer Native IPv6, and a =
large amount of the ISPs in the residential space have a timeline for =
deployment, many have already started trials.<br>Finally, we're having =
problems with equipment that doesn't support IPv6 at all. 6to4 is not =
high on the priority list to implement compared with a functional IPv6 =
stack, meaning that on new gear, it likely won't get implemented until =
it's no longer necessary.<br></div></blockquote><br></div><div>Gear that =
doesn't support IPv6 by now is pretty odd gear. &nbsp; &nbsp; But I'm =
not going to tell you not to use it. &nbsp;I'm just saying, if you want =
odd gear to work for you in your own specific use cases, don't try to =
sabotage other odd things that work for other people in their specific =
use =
cases.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-18-614669036--

From john-ietf@jck.com  Tue Jun  7 18:24:25 2011
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 E732B11E8154; Tue,  7 Jun 2011 18:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4t287JLDcAfZ; Tue,  7 Jun 2011 18:24:25 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 2703B11E80FE; Tue,  7 Jun 2011 18:24:25 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QU7VI-0003I2-K4; Tue, 07 Jun 2011 21:24:16 -0400
Date: Tue, 07 Jun 2011 21:24:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, rontlv <ron.even.tlv@gmail.com>
Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
Message-ID: <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM>
In-Reply-To: <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <1215FCFF-B566-4E52-88DD-233934F6460F@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: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 01:24:26 -0000

--On Tuesday, June 07, 2011 14:43 -0700 Paul Hoffman
<paul.hoffman@vpnc.org> wrote:

>> Section 5.1 of RFC5892 says "If non-backward-compatible
>> changes or other problems arise during the
>>   creation or designated expert review of the table of
>>   derived property values, they should be flagged for the
>>   IESG." . My question was if the change is backward
>> compatible. The 5892bis draft does not say it.
> 
> Ah, very good catch! My earlier comment about us listing this
> new RFC in the registry is, in fact, wrong.
> 
> When we wrote RFC 5892, we said:
>    IANA has created a registry with the derived properties for
> the    versions of Unicode released after (and including)
> version 5.2.   

> That's one registry that has the properties for
> most current version of Unicode at any given time. Thus, the
> registry would be updated *even if* we didn't publish 5892bis.
> We are not updating either 5892, nor the registry, by
> publishing 5892bis. We are simply giving IETF consensus advice
> about what we think the expert reviewer who updates the
> registry should consider.
> 
> Our IANA considerations in 5892bis are:
>    IANA is to update the derived property value registry
> according to    RFC 5892 and property values as defined in The
> Unicode Standard    version 6.0.

> That might sound like they are initiating the registry update,
> but they really aren't: the update was already specified in
> 5892. We can change the IANA considerations to reflect that:

> IANA will update the derived property value registry according
> to    RFC 5892 and property values as defined in The Unicode
> Standard    version 6.0, regardless of the content of this RFC.

Paul,

I think this is an improvement but there is one issue about
which we have slightly different impressions.   I hope the
difference can be resolved without needing yet more tedious
arguments about documentation.  Indeed, if such arguments are
required, I'd prefer that we just forget about it.

Anyway, your comments above about "most current version" imply
to me that IANA should keep derived property tables for the most
current version only.  My expectation when 5982 was completed
was that IANA was expected to keep derived property tables,
clearly identified by version, for each and every Unicode
version from 5.2 forward.  In other words, the tables for the
[most] current version would be added to, not replace, whatever
previous version tables were around.  The reasons for this, in
terms of systems and implementations in various stages of
development, implementation, and deployment, seem obvious... but
maybe it was too obvious to some of us at the time to get the
wording exactly right.

     john


From paul.hoffman@vpnc.org  Tue Jun  7 19:45:55 2011
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 78D5721F84FA; Tue,  7 Jun 2011 19:45:55 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KvrIiajBvDBN; Tue,  7 Jun 2011 19:45:54 -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 E62C421F84F1; Tue,  7 Jun 2011 19:45:43 -0700 (PDT)
Received: from [10.20.30.150] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p582jaN4027228 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Jun 2011 19:45:37 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM>
Date: Tue, 7 Jun 2011 19:45:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org> <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 02:45:55 -0000

On Jun 7, 2011, at 6:24 PM, John C Klensin wrote:

> I think this is an improvement but there is one issue about
> which we have slightly different impressions.   I hope the
> difference can be resolved without needing yet more tedious
> arguments about documentation.  Indeed, if such arguments are
> required, I'd prefer that we just forget about it.
>=20
> Anyway, your comments above about "most current version" imply
> to me that IANA should keep derived property tables for the most
> current version only.  My expectation when 5982 was completed
> was that IANA was expected to keep derived property tables,
> clearly identified by version, for each and every Unicode
> version from 5.2 forward.  In other words, the tables for the
> [most] current version would be added to, not replace, whatever
> previous version tables were around.  The reasons for this, in
> terms of systems and implementations in various stages of
> development, implementation, and deployment, seem obvious... but
> maybe it was too obvious to some of us at the time to get the
> wording exactly right.

While your interpretation could be one thing we might have meant, it is =
not what is reflected in the RFC or the registry. RFC 5892 says:

5.1.  IDNA-Derived Property Value Registry

   IANA has created a registry with the derived properties for the
   versions of Unicode released after (and including) version 5.2.  The
   derived property value is to be calculated in cooperation with a
   designated expert [RFC5226] according to the specifications in
   Sections 2 and 3 and not by copying the non-normative table found in
   Appendix B.

   If non-backward-compatible changes or other problems arise during the
   creation or designated expert review of the table of derived property
   values, they should be flagged for the IESG.  Changes to the rules
   (as specified in Sections 2 and 3), including BackwardCompatible
   (Section 2.7) (a set that is at release of this document is empty)
   require IETF Review, as described in RFC 5226 [RFC5226].

Note that every reference to the registry is singular. Also, the =
registry at =
<http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml> =
doesn't mention "5.2" at all.

If the registry definition does not talk about keeping versions, and the =
registry itself doesn't look like it tried, it may be implausible to =
think that IANA would just start to do so in some future. To me, "a =
registry" means a single registry.

--Paul Hoffman


From stpeter@stpeter.im  Tue Jun  7 21:00:46 2011
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 B646711E807C for <ietf@ietfa.amsl.com>; Tue,  7 Jun 2011 21:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.624
X-Spam-Level: 
X-Spam-Status: No, score=-101.624 tagged_above=-999 required=5 tests=[AWL=0.975, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tMiLCrNjvg4N for <ietf@ietfa.amsl.com>; Tue,  7 Jun 2011 21:00:45 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id A824A11E8071 for <ietf@ietf.org>; Tue,  7 Jun 2011 21:00:44 -0700 (PDT)
Received: from squire.local (dsl-179-111.dynamic-dsl.frii.net [216.17.179.111]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id DFCBB40066; Tue,  7 Jun 2011 22:00:38 -0600 (MDT)
Message-ID: <4DEEF3E3.3070003@stpeter.im>
Date: Tue, 07 Jun 2011 22:00:35 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110505161306.3291.13078.idtracker@ietfa.amsl.com> <4DE42639.5060604@qualcomm.com>
In-Reply-To: <4DE42639.5060604@qualcomm.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms090807030408080006040801"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 04:00:46 -0000

This is a cryptographically signed message in MIME format.

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

Pete, thanks for your helpful summary. Comments inline, now that I've
had a chance to review all of the Last Call feedback.

On 5/30/11 5:20 PM, Pete Resnick wrote:
> On 5/5/11 11:13 AM, The IESG wrote:
>> The IESG has received a request from an individual submitter to consid=
er
>> the following document:
>> - 'Reducing the Standards Track to Two Maturity Levels'
>>    <draft-housley-two-maturity-levels-06.txt>  as a BCP
>>
>> 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 2011-06-02. Exceptionally, comments may=
 be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>   =20
>=20
> Man without hat: Speaking as an individual contributor, not an AD.

Ditto.

> Summary: I am in favor of most of the changes in this document. The
> primary change I am opposed to is the one identified in the title and
> therefore object the adoption of this document as a BCP. However, I
> believe there is a single (though significant) change that would make
> the document acceptable to me.

My summary: I am in favor of many of the changes in this document,
although what you and I like and dislike does not overlap much. :|

> Details:
>=20
> The document says in section 1 that the motivation for the changes is:
>=20
>    In the current environment, many documents are published as Proposed=

>    Standard and never advance to a higher maturity level.=20

I think that's fine and usually appropriate.

>    In addition,
>    IETF working groups and IESG members provide much more scrutiny than=

>    is called for by RFC 2026 [1] prior to publication as Proposed
>    Standard.

Although this is adduced as a motivation, by my reading it doesn't
actually motivate the proposals in this document.

> I certainly agree with addressing the above concerns.=20

I'm not yet convinced that these are real problems.

> Section 2 lists
> one additional motivation for the changes:
>=20
>    The benefit associated with a third maturity level has proven
>    insufficient to justify the effort associated with document
>    progression.
>=20
> I'll address this below.

I think the third maturity level is unnecessary, but I'm not yet
convinced that we understand what results we're trying to achieve and
what behaviors we're trying to encourage by modifying the standards track=
=2E

> Here is a summary of the process changes that occur in the document, by=

> section:
>=20
> Section 2
> (a) Generally, go to two maturity levels, Proposed Standard and Interne=
t
> Standard
> (b) Only review the changes, not the entire document, when recycled at
> Proposed
>=20
> Section 2.1
> (a) Go back to 2026 level of (i.e., less) scrutiny for Proposed Standar=
d
>=20
> Section 2.2
> (a) Specifically, merge Draft Standard into Internet Standard
> (b) Combine criteria from Draft Standard and Standard
>     (i) Significant number of implementations with successful
> operational experience
>     (ii) No unresolved errata causing interoperational problems
>     (iii) No unused features, except allow unused features that do not
> greatly increase implementation complexity
>     (iv) Independent patent/licensing for implementations
> (c) Remove overt requirement for documentation of interoperability test=
ing
>=20
> Section 3
> (a) No more annual review of Proposed Standards for movement to Histori=
c
>=20
> Section 4
> (a) Allow normative references from Internet Standards to Proposed
> Standards
>=20
> (Editorial note: Please move 2(b) into 2.1. That change is a change to
> the handling of Proposed Standards and therefore belongs in 2.1. That
> makes the rest of Section 2 just introductory text and not making a
> specific procedural change.)
>=20
> My analysis by section:
>=20
> 2(a) - I am opposed to this change and will discuss it below in section=

> 2.2(a).

I am in favor of this change.

> 2(b) - I like this change and support it.

I'm mostly agnostic about this, although I note that sometimes things
change (e.g., new security threats) and it makes sense to revisit parts
of a document even if they haven't been changed (or, in some instances,
especially if they haven't been changed).

> 2.1(a) - I wholeheartedly agree with this change (or, more to the point=
,
> reversion to the documented way of doing things).=20

I disagree with this change. It sounds attractive ("let's return to the
golden age") but I agree with those who posted during the Last Call that
it is a significant change from current practice. You could argue that
current practice is not the best practice, but I don't see how a
reversion to RFC 2026 principles here is truly best current practice. In
addition, IMHO we have not thought enough about the consequences of a
lower bar for Proposed Standard (e.g., our "customers" think that an RFC
is an RFC, and if we suddenly start publishing PS specs of lesser
quality then we might be diluting our brand).

> However:
> - This document gives no mechanism to facilitate this change. I would
> like to hear how this will be accomplished.

I have my doubts that this is even achievable now, at least absent
serious changes to IETF culture and individual expectations among spec
authors, WG chairs, Area Directors, review teams, and everyone else.

> - This change, along with 2(b) has the potential to greatly increase th=
e
> number of RFCs published. The document does not discuss the impact of t=
hat.

And, more to the point I think, to greatly decrease the quality of RFCs
published. Perhaps that's OK, but we need pretty strong consensus that
it's the right thing to do, and I haven't seen that consensus in the
Last Call discussion.

> 2.2(a) - I see no motivation for this change other than the one sentenc=
e
> in section 2. This change does not address the difficulty of going from=

> Proposed to Draft, and it doesn't address the heightened scrutiny for
> going to Proposed. Therefore, if the only reason for changing from thre=
e
> levels to two is that getting through the three levels is too hard, and=

> most of the procedural changes in this document are to make it easier t=
o
> get through the first two levels, I see no justification for removing
> the third (and in 2026, easiest to get through) level. It does not solv=
e
> any identified problem.

I'm in favor of this change. I don't think the document describes the
motivation very well, but this one makes sense to me. As Thoreau said,
"simplify, simplify, simplify" (although why did he need to say it three
times?).

> 2.2(b)(i) - This is the current requirement for Internet Standard. I'm
> fine with that remaining, but object to the removal of any notion of
> interoperability. If this were changed to "A significant number of
> interoperable implementations...", I would have no objection.
>
> 2.2(b)(ii) - I have no objection to this new requirement, but have no
> strong feeling about it.
>=20
> 2.2(b)(iii) - I would prefer that this be amended to "All unused 'MUST'=

> requirements will be changed to 'SHOULD' requirements." If deployment i=
s
> interoperable and a feature is unused, it means that the feature was no=
t
> actually REQUIRED for interoperability. I object to this as it stands.
>=20
> 2.2(b)(iv) - This is the current requirement for Draft Standard. I'm
> fine with that remaining.
>=20
> 2.2(c) - If this is actually "subsumed" by 2.2(b)(i) (see my change
> above), then I am fine with this change.

Agreed.

> 3(a) - I have no objection to this change, but hope that the review can=

> be reinstated once the rest of the process settles down.

IMHO this makes a lot of work for various folks with no clear benefit.
Strike it.

> 4(a) - I have no objection to this change as it applies to Draft Standa=
rds.

Right. Although I think various Last Call commenters are right that this
needs to be handled on a case-by-case basis (especially if we start
publishing lower-quality or less-mature PS documents).

> So, to summarize, here is how I break down the changes this document
> proposes and my position on them:
>=20
> A. For Proposed Standard:
> - Go back to 2026 review levels for approval
> - Only review changes, not the entire document, for recycling at Propos=
ed.
>=20
> I am in favor of these changes.

I am not in favor of these changes.

> B. For Draft Standard:
> - Remove requirement for formal documentation of interoperability tests=
=2E
> - Require only a significant number of [interoperable] implementations
> with successful operational experience.
> - Allow no unresolved interoperability errata.
> - Allow for unused [SHOULD level] requirements if they don't increase
> implementation complexity.
> - Allow for downrefs to Proposed Standard documents.
>=20
> I am in favor of these changes with the square bracketed insertions I
> have made, except for the last one which I can live with.

I am in favor of these changes.

> C. Eliminate annual review of Proposed Standards.
>=20
> I would prefer not to make this change, but since it does not reflect
> reality, I am OK with it.

I would prefer to make this change.

> D. For Internet Standards:
> - Combine Draft Standards into this category.
>=20
> This is the only change that I strongly object to since I don't see any=

> problem that is solved by doing this and therefore oppose adoption of
> the present document as BCP.

The is the only change I'm strongly in favor of.

> So, here is my a proposed alternative:
>=20
> 1. Make the changes in (A). We still need to say how to make that
> happen, and how to deal with the increased number of RFCs.

I say: don't make these changes.

> 2. Make the changes in (B).

Agreed.

> 3. Make the changes in (C).

Agreed.

> With regard to the STD numbers, I think that it would be reasonable to:=

>=20
> 4. Assign STD numbers to everything at Draft Standard.

I agree with John Klensin and others that this text can be safely
removed. It's off-topic at this point in the conversation anyway.

> And if people really think that the current *titles* of the levels are =
a
> problem:
>=20
> 5. Change the name of "Internet Standard" to "Mature Standard" (or
> "Deployed Standard" or whatever label we like).
>=20
> 6. Change the name of "Draft Standard" to "Internet Standard".

I disagree -- there's no reason to change the branding.

> I am happy to write an I-D if there is support for this.

And I'm happy to write an I-D that makes a stronger case for two-track.

Peter

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




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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDYw
ODA0MDAzNVowIwYJKoZIhvcNAQkEMRYEFKxVMOxXUzZxw2umlOFvMsQKKDVyMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQCCeAribZzuP5khzfKRCqk1OoKTG4j0icTBRRhmTerDUccQYHmwadhXEc4c
NVlNIvljIxURoqBHDgXHBFUFuEMtM6Fvv/PBtLglnx+EgD5guCpItpMMaig3WXv/wauh0aA1
oK0rxvqUkjhlAy1DV+ZPIpkgE7zhgZSbGXEfALqdkhpteN62EmLgOXXcuefiMaM/fk9jEpzb
6ZsseGNn2DGhMkPCsUUEh0niiw6uDBupZe97Pg6QMvMHBTNfBqmZm/teqVA7qPVJFNCo3j/i
w2SOtwZQ7sXxflyJN326ySTvy+gkzMalJpa1+okL9/Q5off56og14H3E09ag70SkBSvWAAAA
AAAA
--------------ms090807030408080006040801--

From presnick@qualcomm.com  Tue Jun  7 21:57:21 2011
Return-Path: <presnick@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 13B4511E8181 for <ietf@ietfa.amsl.com>; Tue,  7 Jun 2011 21:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.367
X-Spam-Level: 
X-Spam-Status: No, score=-106.367 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K5mDwO2EGdaa for <ietf@ietfa.amsl.com>; Tue,  7 Jun 2011 21:57:19 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id D46A211E8180 for <ietf@ietf.org>; Tue,  7 Jun 2011 21:57:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1307509039; x=1339045039; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4DEF012B.40202@qualcomm.com>|Date:=20Tue, =207=20Jun=202011=2023:57:15=20-0500|From:=20Pete=20Resni ck=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0=20 (Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B=20e n-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Peter=20Saint-Andre=20<stpeter @stpeter.im>|CC:=20<ietf@ietf.org>|Subject:=20Re:=20Last =20Call:=20<draft-housley-two-maturity-levels-06.txt>=20( Reducing=0D=0A=20the=20Standards=20Track=20to=20Two=20Mat urity=20Levels)=20to=20BCP|References:=20<20110505161306. 3291.13078.idtracker@ietfa.amsl.com>=09<4DE42639.5060604@ qualcomm.com>=20<4DEEF3E3.3070003@stpeter.im> |In-Reply-To:=20<4DEEF3E3.3070003@stpeter.im> |Content-Type:=20text/plain=3B=20charset=3D"ISO-8859-1" =3B=20format=3Dflowed|Content-Transfer-Encoding:=207bit |X-Originating-IP:=20[172.30.39.5]; bh=j2zZ3r44Aay3RVE297OxqBPLlo9t/pnL0sZwPdTUcJM=; b=ND7PHfy2BW453QL6yfT3A047KqxWf5gXVQEcUqBGsLvb/MzMpZk9VGt8 Nwtue7oF0/FaIERePSnx76dWcD6suko3j1n/V7YIvh7eLT8uEf84PI1On fyRcrRZ3XaOLw5FKIX8pQI0/xyGTW7V7Csb2PFsF3LKr8JU1zwb+fmLSA 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,6370"; a="96106629"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine02.qualcomm.com with ESMTP; 07 Jun 2011 21:57:18 -0700
X-IronPort-AV: E=Sophos;i="4.65,335,1304319600"; d="scan'208";a="143261186"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 07 Jun 2011 21:57:18 -0700
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 7 Jun 2011 21:57:17 -0700
Message-ID: <4DEF012B.40202@qualcomm.com>
Date: Tue, 7 Jun 2011 23:57:15 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110505161306.3291.13078.idtracker@ietfa.amsl.com>	<4DE42639.5060604@qualcomm.com> <4DEEF3E3.3070003@stpeter.im>
In-Reply-To: <4DEEF3E3.3070003@stpeter.im>
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: Wed, 08 Jun 2011 04:57:21 -0000

On 6/7/11 11:00 PM, Peter Saint-Andre wrote:
> Pete, thanks for your helpful summary. Comments inline, now that I've
> had a chance to review all of the Last Call feedback.
>    

A conversation I'm happy to have. Comments inline. We are still men 
without hats.

> On 5/30/11 5:20 PM, Pete Resnick wrote:
>    
>
>> Details:
>>
>> The document says in section 1 that the motivation for the changes is:
>>
>>     In the current environment, many documents are published as Proposed
>>     Standard and never advance to a higher maturity level.
>>      
> I think that's fine and usually appropriate.
>    

So you think that this is *not* a motivation for the changes and is 
*not* something we need to change? Interesting.

>>     In addition,
>>     IETF working groups and IESG members provide much more scrutiny than
>>     is called for by RFC 2026 [1] prior to publication as Proposed
>>     Standard.
>>      
> Although this is adduced as a motivation, by my reading it doesn't
> actually motivate the proposals in this document.
>    

We agree on that point.

>> I certainly agree with addressing the above concerns.
>>      
> I'm not yet convinced that these are real problems.
>    

This we're likely to agree to disagree on.

>> Section 2 lists
>> one additional motivation for the changes:
>>
>>     The benefit associated with a third maturity level has proven
>>     insufficient to justify the effort associated with document
>>     progression.
>>
>> I'll address this below.
>>      
> I think the third maturity level is unnecessary, but I'm not yet
> convinced that we understand what results we're trying to achieve and
> what behaviors we're trying to encourage by modifying the standards track.
>    

Strongly agreed on the latter point: I'm not at all convinced that we 
understand what results we're trying to achieve and
what behaviors we're trying to encourage by modifying the standards 
track. And given that, whatever change we end up making, I have to say 
that this document can't be it, because it does not explain what we're 
trying to achieve.

Skipping down to "going back to 2026 requirements for proposed":

> I disagree with this change. It sounds attractive ("let's return to the
> golden age") but I agree with those who posted during the Last Call that
> it is a significant change from current practice. You could argue that
> current practice is not the best practice, but I don't see how a
> reversion to RFC 2026 principles here is truly best current practice. In
> addition, IMHO we have not thought enough about the consequences of a
> lower bar for Proposed Standard (e.g., our "customers" think that an RFC
> is an RFC, and if we suddenly start publishing PS specs of lesser
> quality then we might be diluting our brand).
>
>    
>> However:
>> - This document gives no mechanism to facilitate this change. I would
>> like to hear how this will be accomplished.
>>      
> I have my doubts that this is even achievable now, at least absent
> serious changes to IETF culture and individual expectations among spec
> authors, WG chairs, Area Directors, review teams, and everyone else.
>
>    
>> - This change, along with 2(b) has the potential to greatly increase the
>> number of RFCs published. The document does not discuss the impact of that.
>>      
> And, more to the point I think, to greatly decrease the quality of RFCs
> published. Perhaps that's OK, but we need pretty strong consensus that
> it's the right thing to do, and I haven't seen that consensus in the
> Last Call discussion.
>    

All of the above may be true. I personally think that the best thing 
that could happen in some sense is to "decrease the quality" of Proposed 
Standard RFCs, but that's certainly a controversial view. And I think 
it's worthy of an independent discussion. So, at the very least, we 
either need to agree on this as a topic for this document or remove it.

As to the change to 2 levels:

>> 2.2(a) - I see no motivation for this change other than the one sentence
>> in section 2. This change does not address the difficulty of going from
>> Proposed to Draft, and it doesn't address the heightened scrutiny for
>> going to Proposed. Therefore, if the only reason for changing from three
>> levels to two is that getting through the three levels is too hard, and
>> most of the procedural changes in this document are to make it easier to
>> get through the first two levels, I see no justification for removing
>> the third (and in 2026, easiest to get through) level. It does not solve
>> any identified problem.
>>      
> I'm in favor of this change. I don't think the document describes the
> motivation very well, but this one makes sense to me. As Thoreau said,
> "simplify, simplify, simplify" (although why did he need to say it three
> times?).
>    

"Simplify" (even three times) is not a good motivation for this change. 
If "simplify, simplify, simplify" means "cut off your right arm, cut off 
your left arm, and cut off your left leg", I will certainly be a simpler 
being for the act, but none the better; I would argue a bit worse for my 
purposes. "Simplify" is not, in and of itself, a good justification. So 
I want to hear more. Certainly more than is in the current document.

On the downrefs:

>> 4(a) - I have no objection to this change as it applies to Draft Standards.
>>      
> Right. Although I think various Last Call commenters are right that this
> needs to be handled on a case-by-case basis (especially if we start
> publishing lower-quality or less-mature PS documents).
>    

Agreed.

>> So, to summarize, here is how I break down the changes this document
>> proposes and my position on them:
>>
>> A. For Proposed Standard:
>> - Go back to 2026 review levels for approval
>> - Only review changes, not the entire document, for recycling at Proposed.
>>
>> I am in favor of these changes.
>>      
> I am not in favor of these changes.
>    

I'll try to argue separately later for why this is good. But I suspect 
that we're going to be deadlocked at least with regard to this document.

>> B. For Draft Standard:
>> - Remove requirement for formal documentation of interoperability tests.
>> - Require only a significant number of [interoperable] implementations
>> with successful operational experience.
>> - Allow no unresolved interoperability errata.
>> - Allow for unused [SHOULD level] requirements if they don't increase
>> implementation complexity.
>> - Allow for downrefs to Proposed Standard documents.
>>
>> I am in favor of these changes with the square bracketed insertions I
>> have made, except for the last one which I can live with.
>>      
> I am in favor of these changes.
>    

Excellent. This we probably can get agreement on for this document.

>> C. Eliminate annual review of Proposed Standards.
>>
>> I would prefer not to make this change, but since it does not reflect
>> reality, I am OK with it.
>>      
> I would prefer to make this change.
>    

I don't mind, but I might want to wordsmith to still allow the IESG the 
possibility to classify something as Historic with simply a Last Call.

>> D. For Internet Standards:
>> - Combine Draft Standards into this category.
>>
>> This is the only change that I strongly object to since I don't see any
>> problem that is solved by doing this and therefore oppose adoption of
>> the present document as BCP.
>>      
> The is the only change I'm strongly in favor of.
>    

Again, I'll wait to hear the justification. But to say I am very 
skeptical would be to understate.

>> I am happy to write an I-D if there is support for this.
>>      
> And I'm happy to write an I-D that makes a stronger case for two-track.

So, I think I hear us agreeing that it would be fine to make the changes 
to requirements for Draft Standard, but not agreeing to much of anything 
else. You're willing to write an I-D explaining why it's a good idea to 
go to two-tracks and I'm willing to write an I-D explaining why it's a 
good idea to go back to 2026 requirements for Proposed Standard, and we 
both seem to agree that the present I-D does neither of these things. 
Given that, I think it makes sense to remove the two-track business and 
the Prosposed Standard business from this document and simply make it 
about simplifying the requirements for Draft Standard.

I think we will wait for the shepherding AD to give us direction. :-)

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From ajs@anvilwalrusden.com  Tue Jun  7 22:28:50 2011
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 6086511E80EC for <ietf@ietfa.amsl.com>; Tue,  7 Jun 2011 22:28: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DYL+bYXnNwV for <ietf@ietfa.amsl.com>; Tue,  7 Jun 2011 22:28:50 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id D859D11E808E for <ietf@ietf.org>; Tue,  7 Jun 2011 22:28:49 -0700 (PDT)
Received: from shinkuro.com (unknown [107.16.88.244]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 96BB01ECB426 for <ietf@ietf.org>; Wed,  8 Jun 2011 05:28:47 +0000 (UTC)
Date: Wed, 8 Jun 2011 01:28:47 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
Message-ID: <20110608052847.GE44267@shinkuro.com>
References: <20110505161306.3291.13078.idtracker@ietfa.amsl.com> <4DE42639.5060604@qualcomm.com> <4DEEF3E3.3070003@stpeter.im> <4DEF012B.40202@qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4DEF012B.40202@qualcomm.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, 08 Jun 2011 05:28:50 -0000

On Tue, Jun 07, 2011 at 11:57:15PM -0500, Pete Resnick wrote:
> 
> So you think that this is *not* a motivation for the changes and is
> *not* something we need to change? Interesting.

For what it's worth, quite apart from thinking that the draft in
question will do nothing to change the state of affairs with respect
to advancement, I also wonder why anyone cares whether documents
advance.

If someone cares enough, documents will advance.  Someone will do the
work.  For instance, apparently Scott Hollenbeck cared about the
advancement of EPP.  The Extensible Provisioning Protocol is a full
Standard.  Meanwhile, the protocol some EPP-using registries employ to
update the contents of their DNS zone files (DNS Update, RFC 2136) is
a Proposed Standard and has been since 1997.  I assert that someone
fooling with DNS dynamic update such that the protocol changed
incompatably would have far more wide-ranging and deleterious
consequences for the Internet than someone altering EPP in a
backward-incompatible way.  We have a hope of contacting all the EPP
users on Earth, to begin with.  (None of this is to denigrate EPP or
the work that those who moved it along the standards track undertook.
I think it is an excellent example of what to do and how to do it.
It's just also a handy example of a well-defined protocol with a
reasonably tightly packed user community, compared to some other
protocols.)

If the people who use and rely on a protocol don't care about this
maturity-level advancement to do something about it, why should the
rest of us care?

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From dave@cridland.net  Wed Jun  8 00:58:43 2011
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 1767A21F8556 for <ietf@ietfa.amsl.com>; Wed,  8 Jun 2011 00:58: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Een60TFop3V5 for <ietf@ietfa.amsl.com>; Wed,  8 Jun 2011 00:58:39 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [IPv6:2001:470:1f09:882:2e0:81ff:fe29:d16a]) by ietfa.amsl.com (Postfix) with ESMTP id 67E4F21F855B for <ietf@ietf.org>; Wed,  8 Jun 2011 00:58:38 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 480E31168087; Wed,  8 Jun 2011 08:58:32 +0100 (BST)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (peirce.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mLZ6yfH4ARM5; Wed,  8 Jun 2011 08:58:29 +0100 (BST)
Received: from puncture (puncture.dave.cridland.net [IPv6:2001:470:1f09:882:221:85ff:fe3f:1696]) by peirce.dave.cridland.net (Postfix) with ESMTPA id 4AEF21168067; Wed,  8 Jun 2011 08:58:29 +0100 (BST)
Subject: Re: Last Call: <draft-housley-two-maturity-levels-06.txt> (Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110505161306.3291.13078.idtracker@ietfa.amsl.com> <4DE42639.5060604@qualcomm.com> <4DEEF3E3.3070003@stpeter.im> <4DEF012B.40202@qualcomm.com>
In-Reply-To: <4DEF012B.40202@qualcomm.com>
MIME-Version: 1.0
Message-Id: <2961.1307519909.283808@puncture>
Date: Wed, 08 Jun 2011 08:58:29 +0100
From: Dave Cridland <dave@cridland.net>
To: Pete Resnick <presnick@qualcomm.com>, IETF-Discussion <ietf@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; delsp="yes"; 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, 08 Jun 2011 07:58:43 -0000

On Wed Jun  8 05:57:15 2011, Pete Resnick wrote:
> On 6/7/11 11:00 PM, Peter Saint-Andre wrote:
>> And, more to the point I think, to greatly decrease the quality of  
>> RFCs
>> published. Perhaps that's OK, but we need pretty strong consensus  
>> that
>> it's the right thing to do, and I haven't seen that consensus in  
>> the
>> Last Call discussion.
>>    
> 
> All of the above may be true. I personally think that the best  
> thing that could happen in some sense is to "decrease the quality"  
> of Proposed Standard RFCs, but that's certainly a controversial  
> view. And I think it's worthy of an independent discussion. So, at  
> the very least, we either need to agree on this as a topic for this  
> document or remove it.

Just to throw in my tuppence, once more:

I'm entirely in favour of there being a cheaper, rougher,  
lower-quality grade of specification; I think this should be what  
Proposed Standard was originally intended to be; I think there is a  
pressing need for a specification grade to fill this niche within the  
IETF. In this, I think I'm in agreement with Pete.

I am very much against trying to redefine - and at this stage it is a  
de jure redefinition, as it were - Proposed Standard *or any other  
RFC grade* to fill this gap. I think customer expectation of the RFC  
series is now for a much higher quality than RFC 2026 envisaged, and  
the net result of regrading PS would be that of lowering the quality  
of the specifications used in the field. In this, I think I'm in  
agreement with Peter.

The best proposal I've seen - and I'd note that I can't recall now if  
this is Keith Moore's or Scott Bradner's, to my shame - is that of  
marking up specific I-D documents as being a "Stable Snapshot". This  
proposal seems to have the following benefits:

a) It satisfies the two paragraphs above in a non-conflicting manner.  
That is, it provides everything that RFC 2026's PS was intended to  
without being an RFC, with all that that moniker currently implies.

b) It's fairly obvious, in my view, how to start to use the new  
grade, and how we might adapt to it in a smooth manner. Working  
Groups, authors, etc would be able to start to use it in a fairly  
ad-hoc manner, without the kinds of flag day changes to process that  
two-maturity-levels seems to imply.

So if anyone has the patience for another I-D thrown into the soup,  
I'm willing to [re]write this one up, assuming the original  
instigator[s] of the proposal don't wish to.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From alexey.melnikov@isode.com  Wed Jun  8 04:50:36 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B132228010; Wed,  8 Jun 2011 04:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.126
X-Spam-Level: 
X-Spam-Status: No, score=-102.126 tagged_above=-999 required=5 tests=[AWL=0.472, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MBLSBQJe1OEU; Wed,  8 Jun 2011 04:50:35 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 6B24311E8081; Wed,  8 Jun 2011 04:50:34 -0700 (PDT)
Received: from [188.28.88.132] (188.28.88.132.threembb.co.uk [188.28.88.132])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Te9iBAA-uZZV@rufus.isode.com>; Wed, 8 Jun 2011 12:50:31 +0100
Message-ID: <4DEF61F1.6040502@isode.com>
Date: Wed, 08 Jun 2011 12:50:09 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Vint Cerf <vint@google.com>
Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org> <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM> <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org> <BANLkTi=byyNLdFyogh0eicGT2yksa8gh3g@mail.gmail.com>
In-Reply-To: <BANLkTi=byyNLdFyogh0eicGT2yksa8gh3g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------020800040609000909040608"
Cc: IETF-Discussion list <ietf@ietf.org>, gen-art@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>, John C Klensin <john-ietf@jck.com>, draft-faltstrom-5892bis.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: Wed, 08 Jun 2011 11:50:36 -0000

This is a multi-part message in MIME format.
--------------020800040609000909040608
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Vint Cerf wrote:

> setting aside interpretation and semantics for a moment, would there 
> be utility in maintaining tables for each instance of Unicode?

Yes, because developers will have different versions of Unicode 
available to them. It would also help developers to migrate by seeing 
what has changed between versions.

> v
>
> On Tue, Jun 7, 2011 at 10:45 PM, Paul Hoffman <paul.hoffman@vpnc.org 
> <mailto:paul.hoffman@vpnc.org>> wrote:
>
>     On Jun 7, 2011, at 6:24 PM, John C Klensin wrote:
>
>     > I think this is an improvement but there is one issue about
>     > which we have slightly different impressions.   I hope the
>     > difference can be resolved without needing yet more tedious
>     > arguments about documentation.  Indeed, if such arguments are
>     > required, I'd prefer that we just forget about it.
>     >
>     > Anyway, your comments above about "most current version" imply
>     > to me that IANA should keep derived property tables for the most
>     > current version only.  My expectation when 5982 was completed
>     > was that IANA was expected to keep derived property tables,
>     > clearly identified by version, for each and every Unicode
>     > version from 5.2 forward.  In other words, the tables for the
>     > [most] current version would be added to, not replace, whatever
>     > previous version tables were around.  The reasons for this, in
>     > terms of systems and implementations in various stages of
>     > development, implementation, and deployment, seem obvious... but
>     > maybe it was too obvious to some of us at the time to get the
>     > wording exactly right.
>
>     While your interpretation could be one thing we might have meant,
>     it is not what is reflected in the RFC or the registry. RFC 5892 says:
>
>     5.1.  IDNA-Derived Property Value Registry
>
>       IANA has created a registry with the derived properties for the
>       versions of Unicode released after (and including) version 5.2.  The
>       derived property value is to be calculated in cooperation with a
>       designated expert [RFC5226] according to the specifications in
>       Sections 2 and 3 and not by copying the non-normative table found in
>       Appendix B.
>
>       If non-backward-compatible changes or other problems arise
>     during the
>       creation or designated expert review of the table of derived
>     property
>       values, they should be flagged for the IESG.  Changes to the rules
>       (as specified in Sections 2 and 3), including BackwardCompatible
>       (Section 2.7) (a set that is at release of this document is empty)
>       require IETF Review, as described in RFC 5226 [RFC5226].
>
>     Note that every reference to the registry is singular. Also, the
>     registry at
>     <http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml>
>     doesn't mention "5.2" at all.
>
>     If the registry definition does not talk about keeping versions,
>     and the registry itself doesn't look like it tried, it may be
>     implausible to think that IANA would just start to do so in some
>     future. To me, "a registry" means a single registry.
>
>     --Paul Hoffman
>


--------------020800040609000909040608
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Vint Cerf wrote:<br>
<blockquote cite="midBANLkTi=byyNLdFyogh0eicGT2yksa8gh3g@mail.gmail.com"
 type="cite">setting aside interpretation and semantics for a moment,
would there be utility in maintaining tables for each instance of
Unicode?</blockquote>
Yes, because developers will have different versions of Unicode
available to them. It would also help developers to migrate by seeing
what has changed between versions.<br>
<blockquote cite="midBANLkTi=byyNLdFyogh0eicGT2yksa8gh3g@mail.gmail.com"
 type="cite">
  <div>v<br>
  <br>
  <div class="gmail_quote">On Tue, Jun 7, 2011 at 10:45 PM, Paul
Hoffman <span dir="ltr">&lt;<a href="mailto:paul.hoffman@vpnc.org">paul.hoffman@vpnc.org</a>&gt;</span>
wrote:<br>
  <blockquote class="gmail_quote"
 style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
    <div class="im">On Jun 7, 2011, at 6:24 PM, John C Klensin wrote:<br>
    <br>
&gt; I think this is an improvement but there is one issue about<br>
&gt; which we have slightly different impressions. &nbsp; I hope the<br>
&gt; difference can be resolved without needing yet more tedious<br>
&gt; arguments about documentation. &nbsp;Indeed, if such arguments are<br>
&gt; required, I'd prefer that we just forget about it.<br>
&gt;<br>
&gt; Anyway, your comments above about "most current version" imply<br>
&gt; to me that IANA should keep derived property tables for the most<br>
&gt; current version only. &nbsp;My expectation when 5982 was completed<br>
&gt; was that IANA was expected to keep derived property tables,<br>
&gt; clearly identified by version, for each and every Unicode<br>
&gt; version from 5.2 forward. &nbsp;In other words, the tables for the<br>
&gt; [most] current version would be added to, not replace, whatever<br>
&gt; previous version tables were around. &nbsp;The reasons for this, in<br>
&gt; terms of systems and implementations in various stages of<br>
&gt; development, implementation, and deployment, seem obvious... but<br>
&gt; maybe it was too obvious to some of us at the time to get the<br>
&gt; wording exactly right.<br>
    <br>
    </div>
While your interpretation could be one thing we might have meant, it is
not what is reflected in the RFC or the registry. RFC 5892 says:<br>
    <br>
5.1. &nbsp;IDNA-Derived Property Value Registry<br>
    <div class="im"><br>
&nbsp; IANA has created a registry with the derived properties for the<br>
    </div>
&nbsp; versions of Unicode released after (and including) version 5.2. &nbsp;The<br>
&nbsp; derived property value is to be calculated in cooperation with a<br>
&nbsp; designated expert [RFC5226] according to the specifications in<br>
&nbsp; Sections 2 and 3 and not by copying the non-normative table found in<br>
&nbsp; Appendix B.<br>
    <div class="im"><br>
&nbsp; If non-backward-compatible changes or other problems arise during the<br>
&nbsp; creation or designated expert review of the table of derived property<br>
    </div>
&nbsp; values, they should be flagged for the IESG. &nbsp;Changes to the rules<br>
&nbsp; (as specified in Sections 2 and 3), including BackwardCompatible<br>
&nbsp; (Section 2.7) (a set that is at release of this document is empty)<br>
&nbsp; require IETF Review, as described in RFC 5226 [RFC5226].<br>
    <br>
Note that every reference to the registry is singular. Also, the
registry at &lt;<a
 href="http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml"
 target="_blank">http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml</a>&gt;
doesn't mention "5.2" at all.<br>
    <br>
If the registry definition does not talk about keeping versions, and
the registry itself doesn't look like it tried, it may be implausible
to think that IANA would just start to do so in some future. To me, "a
registry" means a single registry.<br>
    <font color="#888888"><br>
--Paul Hoffman</font></blockquote>
  </div>
  </div>
</blockquote>
<br>
</body>
</html>

--------------020800040609000909040608--

From alexey.melnikov@isode.com  Wed Jun  8 04:55:36 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 302A211E80BE; Wed,  8 Jun 2011 04:55:36 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5J5zgRRR4Fe8; Wed,  8 Jun 2011 04:55:35 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 127BB11E80BC; Wed,  8 Jun 2011 04:55:34 -0700 (PDT)
Received: from [188.28.88.132] (188.28.88.132.threembb.co.uk [188.28.88.132])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <Te9jKwA-ucR3@rufus.isode.com>; Wed, 8 Jun 2011 12:55:33 +0100
Message-ID: <4DEF631C.1070306@isode.com>
Date: Wed, 08 Jun 2011 12:55:08 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org> <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM> <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>
In-Reply-To: <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 11:55:36 -0000

Paul Hoffman wrote:

>On Jun 7, 2011, at 6:24 PM, John C Klensin wrote:
>  
>
>>I think this is an improvement but there is one issue about
>>which we have slightly different impressions.   I hope the
>>difference can be resolved without needing yet more tedious
>>arguments about documentation.  Indeed, if such arguments are
>>required, I'd prefer that we just forget about it.
>>
>>Anyway, your comments above about "most current version" imply
>>to me that IANA should keep derived property tables for the most
>>current version only.  My expectation when 5982 was completed
>>was that IANA was expected to keep derived property tables,
>>clearly identified by version, for each and every Unicode
>>version from 5.2 forward.  In other words, the tables for the
>>[most] current version would be added to, not replace, whatever
>>previous version tables were around.  The reasons for this, in
>>terms of systems and implementations in various stages of
>>development, implementation, and deployment, seem obvious... but
>>maybe it was too obvious to some of us at the time to get the
>>wording exactly right.
>>
That was my impression as well when I reviewed RFC 5982 while on IESG.

>While your interpretation could be one thing we might have meant, it is not what is reflected in the RFC or the registry. RFC 5892 says:
>
>5.1.  IDNA-Derived Property Value Registry
>
>   IANA has created a registry with the derived properties for the
>   versions of Unicode released after (and including) version 5.2.  The
>   derived property value is to be calculated in cooperation with a
>   designated expert [RFC5226] according to the specifications in
>   Sections 2 and 3 and not by copying the non-normative table found in
>   Appendix B.
>
>   If non-backward-compatible changes or other problems arise during the
>   creation or designated expert review of the table of derived property
>   values, they should be flagged for the IESG.  Changes to the rules
>   (as specified in Sections 2 and 3), including BackwardCompatible
>   (Section 2.7) (a set that is at release of this document is empty)
>   require IETF Review, as described in RFC 5226 [RFC5226].
>
>Note that every reference to the registry is singular.
>
There is a single registry, but multiple versions of Unicode.

>Also, the registry at <http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml> doesn't mention "5.2" at all.
>
That might be an error created when the registry got setup by IANA.

>If the registry definition does not talk about keeping versions, and the registry itself doesn't look like it tried, it may be implausible to think that IANA would just start to do so in some future. To me, "a registry" means a single registry.
>  
>


From john-ietf@jck.com  Wed Jun  8 04:56:23 2011
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 E0D0F11E80C9; Wed,  8 Jun 2011 04:56: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JGUEKQWNWVTA; Wed,  8 Jun 2011 04:56:23 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 4C5B411E80C5; Wed,  8 Jun 2011 04:56:23 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QUHMq-000DeK-Uk; Wed, 08 Jun 2011 07:56:13 -0400
Date: Wed, 08 Jun 2011 07:56:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, Vint Cerf <vint@google.com>
Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
Message-ID: <71EE769EE4C39C799F40668D@PST.JCK.COM>
In-Reply-To: <4DEF61F1.6040502@isode.com>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com>       <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org>            <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com>            <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org>            <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM>            <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>            <BANLkTi=byyNLdFyogh0eicGT2yksa8gh3g@mail.gmail.com> <4DEF61F1.6040502@isode.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: gen-art@ietf.org, IETF-Discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, draft-faltstrom-5892bis.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: Wed, 08 Jun 2011 11:56:24 -0000

+1

--On Wednesday, June 08, 2011 12:50 +0100 Alexey Melnikov
<alexey.melnikov@isode.com> wrote:

> Vint Cerf wrote:
> 
>> setting aside interpretation and semantics for a moment,
>> would there  be utility in maintaining tables for each
>> instance of Unicode?
> 
> Yes, because developers will have different versions of
> Unicode available to them. It would also help developers to
> migrate by seeing what has changed between versions.





From john-ietf@jck.com  Wed Jun  8 05:32:27 2011
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 BE53821F84E1 for <ietf@ietfa.amsl.com>; Wed,  8 Jun 2011 05:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6XnsdzSzsxCg for <ietf@ietfa.amsl.com>; Wed,  8 Jun 2011 05:32:27 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 9970221F8495 for <ietf@ietf.org>; Wed,  8 Jun 2011 05:32:26 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QUHvk-000EAM-MK; Wed, 08 Jun 2011 08:32:17 -0400
Date: Wed, 08 Jun 2011 08:32:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Contents of the IDNA Derived Properties registry (was; Re: Gen-ART LC review of draft-faltstrom-5892bis-04)
Message-ID: <13BE2E85721B3235A4B272AD@PST.JCK.COM>
In-Reply-To: <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org> <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM> <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@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: draft-faltstrom-5892bis.all@tools.ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 12:32:27 -0000

(Subject line changed to reflect my belief that this is not
about 5892bis.  I've also removed the copy to the gen-art list
-- if this isn't about 5892bis, it isn't on their agenda, even
though Roni's review may have partially stimulated the thread.)

--On Tuesday, June 07, 2011 19:45 -0700 Paul Hoffman
<paul.hoffman@vpnc.org> wrote:

>> Anyway, your comments above about "most current version" imply
>> to me that IANA should keep derived property tables for the
>> most current version only.  My expectation when 5982 was
>> completed was that IANA was expected to keep derived property
>...

> While your interpretation could be one thing we might have
> meant, it is not what is reflected in the RFC or the registry.
> RFC 5892 says:
>...
> Note that every reference to the registry is singular. Also,
> the registry at
> <http://www.iana.org/assignments/idnabis-tables/idnabis-tables
> .xml> doesn't mention "5.2" at all.
> 
> If the registry definition does not talk about keeping
> versions, and the registry itself doesn't look like it tried,
> it may be implausible to think that IANA would just start to
> do so in some future. To me, "a registry" means a single
> registry.

Paul,

Just to be completely clear about the intent of my comment,
while I'm disinclined to split hairs about whether "registry"
(singular) could mean a collection of tables, I completely agree
that, if such a historically-threaded collection were desired,
it should have been crystal-clear in 5892.   And it is not
crystal-clear.

I think this raises three issues:

(1) Whether a historical thread is kept or not, having a
registry of derived property values that does not identify which
version of Unicode it reflects is of poor utility and a possible
source of confusion.  If I don't know to what version of Unicode
the registry has been updated, I cannot comply with the IDNA
requirement that, if I use derived property tables (rather than
recalculating based on the rule set), those be consistent with
the version of Unicode on my system (the level of difficulty
associated with that rule has been discussed on this thread
already; let's not revisit it).  One can, of course, figure it
out by comparing the code points listed as UNASSIGNED with
changes in successive Unicode versions, but it seems to me to be
much more useful to include Unicode version identification in
the registry.  I believe that is fully consistent with your
reading of 5892.

(2) Whether a collection of derived property tables, explicitly
tied to versions of Unicode, is useful.  Vint has already asked
that question and gotten a couple of affirmative answers.
Others might disagree, but it seems to me that we need to arrive
at a conclusion somehow.

(3) If we conclude that it is useful to identify the Unicode
version under which a derived property table was compiled and/or
to keep a historical thread of tables, how do we get from "here"
(one table, no Unicode version identification) to "there".  My
personal preference, strongly motivated by the amount of energy
that has been consumed by the non-change in 5892bis, would be
for the IESG to simply request that IANA make those changes;
doing so is, IMO, clearly within their authority.  If a separate
document is needed, I guess I volunteer to write a short I-D.

In any event and as suggested above, I don't see any changes in
this area as appropriately being part of 5892bis.  Tuning what
IANA should be keeping in the registry and how it should be
identified is not a topic that 5892bis addresses at all.
Moreover, if we do need an RFC to make any changes that are
desired, that RFC actually would update a standards-track RFC
and would hence itself need to be standards-track.   Different
critter.

So I suggest that:

(i) We get 5892bis wrapped up and published.  It says pretty
much what it should say, it doesn't change the basic
specification, and even those who don't like the decisions it
represents appear to believe that we have spent enough time on
it and that continued delay is problematic.

(ii) The relevant ADs consider whether a document clarifying the
registry content and/or identification information is needed and
consult with IANA on that topic as appropriate.  If the answer
is "yes", let's get that document posted and start debating what
changes, if any, should be made using it as a foundation (rather
than finding new weeds to drag 5892bis into).

     john




From housley@vigilsec.com  Wed Jun  8 06:59:37 2011
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 538F821F8498 for <ietf@ietfa.amsl.com>; Wed,  8 Jun 2011 06:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.717
X-Spam-Level: 
X-Spam-Status: No, score=-102.717 tagged_above=-999 required=5 tests=[AWL=-0.118, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id arZBMb-43wnN for <ietf@ietfa.amsl.com>; Wed,  8 Jun 2011 06:59:36 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id B09CF21F848E for <ietf@ietf.org>; Wed,  8 Jun 2011 06:59:36 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id CF734F2403F; Wed,  8 Jun 2011 10:00:03 -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 830f8EJ8sYjj; Wed,  8 Jun 2011 09:59:33 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-241-218-101.washdc.fios.verizon.net [96.241.218.101]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 52782F2401C; Wed,  8 Jun 2011 10:00:03 -0400 (EDT)
Subject: Re: Contents of the IDNA Derived Properties registry (was; Re: Gen-ART LC review of draft-faltstrom-5892bis-04)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <13BE2E85721B3235A4B272AD@PST.JCK.COM>
Date: Wed, 8 Jun 2011 09:59:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CD5E64A7-A687-432F-8F0A-B0F245F21A8C@vigilsec.com>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org> <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM> <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org> <13BE2E85721B3235A4B272AD@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1084)
Cc: 'IETF-Discussion list' <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, draft-faltstrom-5892bis.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: Wed, 08 Jun 2011 13:59:37 -0000

The discussion make it clear to me that the tasks for IANA are not =
clear.   It seems that there needs to be a table for each supported =
version of Unicode.  Thats document should state that clearly.  It is a =
point where RFC 5892 seems to be vague, and we should take this =
opportunity to remove the ambiguity.

This document or a future one needs to answer the following question:
Who is responsible for generating a new table when the next version of =
Unicode comes out?

Russ


On Jun 8, 2011, at 8:32 AM, John C Klensin wrote:

> (ii) The relevant ADs consider whether a document clarifying the
> registry content and/or identification information is needed and
> consult with IANA on that topic as appropriate.  If the answer
> is "yes", let's get that document posted and start debating what
> changes, if any, should be made using it as a foundation (rather
> than finding new weeds to drag 5892bis into).


From alexandru.petrescu@gmail.com  Wed Jun  8 07:30:02 2011
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2BC511E80E3; Wed,  8 Jun 2011 07:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JU6+eDsc8Ub8; Wed,  8 Jun 2011 07:29:57 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 6745711E8094; Wed,  8 Jun 2011 07:29:57 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.2) with ESMTP id p58ETtL4001961 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 8 Jun 2011 16:29:55 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id p58ETs40025921; Wed, 8 Jun 2011 16:29:54 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [132.166.133.178] (is010173.intra.cea.fr [132.166.133.178]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id p58ETsAo023608; Wed, 8 Jun 2011 16:29:54 +0200
Message-ID: <4DEF8762.1090404@gmail.com>
Date: Wed, 08 Jun 2011 16:29:54 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-dhc-subnet-alloc-12.txt> (Subnet Allocation Option) to Informational RFC
References: <20110608133925.25307.67302.idtracker@ietfa.amsl.com>
In-Reply-To: <20110608133925.25307.67302.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: dhcwg@ietf.org, The IESG <iesg-secretary@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 14:30:03 -0000

I have read parts of the document and I find it ok.

> The DHCP Server SHOULD allocate a subnet with prefix size less than
> or equal to the size P specified in the request.  In other words, a
> subnet at least the size requested and possibly bigger.

I agree, but "prefix size less than or equal to the size P" is not very
clear, because (1) there is no "P" in the request but "Prefix", "size"
is hard to understand, etc.  Maybe it should say "the length of the
allocated prefix should have a value non-zero and less than or equal to
value Prefix in the Request; e.g. if the Request demands a prefix of
length 4 the response MUST be of length any of 1, 2, 3 or 4".

There is another point which I think is not discussed in this draft.
Contrary to allocation of an address, always the Relay and sometimes the
Server _must_ update their forwarding/routing tables, according to a
specific rule [subnet,IPaddress], when this allocation of a subnet
prefix is performed - otherwise packet forwarding won't work (packets
don't reach the Host allocated an address from this prefix).

typo " qis " on page 4.

Alex

Le 08/06/2011 15:39, The IESG a écrit :
>
> The IESG has received a request from the Dynamic Host Configuration
> WG (dhc) to consider the following document: - 'Subnet Allocation
> Option' <draft-ietf-dhc-subnet-alloc-12.txt>  as an 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 2011-06-22.
> Exceptionally, comments may be sent to iesg@ietf.org instead. In
> either case, please retain the beginning of the Subject line to allow
> automated sorting.
>
> Abstract
>
>
> This document defines a new DHCP option which is passed between the
> DHCP Client and the DHCP Server to request dynamic allocation of a
> subnet, give specifications of subnet(s) allocated, and report usage
> statistics.  This memo documents the current usage of the option in
> agreement with [RFC3942], which declares that any pre-existing
> usages of option numbers in the range 128 - 223 should be documented
> and the working group will try to officially assign those numbers to
> those options.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-dhc-subnet-alloc/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-dhc-subnet-alloc/
>
>
> The following IPR Declarations may be related to this I-D:
>
> http://datatracker.ietf.org/ipr/811/
>
>
>
> _______________________________________________ IETF-Announce mailing
> list IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>


From mrex@sap.com  Wed Jun  8 08:42:19 2011
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 4CA5611E8182; Wed,  8 Jun 2011 08:42:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.88
X-Spam-Level: 
X-Spam-Status: No, score=-8.88 tagged_above=-999 required=5 tests=[AWL=1.369,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vNYPWOvFgkD9; Wed,  8 Jun 2011 08:42:18 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 18FCF11E8158; Wed,  8 Jun 2011 08:42:17 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p58FgAih028962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Jun 2011 17:42:15 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201106081542.p58FgAcs022229@fs4113.wdf.sap.corp>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
To: mrex@sap.com
Date: Wed, 8 Jun 2011 17:42:10 +0200 (MEST)
In-Reply-To: <201106071850.p57IoDhb011453@fs4113.wdf.sap.corp> from "Martin Rex" at Jun 7, 11 08:50:13 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: v6ops@ietf.org, ietf@ietf.org, wesley.george@twcable.com
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 Jun 2011 15:42:19 -0000

I'm sorry, I seem to have goofed up during mail editing...

I meant to write that cassifying 6to4 as historic is INappropriate use
of the IETF process in the last sentence.

-Martin

Martin Rex wrote:
> 
> George, Wesley wrote:
> > 
> > > It's time to remove the stabilisers on the IPv6 bicycle.
> > 
> > This takes nothing away. It's not as if the day that this draft gets
> > published as an RFC, 6to4 stops working.
> 
> 
> In my personal perception, the "historic" status used to be a technical
> characterization to indicate that 
> 
>   (1) a protocol or technology has been fully replaced by some newer
>       protocol and there is no reason to continue using the original
>       technology anymore because the successor can be used in each
>       of the original usage scenarios today
> 
>   (2) the protocol/technology has been largely put out of use, and its
>       active use has dropped to marginal levels (like less than 1% of the
>       original active use)
> 
> Personally, I have never conciously used anything related to IPv6 so
> far, so for me it is difficult to comment, but what has been said
> looks to me that neither (1) nor (2) apply to 6to4.
> 
> The user base seems to have always been small, and most of the users
> of 6to4 simply did _not_ have an alternative -- and its current
> users still do _not_ have an alternative today.
> 
> Classification of 6to4 as historic is appropriate use of the IETF process,
> because it would be a political, but not an accurate technical statement.
> 
> 
> -Martin

From wesley.george@twcable.com  Tue Jun  7 14:28:01 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46C7911E8147; Tue,  7 Jun 2011 14:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.237
X-Spam-Level: 
X-Spam-Status: No, score=0.237 tagged_above=-999 required=5 tests=[AWL=-0.500,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  J_CHICKENPOX_13=0.6, J_CHICKENPOX_32=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5gONreNjtj3O; Tue,  7 Jun 2011 14:28:00 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id ED5F711E80C2; Tue,  7 Jun 2011 14:27:59 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.65,334,1304308800"; d="scan'208";a="235478474"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 07 Jun 2011 17:35:02 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.29]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Tue, 7 Jun 2011 17:27:59 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: Keith Moore <moore@network-heretics.com>
Date: Tue, 7 Jun 2011 17:27:57 -0400
Subject: RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Thread-Index: AcwlJoh/Y7coZ0uwSNq4LC+KQclORwAA32nA
Message-ID: <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com>
In-Reply-To: <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 08 Jun 2011 08:44:02 -0700
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 21:28:01 -0000

From: Keith Moore [mailto:moore@network-heretics.com]
Sent: Tuesday, June 07, 2011 11:21 AM
To: George, Wesley
Cc: ietf@ietf.org; v6ops@ietf.org
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> =
(Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Histo=
ric status) to Informational RFC

WEG> Please substantiate these claims. What are the use cases, and why are =
there no other solutions for those specific use cases? What is considered "=
widespread ISP support for native IPV6"?

KM>The best current use cases for 6to4 that I'm aware of are:

KM>- Applications developers want to be forward thinking and develop IPv6 a=
pps, but cannot get native IPv6 access.  6to4 allows them to develop those =
apps and test or use them in useful situations (i.e. outside of a lab) with=
out having to configure a separate tunnel to every host involved.   Note th=
at 6to4 is useful in this way even if all of the addresses used are 6to4 ad=
dresses, and the traffic therefore does not cross any relays between 6to4 a=
nd native IPv6.

WEG> Exactly my point. this is a valid use case, but 6to4 is by no means th=
e only way to solve it. Application developers are welcome to set up an IPv=
6 network to test their apps against. That doesn't require IPv6 connectivit=
y to the outside world. If you have more than one of any modern computer on=
 your LAN and you turn the right knobs, they can all talk to each other via=
 IPv6 independent of any external IPv6 connectivity. You seem to want to dr=
aw this distinction between IPv6 between two hosts using 6to4 since that "w=
orks" and using 6to4 as a means to connect to the IPv6 Internet via relays,=
 but then you conflate them by repeatedly complaining about lack of IPv6 se=
rvice available from most ISPs and presenting 6to4 as a solution.
Further, I don't buy the "separate tunnel to every host..." thing. Tunneled=
 IPv6 connectivity is widely available. All any developer needs to do if th=
ey can't get Native IPv6 and a tunneled application is deemed good enough f=
or their testing purposes is connect both ends of their testing environment=
 to their choice of tunnel broker, and through the magic of the internet, t=
hey're all connected to one another.

KM> - Enterprises have applications that need to be able to communicate wit=
h large numbers of hosts spread over a diverse area.  IPv6 is clearly the w=
ay that they want to go, but it's not widely available at present.  6to4 pr=
ovides them with a means of routing traffic to their hosts in the interim u=
ntil widespread support for IPv6 exists.

WEG> So do IPv6IP or GRE tunnels. Been using one at home for 3+ years now. =
And honestly, if this type of application is going to be enterprise-class, =
it needs to be in conjunction with ISP deployment of IPv6, not in spite of =
it.

KM> - Users (including enterprise users) who have small networks with IPv4 =
access (generally behind v4 NATs) can use 6to4 to allow them to remotely ac=
cess individual hosts on those networks.  This can be done either with a NA=
T that also acts as a v6 router and supports 6to4 as an external connection=
, or by configuring the NAT to pass protocol 41 to a IPv6 router for the ne=
twork, internal to the v4 NAT.

WEG> Until CGN becomes common, in which case 6to4 doesn't work again. Also,=
 that same NAT + v6 router combination could just as easily manage a static=
 tunnel.

KM>Widespread IPv6 support for native IPv6 would be when native IPv6 is ava=
ilable everywhere that IPv4 access is available, from at least one provider=
, with quality (connectivity, reliability, support) approximately as good a=
s IPv4, and at a reasonable price.  In other words, you can't expect applic=
ations to rely on native IPv6 until it's reliably available everywhere that=
 they need to use it.

WEG> So Widespread IPv6 has to have reliability and support equivalent to I=
Pv4, yet you're saying that you can expect applications to rely on 6to4 in =
the meantime despite evidence that it's unreliable, and the virtual guarant=
ee that it won't be supported by the upstream ISP?
And you and I disagree about the definition of widespread. I do not think t=
hat widespread means "every small ISP in every corner of the world supports=
 it ubiquitously and at every price point." I think it means "it's availabl=
e for a majority (>50%) of Internet service customers."

WEG> As was discussed in the WGLC for this document, enterprise application=
s will not realistically use 6to4 as a means to reach IPv6 for business cri=
tical applications. It's simply not reliable enough. It's also probably unl=
ikely that those will go directly to IPv6-only vs using dual-stack to ease =
that transition. Individuals and Enterprises that use IPv6-only application=
s will need to make IPv6 service a non-negotiable requirement for their ISP=
s, networks, and devices rather than hoping that 6to4 works.

KM> With respect, the v6ops working group is not in a good position to judg=
e whether enterprise applications will use 6to4.   Operators rarely have a =
good understanding of what individual application users or developers need.=
  They tend to focus mostly on the applications that generate the most traf=
fic,  or cause them particular amounts of trouble, or the ones that their b=
iggest customers need.  Problem is, those aren't the only applications that=
 are important.  Every application is important to its users, no matter how=
 much or little traffic (or revenue) it generates.

WEG> I'm not going to touch the "operators don't know what they're talking =
about" part of your comment, except to note that it's a gross generalizatio=
n that won't help your argument, and wonder how you are uniquely qualified =
to know better than the rest of us... I am simply saying that I do not for =
a second believe that those same applications that are so important to that=
 user community are at the same time unimportant enough that they're the sa=
crificial lamb that has to go IPv6-only when the majority of that user comm=
unity, no matter how small, doesn't have native IPv6 access yet. This is th=
e essence of the IPv6 content vs access chicken/egg problem, and 6to4 absol=
utely will not break the impasse. 6to4 breakage is the most common thing th=
at content providers cite as reasons why they don't just go dual-stack. Why=
 would an enterprise application be any different?

KM> 6to4 is as reliable as IPv4 is, if it isn't asked to cross a relay rout=
er.
WEG> perhaps (with the exception of MTU issues that plague any tunneled pro=
tocol), but you continue to not provide any examples of this being used any=
where, in the face of significant evidence that 6to4 is horribly unreliable=
 *with* a relay. So this gets filed in the same place as my 100% secure fil=
e server which happens to be unplugged from power and network and encased i=
n 10ft of concrete. Theoretically perfect, but otherwise practically useles=
s.

KM> And there are valid reasons to use 6to4 even where IPv4 connectivity al=
ready exists.
WEG> One would hope you wouldn't be trying to use 6to4 where IPv4 connectiv=
ity *doesn't* exist.

KM>Even in cases where 6to4 traffic must cross a relay router, sometimes it=
's the best solution available.
WEG> Perhaps, but again, we're talking about such a small percentage of the=
 time that the cure ends up being worse than the disease. I love orphans an=
d lost causes as much as the next guy, but really...

KM>All of the criticisms in section 3 have to do with the use of relays to =
exchange traffic between 6to4 and native IPv6.   In many cases the criticis=
ms are overbroad.   Not all uses of 6to4 involve relays.  For some of those=
 that do need to use relays, it is not necessarily the case that the relay =
is operated by an unknown third-party.

WEG> Again, please substantiate this with examples of implementations that =
are actively using non-relay 6to4. Also, the number of applications of 6to4=
 that can be guaranteed to avoid any unknown 3rd party relays is extremely =
limited due to the nature of anycast and 6to4's asymmetric routing. The pro=
tocol action requested in this draft in no way prevents one or more consent=
ing networks from using 6to4 and continuing to run relays for their local t=
raffic indefinitely - in fact, it even provides a reference to a document t=
o show them how to make it work as well as possible. It is simply saying th=
at it's not a good idea.

KM> Application implementations shouldn't care whether they're using relay =
6to4, non-relay 6to4, or 6to4 at all.  Application implementations should a=
t most care that they're using IPv6 rather than IPv4, and for some applicat=
ions even this is not appropriate.
Application deployments might well need to care how well their underlying n=
etworks work.  Ideally, they shouldn't have to care, but that's the world w=
e're currently living in.

WEG> First, you're hair-splitting between implementation and deployment. Ho=
wever you want to call it, I'm referring to "situations" where 6to4 is in u=
se without relays and is performing reliably on a business-critical use to =
justify your assertion that we shouldn't toss out this part of 6to4 along w=
ith the anycast/relay part because it's still so useful.

WEG> I agree that properly written applications are IP version-agnostic. Th=
ere is only a question of whether they work through one or more layers of I=
Pv4 NAT, or they don't. If they don't, then the solution is IPv6. If IPv6 i=
sn't available, you have many major content providers saying that they abso=
lutely don't see 6to4 as an acceptable substitute, meaning that your suppos=
ed application of 6to4 as a fix for this problem is so niche as to be harmf=
ul rather than helpful. Why are we having a World IPv6 Day? In part to shak=
e loose the broken 6to4 users that may not even know that 6to4 is enabled/b=
roken so that content providers can be more confident that they can dual-st=
ack their websites without risk of significant user impact due to breakage.

KM> The requested protocol action deprecates 6to4 and discourages its inclu=
sion in future implementations.  That's harmful to applications and users f=
or whom native IPv6 isn't available - which is to say, pretty much everyone=
 at the moment.  When native IPv6 becomes widely available, it will then be=
 appropriate to transition hosts and networks using 6to4 to native IPv6.  B=
ut even then, there will probably still be a need for host implementations

WEG> Well, it'd be more harmful if there weren't alternatives. Also, assumi=
ng that the protocol is declared historical, we're now in a footrace betwee=
n ISPs deploying IPv6 and equipment vendors removing support for 6to4 (or r=
olling out new products that don't support it in the first place). I think =
you're oversensationalizing both the impact of this draft and the lack of I=
Pv6, given that nearly all major ISPs in the commercial space are currently=
 offering or have a timeline to offer Native IPv6, and a large amount of th=
e ISPs in the residential space have a timeline for deployment, many have a=
lready started trials.
Finally, we're having problems with equipment that doesn't support IPv6 at =
all. 6to4 is not high on the priority list to implement compared with a fun=
ctional IPv6 stack, meaning that on new gear, it likely won't get implement=
ed until it's no longer necessary.

Wes George



This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From ben@nostrum.com  Tue Jun  7 15:35:14 2011
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 5D58D11E80FF; Tue,  7 Jun 2011 15:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.15
X-Spam-Level: 
X-Spam-Status: No, score=-101.15 tagged_above=-999 required=5 tests=[AWL=-0.850, BAYES_00=-2.599, MANGLED_LIST=2.3, SPF_PASS=-0.001,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sLm1j8I7Ouvx; Tue,  7 Jun 2011 15:35:14 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5D9A411E8072; Tue,  7 Jun 2011 15:35:13 -0700 (PDT)
Received: from [10.0.1.6] (cpe-76-187-75-59.tx.res.rr.com [76.187.75.59]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p57MZ9iq062444 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Jun 2011 17:35:11 -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-dnsext-rfc2672bis-dname-22
Date: Tue, 7 Jun 2011 17:35:10 -0500
Message-Id: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com>
To: draft-ietf-dnsext-rfc2672bis-dname.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 76.187.75.59 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Wed, 08 Jun 2011 08:44:02 -0700
Cc: The 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, 07 Jun 2011 22:35: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-dnsext-rfc2672bis-dname-22
Reviewer: Ben Campbell
Review Date: 2011-06-07
IETF LC End Date:2011-06-09
IESG Telechat date: (if known)

Summary:

This draft does not seem to be quite ready for publication, in that it =
professes to obsolete RFC 2672, but does not cover all the material from =
that RFC or explain the absence of the missing material. I also have a =
few editorial comments that should be considered prior to final =
publication.

Major issues:

This draft professes to obsolete RFC2672, but there are multiple =
sections of that RFC that are not replicated here, nor are their absence =
explained. I assume, since this draft obsoletes RFC2672, it is expected =
to completely replace it where an implementor would no longer be =
expected to read 2672.

-- section 4.2 of RFC2672, "Processing by Resolvers", is not replicated =
here, or if it is, it's in a substantially different form.=20

-- section 5, "examples of use" is not replicated here. Similar examples =
are mentioned in the introduction, but the detail is removed.

None

Minor issues:

None

Nits/editorial comments:

-- IDNits has some comments, please check.

-- Abstract: "This is a revision of the original specification in RFC =
2672, also aligning RFC 3363 and RFC 4294 with this revision."

The heading says this obsoletes 2672 and updates the other two. It's =
probably worth explicitly using those words here.

-- 3.1, 1st paragraph: "Relevant includes the following cases:"

Awkward sentence. Maybe "Relevant cases include the following:"?

-- 3.1, 5th paragraph: "is synthesized and included in the answer =
section"

What synthesized it? The server? (passive voice obscures responsibility)=20=


-- ... "The DNAME has an RRSIG"

A _signed_ DNAME has an RRSIG, right?

-- 4, 4th paragraph: "...should be revised..."

This document actually executes the revision, right? Better to say "this =
document revises..." rather than "should be revised"

-- ..., 7th paragraph: "...replaced with the word "DELETED"."

Won't that just leave the word "deleted" hanging on page without =
explanation? Wouldn't it be better to just simply delete it?


From kathleen.moriarty@emc.com  Tue Jun  7 20:26:35 2011
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 240F211E8078; Tue,  7 Jun 2011 20:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NYeC+zw6dfrb; Tue,  7 Jun 2011 20:26:34 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 6D7F811E80A1; Tue,  7 Jun 2011 20:26:33 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p583PqkM012726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Jun 2011 23:25:56 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Tue, 7 Jun 2011 23:25:45 -0400
Received: from mxhub25.corp.emc.com (mxhub25.corp.emc.com [10.254.110.181]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p583CmYR010742; Tue, 7 Jun 2011 23:12:48 -0400
Received: from mx06a.corp.emc.com ([169.254.1.35]) by mxhub25.corp.emc.com ([10.254.110.181]) with mapi; Tue, 7 Jun 2011 23:12:31 -0400
From: <kathleen.moriarty@emc.com>
To: <gen-art@ietf.org>, <draft-ietf-ccamp-gmpls-vcat-lcas.all@tools.ietf.org>
Date: Tue, 7 Jun 2011 23:12:46 -0400
Subject: Gen-ART Review of draft-ietf-ccamp-gmpls-vcat-lcas-13
Thread-Topic: Gen-ART Review of draft-ietf-ccamp-gmpls-vcat-lcas-13
Thread-Index: AcwlifDJA02LvIUmTaytRRieWDyXtg==
Message-ID: <AE31510960917D478171C79369B660FA0DBBD21060@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Wed, 08 Jun 2011 08:44:02 -0700
Cc: diego.caviglia@marconi.com, hhelvoort@huawei.com, rabbat@alum.mit.edu, gregb@grotto-networking.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, 08 Jun 2011 03:26:35 -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-ccamp-gmpls-vcat-lcas
Reviewer: Kathleen Moriarty
Review Date: June 7, 2011
IETF LC End Date:
IESG Telechat date: (if known)

Summary:  The document is ready with nits listed below.

Major issues:

Minor issues:

Nits/editorial comments:

Consider breaking the first sentence of the abstract into two sentences.
From: This document describes requirements for, and use of, the
   Generalized Multi-Protocol Label Switching (GMPLS) control plane in
   support of the Virtual Concatenation (VCAT) layer 1 inverse
   multiplexing data plane mechanism and its companion Link Capacity
   Adjustment Scheme (LCAS) which can be used for hitless dynamic
   resizing of the inverse multiplex group.

To: This document describes requirements for, and use of, the
   Generalized Multi-Protocol Label Switching (GMPLS) control plane in
   support of the Virtual Concatenation (VCAT) layer 1 inverse
   multiplexing data plane mechanism and its companion Link Capacity
   Adjustment Scheme (LCAS).  The LCAS can be used for hitless dynamic
   resizing of the inverse multiplex group.


Consider changing the dashes to commas in the paragraph before section 2.4:
From: Identification of the VCG and its associated members. This
       provides information that allows the endpoints to differentiate
       multiple VCGs and to tell what members - label switched paths
       (LSPs)- to associate with a particular VCG.
To: Identification of the VCG and its associated members. This
       provides information that allows the endpoints to differentiate
       multiple VCGs and to tell what member, label switched paths
       (LSPs), to associate with a particular VCG.

Section 3:  There is a mix of dashes and double dashes used at the start of=
 definitions.  Please make the usage consistent (the last one only has one =
dash).  Consider a : instead of double dashes.

Last sentence before section 4:

Add a comma:
From: SONET VCAT group) which is composed of 7 virtually concatenated VC-
   4s (or STS-3c).
To:     SONET VCAT group), which is composed of 7 virtually concatenated VC=
-
   4s (or STS-3c).


Consider breaking the last sentence of the second to last paragraph of Sect=
ion 4.2 up into multiple sentences:
"A node that receives a Path
   message that contains changed fields will process the full Path
   message and, based on the new value of NVC, it will add a component
   signal to the VCAT group, and switch the new timeslot based on the
   new label information."

There is a stray "." Before the last sentence of section 5 and the sentence=
 is indented and I don't think that was intentional.
"          . Conceptual containment relationship between VCG, VCAT
   calls, control plane LSPs, and data plane connections."

Section 5.1, last bullet is another definition, look for consistency in how=
 they are formatted.



_______________________________________________
Gen-art mailing list
Gen-art@ietf.org<mailto:Gen-art@ietf.org>
https://www.ietf.org/mailman/listinfo/gen-art




From vint@google.com  Tue Jun  7 21:08:28 2011
Return-Path: <vint@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C41211E80A1 for <ietf@ietfa.amsl.com>; Tue,  7 Jun 2011 21:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.231
X-Spam-Level: 
X-Spam-Status: No, score=-105.231 tagged_above=-999 required=5 tests=[AWL=0.744, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id icjiD37mPG1k for <ietf@ietfa.amsl.com>; Tue,  7 Jun 2011 21:08:27 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 19BF511E8071 for <ietf@ietf.org>; Tue,  7 Jun 2011 21:08:26 -0700 (PDT)
Received: from wpaz17.hot.corp.google.com (wpaz17.hot.corp.google.com [172.24.198.81]) by smtp-out.google.com with ESMTP id p5848PZ8024113 for <ietf@ietf.org>; Tue, 7 Jun 2011 21:08:25 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1307506106; bh=RHod9YhkiCqFB7aqNJeoDJChIqQ=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=TEQA45X6thDe86ukUXoT6ZhlhzYpnYiMmy+eVrdN75mxY21T1GbkA4JB8vSUYqHr5 aOejuwEUIaWu61XjmMX/w==
Received: from qyk27 (qyk27.prod.google.com [10.241.83.155]) by wpaz17.hot.corp.google.com with ESMTP id p5848OYk024473 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Tue, 7 Jun 2011 21:08:24 -0700
Received: by qyk27 with SMTP id 27so67450qyk.6 for <ietf@ietf.org>; Tue, 07 Jun 2011 21:08:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=h6PhemJ6yOrLTYNPLImApqCFdo2TixipzbaBvQGYMIw=; b=P15y/JB/C+4oZTWy7UDxjyaOlolq7IxOFwZlSqWP/JsATOCUlh2jsU+++MQGtQdU7X 7G2RyX38lnxiS1g6Q4sQ==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QYUMtIUuODpGJ4/MJH1bzusLtVkrKBGTCJZRaAIN8iniU5sL1AKAaDAJpoAxd98Yxn SZYltEynZFSwI/k1CltQ==
MIME-Version: 1.0
Received: by 10.229.251.13 with SMTP id mq13mr5169877qcb.36.1307506102789; Tue, 07 Jun 2011 21:08:22 -0700 (PDT)
Received: by 10.229.7.20 with HTTP; Tue, 7 Jun 2011 21:08:22 -0700 (PDT)
In-Reply-To: <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>
References: <4de22aaa.8aecd80a.3728.ffffa184@mx.google.com> <E54DF8D5-7299-4E6F-9AF0-78115585E23D@vpnc.org> <4dee03bf.d04ee50a.6936.ffff9483@mx.google.com> <1215FCFF-B566-4E52-88DD-233934F6460F@vpnc.org> <01C15A30F3CF4E4F60DCA1E9@PST.JCK.COM> <3751CF5C-FF3D-4EE0-A96B-BACC0DFC7B1B@vpnc.org>
Date: Wed, 8 Jun 2011 00:08:22 -0400
Message-ID: <BANLkTi=byyNLdFyogh0eicGT2yksa8gh3g@mail.gmail.com>
Subject: Re: Gen-ART LC review of draft-faltstrom-5892bis-04
From: Vint Cerf <vint@google.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary=00163630f39bcc672904a52b7c46
X-System-Of-Record: true
X-Mailman-Approved-At: Wed, 08 Jun 2011 08:44:02 -0700
Cc: John C Klensin <john-ietf@jck.com>, gen-art@ietf.org, draft-faltstrom-5892bis.all@tools.ietf.org, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 04:08:28 -0000

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

setting aside interpretation and semantics for a moment, would there be
utility in maintaining tables for each instance of Unicode?

v


On Tue, Jun 7, 2011 at 10:45 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On Jun 7, 2011, at 6:24 PM, John C Klensin wrote:
>
> > I think this is an improvement but there is one issue about
> > which we have slightly different impressions.   I hope the
> > difference can be resolved without needing yet more tedious
> > arguments about documentation.  Indeed, if such arguments are
> > required, I'd prefer that we just forget about it.
> >
> > Anyway, your comments above about "most current version" imply
> > to me that IANA should keep derived property tables for the most
> > current version only.  My expectation when 5982 was completed
> > was that IANA was expected to keep derived property tables,
> > clearly identified by version, for each and every Unicode
> > version from 5.2 forward.  In other words, the tables for the
> > [most] current version would be added to, not replace, whatever
> > previous version tables were around.  The reasons for this, in
> > terms of systems and implementations in various stages of
> > development, implementation, and deployment, seem obvious... but
> > maybe it was too obvious to some of us at the time to get the
> > wording exactly right.
>
> While your interpretation could be one thing we might have meant, it is not
> what is reflected in the RFC or the registry. RFC 5892 says:
>
> 5.1.  IDNA-Derived Property Value Registry
>
>   IANA has created a registry with the derived properties for the
>    versions of Unicode released after (and including) version 5.2.  The
>   derived property value is to be calculated in cooperation with a
>   designated expert [RFC5226] according to the specifications in
>   Sections 2 and 3 and not by copying the non-normative table found in
>   Appendix B.
>
>   If non-backward-compatible changes or other problems arise during the
>   creation or designated expert review of the table of derived property
>    values, they should be flagged for the IESG.  Changes to the rules
>   (as specified in Sections 2 and 3), including BackwardCompatible
>   (Section 2.7) (a set that is at release of this document is empty)
>   require IETF Review, as described in RFC 5226 [RFC5226].
>
> Note that every reference to the registry is singular. Also, the registry
> at <http://www.iana.org/assignments/idnabis-tables/idnabis-tables.xml>
> doesn't mention "5.2" at all.
>
> If the registry definition does not talk about keeping versions, and the
> registry itself doesn't look like it tried, it may be implausible to think
> that IANA would just start to do so in some future. To me, "a registry"
> means a single registry.
>
> --Paul Hoffman
>
>

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

setting aside interpretation and semantics for a moment, would there be uti=
lity in maintaining tables for each instance of Unicode?<div><br></div><div=
>v</div><div><br><br><div class=3D"gmail_quote">On Tue, Jun 7, 2011 at 10:4=
5 PM, Paul Hoffman <span dir=3D"ltr">&lt;<a href=3D"mailto:paul.hoffman@vpn=
c.org">paul.hoffman@vpnc.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div class=3D"im">On Jun 7, 2011, at 6:24 P=
M, John C Klensin wrote:<br>
<br>
&gt; I think this is an improvement but there is one issue about<br>
&gt; which we have slightly different impressions. =A0 I hope the<br>
&gt; difference can be resolved without needing yet more tedious<br>
&gt; arguments about documentation. =A0Indeed, if such arguments are<br>
&gt; required, I&#39;d prefer that we just forget about it.<br>
&gt;<br>
&gt; Anyway, your comments above about &quot;most current version&quot; imp=
ly<br>
&gt; to me that IANA should keep derived property tables for the most<br>
&gt; current version only. =A0My expectation when 5982 was completed<br>
&gt; was that IANA was expected to keep derived property tables,<br>
&gt; clearly identified by version, for each and every Unicode<br>
&gt; version from 5.2 forward. =A0In other words, the tables for the<br>
&gt; [most] current version would be added to, not replace, whatever<br>
&gt; previous version tables were around. =A0The reasons for this, in<br>
&gt; terms of systems and implementations in various stages of<br>
&gt; development, implementation, and deployment, seem obvious... but<br>
&gt; maybe it was too obvious to some of us at the time to get the<br>
&gt; wording exactly right.<br>
<br>
</div>While your interpretation could be one thing we might have meant, it =
is not what is reflected in the RFC or the registry. RFC 5892 says:<br>
<br>
5.1. =A0IDNA-Derived Property Value Registry<br>
<div class=3D"im"><br>
 =A0 IANA has created a registry with the derived properties for the<br>
</div> =A0 versions of Unicode released after (and including) version 5.2. =
=A0The<br>
 =A0 derived property value is to be calculated in cooperation with a<br>
 =A0 designated expert [RFC5226] according to the specifications in<br>
 =A0 Sections 2 and 3 and not by copying the non-normative table found in<b=
r>
 =A0 Appendix B.<br>
<div class=3D"im"><br>
 =A0 If non-backward-compatible changes or other problems arise during the<=
br>
 =A0 creation or designated expert review of the table of derived property<=
br>
</div> =A0 values, they should be flagged for the IESG. =A0Changes to the r=
ules<br>
 =A0 (as specified in Sections 2 and 3), including BackwardCompatible<br>
 =A0 (Section 2.7) (a set that is at release of this document is empty)<br>
 =A0 require IETF Review, as described in RFC 5226 [RFC5226].<br>
<br>
Note that every reference to the registry is singular. Also, the registry a=
t &lt;<a href=3D"http://www.iana.org/assignments/idnabis-tables/idnabis-tab=
les.xml" target=3D"_blank">http://www.iana.org/assignments/idnabis-tables/i=
dnabis-tables.xml</a>&gt; doesn&#39;t mention &quot;5.2&quot; at all.<br>

<br>
If the registry definition does not talk about keeping versions, and the re=
gistry itself doesn&#39;t look like it tried, it may be implausible to thin=
k that IANA would just start to do so in some future. To me, &quot;a regist=
ry&quot; means a single registry.<br>

<font color=3D"#888888"><br>
--Paul Hoffman<br>
<br>
</font></blockquote></div><br></div>

--00163630f39bcc672904a52b7c46--

From yaojk@cnnic.cn  Wed Jun  8 00:04:49 2011
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 D35B511E80B3 for <ietf@ietfa.amsl.com>; Wed,  8 Jun 2011 00:04:49 -0700 (PDT)
X-Quarantine-ID: <ogM-jUIpr9Xs>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: -99.733
X-Spam-Level: 
X-Spam-Status: No, score=-99.733 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ogM-jUIpr9Xs for <ietf@ietfa.amsl.com>; Wed,  8 Jun 2011 00:04:48 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id 55C3211E80AB for <ietf@ietf.org>; Wed,  8 Jun 2011 00:04:46 -0700 (PDT)
Received: (eyou send program); Wed, 08 Jun 2011 15:04:42 +0800
Message-ID: <507516682.01337@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO lenovo47e041cf) (127.0.0.1) by 127.0.0.1 with SMTP; Wed, 08 Jun 2011 15:04:42 +0800
Message-ID: <FFB4A22E53204E7E8DDACF16D2F5588D@LENOVO47E041CF>
From: "Jiankang YAO" <yaojk@cnnic.cn>
To: "IETF-Discussion list" <ietf@ietf.org>
Subject: Summary for IESG last call to 5892bis draft
Date: Wed, 8 Jun 2011 15:04:40 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
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.6090
X-Mailman-Approved-At: Wed, 08 Jun 2011 08:44:02 -0700
Cc: appsawg-ads@tools.ietf.org, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 07:04:49 -0000

RGVhciBhbGwsDQoNCiAgDQogIEFEIHN1Z2dlc3RzIHRoYXQgd2Ugc2VuZCBhIGxhc3QgY2FsbCBz
dW1tYXJ5IHRvIHRoZSBsaXN0Lg0KDQogIEJlbG93IGlzIHRoZSBzdW1tYXJ5IGZvciBJRVNHIGxh
c3QgY2FsbCB0byA1ODkyYmlzIGRyYWZ0Lg0KDQogIEFueSBjb21tZW50cyBhcmUgd2VsY29tZS4N
Cg0KICBKaWFua2FuZyBZYW8gYXMgYSBjby1jaGFpciBvZiBBUFBTQVdHDQoNCi0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KU3VtbWFyeToNCiBUaGUgSUVTRyBsYXN0IGNhbGwgZm9yIGRyYWZ0
LWZhbHRzdHJvbS01ODkyYmlzLTA0LnR4dCBlbmRlZCBvbiA2IEp1bmUuDQogTW9zdCBwYXJ0aWNp
cGFudHMgc3VwcG9ydCB0aGUgcHVibGljYXRpb24gb2YgdGhpcyBkcmFmdC4gTm9ib2R5IGV4cGxp
Y2l0bHkgc2F5IHRoYXQgdGhleSBvYmplY3QgdGhlIHB1YmxpY2F0aW9uIG9mIHRoaXMgZHJhZnQu
DQoNCkJlbG93IGFyZSBzb21lIHF1ZXN0aW9ucyBvciBpc3N1ZXMgZGlzY3Vzc2VkIGR1cmluZyB0
aGUgSUVTRyBsYXN0IGNhbGwNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KaXNzdWUxOiBB
Ym91dCB0aGUgdGV4dCBvZiB0aGUgZmlyc3QgcGFyYWdyYXBoIG9mIHRoZSBJbnRyb2R1Y3Rpb24g
DQpQZXRlciBTYWludC1BbmRyZTpUaGUgZmlyc3QgcGFyYWdyYXBoIG9mIHRoZSBJbnRyb2R1Y3Rp
b24gY29udGFpbnMgYSBmZXcgaW5mZWxpY2l0aWVzIGFuZCBncmFtbWF0aWNhbCBlcnJvcnMsIGFu
ZCBJIHN1Z2dlc3Qgc29tZSBtb2RpZnlpbmcuIA0KQ2xhcmlmaWNhdGlvbiBmcm9tIEpvaG4gQyBL
bGVuc2luOiBXZSBzaG91bGQgbGVhdmUgdGhlIGVkaXRpbmcgd29yayBvciBtb2RpZnlpbmcgd29y
ayB0byBSRkMgRWRpdG9yLg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KaXNzdWUyOiBB
Ym91dCB0aGUgb2xkIElETkFiaXMgV0cncyBkZWNpc2lvbg0KQ2xhcmlmaWNhdGlvbiBmcm9tIEpv
aG4gQyBLbGVuc2luOiB0aGUgV0cgY29uY2x1ZGVkIHRoYXQgVW5pY29kZSBjaGFuZ2VzIG9mIGNo
YXJhY3Rlcg0KIHByb3BlcnRpZXMgdGhhdCBhZmZlY3RlZCBJRE5BIG5lZWRlZCB0byBiZSBldmFs
dWF0ZWQgaW4gdGhlIElFVEYNCiBvbiBhIGNhc2UtYnktY2FzZSBiYXNpcyBhcyB0byB3aGV0aGVy
IHRoZXkgd2VyZSBpbXBvcnRhbnQgZW5vdWdoDQogdG8ganVzdGlmeSBhbiBhZGRpdGlvbiB0byB0
aGF0IGV4Y2VwdGlvbnMgdGFibGUgb3Igd2hldGhlciB0aGUNCiBiYWxhbmNlIGZlbGwgb24gdGhl
IHNpZGUgb2Yga2VlcGluZyB0aGUgdGFibGUgc21hbGwuICANCg0KLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tIA0KaXNzdWUzOiBBYm91dCB0aGUgSUFOQSBjb25zaWRlcmF0aW9uIHNlY3Rpb24g
DQpSb25pIEV2ZW46IEkgYW0gbm90IHN1cmUgaG93IHRoZSBJQU5BIGNvbnNpZGVyYXRpb24gc2Vj
dGlvbiBpcyBpbi1saW5lIHdpdGggdGhlIElBTkEgY29uc2lkZXJhdGlvbiBzZWN0aW9uIG9mIFJG
QzU4OTIuIE1heWJlIHNvbWUgY2xhcmlmaWNhdGlvbiB0ZXh0IHdvdWxkIGJlIGhlbHBmdWwuIA0K
Q2xhcmlmaWNhdGlvbiBmcm9tIFBhdWwgSG9mZm1hbjogV2UgdGhpbmsgdGhhdCB0aGUgSUFOQSBj
b25zaWRlcmF0aW9ucyBoZXJlIGFyZSwgaW4gZmFjdCwgd2hhdCBSRkMgNTg5MiB3YXMgZGVzaWdu
ZWQgZm9yLiBUaGF0IGlzLCBSRkMgNTg5MiBzYXlzIHRoYXQgdGhlIHJlZ2lzdHJ5IHdpbGwgYmUg
dXBkYXRlZCAoIklBTkEgaGFzIGNyZWF0ZWQgYSByZWdpc3RyeSB3aXRoIHRoZSBkZXJpdmVkIHBy
b3BlcnRpZXMgZm9yIHRoZSB2ZXJzaW9ucyBvZiBVbmljb2RlIHJlbGVhc2VkIGFmdGVyIChhbmQg
aW5jbHVkaW5nKSB2ZXJzaW9uIDUuMiIpLiANCldlIGFyZSBub3QgdXBkYXRpbmcgZWl0aGVyIDU4
OTIsIG5vciB0aGUgcmVnaXN0cnksIGJ5IHB1Ymxpc2hpbmcgNTg5MmJpcy4gV2UgYXJlIHNpbXBs
eSBnaXZpbmcgSUVURiBjb25zZW5zdXMgYWR2aWNlIGFib3V0IHdoYXQgd2UgdGhpbmsgdGhlIGV4
cGVydCByZXZpZXdlciB3aG8gdXBkYXRlcyB0aGUgcmVnaXN0cnkgc2hvdWxkIGNvbnNpZGVyLg0K
V2UgY2FuIGNoYW5nZSB0aGUgSUFOQSBjb25zaWRlcmF0aW9ucyB0byByZWZsZWN0IHRoYXQ6DQog
ICBJQU5BIHdpbGwgdXBkYXRlIHRoZSBkZXJpdmVkIHByb3BlcnR5IHZhbHVlIHJlZ2lzdHJ5IGFj
Y29yZGluZyB0bw0KICAgUkZDIDU4OTIgYW5kIHByb3BlcnR5IHZhbHVlcyBhcyBkZWZpbmVkIGlu
IFRoZSBVbmljb2RlIFN0YW5kYXJkDQogICB2ZXJzaW9uIDYuMCwgcmVnYXJkbGVzcyBvZiB0aGUg
Y29udGVudCBvZiB0aGlzIFJGQy4NCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpp
c3N1ZTQ6IEFkZCB0aGUgSUFOQSBJRE5BIHJlZ2lzdHJ5IG9yIHJlcGxhY2UgdGhlIG9sZCBvbmU/
IA0KQ29tbWVudCBmcm9tIEpvaG4gQyBLbGVuc2luOiBNeSBleHBlY3RhdGlvbiB3aGVuIDU5ODIg
d2FzIGNvbXBsZXRlZA0Kd2FzIHRoYXQgSUFOQSB3YXMgZXhwZWN0ZWQgdG8ga2VlcCBkZXJpdmVk
IHByb3BlcnR5IHRhYmxlcywNCmNsZWFybHkgaWRlbnRpZmllZCBieSB2ZXJzaW9uLCBmb3IgZWFj
aCBhbmQgZXZlcnkgVW5pY29kZQ0KdmVyc2lvbiBmcm9tIDUuMiBmb3J3YXJkLiAgSW4gb3RoZXIg
d29yZHMsIHRoZSB0YWJsZXMgZm9yIHRoZQ0KW21vc3RdIGN1cnJlbnQgdmVyc2lvbiB3b3VsZCBi
ZSBhZGRlZCB0bywgbm90IHJlcGxhY2UsIHdoYXRldmVyDQpwcmV2aW91cyB2ZXJzaW9uIHRhYmxl
cyB3ZXJlIGFyb3VuZC4gIFRoZSByZWFzb25zIGZvciB0aGlzLCBpbg0KdGVybXMgb2Ygc3lzdGVt
cyBhbmQgaW1wbGVtZW50YXRpb25zIGluIHZhcmlvdXMgc3RhZ2VzIG9mDQpkZXZlbG9wbWVudCwg
aW1wbGVtZW50YXRpb24sIGFuZCBkZXBsb3ltZW50LCBzZWVtIG9idmlvdXMuLi4gYnV0DQptYXli
ZSBpdCB3YXMgdG9vIG9idmlvdXMgdG8gc29tZSBvZiB1cyBhdCB0aGUgdGltZSB0byBnZXQgdGhl
DQp3b3JkaW5nIGV4YWN0bHkgcmlnaHQuDQpDb21tZW50IGZyb20gUGF1bCBIb2ZmbWFuOiBXaGls
ZSBKb2huJ3MgaW50ZXJwcmV0YXRpb24gY291bGQgYmUgb25lIHRoaW5nIHdlIG1pZ2h0IGhhdmUg
bWVhbnQsIGl0IGlzIG5vdCB3aGF0IGlzIHJlZmxlY3RlZCBpbiB0aGUgUkZDIG9yIHRoZSByZWdp
c3RyeS4NCk5vdGUgdGhhdCBldmVyeSByZWZlcmVuY2UgdG8gdGhlIHJlZ2lzdHJ5IGlzIHNpbmd1
bGFyLiBBbHNvLCB0aGUgcmVnaXN0cnkgYXQgPGh0dHA6Ly93d3cuaWFuYS5vcmcvYXNzaWdubWVu
dHMvaWRuYWJpcy10YWJsZXMvaWRuYWJpcy10YWJsZXMueG1sPiBkb2Vzbid0IG1lbnRpb24gIjUu
MiIgYXQgYWxsLg0KSWYgdGhlIHJlZ2lzdHJ5IGRlZmluaXRpb24gZG9lcyBub3QgdGFsayBhYm91
dCBrZWVwaW5nIHZlcnNpb25zLCBhbmQgdGhlIHJlZ2lzdHJ5IGl0c2VsZiBkb2Vzbid0IGxvb2sg
bGlrZSBpdCB0cmllZCwgaXQgbWF5IGJlIGltcGxhdXNpYmxlIHRvIHRoaW5rIHRoYXQgSUFOQSB3
b3VsZCBqdXN0IHN0YXJ0IHRvIGRvIHNvIGluIHNvbWUgZnV0dXJlLiBUbyBtZSwgImEgcmVnaXN0
cnkiIG1lYW5zIGEgc2luZ2xlIHJlZ2lzdHJ5Lg0KKioqKipXZSBhcmUgd2FpdGluZyBmb3IgSm9o
biBhbmQgUGF1bCByZWFjaGluZyB0aGUgYWdyZWVtZW50IGFib3V0IHRoaXMgaXNzdWUqKioqKioq
DQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KaXNzZTU6IEFib3V0IG5vbi1iYWNr
d2FyZC1jb21wYXRpYmxlIGNoYW5nZXMgb2YgdGhlIHRhYmxlIG9mIGRlcml2ZWQgcHJvcGVydHkg
dmFsdWVzDQpSb25pIEV2ZW46IFNlY3Rpb24gNS4xIG9mIFJGQzU4OTIgc2F5cyAiSWYgbm9uLWJh
Y2t3YXJkLWNvbXBhdGlibGUgY2hhbmdlcyBvciBvdGhlcg0KcHJvYmxlbXMgYXJpc2UgZHVyaW5n
IHRoZSBjcmVhdGlvbiBvciBkZXNpZ25hdGVkIGV4cGVydCByZXZpZXcgb2YgdGhlIHRhYmxlIG9m
IGRlcml2ZWQgcHJvcGVydHkgdmFsdWVzLCB0aGV5IHNob3VsZCBiZSBmbGFnZ2VkIGZvciB0aGUg
SUVTRy4iIC4gTXkgcXVlc3Rpb24gd2FzIGlmIHRoZQ0KY2hhbmdlIGlzIGJhY2t3YXJkIGNvbXBh
dGlibGUuIFRoZSA1ODkyYmlzIGRyYWZ0IGRvZXMgbm90IHNheSBpdC4NCkNsYXJpZmljYXRpb24g
ZnJvbSBQYXVsIEhvZmZtYW46IFdlIGludGVuZGVkIHRoYXQgYXMgIm5vbi1iYWNrd2FyZHMtY29t
cGF0aWJsZSI7d2UgY2FuIGNoYW5nZSB0aGUgd29yZGluZyB0byBtYWtlIHRoYXQgZXhwbGljaXQu
DQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIA0KaXNzdWU2OiBBYm91dCB0aGUgcmVm
ZXJlbmNlIG9mIHRoZSBJQU5BIHJlZ2lzdHJ5IGZvciBkZXJpdmVkIHByb3BlcnR5IHZhbHVlIA0K
Um9uaSBFdmVuOiAgVGhlIElBTkEgcmVnaXN0cnkgZm9yIGRlcml2ZWQgcHJvcGVydHkgdmFsdWUg
aGFzIFJGQyA1ODkyLCBkb2VzIHRoaXMgZHJhZnQgd2FudCB0byBjaGFuZ2UgdGhlIHJlZmVyZW5j
ZSwgaG93IHdpbGwgaXQgYmUgZG9uZT8NCkNsYXJpZmljYXRpb24gZnJvbSBQYXVsIEhvZmZtYW46
ICBTZWN0aW9uIDIgb2YgdGhlIGRyYWZ0IGlzIHByZXR0eSBjbGVhciBoZXJlOiAiTm8gY2hhbmdl
IHRvIFJGQyA1ODkyIGlzIG5lZWRlZCBiYXNlZCBvbiB0aGUgY2hhbmdlcyBtYWRlIGluIFVuaWNv
ZGUgNi4wIi4NCjU4OTJiaXMoUkZDKSB3aWxsIG5vdCBiZSBsaXN0ZWQgaW4gdGhlIHJlZ2lzdHJ5
LiANCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIA0KaXNzdWU3OiBBYm91dCB0aGUgaW1w
YWN0cyBvbiB0aGUgY3VycmVudCBpbXBsZW1lbnRhdGlvbiBvZiBSRkMgNTg5MiAodGhlIHJlbGF0
aW9uc2hpcCBiZXR3ZWVuIHRoZSBydWxlcyBhbmQgdGhlIHRhYmxlcykNClNpbW9uIEpvc2Vmc3Nv
bqO6SWYgdGhlIGRvY3VtZW50IGRvZXMgbm90IHVwZGF0ZSBSRkMgNTg5MiAob3Igc29tZSBvdGhl
ciBkb2N1bWVudCksIEkNCnN1cHBvcnQgcHVibGlzaGluZyB0aGlzIGRvY3VtZW50IGJlY2F1c2Ug
aXQgd2lsbCBub3QgYWZmZWN0IG15DQppbXBsZW1lbnRhdGlvbiBvZiBSRkMgNTg5Mi4gSWYgaXQg
bWFya3MgdXBkYXRpbmcgUkZDNTg5MiwgSSBhbSBhZnJhaWQgdGhhdCBJIGhhcyB0byB1cGRhdGUg
dGhlIGltcGxlbWVudGF0aW9uLg0KDQpDbGFyaWZpY2F0aW9uIGZyb20gSm9obiBDIEtsZW5zaW46
IA0KVGhlIHRleHQgaW4gU2VjdGlvbiA0IG9mIHRoaXMgZHJhZnQgc2F5czoNCiJUaGUgdGFibGUg
aW4gQXBwZW5kaXggQiBzaG93cywgZm9yIGlsbHVzdHJhdGl2ZQ0KcHVycG9zZXMsIHRoZSBjb25z
ZXF1ZW5jZXMgb2YgdGhlIGNhdGVnb3JpZXMgYW5kDQpjbGFzc2lmaWNhdGlvbiBydWxlcywgYW5k
IHRoZSByZXN1bHRpbmcgcHJvcGVydHkgdmFsdWVzLiINCg0KIlRoZSBsaXN0IG9mIGNvZGUgcG9p
bnRzIHRoYXQgY2FuIGJlIGZvdW5kIGluIEFwcGVuZGl4IEINCmlzIG5vbi1ub3JtYXRpdmUuICBT
ZWN0aW9ucyAyIGFuZCAzIGFyZSBub3JtYXRpdmUuIg0KDQoNClRob3NlIHRhYmxlcyBjb250YWlu
aW5nIFUrMTlEQSBjaGFyYWN0ZXIgYXJlIG5vdCBub3JtYXRpdmUsIHNvIGl0IGlzIG5vdCBwb3Nz
aWJsZSB0byBzYXkgIkkNCmltcGxlbWVudGVkIHRoZSB0YWJsZXMgaW4gUkZDIDU4OTIgYW5kIHRo
ZXJlZm9yZSBJIGNvbmZvcm0gdG8NCnRoZSBzdGFuZGFyZCIuICBUaGUgY2xvc2VzdCB5b3UgY2Fu
IGdldCB3b3VsZCBiZSB0byBzYXkgIkkNCmltcGxlbWVudGVkIHRoZSBydWxlcyBhbmQgdGVzdGVk
IGFnYWluc3QgdGhlIHRhYmxlcyB3aGVuIHRob3NlDQpydWxlcyB3ZXJlIGFwcGxpZWQgdG8gVW5p
Y29kZSA1LjIgYW5kIHRoZXJlZm9yZSBoYXZlIGdyZWF0DQpjb25maWRlbmNlIGluIG15IGltcGxl
bWVudGF0b24iLCBidXQgY29uZm9ybWFuY2Ugc3RhdGVtZW50cyBzdG9wDQp3aXRoICJpbXBsZW1l
bnRlZCB0aGUgcnVsZXMgY29ycmVjdGx5Ii4=


From jnc@mercury.lcs.mit.edu  Wed Jun  8 09:04:17 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37C6711E8142; Wed,  8 Jun 2011 09:04:17 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4VahQG86UmOI; Wed,  8 Jun 2011 09:04:16 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 1FF4511E8158; Wed,  8 Jun 2011 09:04:15 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 1F8CF18C121; Wed,  8 Jun 2011 12:04:15 -0400 (EDT)
To: ietf@ietf.org, v6ops@ietf.org
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
Message-Id: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu>
Date: Wed,  8 Jun 2011 12:04:15 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 16:04:17 -0000

    > From: Martin Rex <mrex@sap.com>

    > Classification of 6to4 as historic is [in]appropriate use of the IETF
    > process, because it would be a political .. statement.

Well, we've never done _that_ before, have we? Wouldn't want to set an
unfortunate precedent.

	Noel

From jhw@apple.com  Wed Jun  8 09:17:45 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E59A911E81D7; Wed,  8 Jun 2011 09:17:44 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A5pmuyC+af5o; Wed,  8 Jun 2011 09:17:43 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 709B411E81D5; Wed,  8 Jun 2011 09:17:43 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LMH002P3BW0AKF1@mail-out.apple.com>; Wed, 08 Jun 2011 09:17:41 -0700 (PDT)
X-AuditID: 11807134-b7c00ae0000074fb-f9-4defa0a49e7e
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay14.apple.com (Apple SCV relay) with SMTP id 86.4E.29947.5A0AFED4; Wed, 08 Jun 2011 09:17:41 -0700 (PDT)
Received: from event-10-1-91-170.venue.apple.com (unknown [192.42.249.91]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LMH00JOYBXGRQ40@cardamom.apple.com>; Wed, 08 Jun 2011 09:17:40 -0700 (PDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
From: james woodyatt <jhw@apple.com>
In-reply-to: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu>
Date: Wed, 08 Jun 2011 09:17:41 -0700
Message-id: <49D685CB-00FD-42E5-9AD8-15E51545D9A2@apple.com>
References: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1237.1)
X-Brightmail-Tracker: AAAAAA==
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 16:17:45 -0000

On Jun 8, 2011, at 9:04 AM, Noel Chiappa wrote:
> From: Martin Rex <mrex@sap.com>
>> 
>> Classification of 6to4 as historic is [in]appropriate use of the IETF process, because it would be a political .. statement.
> 
> Well, we've never done _that_ before, have we? Wouldn't want to set an unfortunate precedent.

I see no reason for IETF to avoid setting standards for layer-9 protocols.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From presnick@qualcomm.com  Wed Jun  8 10:12:05 2011
Return-Path: <presnick@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 BC6E321F8546; Wed,  8 Jun 2011 10:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.391
X-Spam-Level: 
X-Spam-Status: No, score=-106.391 tagged_above=-999 required=5 tests=[AWL=0.208, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3Qdxm2d1n-B; Wed,  8 Jun 2011 10:12:04 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id BA76D21F8526; Wed,  8 Jun 2011 10:12:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1307553124; x=1339089124; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4DEFAD27.1070701@qualcomm.com>|Date:=20We d,=208=20Jun=202011=2012:11:03=20-0500|From:=20Pete=20Res nick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Jiankang=20YAO=20<yaojk@cnnic. cn>|CC:=20IETF-Discussion=20list=20<ietf@ietf.org>,=20<ap psawg-ads@tools.ietf.org>,=0D=0A=09<apps-discuss@ietf.org >|Subject:=20Re:=20Summary=20for=20IESG=20last=20call=20t o=205892bis=20draft|References:=20<FFB4A22E53204E7E8DDACF 16D2F5588D@LENOVO47E041CF>|In-Reply-To:=20<FFB4A22E53204E 7E8DDACF16D2F5588D@LENOVO47E041CF>|Content-Type:=20text/p lain=3B=20charset=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.48.1]; bh=aB8qEwTHYfUu7F1i2dB55ZYUz7ccKNUyEfQoELPtK+M=; b=DtCcBkw5iOb9vGj3x1+wjawlk4JVsvEjiMLo4eo7Vt30GLbyk2+hxkT6 xqnMSsQ7ihKkWzxWFsMAd+uxCLkpCmbA/DaH5KEAVCdsn+03Xdfw76GYl jrW+tYpL0CG68uEXnkjT5YgNZcFMGOBcyNiJX5cmsLcl7CtbnVkObipTx U=;
X-IronPort-AV: E=McAfee;i="5400,1158,6370"; a="96232796"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine02.qualcomm.com with ESMTP; 08 Jun 2011 10:12:04 -0700
X-IronPort-AV: E=Sophos;i="4.65,339,1304319600"; d="scan'208";a="143323448"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 08 Jun 2011 10:12:04 -0700
Received: from Macintosh-4.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.1.270.1; Wed, 8 Jun 2011 10:11:05 -0700
Message-ID: <4DEFAD27.1070701@qualcomm.com>
Date: Wed, 8 Jun 2011 12:11:03 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Jiankang YAO <yaojk@cnnic.cn>
Subject: Re: Summary for IESG last call to 5892bis draft
References: <FFB4A22E53204E7E8DDACF16D2F5588D@LENOVO47E041CF>
In-Reply-To: <FFB4A22E53204E7E8DDACF16D2F5588D@LENOVO47E041CF>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: IETF-Discussion list <ietf@ietf.org>, apps-discuss@ietf.org, appsawg-ads@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 17:12:05 -0000

Well, a little miscommunication; I had meant to send the summary to the 
APPSAWG where the document was discussed, but sending it to the IETF 
list is OK too. Since it's here, one comment:

On 6/8/11 2:04 AM, Jiankang YAO wrote:
> ----------------------------
> issue4: Add the IANA IDNA registry or replace the old one?
> [...]
> *****We are waiting for John and Paul reaching the agreement about this issue*******
>    

I think we have gotten agreement from folks (including but not limited 
to doc authors and ADs involved in the conversation) that we'll go ahead 
with this document and write a quick new document clarifying that what 
5892 meant was that IANA should *add* a new table to the registry and 
(with the older one) label it as to from which version of Unicode the 
table was generated.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From brian.e.carpenter@gmail.com  Wed Jun  8 10:52:52 2011
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 DB22511E8125; Wed,  8 Jun 2011 10:52:52 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TelmRgEVz0yo; Wed,  8 Jun 2011 10:52:52 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 041F111E8076; Wed,  8 Jun 2011 10:52:51 -0700 (PDT)
Received: by fxm15 with SMTP id 15so574315fxm.31 for <multiple recipients>; Wed, 08 Jun 2011 10:52:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=7x+fiy/1CXZMidDy3X1YCnNBKxDxJgIoeziR6mxgcgA=; b=cdYoYRj3nwl4fVXf2D0lDjtlSI9ufyyeuMspmrKKBGPBNJ+HDB+vYJ/rUUDBFYciJQ EWy/lO/d6u943ipiGPQdx2ib0QO3kjTx0BViw5mLxpXlah+TmYHmxTwhOuWQzg43zvAw E2R7Aay+K1CwUKEF8AmfyMfnssSvu4GsFSYM8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=nxKnahLzMwBMDnxvlA57ARnE4ZBgKezw2belrYZ+JTZ7o/q95m/ixhUC/+4jaVLDRw fotUcoGMdNVw2IKYiPPMsLZ+M/ol21Z9g3VKmqy1SFGQQlZGGl+Ajba+FS9i19TscMJF wMUqi5KXlm4O4QfIKTzAmT9AF4VB4ZF7fW8KY=
Received: by 10.223.97.142 with SMTP id l14mr1133108fan.137.1307555570771; Wed, 08 Jun 2011 10:52:50 -0700 (PDT)
Received: from [10.255.25.89] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id q21sm330138fan.40.2011.06.08.10.52.47 (version=SSLv3 cipher=OTHER); Wed, 08 Jun 2011 10:52:49 -0700 (PDT)
Message-ID: <4DEFB6EB.8020103@gmail.com>
Date: Thu, 09 Jun 2011 05:52: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: james woodyatt <jhw@apple.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
References: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu> <49D685CB-00FD-42E5-9AD8-15E51545D9A2@apple.com>
In-Reply-To: <49D685CB-00FD-42E5-9AD8-15E51545D9A2@apple.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org WG" <v6ops@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, 08 Jun 2011 17:52:55 -0000

On 2011-06-09 04:17, james woodyatt wrote:
> On Jun 8, 2011, at 9:04 AM, Noel Chiappa wrote:
>> From: Martin Rex <mrex@sap.com>
>>> Classification of 6to4 as historic is [in]appropriate use of the IETF process, because it would be a political .. statement.
>> Well, we've never done _that_ before, have we? Wouldn't want to set an unfortunate precedent.
> 
> I see no reason for IETF to avoid setting standards for layer-9 protocols.

In any case, I don't see the politics, unless (for example) declaring
RFC 1267 Historic was politics too.

   Brian

From randy_presuhn@mindspring.com  Wed Jun  8 11:41:59 2011
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 AED0C21F85E4 for <ietf@ietfa.amsl.com>; Wed,  8 Jun 2011 11:41: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X2mbttLUVap4 for <ietf@ietfa.amsl.com>; Wed,  8 Jun 2011 11:41:59 -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 28AD921F85B0 for <ietf@ietf.org>; Wed,  8 Jun 2011 11:41:59 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=Upfs+Ll33KZFc0Wf/YDeEVfeGghiCWqblEIEWCTSjSjD/zNEnervQOdRV8Lh08QC; 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.38.145.135] (helo=oemcomputer) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1QUNhW-00089X-6t for ietf@ietf.org; Wed, 08 Jun 2011 14:41:58 -0400
Message-ID: <006601cc260c$4a0c87e0$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu> <49D685CB-00FD-42E5-9AD8-15E51545D9A2@apple.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
Date: Wed, 8 Jun 2011 11:45:49 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888cc964a8bf633b38267a243df9feea9b1b8e7832b6406859f350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.38.145.135
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 18:41:59 -0000

Hi -

> From: "james woodyatt" <jhw@apple.com>
> To: <ietf@ietf.org>
> Cc: <v6ops@ietf.org>
> Sent: Wednesday, June 08, 2011 9:17 AM
> Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
>
> On Jun 8, 2011, at 9:04 AM, Noel Chiappa wrote:
> > From: Martin Rex <mrex@sap.com>
> >> 
> >> Classification of 6to4 as historic is [in]appropriate use of the IETF process, because it would be a political .. statement.
> > 
> > Well, we've never done _that_ before, have we? Wouldn't want to set an unfortunate precedent.
> 
> I see no reason for IETF to avoid setting standards for layer-9 protocols.

I'm pretty sure Noel was being scarcastic.  There's clear precedent in the
analogous case where RFC 1227 was  declared historic, despite its
widespread use for that particular application at the time.

On the other side of the argument, declaring RFC 1227 historic had little
(I'm being generous) impact on its continued use.  The folks that needed it
kept using it, in some cases long after the IETF's replacement for it became
widely available.

Randy


From moore@network-heretics.com  Wed Jun  8 13:19:18 2011
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 E848C21F85D1; Wed,  8 Jun 2011 13:19:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.081
X-Spam-Level: 
X-Spam-Status: No, score=-0.081 tagged_above=-999 required=5 tests=[AWL=-2.798, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_21=0.6, J_CHICKENPOX_210=0.6, J_CHICKENPOX_23=0.6, J_CHICKENPOX_24=0.6, J_CHICKENPOX_25=0.6, J_CHICKENPOX_31=0.6, J_CHICKENPOX_32=0.6, J_CHICKENPOX_34=0.6, J_CHICKENPOX_37=0.6, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ILu4z6jd4M7; Wed,  8 Jun 2011 13:19:15 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id AC44521F85CC; Wed,  8 Jun 2011 13:19:14 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 7FF5920773; Wed,  8 Jun 2011 16:19:12 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Wed, 08 Jun 2011 16:19:12 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=z3stzUjtnjMm/mp+0TFJ2zEpOmI=; b=Op8Q1FZIUx0uOwY6LNQHUnhOqYskrMy8QIMbi7fipvztBWjk+YEXRARvyErPdNR2L7z6tjRqO3+4Wb9qx2J0DxZwwEFghHiUNSQFQGFALGp3UHeGbkfnfQqSEPN+HPxIX8QEtOjTviOK+c1hTWkgLkTGbl/CUQfi3zq1C8MzxyY=
X-Sasl-enc: zPI7fwp8naEnG8L+cb9XjiOu9TX98R/ePcW9ASRgX7Li 1307564345
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 6CF904047BA; Wed,  8 Jun 2011 16:19:05 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-21-692146429
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <34E4F50CAFA10349A41E0756550084FB0690A2B5@PRVPEXVS04.corp.twcable.com>
Date: Wed, 8 Jun 2011 16:19:04 -0400
Message-Id: <C58AF2D7-C362-4A76-BD59-F6B78C6746B0@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0690A2B5@PRVPEXVS04.corp.twcable.com>
To: "George, Wesley" <wesley.george@twcable.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <v6ops@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, 08 Jun 2011 20:19:18 -0000

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


On Jun 8, 2011, at 3:28 PM, George, Wesley wrote:

> =20
> From: Keith Moore [mailto:moore@network-heretics.com]=20
> Sent: Tuesday, June 07, 2011 6:48 PM
> To: George, Wesley
> Cc: ietf@ietf.org; v6ops@ietf.org
> Subject: Re: [v6ops] Last Call: =
<draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection =
of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to =
Informational RFC
> =20
> KM>I've been using 6to4 on a regular, often daily, basis since the =
late 1990s.   6to4 has allowed me to develop IPv6 applications and test =
them on real networks, and deploy them in limited circumstances.  6to4 =
has also allowed me to remotely access computers on my SOHO networks, =
using any application protocol that I chose to do so, with =
out-of-the-box hardware and software, without any application-specific =
proxies, and generally without any application-specific configuration.  =
None of these scenarios required a relay router.  All of them were, and =
continue to be, useful.
> =20
> KM> Yes, I've experienced on many occasions that using 6to4 to access =
dual-stack web servers doesn't always work so well.  Sometimes it picks =
a suboptimal path because the relay router isn't convenient.  Sometimes =
the v6 path doesn't work at all and the application has to time out and =
retry using v4.   But this never really bothered me much, because my =
purpose in using 6to4 wasn't to try to access services that I could get =
to via IPv4 anyway.  And neither, I suggest, is that a reasonable metric =
for evaluating 6to4 or any other IPv6 transition mechanism.   The metric =
for evaluating an IPv6 transition mechanism should be based on its =
effectiveness in accessing services that are IPv6 only.  =20
> =20
> WEG> Again, are you or are you not using a relay router? You keep =
going back and forth.

No, I don't keep going back and forth.  I am able to use 6to4 usefully =
without a relay router.   But I do have the anycast address configured =
as the relay router, and I find that useful also.

> Bluntly, this isn=92t about whether you, or anyone else at IETF use =
6to4.

Nor, bluntly, is it about a few big content providers or whomever else =
you want to label as important.  The internet is a hugely diverse place, =
and you don't get to dismiss the concerns of people whom you want to =
label as red herrings.   Again, 40-something percent of the IPv6 traffic =
that is observed on the net today uses 6to4.  That's about as much as =
Teredo, it's a hell of a lot more than native v6.  As long as 6to4 is =
one of the major ways that people get IPv6 connectivity (and it clearly =
is), it's premature to declare 6to4 historic.

> We are the longest of the long tail; the smallest percentage, the =
exception to the rule, not the exception that proves the rule. We=92re =
network geeks; we=92re willing to deal with dodgy connectivity or =
otherwise fiddly methods of doing things to test them and to prove a =
point. This discussion cannot be about whether the protocol should be =
preserved because some marginal percentage of folks in IETF use 6to4 =
successfully.

40-something percent of the traffic is not marginal.  The marginal use =
is, currently, of native IPv6.

> I am not disagreeing that for some value of =93work=94 6to4 works to =
reach IPv6-only things. What I am saying is that the very things you =
illustrate here make it only acceptable for testing, and not for any =
sort of real substitute for IPv6 connectivity. What user is going to =
accept +100ms in latency due to suboptimal relay choice, or waiting =
multiple seconds for IPv6 to time out because 6to4 didn=92t work in that =
particular network setup?

100ms extra latency as compared to what?  Nonexistent v6 service when =
they need to use v6?   Using v6 for services for which v4 will do just =
fine?   And in which use cases does that 100ms extra latency apply?  =
None in the ones I'm seeing today, on IPv6 day.  =20

You are the one who keeps citing red herrings as evidence that 6to4 =
should be deprecated.  You want to take the least compelling use cases =
for IPv6, and when 6to4 performs suboptimally for some of those cases, =
use that as an excuse to sabotage it. =20

> I think that the evidence says that 6to4 is actually *ineffective* by =
the evaluation you suggest =96 a good portion of the time it either =
utterly fails or provides such degraded service that it may as well not =
work.=20

The evidence is that people are using it.  You're trying to subject it =
to test cases that are largely meaningless - because in those cases IPv6 =
(of any kind) provides no marginal value in the near term.

> KM> - Enterprises have applications that need to be able to =
communicate with large numbers of hosts spread over a diverse area.  =
IPv6 is clearly the way that they want to go, but it's not widely =
available at present.  6to4 provides them with a means of routing =
traffic to their hosts in the interim until widespread support for IPv6 =
exists.
>=20
> WEG> So do IPv6IP or GRE tunnels. Been using one at home for 3+ years =
now. And honestly, if this type of application is going to be =
enterprise-class, it needs to be in conjunction with ISP deployment of =
IPv6, not in spite of it.

Almost all usage of IPv6 today is in spite of ISPs.   For that matter, a =
great many successful IPv4 applications today are deployed in spite of =
ISPs.  Again, ISPs in general have let us down, and 6to4 and Teredo are =
carrying ~90% of IPv6 traffic.   ISPs are not in a good position to =
demand that 6to4 be deprecated. =20

> KM> What you're saying is that applications developers shouldn't =
bother with actually trying to use IPv6 until the ISPs get their act =
together and deploy it.  Well guess what?  The ISPs have let us down.  =
We've been waiting for 15 years for the ISPs to roll out IPv6, and for =
most of those 15 years they were all telling us that there were no =
applications for it.  Now the ISPs are scrambling to get IPv6 into their =
networks, and they want to sabotage the IPv6 mechanisms that we have in =
place even before they are actually offering product.
> =20
> WEG> Yes, yes, shame on the big, bad ISPs and their lack of =
deployment. Trust me, I=92m as annoyed with the ISPs I=92ve worked for =
and been a customer of that it is taking so long to get IPv6 out there =
too.
> But=856to4 sabotaged itself. This draft is acknowledging reality that =
it really didn=92t work the way we=92d hoped.

I have no problem with acknowledging the shortcomings of 6to4 and =
especially of the use of anycast addresses for relay routers.   There =
are valuable lessons to be learned there.  But face it, a lot of stuff =
that's widely deployed on the Internet and useful doesn't work as well =
as we hoped.  We generally don't try to sabotage things that are useful =
to people.

> There is no active malevolence here on the part of the ISPs. In fact =
many of them (us?) have deployed or will be deploying 6to4 relays to =
improve the customer experience until native service is available, and =
are supporting the recommendations to make 6to4 suck less in =
draft-carpenter.

That's excellent news.  But the current proposal on the table to =
deprecate 6to4 is premature, confusing, and harmful to real users.

> KM>Widespread IPv6 support for native IPv6 would be when native IPv6 =
is available everywhere that IPv4 access is available, from at least one =
provider, with quality (connectivity, reliability, support) =
approximately as good as IPv4, and at a reasonable price.  In other =
words, you can't expect applications to rely on native IPv6 until it's =
reliably available everywhere that they need to use it.
>=20
> WEG> So Widespread IPv6 has to have reliability and support equivalent =
to IPv4, yet you're saying that you can expect applications to rely on =
6to4 in the meantime despite evidence that it's unreliable, and the =
virtual guarantee that it won't be supported by the upstream ISP?
> =20
> KM>There's no such virtual guarantee.  =20
> WEG>I should probably have clarified that by =93support=94 I don=92t =
mean =93will pass protocol 41 IPv4 packets.=94 I mean =93can call and =
yell at someone when it breaks.=94 Make more sense now?

So let's narrow the focus on relay routers that advertise anycast =
addresses.   I think it's clear that they're the major part of the =
problem with 6to4.    Maybe there is a way to filter out the =
advertisements for the ones that blackhole traffic; maybe all such =
advertisements for those prefixes should be filtered and 6to4 users =
should have to explicitly configure relay routers.   But whatever the =
fix, this is a fairly narrow problem and it warrants narrow corrective =
action.

> WEG> I am simply saying that I do not for a second believe that those =
same applications that are so important to that user community are at =
the same time unimportant enough that they're the sacrificial lamb that =
has to go IPv6-only when the majority of that user community, no matter =
how small, doesn't have native IPv6 access yet.
> =20
> KM>You have absolutely no idea which applications will be important to =
the user community tomorrow.   Who knows what will be the next netflix, =
twitter, facebook, youtube, ... ?   The Internet is successful not =
because it supports some small number of apps that operators think are a =
good idea; it's successful because it (at least as originally =
architected) can support a wide range of apps without operators having =
to bless them.=20
> WEG> One of the few places I=92m in agreement with you. However, it=92s =
not a justification for 6to4. It=92s a justification for ubiquitous =
IPv6.

It's not one versus the other.   6to4 is helping to promote ubiquitous =
IPv6.

> It=92s not about whether the operators =93bless=94 an application or =
not. If those up-and-coming applications are saddled with the =
performance hit that 6to4 represents, they are unlikely to be =
successful. In other words, 6to4 will not move the needle on innovative =
IPv6-only applications, so they=92re tied to the native IPv6 rollout =
schedule. Sad, but true.

There are many applications that can't be widely successful because of =
NATs, or lack of addresses.  IPv6 (and 6to4) offer those applications a =
chance to be successful.   6to4 does not inherently represent a =
performance hit.  In some cases, it provides connectivity to other IPv6 =
hosts (whether 6to4 or native) where no other connectivity was as easily =
available (and without having to explicitly set up tunnels that also =
cause performance hits.)   Some connectivity to IPv6 is generally better =
than none.   Again, if you try to compare v6 performance to v4 =
performance, it will be a long time until there are no cases where the =
v6 performance comes up short.   Those comparisons are meaningless, =
because the reason to move to 6to4 isn't to get better performance than =
v6 for applications that already work fine with v4.  It's to enable new =
kinds of apps that don't work well in a v4 network full of NATs, and to =
enable new users and new kinds of devices to be able to fully =
participate in the Internet.

> =20
> WEG>This is the essence of the IPv6 content vs access chicken/egg =
problem, and 6to4 absolutely will not break the impasse. 6to4 breakage =
is the most common thing that content providers cite as reasons why they =
don't just go dual-stack. Why would an enterprise application be any =
different?
> =20
> KM> It doesn't really matter much whether "content-providers" (as in =
web site providers) go "dual stack" now.  Sure, they need to be gearing =
up for it, making sure that they understand it, making sure that their =
networks support it.  (Or maybe they'll just install v6-to-v4 proxies at =
their borders so that they can keep providing good customer service in =
the face of LSN-induced brain damage on the public v4 network.)   But =
assuming their applications work through LSN, they're going to keep =
supporting v4 for a long time anyway, because that's the established =
base of interoperability for their products and services.   Existing =
"content providers" are not going to drive adoption of IPv6.   They're =
going to follow it.  Web and email will be the last applications to =
migrate.  New content might appear on v6, and that might drive adoption. =
 But to the extent that it drives adoption, it probably won't be from =
the currently established players that already have plenty of v4 =
addresses and infrastructure.  It will be from new things that take =
advantage of the niches created by IPv6 that didn't exist before.
> WEG> This is a variant of the old =93IPv6 Killer App=94 discussion. =
We=92re still waiting for one, largely because people are afraid of =
excluding some non-trivial percentage of the populace from being able to =
use their new, cool thing because it=92s IPv6-only, and they don=92t =
think it will so compelling as to be a justification for people to find =
a workaround or clamor for IPv6 support.

Though I have no doubt that some such apps will eventually appear, the =
case for IPv6 doesn't have to be a single killer app that's visible to =
everybody.  The Internet isn't only valuable because of killer apps.   =
B2b communication (e.g. EDI), for instance, isn't any single kind of =
killer app that people generally recognize.  But it's extremely valuable =
to society, and it's tremendously impaired by NATs and widespread use of =
private IPv4 address space.

> IMO, IPv4 exhaustion and CGN is the closest thing we have to a Killer =
App for IPv6. If 6to4 somehow provides an incentive for folks to =
generate IPv6-only applications, and for ordinary users to start using =
6to4 to connect to IPv6, I=92m wondering why it hasn=92t accomplished =
that goal in the last 10 years?What would be different all of the =
sudden?=20

Killer apps are in the eyes of the beholders.  Early adopters of IPv6 =
are using it in myriad ways that are quite useful to them.   If they can =
find uses for v6, so can new users, and makers of new products.    It's =
not necessary for there to be a single killer app that requires v6 that =
everyone knows about, for IPv6 to be widely useful.

> KM> 6to4 is as reliable as IPv4 is, if it isn't asked to cross a relay =
router.
> WEG> perhaps (with the exception of MTU issues that plague any =
tunneled protocol), but you continue to not provide any examples of this =
being used anywhere, in the face of significant evidence that 6to4 is =
horribly unreliable *with* a relay. So this gets filed in the same place =
as my 100% secure file server which happens to be unplugged from power =
and network and encased in 10ft of concrete. Theoretically perfect, but =
otherwise practically useless.
> =20
> KM>What is "anywhere" to you?  You seem to have a content-centric view =
of the Internet.  I do not.   Meanwhile, you persist in saying that =
something that I've used regularly for more than 10 years, to do useful =
work, isn't being used anywhere.
> WEG> No, I=92m trying to follow the same distinction you=92ve drawn =
between 6to4 with relays and without and understand how that=92s being =
used, since apparently 6to4 without relays is a lot less problematic and =
you=92ve had such success with it. What I=92ve read is multiple people =
trying to explain to you that non-anycast 6to4 (3056) is not being used, =
and you continuing to insist that it=92s heavily used by providing =
examples of 3068.

Sorry, that's a complete mischaracterization of everything I have said.  =
 =20

> KM>  I keep seeing figures that 6to4 comprises 40-some-odd percent of =
IPv6 traffic, while native IPv6 is around 10 percent.  By your logic, =
native v6 should be deprecated because it doesn't work reliably and it's =
not being used anywhere.
> WEG> While my general view is that 40% of less than 1% of Internet =
traffic amounts to a statistical anomaly, citation, please? Assuming =
that the source of your statistic is able to distinguish between types =
of protocol 41 traffic, that 40% is almost definitely traffic that is =
using a relay, BTW.

You are as capable of using google as I am.    And the sources I found =
didn't break the 6to4 traffic down between 6to4-to-6to4 vs. =
6to4-to-native (that would definitely have been useful), but your BTW is =
pure speculation.  My speculation would be the opposite, but that's just =
based on my personal experience with 6to4.  =20

(actually it would be nice for such stats to get a full breakdown of the =
different cases: native to native, native to 6to4, native to Teredo, =
6to4 to Teredo, 6to4 to 6to4, Teredo to Teredo)
=20
> KM> The disease is the current IPv4 network with NATs and LSNs and a =
paucity of address space.  6to4 is like a drug that can let some =
valuable v6 applications grow (even if a bit stunted) and survive until =
there's once again a network that will support them.  Sure, there are =
some side effects and contraindications.  But it's useful when used with =
awareness of its limitations.  You're arguing that it should be =
discouraged because it causes some problems.  Indeed it does.  But LSN =
also causes problems, and is a bigger dead-end than 6to4, and it's full =
steam ahead with that.  At least 6to4 is designed to ease transition to =
a saner world, which is a lot more than I can say for LSN.
> WEG> LSN is a necessary evil brought on by the lack of ubiquitous IPv6 =
support, which has many causes. I don=92t like it either. The thing you =
are failing to realize is that IETF saying that 6to4 use is a bad idea =
in no way stops consenting adults from using it in spite of the side =
effects and contraindications, but it does put a much finer point on =
those contraindications.

People who are using 6to4 now might need for new implementations of =
hardware and operating systems to support it.  This draft explicitly =
discourages that. =20

On a broader level, people have a hard time grasping what it means to =
'deprecate' something or to declare it Historic even if the document =
goes into a fair amount of detail about it.  They tend to get the =
high-order bit and to misinterpret that. =20

> KM> I have no doubt that many of those "major content providers" are =
correct when they don't see 6to4 as an acceptable substitute for them.  =
But the Internet doesn't exist just to support "major content =
providers".  So stop trying to sabotage something that works well enough =
for other users.
> WEG> Not trying to imply that it does. I=92m saying that your =
definition of =93works well enough=94 and the average user=92s are =
widely different, making 6to4 a no-op for the average user. The content =
providers=92 position on end users trying to use 6to4 to reach their =
content is an example of that point.=20

The average user of what?   Of IPv6 apps?  I don't think content =
providers know squat about the average users of IPv6 apps.  And anything =
that compares 6to4 performance to IPv4 performance is a red herring, at =
least as applied to an argument about whether 6to4 or not is justified. =20=


> WEG> Why are we having a World IPv6 Day? In part to shake loose the =
broken 6to4 users that may not even know that 6to4 is enabled/broken so =
that content providers can be more confident that they can dual-stack =
their websites without risk of significant user impact due to breakage.
> =20
> KM> I'm looking forward to World IPv6 Day, and what will be learned =
from it.   But again, how well 6to4 works with "major content providers" =
is irrelevant.
> WEG> I might argue that this is because 6to4 is largely irrelevant and =
will become increasingly more so as major ISPs roll out IPv6 in the next =
12-18 months. This is about removing barriers to deployment and use of =
IPv6 for the increasing population of Native IPv6 users, not trying to =
buff the turd for a tiny (but unfortunately very vocal) minority.=20

I'll be happy to abandon use of 6to4 when I can get native (and =
non-NATted) IPv6 access anywhere I live, anywhere I work, and anywhere I =
travel.  If that happens in the next 12-18 months I'll be ecstatic.   =
But I'm not holding my breath.  In 12-18 months I'll be lucky if I can =
get native v6 access in one of those cases.  For the others, I'll =
continue to need some kind of tunneling solution, and 6to4 is often the =
one that works best.   Deprecating 6to4 is imposing a barrier to =
deployment, not removing one.

> WEG>Finally, we're having problems with equipment that doesn't support =
IPv6 at all. 6to4 is not high on the priority list to implement compared =
with a functional IPv6 stack, meaning that on new gear, it likely won't =
get implemented until it's no longer necessary.
> =20
> KM> Gear that doesn't support IPv6 by now is pretty odd gear.     But =
I'm not going to tell you not to use it.  I'm just saying, if you want =
odd gear to work for you in your own specific use cases, don't try to =
sabotage other odd things that work for other people in their specific =
use cases.
> WEG> No. As have multiple others, you assume that I am talking about =
the usual suspects in core routing and enterprise-class networking and =
servers.

Where did you get that idea?

> The consumer electronics space is WOEFULLY behind by comparison. =
That=92s not =93odd=94 gear.

If I were to apply your criteria about what justifies use of 6to4 to =
such devices, they would be odd gear.

> And this isn=92t about me (for some value of me) wanting that gear to =
work for some corner case application. This is  about me having to =
support millions of customers who want that gear to work because they =
don=92t want to buy replacements for something that they see as working =
just fine today. See also CGN =3D necessary evil.

Yes, it's an important problem.     Good luck trying to solve it while =
you're sabotaging things that work for other people.

Keith



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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jun 8, 2011, at 3:28 PM, George, Wesley =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: =
'Times New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div><div style=3D"border-right-style: =
none; border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; border-top-style: solid; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; =
padding-top: 3pt; padding-right: 0in; padding-bottom: 0in; padding-left: =
0in; "><div style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: =
0.0001pt; margin-left: 0in; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><b><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif; ">From:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span>Keith Moore =
[mailto:moore@network-heretics.com]<span =
class=3D"Apple-converted-space">&nbsp;</span><br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Tuesday, June 07, 2011 6:48 =
PM<br><b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span>George,=
 Wesley<br><b>Cc:</b><span class=3D"Apple-converted-space">&nbsp;</span><a=
 href=3D"mailto:ietf@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">ietf@ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:v6ops@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">v6ops@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [v6ops] Last Call: =
&lt;draft-ietf-v6ops-6to4-to-historic-04.txt&gt; (Request to move =
Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to =
Informational RFC<o:p></o:p></span></div></div></div><div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span style=3D"color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div></div></div><div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span style=3D"color: rgb(31, 73, 125); ">KM&gt;</span>I've =
been using 6to4 on a regular, often daily, basis since the late 1990s. =
&nbsp; 6to4 has allowed me to develop IPv6 applications and test them on =
real networks, and deploy them in limited circumstances. &nbsp;6to4 has =
also allowed me to remotely access computers on my SOHO networks, using =
any application protocol that I chose to do so, with out-of-the-box =
hardware and software, without any application-specific proxies, and =
generally without any application-specific configuration. &nbsp;None of =
these scenarios required a relay router. &nbsp;All of them were, and =
continue to be, useful.<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"color: rgb(31, 73, 125); ">KM&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span>Yes, I've =
experienced on many occasions that using 6to4 to access dual-stack web =
servers doesn't always work so well. &nbsp;Sometimes it picks a =
suboptimal path because the relay router isn't convenient. =
&nbsp;Sometimes the v6 path doesn't work at all and the application has =
to time out and retry using v4. &nbsp; But this never really bothered me =
much, because<span class=3D"Apple-converted-space">&nbsp;</span><i>my =
purpose in using 6to4 wasn't to try to access services that I could get =
to via IPv4 anyway. &nbsp;</i>And neither, I suggest, is that a =
reasonable metric for evaluating 6to4 or any other IPv6 transition =
mechanism. &nbsp; The metric for evaluating an IPv6 transition mechanism =
should be based on its effectiveness in accessing services that are IPv6 =
only. &nbsp;&nbsp;<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">WEG&gt; Again, are you or are you not using a relay router? You keep =
going back and =
forth.</span></div></div></div></div></div></span></blockquote><div><br></=
div>No, I don't keep going back and forth. &nbsp;I am able to use 6to4 =
usefully without a relay router. &nbsp; But I do have the anycast =
address configured as the relay router, and I find that useful =
also.</div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Bluntly, =
this isn=92t about whether you, or anyone else at IETF use 6to4. =
</span></div></div></div></div></div></span></blockquote><div><br></div>No=
r, bluntly, is it about a few big content providers or whomever else you =
want to label as important. &nbsp;The internet is a hugely diverse =
place, and you don't get to dismiss the concerns of people whom you want =
to label as red herrings. &nbsp; Again, 40-something percent of the IPv6 =
traffic that is observed on the net today uses 6to4. &nbsp;That's about =
as much as Teredo, it's a hell of a lot more than native v6. &nbsp;As =
long as 6to4 is one of the major ways that people get IPv6 connectivity =
(and it clearly is), it's premature to declare 6to4 =
historic.</div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">We are the =
longest of the long tail; the smallest percentage, the exception to the =
rule, not the exception that proves the rule. We=92re network geeks; =
we=92re willing to deal with dodgy connectivity or otherwise fiddly =
methods of doing things to test them and to prove a point. This =
discussion cannot be about whether the protocol should be preserved =
because some marginal percentage of folks in IETF use 6to4 =
successfully.</span></div></div></div></div></div></span></blockquote><div=
><br></div>40-something percent of the traffic is not marginal. =
&nbsp;The marginal use is, currently, of native =
IPv6.</div><div><br></div><div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "> I am not =
disagreeing that for some value of =93work=94 6to4 works to reach =
IPv6-only things. What I am saying is that the very things you =
illustrate here make it only acceptable for testing, and not for any =
sort of real substitute for IPv6 connectivity. What user is going to =
accept +100ms in latency due to suboptimal relay choice, or waiting =
multiple seconds for IPv6 to time out because 6to4 didn=92t work in that =
particular network setup? =
</span></div></div></div></div></div></span></blockquote><div><br></div><d=
iv>100ms extra latency as compared to what? &nbsp;Nonexistent v6 service =
when they need to use v6? &nbsp; Using v6 for services for which v4 will =
do just fine? &nbsp; And in which use cases does that 100ms extra =
latency apply? &nbsp;None in the ones I'm seeing today, on IPv6 day. =
&nbsp;&nbsp;</div><div><br></div><div>You are the one who keeps citing =
red herrings as evidence that 6to4 should be deprecated. &nbsp;You want =
to take the least compelling use cases for IPv6, and when 6to4 performs =
suboptimally for some of those cases, use that as an excuse to sabotage =
it. &nbsp;</div></div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">I think =
that the evidence says that 6to4 is actually *<b>ineffective</b>* by the =
evaluation you suggest =96 a good portion of the time it either utterly =
fails or provides such degraded service that it may as well not =
work.<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br></div></div></div>=
</div></div></span></blockquote><div><br></div>The evidence is that =
people are using it. &nbsp;You're trying to subject it to test cases =
that are largely meaningless - because in those cases IPv6 (of any kind) =
provides no marginal value in the near term.</div><div><br><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p></o:p></span></div></div></div><div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">KM&gt; - =
Enterprises have applications that need to be able to communicate with =
large numbers of hosts spread over a diverse area. &nbsp;IPv6 is clearly =
the way that they want to go, but it's not widely available at present. =
&nbsp;6to4 provides them with a means of routing traffic to their hosts =
in the interim until widespread support for IPv6 exists.<br><br>WEG&gt; =
So do IPv6IP or GRE tunnels. Been using one at home for 3+ years now. =
And honestly, if this type of application is going to be =
enterprise-class, it needs to be in conjunction with ISP deployment of =
IPv6, not in spite of =
it.</div></div></div></div></div></span></blockquote><div><br></div>Almost=
 all usage of IPv6 today is in spite of ISPs. &nbsp; For that matter, a =
great many successful IPv4 applications today are deployed in spite of =
ISPs. &nbsp;Again, ISPs in general have let us down, and 6to4 and Teredo =
are carrying ~90% of IPv6 traffic. &nbsp; ISPs are not in a good =
position to demand that 6to4 be deprecated. =
&nbsp;</div><div><br></div><div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"color: rgb(31, =
73, 125); ">KM&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span>What you're saying =
is that applications developers shouldn't bother with actually trying to =
use IPv6 until the ISPs get their act together and deploy it. &nbsp;Well =
guess what? &nbsp;The ISPs have let us down. &nbsp;We've been waiting =
for 15 years for the ISPs to roll out IPv6, and for most of those 15 =
years they were all telling us that there were no applications for it. =
&nbsp;Now the ISPs are scrambling to get IPv6 into their networks, and =
they want to sabotage the IPv6 mechanisms that we have in place even =
before they are actually offering product.<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">WEG&gt; Yes, yes, shame on the big, bad ISPs and their lack of =
deployment. Trust me, I=92m as annoyed with the ISPs I=92ve worked for =
and been a customer of that it is taking so long to get IPv6 out there =
too.<o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">But=856to4 =
sabotaged itself. This draft is acknowledging reality that it really =
didn=92t work the way we=92d hoped. =
</span></div></div></div></div></div></span></blockquote><div><br></div>I =
have no problem with acknowledging the shortcomings of 6to4 and =
especially of the use of anycast addresses for relay routers. &nbsp; =
There are valuable lessons to be learned there. &nbsp;But face it, a lot =
of stuff that's widely deployed on the Internet and useful doesn't work =
as well as we hoped. &nbsp;We generally don't try to sabotage things =
that are useful to people.</div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">There is no =
active malevolence here on the part of the ISPs. In fact many of them =
(us?) have deployed or will be deploying 6to4 relays to improve the =
customer experience until native service is available, and are =
supporting the recommendations to make 6to4 suck less in =
draft-carpenter.</span></div></div></div></div></div></span></blockquote><=
div><br></div>That's excellent news. &nbsp;But the current proposal on =
the table to deprecate 6to4 is premature, confusing, and harmful to real =
users.</div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p></o:p></span></div></div></div><div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
">KM&gt;Widespread IPv6 support for native IPv6 would be when native =
IPv6 is available everywhere that IPv4 access is available, from at =
least one provider, with quality (connectivity, reliability, support) =
approximately as good as IPv4, and at a reasonable price. &nbsp;In other =
words, you can't expect applications to rely on native IPv6 until it's =
reliably available everywhere that they need to use it.<br><br>WEG&gt; =
So Widespread IPv6 has to have reliability and support equivalent to =
IPv4, yet you're saying that you can expect applications to rely on 6to4 =
in the meantime despite evidence that it's unreliable, and the virtual =
guarantee that it won't be supported by the upstream =
ISP?<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"color: =
rgb(31, 73, 125); ">KM&gt;</span>There's no such virtual guarantee. =
&nbsp;&nbsp;<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">WEG&gt;I should probably have clarified that by =93support=94 I don=92t =
mean =93will pass protocol 41 IPv4 packets.=94 I mean =93can call and =
yell at someone when it breaks.=94 Make more sense =
now?</span></div></div></div></div></span></blockquote><div><br></div>So =
let's narrow the focus on relay routers that advertise anycast =
addresses. &nbsp; I think it's clear that they're the major part of the =
problem with 6to4. &nbsp; &nbsp;Maybe there is a way to filter out the =
advertisements for the ones that blackhole traffic; maybe all such =
advertisements for those prefixes should be filtered and 6to4 users =
should have to explicitly configure relay routers. &nbsp; But whatever =
the fix, this is a fairly narrow problem and it warrants narrow =
corrective action.</div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: =
'Times New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p></o:p></span></div></div><div><blockquote style=3D"margin-top: =
5pt; margin-bottom: 5pt; "><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"color: =
rgb(31, 73, 125); ">WEG&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span>I am simply saying =
that I do not for a second believe that those same applications that are =
so important to that user community are at the same time unimportant =
enough that they're the sacrificial lamb that has to go IPv6-only when =
the majority of that user community, no matter how small, doesn't have =
native IPv6 access yet.<o:p></o:p></div></div></blockquote><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"color: rgb(31, 73, 125); ">KM&gt;</span>You have absolutely no =
idea which applications will be important to the user community =
tomorrow. &nbsp; Who knows what will be the next netflix, twitter, =
facebook, youtube, ... ? &nbsp; The Internet is successful not because =
it supports some small number of apps that operators think are a good =
idea; it's successful because it (at least as originally architected) =
can support a wide range of apps<span =
class=3D"Apple-converted-space">&nbsp;</span><i>without</i><span =
class=3D"Apple-converted-space">&nbsp;</span>operators having to bless =
them.&nbsp;<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">WEG&gt; One =
of the few places I=92m in agreement with you. However, it=92s not a =
justification for 6to4. It=92s a justification for ubiquitous IPv6. =
</span></div></div></div></div></div></span></blockquote><div><br></div>It=
's not one versus the other. &nbsp; 6to4 is helping to promote =
ubiquitous IPv6.</div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">It=92s not =
about whether the operators =93bless=94 an application or not. If those =
up-and-coming applications are saddled with the performance hit that =
6to4 represents, they are unlikely to be successful. In other words, =
6to4 will not move the needle on innovative IPv6-only applications, so =
they=92re tied to the native IPv6 rollout schedule. Sad, but =
true.</span></div></div></div></div></div></span></blockquote><div><br></d=
iv>There are many applications that can't be widely successful because =
of NATs, or lack of addresses. &nbsp;IPv6 (and 6to4) offer those =
applications a chance to be successful. &nbsp; 6to4 does not inherently =
represent a performance hit. &nbsp;In some cases, it provides =
connectivity to other IPv6 hosts (whether 6to4 or native) where no other =
connectivity was as easily available (and without having to explicitly =
set up tunnels that also cause performance hits.) &nbsp; Some =
connectivity to IPv6 is generally better than none. &nbsp; Again, if you =
try to compare v6 performance to v4 performance, it will be a long time =
until there are no cases where the v6 performance comes up short. &nbsp; =
Those comparisons are meaningless, because the reason to move to 6to4 =
isn't to get better performance than v6 for applications that already =
work fine with v4. &nbsp;It's to enable new kinds of apps that don't =
work well in a v4 network full of NATs, and to enable new users and new =
kinds of devices to be able to fully participate in the =
Internet.</div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p></o:p></span></div></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"color: =
rgb(31, 73, 125); ">WEG&gt;</span>This is the essence of the IPv6 =
content vs access chicken/egg problem, and 6to4 absolutely will not =
break the impasse. 6to4 breakage is the most common thing that content =
providers cite as reasons why they don't just go dual-stack. Why would =
an enterprise application be any =
different?<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"color: =
rgb(31, 73, 125); ">KM&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span>It doesn't really =
matter much whether "content-providers" (as in web site providers) go =
"dual stack" now. &nbsp;Sure, they need to be gearing up for it, making =
sure that they understand it, making sure that their networks support =
it. &nbsp;(Or maybe they'll just install v6-to-v4 proxies at their =
borders so that they can keep providing good customer service in the =
face of LSN-induced brain damage on the public v4 network.) &nbsp; But =
assuming their applications work through LSN, they're going to keep =
supporting v4 for a long time anyway, because that's the established =
base of interoperability for their products and services. &nbsp; =
Existing "content providers" are not going to drive adoption of IPv6. =
&nbsp; They're going to follow it. &nbsp;Web and email will be the last =
applications to migrate. &nbsp;New content might appear on v6, and that =
might drive adoption. &nbsp;But to the extent that it drives adoption, =
it probably won't be from the currently established players that already =
have plenty of v4 addresses and infrastructure. &nbsp;It will be from =
new things that take advantage of the niches created by IPv6 that didn't =
exist before.<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">WEG&gt; This is a variant of the old =93IPv6 Killer App=94 discussion. =
We=92re still waiting for one, largely because people are afraid of =
excluding some non-trivial percentage of the populace from being able to =
use their new, cool thing because it=92s IPv6-only, and they don=92t =
think it will so compelling as to be a justification for people to find =
a workaround or clamor for IPv6 support. =
</span></div></div></div></div></span></blockquote><div><br></div><div>Tho=
ugh I have no doubt that some such apps will eventually appear, the case =
for IPv6 doesn't have to be a single killer app that's visible to =
everybody. &nbsp;The Internet isn't only valuable because of killer =
apps. &nbsp; B2b communication (e.g. EDI), for instance, isn't any =
single kind of killer app that people generally recognize. &nbsp;But =
it's extremely valuable to society, and it's tremendously impaired by =
NATs and widespread use of private IPv4 address =
space.</div><br><blockquote type=3D"cite"><span class=3D"Apple-style-span"=
 style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: =
'Times New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); ">IMO, IPv4 exhaustion and =
CGN is the closest thing we have to a Killer App for IPv6. If 6to4 =
somehow provides an incentive for folks to generate IPv6-only =
applications, and for ordinary users to start using 6to4 to connect to =
IPv6, I=92m wondering why it hasn=92t accomplished that goal in the last =
10 years?What would be different all of the sudden?<span =
class=3D"Apple-converted-space">&nbsp;</span></span></div></div></div></di=
v></span></blockquote><div><br></div>Killer apps are in the eyes of the =
beholders. &nbsp;Early adopters of IPv6 are using it in myriad ways that =
are quite useful to them. &nbsp; If they can find uses for v6, so can =
new users, and makers of new products. &nbsp; &nbsp;It's not necessary =
for there to be a single killer app that requires v6 that everyone knows =
about, for IPv6 to be widely useful.</div><div><br><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; ">KM&gt; 6to4 is as reliable as =
IPv4 is, if it isn't asked to cross a relay router.<br>WEG&gt; perhaps =
(with the exception of MTU issues that plague any tunneled protocol), =
but you continue to not provide any examples of this being used =
anywhere, in the face of significant evidence that 6to4 is horribly =
unreliable *with* a relay. So this gets filed in the same place as my =
100% secure file server which happens to be unplugged from power and =
network and encased in 10ft of concrete. Theoretically perfect, but =
otherwise practically useless.<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"color: rgb(31, 73, 125); ">KM&gt;</span>What is "anywhere" to =
you? &nbsp;You seem to have a content-centric view of the Internet. =
&nbsp;I do not. &nbsp; Meanwhile, you persist in saying that something =
that I've used regularly for more than 10 years, to do useful work, =
isn't being used anywhere.<span style=3D"color: rgb(31, 73, 125); =
"><o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">WEG&gt; No, =
I=92m trying to follow the same distinction you=92ve drawn between 6to4 =
with relays and without and understand how that=92s being used, since =
apparently 6to4 without relays is a lot less problematic and you=92ve =
had such success with it. What I=92ve read is multiple people trying to =
explain to you that non-anycast 6to4 (3056) is not being used, and you =
continuing to insist that it=92s heavily used by providing examples of =
3068.</span></div></div></div></div></div></span></blockquote><div><br></d=
iv>Sorry, that's a complete mischaracterization of everything I have =
said. &nbsp; &nbsp;</div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"color: rgb(31, =
73, 125); ">KM&gt;</span>&nbsp; I keep seeing figures that 6to4 =
comprises 40-some-odd percent of IPv6 traffic, while native IPv6 is =
around 10 percent. &nbsp;By your logic, native v6 should be deprecated =
because it doesn't work reliably and it's not being used =
anywhere.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">WEG&gt; =
While my general view is that 40% of less than 1% of Internet traffic =
amounts to a statistical anomaly, citation, please? Assuming that the =
source of your statistic is able to distinguish between types of =
protocol 41 traffic, that 40% is almost definitely traffic that is using =
a relay, =
BTW.</span></div></div></div></div></div></span></blockquote><div><br></di=
v>You are as capable of using google as I am. &nbsp; &nbsp;And the =
sources I found didn't break the 6to4 traffic down between 6to4-to-6to4 =
vs. 6to4-to-native (that would definitely have been useful), but your =
BTW is pure speculation. &nbsp;My speculation would be the opposite, but =
that's just based on my personal experience with 6to4. =
&nbsp;&nbsp;</div><div><br></div><div>(actually it would be nice for =
such stats to get a full breakdown of the different cases: native to =
native, native to 6to4, native to Teredo, 6to4 to Teredo, 6to4 to 6to4, =
Teredo to Teredo)</div><div><span class=3D"Apple-style-span" =
style=3D"font-family: 'Times New Roman', serif; font-size: 16px; =
">&nbsp;</span></div><div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: =
'Times New Roman', serif; "><span style=3D"color: rgb(31, 73, 125); =
">KM&gt;<span class=3D"Apple-converted-space">&nbsp;</span></span>The =
disease is the current IPv4 network with NATs and LSNs and a paucity of =
address space. &nbsp;6to4 is like a drug that can let some valuable v6 =
applications grow (even if a bit stunted) and survive until there's once =
again a network that will support them. &nbsp;Sure, there are some side =
effects and contraindications. &nbsp;But it's useful when used with =
awareness of its limitations. &nbsp;You're arguing that it should be =
discouraged because it causes some problems. &nbsp;Indeed it does. =
&nbsp;But LSN also causes problems, and is a bigger dead-end than 6to4, =
and it's full steam ahead with that. &nbsp;At least 6to4 is designed to =
ease transition to a saner world, which is a lot more than I can say for =
LSN.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: =
'Times New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); ">WEG&gt; LSN is a =
necessary evil brought on by the lack of ubiquitous IPv6 support, which =
has many causes. I don=92t like it either. The thing you are failing to =
realize is that IETF saying that 6to4 use is a bad idea in no way stops =
consenting adults from using it in spite of the side effects and =
contraindications, but it does put a much finer point on those =
contraindications.</span><br></div></div></div></div></span></blockquote><=
div><br></div><div>People who are using 6to4 now might need for new =
implementations of hardware and operating systems to support it. =
&nbsp;This draft explicitly discourages that. =
&nbsp;</div><div><br></div><div>On a broader level, people have a hard =
time grasping what it means to 'deprecate' something or to declare it =
Historic even if the document goes into a fair amount of detail about =
it. &nbsp;They tend to get the high-order bit and to misinterpret that. =
&nbsp;</div><div><br></div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: =
'Times New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p></o:p></span></div></div><div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"color: =
rgb(31, 73, 125); ">KM&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span>I have no doubt that =
many of those "major content providers" are correct when they don't see =
6to4 as an acceptable substitute for them. &nbsp;But the Internet =
doesn't exist just to support "major content providers". &nbsp;So stop =
trying to sabotage something that works well enough for other =
users.<o:p></o:p></div></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"color: =
rgb(31, 73, 125); ">WEG&gt; Not trying to imply that it does. I=92m =
saying that your definition of =93works well enough=94 and the average =
user=92s are widely different, making 6to4 a no-op for the average user. =
The content providers=92 position on end users trying to use 6to4 to =
reach their content is an example of that point.<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br></div></div></div>=
</div></span></blockquote><div><br></div><div>The average user of what? =
&nbsp; Of IPv6 apps? &nbsp;I don't think content providers know squat =
about the average users of IPv6 apps. &nbsp;And anything that compares =
6to4 performance to IPv4 performance is a red herring, at least as =
applied to an argument about whether 6to4 or not is justified. =
&nbsp;</div><br><blockquote type=3D"cite"><span class=3D"Apple-style-span"=
 style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: =
'Times New Roman', serif; "><o:p></o:p></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span style=3D"color: rgb(31, 73, 125); ">WEG&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span>Why are we having a =
World IPv6 Day? In part to shake loose the broken 6to4 users that may =
not even know that 6to4 is enabled/broken so that content providers can =
be more confident that they can dual-stack their websites without risk =
of significant user impact due to =
breakage.<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"color: =
rgb(31, 73, 125); ">KM&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span>I'm looking forward =
to World IPv6 Day, and what will be learned from it. &nbsp; But again, =
how well 6to4 works with "major content providers" is =
irrelevant.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">WEG&gt; I =
might argue that this is because 6to4 is largely irrelevant and will =
become increasingly more so as major ISPs roll out IPv6 in the next =
12-18 months. This is about removing barriers to deployment and use of =
IPv6 for the increasing population of Native IPv6 users, not trying to =
buff the turd for a tiny (but unfortunately very vocal) minority.<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br></div></div></div>=
</div></div></span></blockquote><div><br></div>I'll be happy to abandon =
use of 6to4 when I can get native (and non-NATted) IPv6 access anywhere =
I live, anywhere I work, and anywhere I travel. &nbsp;If that happens in =
the next 12-18 months I'll be ecstatic. &nbsp; But I'm not holding my =
breath. &nbsp;In 12-18 months I'll be lucky if I can get native v6 =
access in one of those cases. &nbsp;For the others, I'll continue to =
need some kind of tunneling solution, and 6to4 is often the one that =
works best. &nbsp; Deprecating 6to4 is imposing a barrier to deployment, =
not removing one.</div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p></o:p></span></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"color: =
rgb(31, 73, 125); ">WEG&gt;</span>Finally, we're having problems with =
equipment that doesn't support IPv6 at all. 6to4 is not high on the =
priority list to implement compared with a functional IPv6 stack, =
meaning that on new gear, it likely won't get implemented until it's no =
longer necessary.<o:p></o:p></div></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"color: =
rgb(31, 73, 125); ">KM&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span>Gear that doesn't =
support IPv6 by now is pretty odd gear. &nbsp; &nbsp; But I'm not going =
to tell you not to use it. &nbsp;I'm just saying, if you want odd gear =
to work for you in your own specific use cases, don't try to sabotage =
other odd things that work for other people in their specific use =
cases.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: =
'Times New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); ">WEG&gt; No. As have =
multiple others, you assume that I am talking about the usual suspects =
in core routing and enterprise-class networking and servers. =
</span></div></div></div></div></span></blockquote><div><br></div><div>Whe=
re did you get that idea?</div><div><br></div><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: =
'Times New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); ">The consumer electronics =
space is WOEFULLY behind by comparison. That=92s not =93odd=94 gear. =
</span></div></div></div></div></span></blockquote><div><br></div><div>If =
I were to apply your criteria about what justifies use of 6to4 to such =
devices, they would be odd gear.</div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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 =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; font-family: =
'Times New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); ">And this isn=92t about =
me (for some value of me) wanting that gear to work for some corner case =
application. This is&nbsp; about me having to support millions of =
customers who want that gear to work because they don=92t want to buy =
replacements for something that they see as working just fine today. See =
also CGN =3D necessary =
evil.<o:p></o:p></span></div></div></div></div></span></blockquote><br></d=
iv><div>Yes, it's an important problem. &nbsp; &nbsp; Good luck trying =
to solve it while you're sabotaging things that work for other =
people.</div><div><br></div><div>Keith</div><div><br></div><br></body></ht=
ml>=

--Apple-Mail-21-692146429--

From mrex@sap.com  Wed Jun  8 13:37:10 2011
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 429DE11E8104; Wed,  8 Jun 2011 13:37:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.108
X-Spam-Level: 
X-Spam-Status: No, score=-9.108 tagged_above=-999 required=5 tests=[AWL=1.141,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qH5hss9NPbnM; Wed,  8 Jun 2011 13:37:09 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 5155B11E8107; Wed,  8 Jun 2011 13:37:09 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p58Kb7jB028099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Jun 2011 22:37:07 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201106082037.p58Kb7g5008839@fs4113.wdf.sap.corp>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Date: Wed, 8 Jun 2011 22:37:07 +0200 (MEST)
In-Reply-To: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu> from "Noel Chiappa" at Jun 8, 11 12:04:15 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: v6ops@ietf.org, ietf@ietf.org, jnc@mercury.lcs.mit.edu
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 Jun 2011 20:37:10 -0000

Noel Chiappa wrote:
> 
> > From: Martin Rex <mrex@sap.com>
> >
> > Classification of 6to4 as historic is [in]appropriate use of the IETF
> > process, because it would be a political .. statement.
> 
> Well, we've never done _that_ before, have we? Wouldn't want to set an
> unfortunate precedent.

I'm much more worried about the important part that you didn't quote,
that moving 6to4 to historic is a technically inaccurate statement.

How about downgrading it (rfc3056+rfc3068, I assume) from "Proposed" to
"Experimental", acknowledging the fact that "consumers" will likely
have to set it up themselves, it is rarely going to work out of the box
and might not be available in all implementations.

-Martin

From moore@network-heretics.com  Wed Jun  8 13:48:27 2011
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 B01831F0C54; Wed,  8 Jun 2011 13:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.772
X-Spam-Level: 
X-Spam-Status: No, score=-2.772 tagged_above=-999 required=5 tests=[AWL=0.827,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vQe2EPmJAu4j; Wed,  8 Jun 2011 13:48:26 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id CA01E1F0C53; Wed,  8 Jun 2011 13:48:26 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 7C66A206BD; Wed,  8 Jun 2011 16:48:26 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Wed, 08 Jun 2011 16:48:26 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=content-type:mime-version:subject:from:date:cc:content-transfer-encoding:message-id:to; s=smtpout; bh=5zTvYysr7H29tDv8FI0br89Z8FE=; b=VRh6/GK7XNKLr+BWu8M0BqelYLhMg1PaDkZfGV4WID2KjXEDk8Hm7NPBNShnZtP6+s7Yj4mQnfbdXM8ZByJ+ELAJ7Pp+VeHCTMHke+lUB4ZT+0MI2v7f2HfJ9M5eMVWqjjRv/00b8SydWihm75ORh0DTh2ibbcs34PUs1CMcFZ0=
X-Sasl-enc: MLCY0YGfytMLx1oDa691v12FKXRaVRlDd1oFlfO5O+4Y 1307566106
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id BFE24404842; Wed,  8 Jun 2011 16:48:25 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: compromise on the 6to4->Historic debate
From: Keith Moore <moore@network-heretics.com>
Date: Wed, 8 Jun 2011 16:48:24 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <92FB2780-5F10-4173-A982-12E114BFF130@network-heretics.com>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 20:48:27 -0000

I really think that the right answer is to write an applicability =
statement for 6to4 that:

- refers to the existing documents about 6to4 problems
- points out use cases for 6to4 which work well, and others that work =
less well
- emphasizes that 6to4 is a short-term solution and was always intended =
to be such

Deprecating 6to4 and declaring it Historic are premature and overkill, =
but an applicability statement seems entirely appropriate to me.

Beyond that, the question of anycast advertisement for 6to4 relay =
routers (RFC 3068) is a tough one.  I'd like to find a way to be able to =
keep them, because there's a huge utility in being able to automatically =
configure such things.  But everybody acknowledges the problems that are =
caused when relay routers are advertised in BGP that don't actually get =
the traffic there.   If there's not a way to weed out the bad ones that =
is easy for operators to implement, maybe RFC 3068 really should be =
deprecated.

Keith


From joelja@bogus.com  Wed Jun  8 14:23:15 2011
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 1FAF011E8142; Wed,  8 Jun 2011 14:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.23
X-Spam-Level: 
X-Spam-Status: No, score=-101.23 tagged_above=-999 required=5 tests=[AWL=0.299, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFo3RvPDcrlC; Wed,  8 Jun 2011 14:23:14 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3581D11E8076; Wed,  8 Jun 2011 14:23:13 -0700 (PDT)
Received: from [192.168.1.170] (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p58LMIip065623 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 8 Jun 2011 21:22:32 GMT (envelope-from joelja@bogus.com)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-4-654742651
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <BANLkTikC06JkjJufNTaDA6r5X=Qrs7ozyw@mail.gmail.com>
Date: Wed, 8 Jun 2011 02:55:40 -0700
Message-Id: <DEA5FDF1-1A6F-4328-806C-79E1BB0A4BAA@bogus.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <BANLkTikaGbFASQfisP5=H3yXKgDUpdKEqA@mail.gmail.com> <4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk> <20110607063336.GO45955@Space.Net> <EMEW3|c03704711a0f54e1e9000b2d94a04e2dn568EX03tjc|ecs.soton.ac.uk|4A7A2E91-F290-4DBE-88D0-965443DCECBB@ecs.soton.ac.uk> <BANLkTikC06JkjJufNTaDA6r5X=Qrs7ozyw@mail.gmail.com>
To: trejrco@gmail.com
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 08 Jun 2011 21:22:34 +0000 (UTC)
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "v6ops@ietf.org WG" <v6ops@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, 08 Jun 2011 21:23:15 -0000

--Apple-Mail-4-654742651
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jun 7, 2011, at 4:33 AM, TJ wrote:

>=20
> > Less than 1% of the IPv6 traffic reaching us is 6to4.
>=20
> Unless you provide IPv6 only sites, you should see very little ... =
that is part of the point :).
>=20
> <snip>
>=20
> > It's time to remove the stabilisers on the IPv6 bicycle.
>=20
> I agree, but get me native everywhere before taking away one =
connection mechanism that does work.
>=20
That fails, 20% of time. Seems unlikely that it's going to go away =
anytime soon, draft or no, that said it seems unwise to keep telling the =
users and implementors to use it. by default. =20
> Just my $.02,
> /TJ ... ready for world IPv6 Day?=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-4-654742651
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 7, 2011, at 4:33 AM, TJ wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p><br>
&gt; Less than 1% of the IPv6 traffic reaching us is 6to4. </p><p>Unless you provide IPv6 only sites, you should see very little ... that is part of the point :).</p><p>&lt;snip&gt;</p><p>&gt; It's time to remove the stabilisers on the IPv6 bicycle.</p><p>I agree, but get me native everywhere before taking away one connection mechanism that does work.<br></p></blockquote>That fails, 20% of time. Seems unlikely that it's going to go away anytime soon, draft or no, that said it seems unwise to keep telling the users and implementors to use it. by default. &nbsp;<br><blockquote type="cite"><p>Just my $.02,<br>
/TJ ... ready for world IPv6 Day? <br>
</p>
_______________________________________________<br>Ietf mailing list<br><a href="mailto:Ietf@ietf.org">Ietf@ietf.org</a><br><a href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a><br></blockquote></div><br></body></html>
--Apple-Mail-4-654742651--

From tjc@ecs.soton.ac.uk  Wed Jun  8 16:05:23 2011
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 1FF1821F84A2; Wed,  8 Jun 2011 16:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.401
X-Spam-Level: **
X-Spam-Status: No, score=2.401 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_SUMOF=5]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X7+olH0vNlTZ; Wed,  8 Jun 2011 16:05:22 -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 1303621F847A; Wed,  8 Jun 2011 16:05:20 -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 p58N5FQe017014;  Thu, 9 Jun 2011 00:05:15 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p58N5FQe017014
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1307574316; bh=lQJKGXrkyHamtz5HFRjxyMfHwms=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=2rg2ZA6mj0fB+bdafqmderRsxhUq0xITFsSzTDhD16Y5ql8gGm4/dDRKp0OqPjD3E k0KJpIjB8CM5gHaUiSZszVBRX91E9x0XPPwjblfXRcz3K+wGFOCGIsZtjfaYdZobA2 xXJO/2nFTRNvlA82dQac9+pcJ33bhcN1YC1d4lag=
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 id n5805F0035658597Yr ret-id none; Thu, 09 Jun 2011 00:05:15 +0100
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p58N58lN013616 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 9 Jun 2011 00:05:09 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <C58AF2D7-C362-4A76-BD59-F6B78C6746B0@network-heretics.com>
Date: Thu, 9 Jun 2011 00:05:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|360cdb2b2a17d7015f19c70d5ca71283n5805F03tjc|ecs.soton.ac.uk|24F8A8B2-3AA7-47F4-9AC3-52CCF5C8DF34@ecs.soton.ac.uk>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0690A2B5@PRVPEXVS04.corp.twcable.com> <C58AF2D7-C362-4A76-BD59-F6B78C6746B0@network-heretics.com> <24F8A8B2-3AA7-47F4-9AC3-52CCF5C8DF34@ecs.soton.ac.uk>
To: "v6ops@ietf.org WG" <v6ops@ietf.org>, ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n5805F003565859700; tid=n5805F0035658597Yr; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p58N5FQe017014
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 23:05:23 -0000

On 8 Jun 2011, at 21:19, Keith Moore wrote:
>=20
> Nor, bluntly, is it about a few big content providers or whomever else =
you want to label as important.  The internet is a hugely diverse place, =
and you don't get to dismiss the concerns of people whom you want to =
label as red herrings.   Again, 40-something percent of the IPv6 traffic =
that is observed on the net today uses 6to4.  That's about as much as =
Teredo, it's a hell of a lot more than native v6.  As long as 6to4 is =
one of the major ways that people get IPv6 connectivity (and it clearly =
is), it's premature to declare 6to4 historic.

You see 40% of your IPv6 traffic as 6to4, we see rather less than 1%.  =
Our observation point is as a university on an academic/research network =
that is native dual-stack.  We probably have most of our IPv6 traffic =
come from other universities around the world, who are also most likely =
natively connected.  Hence little if any need for transition methods.  =
This may be different to your scenario, of course, but it is hopefully a =
future that will be more widespread in time.

We did use 6to4 in its router-to-router, site-to-site flavour many years =
ago while a project called 6NET ran, but have had no use case for it =
since.  Perhaps it would be useful to see your use cases more clearly =
documented with examples.

> Almost all usage of IPv6 today is in spite of ISPs.   For that matter, =
a great many successful IPv4 applications today are deployed in spite of =
ISPs.  Again, ISPs in general have let us down, and 6to4 and Teredo are =
carrying ~90% of IPv6 traffic.   ISPs are not in a good position to =
demand that 6to4 be deprecated. =20

We see even less Teredo, i.e. the sum of the 6to4 and Teredo we see is =
under 1% of our total IPv6 traffic.  I don't know where you see 90%; I =
assume it's an environment with home-to-home networks, with no broker or =
IPv6 VPN use?

> That's excellent news.  But the current proposal on the table to =
deprecate 6to4 is premature, confusing, and harmful to real users.

The problem is that 6to4 is unfortunately also harmful to real users, at =
least the ones that don't want to know about IPv6. It will continue to =
be until we can be confident no vendor anywhere has 6to4 on by default, =
won't it?

The question is whether Historic stops knowledgeable people like you =
using 6to4 safely in your own context/community, without affecting =
'normal' users.  Does it mean 6to4 off be default, or 6to4 removed from =
product?

> It's not one versus the other.   6to4 is helping to promote ubiquitous =
IPv6.

The other view is that 6to4 is delaying ubiquitous IPv6 deployment, by =
adding brokenness. Geoff's stats illustrate that very well, though those =
are not based on vanilla 6to4.

Tim



From jhw@apple.com  Wed Jun  8 16:21:53 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5BD411E808D; Wed,  8 Jun 2011 16:21:53 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKO9W5+DGQsv; Wed,  8 Jun 2011 16:21:53 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 9F3E411E8087; Wed,  8 Jun 2011 16:21:52 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LMH007GSVDWUBY0@mail-out.apple.com>; Wed, 08 Jun 2011 16:20:44 -0700 (PDT)
X-AuditID: 1180711d-b7c70ae00000719a-75-4df003cc0d09
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id 21.FB.29082.CC300FD4; Wed, 08 Jun 2011 16:20:44 -0700 (PDT)
Received: from event-10-2-63-213.venue.apple.com (unknown [192.42.249.191]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LMH00J8MVIKRQA0@cardamom.apple.com>; Wed, 08 Jun 2011 16:20:44 -0700 (PDT)
Subject: Re: [v6ops] Last Call:	<draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move	Connection of IPv6 Domains via IPv4 Clouds	(6to4) to Historic status) to Informational RFC
From: james woodyatt <jhw@apple.com>
In-reply-to: <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com>
Date: Wed, 08 Jun 2011 16:20:44 -0700
Message-id: <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1237.1)
X-Brightmail-Tracker: AAAAAA==
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 23:21:53 -0000

On Jun 8, 2011, at 2:32 PM, Dmitry Anipko wrote:
> 
> [...] And it unclear to me why IETF would want to take away a _transition_ technique from people for whom it is working...

Let's be very clear.  This proposed RFC would not "take away" the 6to4 transition mechanism.  The working group considered and rejected the idea of publishing a phase-out plan.  This draft sets no new requirements for most current vendors of 6to4-capable equipment.  It is a purely procedural bill, not a technical one.  As such, it will damage no one.

This draft does redundantly make some recommendations that are also made in I-D.ietf-v6ops-6to4-advisory, which is the companion document with technical content intended for audiences other than the IETF itself.  These recommendations mainly say that 6to4 SHOULD NOT be enabled by DEFAULT.  Beyond that, the principle point of this draft is to flip a categorization flag that nobody outside IETF cares about.  The practical effect of that will be to free the authors of future working group drafts from a procedural requirement to consider whether 6to4 poses any special problems for the subjects of future standards efforts.  I'm okay with that, actually, but I have a hard time imagining how it helps them avoid being pragmatic about what's actually deployed in the real world.  Reality must take precedence over public relations, as Professor Feynman said.

After much consideration on this draft, I have concluded that every moment IETF spends arguing over it is one that would be put to better use discussing almost anything else... even which cute word we should use for the colon-separated fields in the IPv6 address presentation format.

Publish it.  Publish it now.  Let its authors be free to pursue more useful ends than defending it.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From moore@network-heretics.com  Wed Jun  8 17:31:55 2011
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 CCB5B21F849B; Wed,  8 Jun 2011 17:31:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.891
X-Spam-Level: 
X-Spam-Status: No, score=-2.891 tagged_above=-999 required=5 tests=[AWL=0.709,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 91UywH305h8c; Wed,  8 Jun 2011 17:31:54 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 5A7B021F849A; Wed,  8 Jun 2011 17:31:54 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 08EB92076B; Wed,  8 Jun 2011 20:31:54 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Wed, 08 Jun 2011 20:31:54 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=uJD0w953a2cjEEHkMJaAXbnLZyo=; b=krw3s37onM1VxMcybmoiAPlFBuaLej4DC6Emb5ICC4OPQXUNQ7zfV8iejzCmcG5FDSjAOrjdnW/nIuhes2Eg/BvcytkQIp4f2zLpZXiR2l8yM5Ie5BClWFkRfC/TVA4CuMlszac14WUuuVNZJcM/0BnWJMNRYj/9iJK7rGbWlNY=
X-Sasl-enc: scUcwohD1g/qVidYnmurMmIoCX8z5xcsEbQ/eqjg6g3x 1307579513
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id AB08B4013BE; Wed,  8 Jun 2011 20:31:52 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <EMEW3|360cdb2b2a17d7015f19c70d5ca71283n5805F03tjc|ecs.soton.ac.uk|24F8A8B2-3AA7-47F4-9AC3-52CCF5C8DF34@ecs.soton.ac.uk>
Date: Wed, 8 Jun 2011 20:31:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B27E3A5-3882-4801-ADDF-0E90A848F259@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0690A2B5@PRVPEXVS04.corp.twcable.com> <C58AF2D7-C362-4A76-BD59-F6B78C6746B0@network-heretics.com> <24F8A8B2-3AA7-47F4-9AC3-52CCF5C8DF34@ecs.soton.ac.uk> <EMEW3|360cdb2b2a17d7015f19c70d5ca71283n5805F03tjc|ecs.soton.ac.uk|24F8A8B2-3AA7-47F4-9AC3-52CCF5C8DF34@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org WG" <v6ops@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, 09 Jun 2011 00:31:55 -0000

On Jun 8, 2011, at 7:05 PM, Tim Chown wrote:

> On 8 Jun 2011, at 21:19, Keith Moore wrote:
>>=20
>> Nor, bluntly, is it about a few big content providers or whomever =
else you want to label as important.  The internet is a hugely diverse =
place, and you don't get to dismiss the concerns of people whom you want =
to label as red herrings.   Again, 40-something percent of the IPv6 =
traffic that is observed on the net today uses 6to4.  That's about as =
much as Teredo, it's a hell of a lot more than native v6.  As long as =
6to4 is one of the major ways that people get IPv6 connectivity (and it =
clearly is), it's premature to declare 6to4 historic.
>=20
> You see 40% of your IPv6 traffic as 6to4, we see rather less than 1%.  =
Our observation point is as a university on an academic/research network =
that is native dual-stack.  We probably have most of our IPv6 traffic =
come from other universities around the world, who are also most likely =
natively connected.  Hence little if any need for transition methods.  =
This may be different to your scenario, of course, but it is hopefully a =
future that will be more widespread in time.

I'd love it if we all saw a lot more native IPv6 traffic soon.=20

Just to clarify, the 40% is not from my measurement.  It's an =
approximation to figures I've seen quoted elsewhere.   Like you, I'm =
sure this figure will vary from place to place.  I haven't tried to do =
any measurement myself, because the amount of traffic is not a good =
indicator of overall usefulness.   On the other hand, if any transit =
provider anywhere in the world is seeing 40% of v6 traffic as 6to4, that =
is a pretty good indication that somebody (besides myself) is using it. =20=


For that matter, the very fact that operators are observing problems =
with relay routers is another indication that people are using 6to4.  =
Why would they be using it if they didn't want to?   I realize that some =
platforms enable 6to4 by default, but not all of them do.  And I've =
already said I support having hosts and routers ship with 6to4 disabled =
by default.

> We did use 6to4 in its router-to-router, site-to-site flavour many =
years ago while a project called 6NET ran, but have had no use case for =
it since.  Perhaps it would be useful to see your use cases more clearly =
documented with examples.

I've already given examples.  People keep looking for more specific =
examples in an argument where any specific example can be dismissed as =
irrelevant.  It's not any one specific example that matters, it's the =
fact that people are using 6to4 and there's not an obviously better =
replacement that's available to them.

> The problem is that 6to4 is unfortunately also harmful to real users, =
at least the ones that don't want to know about IPv6. It will continue =
to be until we can be confident no vendor anywhere has 6to4 on by =
default, won't it?

NATs are harmful to real users too, and they do a lot more harm than =
6to4 does.  When will we deprecate them?  When will we declare them =
Historic?

It's misleading to talk about only the harm being done by 6to4 without =
acknowledging the benefits of 6to4 or the lack of a suitable =
alternative.  And to say that 6to4 does harm is misleading.  Is it 6to4 =
that's doing the harm, or people who advertise routes to relay routers =
that don't function properly?  Why are people blaming the 6to4 protocol =
for configuration errors made by network operators?

> The question is whether Historic stops knowledgeable people like you =
using 6to4 safely in your own context/community, without affecting =
'normal' users.  Does it mean 6to4 off be default, or 6to4 removed from =
product?

Historic doesn't stop someone who can write his own code.  But if it =
results in implementations removing support for 6to4, declaring 6to4 as =
Historic will stop people who use those implementations.

>> It's not one versus the other.   6to4 is helping to promote =
ubiquitous IPv6.
>=20
> The other view is that 6to4 is delaying ubiquitous IPv6 deployment, by =
adding brokenness. Geoff's stats illustrate that very well, though those =
are not based on vanilla 6to4.

I disagree with that assessment, because it's only considering the case =
of using 6to4 when IPv4 would work just fine.   That's not an =
appropriate metric.    Nobody who has native IPv6 connectivity needs to =
use 6to4 to reach native IPv6 destination addresses.  =20

But a deeper problem is the notion that a single set of address =
selection rules will work well for all, or even most, applications.

Keith


From marka@isc.org  Wed Jun  8 20:35:42 2011
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 3676321F84FF; Wed,  8 Jun 2011 20:35:42 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4djg9iwkO+I; Wed,  8 Jun 2011 20:35:41 -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 4382C21F84F9; Wed,  8 Jun 2011 20:35:41 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 378AFC9465; Thu,  9 Jun 2011 03:35:12 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 C8C1E216C7B; Thu,  9 Jun 2011 03:35:11 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 4397F109F8EA; Thu,  9 Jun 2011 13:35:09 +1000 (EST)
To: Keith Moore <moore@network-heretics.com>
From: Mark Andrews <marka@isc.org>
References: <92FB2780-5F10-4173-A982-12E114BFF130@network-heretics.com>
Subject: Re: compromise on the 6to4->Historic debate
In-reply-to: Your message of "Wed, 08 Jun 2011 16:48:24 -0400." <92FB2780-5F10-4173-A982-12E114BFF130@network-heretics.com>
Date: Thu, 09 Jun 2011 13:35:09 +1000
Message-Id: <20110609033509.4397F109F8EA@drugs.dv.isc.org>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 03:35:42 -0000

In message <92FB2780-5F10-4173-A982-12E114BFF130@network-heretics.com>, Keith M
oore writes:
> I really think that the right answer is to write an applicability statement f
> or 6to4 that:
> 
> - refers to the existing documents about 6to4 problems
> - points out use cases for 6to4 which work well, and others that work less we
> ll
> - emphasizes that 6to4 is a short-term solution and was always intended to be
>  such
> 
> Deprecating 6to4 and declaring it Historic are premature and overkill, but an
>  applicability statement seems entirely appropriate to me.
> 
> Beyond that, the question of anycast advertisement for 6to4 relay routers (RF
> C 3068) is a tough one.  I'd like to find a way to be able to keep them, beca
> use there's a huge utility in being able to automatically configure such thin
> gs.  But everybody acknowledges the problems that are caused when relay route
> rs are advertised in BGP that don't actually get the traffic there.   If ther
> e's not a way to weed out the bad ones that is easy for operators to implemen
> t, maybe RFC 3068 really should be deprecated.
> 
> Keith

Have broken 6to4 relays is *good* for the long term health of the
Internet.  Applications should cope well with one address of a
multi-homed server being unreachable.  Billions of dollars have
been wasted because this has not been seen as a basic requirement
for applications.  It really isn't any harder in most cases to do
this right.

> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
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  Wed Jun  8 20:45:48 2011
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 EC97621F8539; Wed,  8 Jun 2011 20:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.979
X-Spam-Level: 
X-Spam-Status: No, score=-2.979 tagged_above=-999 required=5 tests=[AWL=0.620,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sN+CKsYddpGZ; Wed,  8 Jun 2011 20:45: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 4D53C21F8538; Wed,  8 Jun 2011 20:45:48 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id EE4BA2076E; Wed,  8 Jun 2011 23:45:47 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute6.internal (MEProxy); Wed, 08 Jun 2011 23:45:47 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=ycZKVJ+7e7SqiXt8BTVvu6Pfw8M=; b=bXi73JlYF+77JebZ89SRsj/N47pDdoY63SykLC/xS/YmjWU84ygjiWJEVkiYzKH2V7cmPOXvsa/3q7X15pVPIISeIKAKZfaZuxmZtoE0B37Mp+oKzw2d8VrTYqqUgZd3XOKmAmijS9iWoJjP/UjoeU0+B8e6cvgfd9gIbvXUba0=
X-Sasl-enc: Bbae1E/m99gxER4cbJmB8q4PNCRXeWoTlnSqr9nwvF4z 1307591147
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 24F21440D39; Wed,  8 Jun 2011 23:45:47 -0400 (EDT)
Subject: Re: compromise on the 6to4->Historic debate
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110609033509.4397F109F8EA@drugs.dv.isc.org>
Date: Wed, 8 Jun 2011 23:45:46 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <19FB0BB1-9048-476A-A901-67F962A116B1@network-heretics.com>
References: <92FB2780-5F10-4173-A982-12E114BFF130@network-heretics.com> <20110609033509.4397F109F8EA@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1084)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 03:45:49 -0000

On Jun 8, 2011, at 11:35 PM, Mark Andrews wrote:

> Have broken 6to4 relays is *good* for the long term health of the
> Internet.  Applications should cope well with one address of a
> multi-homed server being unreachable.  Billions of dollars have
> been wasted because this has not been seen as a basic requirement
> for applications.  It really isn't any harder in most cases to do
> this right.

Not that I disagree with the idea that applications should be able to =
fail over from one address to another, but ... why do you assume that =
the server is multihomed? =20

The problem with the broken 6to4 relay on an anycast address is that the =
application (or user, or site) doesn't get to choose a different relay. =20=


Keith=

From marka@isc.org  Thu Jun  9 01:04:26 2011
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 B337311E807F; Thu,  9 Jun 2011 01:04:26 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHkVEfFvtvmG; Thu,  9 Jun 2011 01:04: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 887AB11E8071; Thu,  9 Jun 2011 01:04:25 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 5592EC94BE; Thu,  9 Jun 2011 08:03:55 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 E24C3216C80; Thu,  9 Jun 2011 08:03:54 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 7DFEA10A2C44; Thu,  9 Jun 2011 18:03:52 +1000 (EST)
To: Keith Moore <moore@network-heretics.com>
From: Mark Andrews <marka@isc.org>
References: <92FB2780-5F10-4173-A982-12E114BFF130@network-heretics.com> <20110609033509.4397F109F8EA@drugs.dv.isc.org> <19FB0BB1-9048-476A-A901-67F962A116B1@network-heretics.com>
Subject: Re: compromise on the 6to4->Historic debate
In-reply-to: Your message of "Wed, 08 Jun 2011 23:45:46 -0400." <19FB0BB1-9048-476A-A901-67F962A116B1@network-heretics.com>
Date: Thu, 09 Jun 2011 18:03:52 +1000
Message-Id: <20110609080352.7DFEA10A2C44@drugs.dv.isc.org>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 08:04:26 -0000

In message <19FB0BB1-9048-476A-A901-67F962A116B1@network-heretics.com>, Keith M
oore writes:
> On Jun 8, 2011, at 11:35 PM, Mark Andrews wrote:
> 
> > Have broken 6to4 relays is *good* for the long term health of the
> > Internet.  Applications should cope well with one address of a
> > multi-homed server being unreachable.  Billions of dollars have
> > been wasted because this has not been seen as a basic requirement
> > for applications.  It really isn't any harder in most cases to do
> > this right.
> 
> Not that I disagree with the idea that applications should be able to
> fail over from one address to another, but ... why do you assume that
> the server is multihomed?

Yes, that is a assumption which isn't always true but mostly is now.  It's
definitely true for the content providers complaining that 6to4 is stopping
them deploying IPv6.

> The problem with the broken 6to4 relay on an anycast address is that the
> application (or user, or site) doesn't get to choose a different relay.

The site can always pick a differnet relay as long as they know the IPv4
address of one.  There used to be lists of them.  The anycast address is
or should be just a convenience function.

I have suggested that ISP's could advertise 6to4 relay routers to customers
via DHCP draft-andrews-v6ops-6to4-router-option, this can also be used to
turn off 6to4 when it is known not to work (e.g. firewall, behind a NAT) or
there is working IPv6.

But rather than make the transition mechanism work there is this mind set
that 6to4 needs to be killed.

Mark

> Keith
-- 
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  Thu Jun  9 06:25:45 2011
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 5268E11E8081; Thu,  9 Jun 2011 06:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.047
X-Spam-Level: 
X-Spam-Status: No, score=-3.047 tagged_above=-999 required=5 tests=[AWL=0.551,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JB5xDfNz5ZR1; Thu,  9 Jun 2011 06:25:43 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 0E27611E80B7; Thu,  9 Jun 2011 06:25:42 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 233B2208C7; Thu,  9 Jun 2011 09:25:42 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 09 Jun 2011 09:25:42 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=X1R5hvIIzLHRrSR21WGAiavgbO8=; b=lMIzTTYp8Yppfh/5ENWkK1NmjfPNzmHa23tcPPmZd3wjyFrOWz3MZmPUZVVOB3FxFcwXUXOV5HkZWtKTxFqnO4/Znj7TWQ7lCchQ4ND2j3gVO9hW49Q5aMaSj8LH7ZlthpxBKxwHVwmBI5yejpzU7uOlUWPiAsC0em6gq/oraBk=
X-Sasl-enc: bPQl/qcydk0/bbNS8EUzE3i71lXxzw5e5dzS+xTfHKf5 1307625941
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 94B71444C51; Thu,  9 Jun 2011 09:25:40 -0400 (EDT)
Subject: Re: compromise on the 6to4->Historic debate
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-22-753741632
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110609080352.7DFEA10A2C44@drugs.dv.isc.org>
Date: Thu, 9 Jun 2011 09:25:39 -0400
Message-Id: <BF6F91BB-F643-4FFD-876A-1C7FA6042601@network-heretics.com>
References: <92FB2780-5F10-4173-A982-12E114BFF130@network-heretics.com> <20110609033509.4397F109F8EA@drugs.dv.isc.org> <19FB0BB1-9048-476A-A901-67F962A116B1@network-heretics.com> <20110609080352.7DFEA10A2C44@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1084)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 13:25:45 -0000

--Apple-Mail-22-753741632
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 9, 2011, at 4:03 AM, Mark Andrews wrote:

> In message =
<19FB0BB1-9048-476A-A901-67F962A116B1@network-heretics.com>, Keith M
> oore writes:
>> On Jun 8, 2011, at 11:35 PM, Mark Andrews wrote:
>>=20
>>> Have broken 6to4 relays is *good* for the long term health of the
>>> Internet.  Applications should cope well with one address of a
>>> multi-homed server being unreachable.  Billions of dollars have
>>> been wasted because this has not been seen as a basic requirement
>>> for applications.  It really isn't any harder in most cases to do
>>> this right.
>>=20
>> Not that I disagree with the idea that applications should be able to
>> fail over from one address to another, but ... why do you assume that
>> the server is multihomed?
>=20
> Yes, that is a assumption which isn't always true but mostly is now.  =
It's
> definitely true for the content providers complaining that 6to4 is =
stopping
> them deploying IPv6.

I get the latter part.   It's the "mostly is now" part that I wonder =
about.  Sure, I use the web a lot.  But I never think of the Internet as =
being only, or primarily, about a small number of applications that =
users on the outside use to get to content in the center.  To me it's =
about this huge variety of applications, that have all kinds of =
different traffic patterns.

>> The problem with the broken 6to4 relay on an anycast address is that =
the
>> application (or user, or site) doesn't get to choose a different =
relay.
>=20
> The site can always pick a differnet relay as long as they know the =
IPv4
> address of one.  There used to be lists of them.  The anycast address =
is
> or should be just a convenience function.

It's *very* convenient.  The existence of the anycast service means that =
there can be a simple check box that says "enable 6to4" or that it can =
be enabled by default when no native connectivity is available.    Which =
ought to be a great thing. =20

The problems with that appear to be:
Too many people have decided to "help out" without really understanding =
what is required of a relay router that is advertised via =
anycast...along with a lack of recommended practices for management of =
such routers.   (Yay that there's still some sense of Internet =
community.  But of course there is a learning curve associated with =
anything new.)
Default address selection rules that favor 6to4-to-nativev6 or even =
6to4-to-6to4, over IPv4-to-IPv4.

(Then again there are rumors of some transit networks filtering protocol =
41...which strikes me as more malicious.)

> I have suggested that ISP's could advertise 6to4 relay routers to =
customers
> via DHCP draft-andrews-v6ops-6to4-router-option, this can also be used =
to
> turn off 6to4 when it is known not to work (e.g. firewall, behind a =
NAT) or
> there is working IPv6.
>=20
> But rather than make the transition mechanism work there is this mind =
set
> that 6to4 needs to be killed.

Indeed.   And really, I'd be okay with killing it if native v6 were =
universally available.  But that might take another five or ten years.

Keith


--Apple-Mail-22-753741632
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 9, 2011, at 4:03 AM, Mark Andrews =
wrote:</div><br><blockquote type=3D"cite"><div>In message &lt;<a =
href=3D"mailto:19FB0BB1-9048-476A-A901-67F962A116B1@network-heretics.com">=
19FB0BB1-9048-476A-A901-67F962A116B1@network-heretics.com</a>&gt;, Keith =
M<br>oore writes:<br><blockquote type=3D"cite">On Jun 8, 2011, at 11:35 =
PM, Mark Andrews wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Have broken 6to4 relays is *good* for the long term health =
of the<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Internet. &nbsp;Applications should cope well with one =
address of a<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">multi-homed server being =
unreachable. &nbsp;Billions of dollars =
have<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">been wasted because this has not been seen as a basic =
requirement<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">for applications. &nbsp;It =
really isn't any harder in most cases to =
do<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">this right.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Not that I =
disagree with the idea that applications should be able =
to<br></blockquote><blockquote type=3D"cite">fail over from one address =
to another, but ... why do you assume that<br></blockquote><blockquote =
type=3D"cite">the server is multihomed?<br></blockquote><br>Yes, that is =
a assumption which isn't always true but mostly is now. =
&nbsp;It's<br>definitely true for the content providers complaining that =
6to4 is stopping<br>them deploying =
IPv6.<br></div></blockquote><div><br></div>I get the latter part. &nbsp; =
It's the "mostly is now" part that I wonder about. &nbsp;Sure, I use the =
web a lot. &nbsp;But I never think of the Internet as being only, or =
primarily, about a small number of applications that users on the =
outside use to get to content in the center. &nbsp;To me it's about this =
huge variety of applications, that have all kinds of different traffic =
patterns.</div><div><br><blockquote type=3D"cite"><div><blockquote =
type=3D"cite">The problem with the broken 6to4 relay on an anycast =
address is that the<br></blockquote><blockquote type=3D"cite">application =
(or user, or site) doesn't get to choose a different =
relay.<br></blockquote><br>The site can always pick a differnet relay as =
long as they know the IPv4<br>address of one. &nbsp;There used to be =
lists of them. &nbsp;The anycast address is<br>or should be just a =
convenience function.<br></div></blockquote><div><br></div>It's *very* =
convenient. &nbsp;The existence of the anycast service means that there =
can be a simple check box that says "enable 6to4" or that it can be =
enabled by default when no native connectivity is available. &nbsp; =
&nbsp;Which ought to be a great thing. =
&nbsp;</div><div><br></div><div>The problems with that appear to =
be:</div><div><ul class=3D"MailOutline"><li>Too many people have decided =
to "help out" without really understanding what is required of a relay =
router that is advertised via anycast...along with a lack of recommended =
practices for management of such routers. &nbsp; (Yay that there's still =
some sense of Internet community. &nbsp;But of course there is a =
learning curve associated with anything new.)</li><li>Default address =
selection rules that favor 6to4-to-nativev6 or even 6to4-to-6to4, over =
IPv4-to-IPv4.</li></ul><div><br></div><div>(Then again there are rumors =
of some transit networks filtering protocol 41...which strikes me as =
more malicious.)</div></div><div><br><blockquote type=3D"cite"><div>I =
have suggested that ISP's could advertise 6to4 relay routers to =
customers<br>via DHCP draft-andrews-v6ops-6to4-router-option, this can =
also be used to<br>turn off 6to4 when it is known not to work (e.g. =
firewall, behind a NAT) or<br>there is working IPv6.<br><br>But rather =
than make the transition mechanism work there is this mind set<br>that =
6to4 needs to be killed.<br></div></blockquote></div><br><div>Indeed. =
&nbsp; And really, I'd be okay with killing it if native v6 were =
universally available. &nbsp;But that might take another five or ten =
years.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-22-753741632--

From moore@network-heretics.com  Thu Jun  9 07:38:01 2011
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 0A33611E80ED; Thu,  9 Jun 2011 07:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.803
X-Spam-Level: 
X-Spam-Status: No, score=-2.803 tagged_above=-999 required=5 tests=[AWL=0.196,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m61qD43RGNHB; Thu,  9 Jun 2011 07:38:00 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 483C511E80E1; Thu,  9 Jun 2011 07:38:00 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 512D720399; Thu,  9 Jun 2011 10:37:59 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 09 Jun 2011 10:37:59 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=5y4vauCwBv0RNJbaZXWyHhWBB20=; b=jKQ1F97IfQbgGhNgp9IV0AV0lIYR8NU/frLHM2wYjnECepap0iFwGkYXS8DGB8YpOpKxpL05KJcabS1qRy7Es7W56j8c0DpkGql5CcR6F7MfB+0K5KegCpyrSVKOM2rzPS3RxDaO+Zg4Tdgp3O5BOOQo2JBci0g8zKlbS4htxZ4=
X-Sasl-enc: knppnJKbfOaOOqGaDIs+JaQceKlMC94XICs/Qiy45T6C 1307630278
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 0F44F445183; Thu,  9 Jun 2011 10:37:57 -0400 (EDT)
Subject: Re: [v6ops] Last Call:	<draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move	Connection of IPv6 Domains via IPv4 Clouds	(6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com>
Date: Thu, 9 Jun 2011 10:37:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com> <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org WG" <v6ops@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, 09 Jun 2011 14:38:01 -0000

On Jun 8, 2011, at 7:20 PM, james woodyatt wrote:

> On Jun 8, 2011, at 2:32 PM, Dmitry Anipko wrote:
>>=20
>> [...] And it unclear to me why IETF would want to take away a =
_transition_ technique from people for whom it is working...
>=20
> Let's be very clear.  This proposed RFC would not "take away" the 6to4 =
transition mechanism.  The working group considered and rejected the =
idea of publishing a phase-out plan.  This draft sets no new =
requirements for most current vendors of 6to4-capable equipment.  It is =
a purely procedural bill, not a technical one.  As such, it will damage =
no one.

I have also seen those claims in v6ops email (haven't caught up with all =
of it, but have seen a few messages).  I don't buy the argument.  =
Clearly the intent of this draft and protocol action are to discourage =
use of 6to4, particularly in new implementations.  You can't discourage =
use of 6to4 in new implementations without harming people who are =
already using it and depending on it.   =20

(That would be a bit like declaring IPv4 Historic and discouraging new =
implementations from supporting it - when we all know that there will be =
people using IPv4 in corner cases for many years even after the public =
Internet no longer routes it.  Legacy hardware and software that's still =
in use, etc.)

When the draft is clearly intended to do harm to 6to4, and there are =
clearly people using 6to4 in the Real World, it strikes me as =
disingenuous for its proponents to claim that the document will do no =
harm.

> Publish it.  Publish it now.  Let its authors be free to pursue more =
useful ends than defending it.

The authors are already free to abandon the effort and pursue more =
useful ends.  Not only would publishing this do harm to 6to4 and its =
users, it would set a bad precedent.   We're supposed to be working =
toward consensus, not trying to cause harm to things that people use.

Keith


From moore@network-heretics.com  Thu Jun  9 08:05:42 2011
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 B304021F8591; Thu,  9 Jun 2011 08:05:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.521
X-Spam-Level: 
X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[AWL=-0.122, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8LaGINPS1BfA; Thu,  9 Jun 2011 08:05:40 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id A710821F8584; Thu,  9 Jun 2011 08:05:31 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 55E3C20E1B; Thu,  9 Jun 2011 11:05:31 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 09 Jun 2011 11:05:31 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=/wd/LCb19uuJwWP5aJ3gxnSyxW4=; b=KXr+9tKuhVtY17gXZqVywFQDtlOgD1pWxD2K1ex4aqRpsd1pxhY8xBVb0OOUT+lA6bj/VG0uuTvWy/pHDJ5zXpPHiCWy4PJ8Tpw35lpkaDjDkFxdujj8kPefnt57aNyFBTlszDRXfvt4zNIT2sn2Zw9YPntegP57HpmPlZqZCKk=
X-Sasl-enc: lrjHu1Mmn9CeCX1ilqhsIo5RyJhSn6O9gXbOjvXvTOVq 1307631930
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 32DF0446A50; Thu,  9 Jun 2011 11:05:30 -0400 (EDT)
Subject: Re: [v6ops] Last Call:	<draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move	Connection of IPv6 Domains via IPv4Clouds	(6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4269EA985EACD24987D82DAE2FEC62E503D14295@XMB-AMS-101.cisco.com>
Date: Thu, 9 Jun 2011 11:05:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A460E821-DB54-4898-8498-FDFFE8FE2432@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com><B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com><34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com><08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com><34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com><840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com><DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com><677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <4269EA985EACD24987D82DAE2FEC62E503D14295@XMB-AMS-101.cisco.com>
To: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: v6ops@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, 09 Jun 2011 15:05:42 -0000

On Jun 9, 2011, at 10:59 AM, Gunter Van de Velde (gvandeve) wrote:

> Its 'rough' consensus...
> I don't wanna rat-hole here, but imho send the draft onwards for
> publication asap please.

I'm not even sure it's rough consensus within the v6ops group.  Again, =
haven't read all of the messages, but definitely get the impression that =
it falls short of consensus.

And just to be clear on procedure:

- you need more than rough consensus in v6ops, you need rough =
community-wide consensus. =20
- the criteria for standards track actions (which this is, despite the =
document being labeled as Informational) requires both rough consensus =
and technical soundness.

The best way to not rat-hole is just to drop the proposed action. =20

Keith


From joelja@bogus.com  Thu Jun  9 08:20:05 2011
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 E36A111E8106; Thu,  9 Jun 2011 08:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.398
X-Spam-Level: 
X-Spam-Status: No, score=-101.398 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_36=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CRB3Ef-mMZIu; Thu,  9 Jun 2011 08:20:05 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5138911E80F8; Thu,  9 Jun 2011 08:20:04 -0700 (PDT)
Received: from 000154tjennings.corp.zynga.com ([12.184.108.202]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p59FK0Kn086266 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 9 Jun 2011 15:20:01 GMT (envelope-from joelja@bogus.com)
Subject: Re: [v6ops] Last Call:	<draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move	Connection of IPv6 Domains via IPv4Clouds	(6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-8-760597162
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <A460E821-DB54-4898-8498-FDFFE8FE2432@network-heretics.com>
Date: Thu, 9 Jun 2011 08:19:55 -0700
Message-Id: <86D615E0-AC0B-49C1-8CFB-1E80D261CA62@bogus.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com><B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com><34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com><08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com><34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com><840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com><DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com><677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <4269EA985EACD24987D82DAE2FEC62E503D14295@XMB-AMS-101.cisco.com> <A460E821-DB54-4898-8498-FDFFE8FE2432@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 09 Jun 2011 15:20:02 +0000 (UTC)
Cc: "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>, v6ops@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, 09 Jun 2011 15:20:06 -0000

--Apple-Mail-8-760597162
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jun 9, 2011, at 8:05 AM, Keith Moore wrote:

> On Jun 9, 2011, at 10:59 AM, Gunter Van de Velde (gvandeve) wrote:
>=20
>> Its 'rough' consensus...
>> I don't wanna rat-hole here, but imho send the draft onwards for
>> publication asap please.
>=20
> I'm not even sure it's rough consensus within the v6ops group.  Again, =
haven't read all of the messages, but definitely get the impression that =
it falls short of consensus.

If you disagree the wg chairs conclusions as far as the wg process =
outcome and the document shepherds report which can you can find here:

=
https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/history=
/

Then you should consider talking to the responsible ad or an appeal to =
the IESG. As far as I am concerned the accusation that the process has =
gone off the rails is a seperate issue from the merits or lack thereof =
of the proposal.

> And just to be clear on procedure:
>=20
> - you need more than rough consensus in v6ops, you need rough =
community-wide consensus. =20

This is an ietf last call...=20

> - the criteria for standards track actions (which this is, despite the =
document being labeled as Informational) requires both rough consensus =
and technical soundness.

Informational status was at the behest of the iesg, we have been advised =
that an informational document may confer historical status on a =
standards track document.

> The best way to not rat-hole is just to drop the proposed action. =20
>=20
> Keith
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20


--Apple-Mail-8-760597162
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jun 9, 2011, at 8:05 AM, Keith Moore wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
Jun 9, 2011, at 10:59 AM, Gunter Van de Velde (gvandeve) =
wrote:<br><br><blockquote type=3D"cite">Its 'rough' =
consensus...<br></blockquote><blockquote type=3D"cite">I don't wanna =
rat-hole here, but imho send the draft onwards =
for<br></blockquote><blockquote type=3D"cite">publication asap =
please.<br></blockquote><br>I'm not even sure it's rough consensus =
within the v6ops group. &nbsp;Again, haven't read all of the messages, =
but definitely get the impression that it falls short of =
consensus.<br></div></blockquote><div><br></div><div>If you disagree the =
wg chairs conclusions as far as the wg process outcome and the document =
shepherds report which can you can find =
here:</div><div><br></div><div><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic=
/history/">https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-histo=
ric/history/</a></div><div><br></div><div>Then you should consider =
talking to the responsible ad or an appeal to the IESG. As far as I am =
concerned the accusation that the process has gone off the rails is a =
seperate issue from the merits or lack thereof of the =
proposal.</div><br><blockquote type=3D"cite"><div>And just to be clear =
on procedure:<br><br>- you need more than rough consensus in v6ops, you =
need rough community-wide consensus. =
&nbsp;<br></div></blockquote><div><br></div><div>This is an ietf last =
call...&nbsp;</div><br><blockquote type=3D"cite"><div>- the criteria for =
standards track actions (which this is, despite the document being =
labeled as Informational) requires both rough consensus and technical =
soundness.<br></div></blockquote><div><br></div><div>Informational =
status was at the behest of the iesg, we have been advised that an =
informational document may confer historical status on a standards track =
document.</div><div><br></div><blockquote type=3D"cite"><div>The best =
way to not rat-hole is just to drop the proposed action. =
&nbsp;<br><br>Keith<br><br>_______________________________________________=
<br>v6ops mailing list<br><a =
href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/v6ops<br><br></div></blockquote></div><br></body></html>=

--Apple-Mail-8-760597162--

From rogerj@gmail.com  Thu Jun  9 08:24:15 2011
Return-Path: <rogerj@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A35E011E80FD; Thu,  9 Jun 2011 08:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_36=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2eM+mvycYua8; Thu,  9 Jun 2011 08:24:14 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id D528B11E810B; Thu,  9 Jun 2011 08:24:13 -0700 (PDT)
Received: by wyb29 with SMTP id 29so1365998wyb.31 for <multiple recipients>; Thu, 09 Jun 2011 08:24:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=qkqcjZcBw+UVE0NNR/d+aBA1ri+m9pgXSe5VAKJutQM=; b=fkL0W/JB7BNAon4VuB0FClSsuQkfqIXJZtlfiWPQIwHcKG2zoJSnlxH/i1gcHPvAYH /ggE9Ixj4f7Ll7cj5QehWRYAXgU4fCbhDbIheWEgvkpZuaQUZ7M6N6HIdWqesquwxVJj Xeh+DuDpJppvXj3YUxVcSMfxP+DrM/QyHq0o8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=AfJ0AMqdqnYFtua31yj9Yu3E7KzuK97vJ0UwvHxGpslGxTA+bDezDGmur3kZ5utj4T SL3wGEABnWcPPPto9tYxIIqSBdTparyva9QWUcyoSkaWQwInUTXkxDFPq5RWPJdbfqnb mP5R+qmaeYwGGljBPVfIkGchNzwSdlJv5Wv0c=
MIME-Version: 1.0
Received: by 10.227.55.67 with SMTP id t3mr927492wbg.90.1307633052890; Thu, 09 Jun 2011 08:24:12 -0700 (PDT)
Received: by 10.227.132.142 with HTTP; Thu, 9 Jun 2011 08:24:12 -0700 (PDT)
In-Reply-To: <A460E821-DB54-4898-8498-FDFFE8FE2432@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com> <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <4269EA985EACD24987D82DAE2FEC62E503D14295@XMB-AMS-101.cisco.com> <A460E821-DB54-4898-8498-FDFFE8FE2432@network-heretics.com>
Date: Thu, 9 Jun 2011 17:24:12 +0200
Message-ID: <BANLkTimCL9NFWOHCQ6ry3MV32PbXPrVZMA@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move Connection of IPv6 Domains via IPv4Clouds (6to4) to Historic status) to Informational RFC
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>, v6ops@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, 09 Jun 2011 15:24:15 -0000

On Thu, Jun 9, 2011 at 5:05 PM, Keith Moore <moore@network-heretics.com> wr=
ote:
> On Jun 9, 2011, at 10:59 AM, Gunter Van de Velde (gvandeve) wrote:
>> Its 'rough' consensus...
>> I don't wanna rat-hole here, but imho send the draft onwards for
>> publication asap please.
>
> I'm not even sure it's rough consensus within the v6ops group. =A0Again, =
haven't read all of the messages, but definitely get the impression that it=
 falls short of consensus.

There were quite heavy discussion and in the end, there were a few
that was totally against it, the rest supported the document.

No point in repeating that entire discussion here really, go back and
look at the archive.


> And just to be clear on procedure:
>
> - you need more than rough consensus in v6ops, you need rough community-w=
ide consensus.
> - the criteria for standards track actions (which this is, despite the do=
cument being labeled as Informational) requires both rough consensus and te=
chnical soundness.
>
> The best way to not rat-hole is just to drop the proposed action.


Let's take a few step back and think about what we are trying to
achieve here, what is our goal.
IPv6 for everyone for any price? A IPv6 only world? A world where both
IPv4 and IPv6 work or?

I will claim our goal is native IPv6 along IPv4, and in the long run, IPv6 =
only.
We don't need more tunneling of IPv6 over IPv4, that was okay 10years
ago, maybe even 5 or 3 years ago.
Now it is time to actual do the right thing and say "let's do it
properly, let's do IPv6 native".


...and stop discussing yesterdays technology.



--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From moore@network-heretics.com  Thu Jun  9 08:42:42 2011
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 5486811E80E1; Thu,  9 Jun 2011 08:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.811
X-Spam-Level: 
X-Spam-Status: No, score=-3.811 tagged_above=-999 required=5 tests=[AWL=1.188,  BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LwX3QPq8Xr39; Thu,  9 Jun 2011 08:42:41 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 00DDF11E808B; Thu,  9 Jun 2011 08:42:40 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 76D5720DCE; Thu,  9 Jun 2011 11:42:40 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 09 Jun 2011 11:42:40 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=T4irFEBm68YXf1TyUtLbQob/qQg=; b=bI78FXhzxXHMnOsmuOpfC4bRkLJXnfPwlbzQLKNBkRLnAUP5kBemSmN1i6oEAJOQW1Ucv5C49YSsy73DC4LYKeutgsUML2UUxtO8d/AICbLiODQe0XFhIaSWw9oLFxmVZ+rWh5J6SVapXlO0IHh4+P3g8591pM8Mpx42PUbq6VY=
X-Sasl-enc: haGFmkhE5FelPfd4ILOPV9kuQBcXnNF1RzAlmPglXCTG 1307634159
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 03A63443C55; Thu,  9 Jun 2011 11:42:38 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC 
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <m1QUh0G-0001hEC@stereo.hq.phicoh.net>
Date: Thu, 9 Jun 2011 11:42:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CCD853BD-A99F-49B5-A168-D396A606E243@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com> <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <m1QUh0G-0001hEC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-v6ops@u-1.phicoh.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org WG" <v6ops@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, 09 Jun 2011 15:42:42 -0000

On Jun 9, 2011, at 11:18 AM, Philip Homburg wrote:

> In your letter dated Thu, 9 Jun 2011 10:37:56 -0400 you wrote:
>> I have also seen those claims in v6ops email (haven't caught up with =
all of it
>> , but have seen a few messages).  I don't buy the argument.  Clearly =
the inten
>> t of this draft and protocol action are to discourage use of 6to4, =
particularl
>> y in new implementations.  You can't discourage use of 6to4 in new =
implementat
>> ions without harming people who are already using it and depending on =
it.   =20
>>=20
>> (That would be a bit like declaring IPv4 Historic and discouraging =
new impleme
>> ntations from supporting it - when we all know that there will be =
people using
>> IPv4 in corner cases for many years even after the public Internet no =
longer=20
>> routes it.  Legacy hardware and software that's still in use, etc.)
>>=20
>> When the draft is clearly intended to do harm to 6to4, and there are =
clearly p
>> eople using 6to4 in the Real World, it strikes me as disingenuous for =
its prop
>> onents to claim that the document will do no harm.
>=20
> I think this is likely to happen anyway. In all discussions it has =
been come
> clear that 6to4 has nothing to offer for ordinary users, and that the =
situation
> is going to get worse over time (more NAT, more broken 6to4 =
installation).

I don't buy the notion that "ordinary users" only use some small number =
of killer apps.  "ordinary users" are quite diverse.

I certainly agree that increased deployment of LSN will do harm to 6to4 =
and its users.  This wouldn't bother me if ISPs were going to roll out a =
native v6 solution concurrently with LSNs, but my impression is that v6 =
support is going to lag LSN imposition.

> So for any CPE manufacturer is makes perfect sense to start planning =
on
> dropping support for 6to4 in future CPEs, or not add it at all, if =
they have
> yet to release firmware with IPv6 support.

I agree that v4 CPE manufacturers, at least those for consumer =
applications where the networks are likely to be saddled with LSN, =
certainly should not automatically enable 6to4 in their products. =20

There's some justification for their not implementing it at all.  =
However it's my experience that "consumer" CPEs are often used to =
provide connectivity for small business customers also.  In general, LSN =
is not suitable for those customers, and they could benefit from 6to4 =
support in the CPE.

But I'm more concerned about the potential for this action to result in =
6to4 support being prematurely removed from hosts, than I am about its =
effects on CPEs. =20

> This is independent of whether the protocol is declared historic.
>=20
> On the other hand, there is no reason why open source distribution =
would=20
> have to drop 6to4 support. As long as there are people to maintain it, =
it
> can stay. Also on other operation systems, as long as there is some =
sort of
> tunnel interface, you can implement 6to4. It is just a few lines of =
code,=20
> everybody can do it.

"A few lines of code" imposes a significant barrier.  I've done a fair =
amount of kernel hacking in the past, written device drivers, and =
brought up Linux and FreeBSD and NetBSD (in that order) on laptops back =
in the days when laptop hardware was really flaky and poorly documented =
and there was no support in the kernels for their network interfaces.  =
I'm not scared of writing kernel-level C code.  But I don't do it all =
the time, and realistically it would take me several days to fetch the =
source code, update myself on the build process, and figure out exactly =
how to re-insert 6to4 into the kernel.   And that's for Linux or NetBSD =
- I have less familiarity with MacOS and other kernels.  And I'd have no =
idea about how to retro-fit 6to4 into Windows if support for it were =
removed.  I generally don't write code for Windows, but I am =
occasionally forced to use it.

And somehow I suspect that my skills in this area are considerably more =
than the typical 6to4 user.

> So I don't see the big fuzz. If you want to use it, just create a web =
page
> that lists software implementation of 6to4 for every possible =
platform. And
> let the authors of the software know have much their software is =
appreciated.

Similarly, I don't see why there's such a desire to deprecate 6to4 and =
declare it Historic.   It's the first time I can recall a proposal to =
move something to Historic that was widely deployed, widely used, and =
for which there was no suitable and widely available replacement.

Nor do I understand why, in an organization that is supposedly about =
building consensus, there's such a demand for a divisive and obviously =
harmful action.  Generally the way you build consensus is by focusing on =
things for which there is wide agreement, and crafting compromises on =
the other things.   But the proponents of this draft have taken a 'no =
compromise' position.

Keith


From moore@network-heretics.com  Thu Jun  9 08:51:01 2011
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 D9AF711E810F; Thu,  9 Jun 2011 08:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[AWL=-0.204, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NuaLDG0aAxZ3; Thu,  9 Jun 2011 08:50:59 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id A768A11E80F4; Thu,  9 Jun 2011 08:50:59 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 3806320E3F; Thu,  9 Jun 2011 11:50:59 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Thu, 09 Jun 2011 11:50:59 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=TBY9dNQwwHR/6lEks8sSkhxYq90=; b=R20ByUM8EA6IKs4lRJ7S/TBcTGh5IuVKtNPb6qHlZ3CT1BTc1JBO0ame0TRufVWmbclA1KF6UYn3lk3x/GPpWg5Ew4B9nbnR5uKc+27T22Y0Ak+0oXktfIcmoD/HRqqAyHmEGRR99H2rGQGQ7J87+H/3P89wfiAQ2YeXw2Xttrw=
X-Sasl-enc: Fmxbwr/EEPAoZ98uz7grcOmUXmu94mz2Y1TiPe6jHulB 1307634658
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 9FC7A440290; Thu,  9 Jun 2011 11:50:57 -0400 (EDT)
Subject: Re: [v6ops] Last Call:	<draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move	Connection of IPv6 Domains via IPv4Clouds	(6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-23-762458593
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <86D615E0-AC0B-49C1-8CFB-1E80D261CA62@bogus.com>
Date: Thu, 9 Jun 2011 11:50:56 -0400
Message-Id: <4816E77C-C42B-4145-B115-1E6A53AF6002@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com><B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com><34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com><08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com><34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com><840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com><DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com><677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <4269EA985EACD24987D82DAE2FEC62E503D14295@XMB-AMS-101.cisco.com> <A460E821-DB54-4898-8498-FDFFE8FE2432@network-heretics.com> <86D615E0-AC0B-49C1-8CFB-1E80D261CA62@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1084)
Cc: "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>, v6ops@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, 09 Jun 2011 15:51:02 -0000

--Apple-Mail-23-762458593
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 9, 2011, at 11:19 AM, Joel Jaeggli wrote:

> If you disagree the wg chairs conclusions as far as the wg process =
outcome and the document shepherds report which can you can find here:
>=20
> =
https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/history=
/
> Then you should consider talking to the responsible ad or an appeal to =
the IESG. As far as I am concerned the accusation that the process has =
gone off the rails is a seperate issue from the merits or lack thereof =
of the proposal.

I agree that it's a separate issue, and should be treated separately.  =
Again, I haven't read all of the discussion, probably won't have time to =
do that for several more days, and will withhold a decision about any =
process appeal until I've done so. =20

(And frankly, if IESG wants to sabotage 6to4 also, I doubt that a =
process appeal would do any good.  I'll argue vigorously for something =
that I think is useful and/or important, but I have no interest in =
making hard-working people's lives harder for no good reason.)

>> And just to be clear on procedure:
>>=20
>> - you need more than rough consensus in v6ops, you need rough =
community-wide consensus. =20
>=20
> This is an ietf last call...=20

indeed.  I just wanted to counter the possibly-implied assertion that =
v6ops rough consensus was sufficient.

>> - the criteria for standards track actions (which this is, despite =
the document being labeled as Informational) requires both rough =
consensus and technical soundness.
>=20
> Informational status was at the behest of the iesg, we have been =
advised that an informational document may confer historical status on a =
standards track document.

I don't have a problem with the idea that an Informational document can =
describe the consequences of moving something to Historic.  I have a =
serious problem with the idea that a standards-track document can be =
moved off of the standards track by less than an IETF Consensus process, =
or by ignoring the criteria for standards-track actions.  I haven't seen =
any evidence that IESG is trying to do that - they are doing a Last Call =
after all.  But I don't think we want to set a precedent that removing =
something from the standards track is easier or requires less scrutiny =
of the technical criteria than putting something on the standards track.

Keith


--Apple-Mail-23-762458593
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 9, 2011, at 11:19 AM, Joel Jaeggli =
wrote:</div><div><br></div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>If you disagree the =
wg chairs conclusions as far as the wg process outcome and the document =
shepherds report which can you can find =
here:</div><div><br></div><div><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic=
/history/">https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-histo=
ric/history/</a></div></div></div></blockquote><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><div>Then you =
should consider talking to the responsible ad or an appeal to the IESG. =
As far as I am concerned the accusation that the process has gone off =
the rails is a seperate issue from the merits or lack thereof of the =
proposal.</div></div></div></blockquote><div><br></div>I agree that it's =
a separate issue, and should be treated separately. &nbsp;Again, I =
haven't read all of the discussion, probably won't have time to do that =
for several more days, and will withhold a decision about any process =
appeal until I've done so. &nbsp;</div><div><br></div><div>(And frankly, =
if IESG wants to sabotage 6to4 also, I doubt that a process appeal would =
do any good. &nbsp;I'll argue vigorously for something that I think is =
useful and/or important, but I have no interest in making hard-working =
people's lives harder for no good reason.)</div><div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><blockquote =
type=3D"cite"><div>And just to be clear on procedure:<br><br>- you need =
more than rough consensus in v6ops, you need rough community-wide =
consensus. &nbsp;<br></div></blockquote><div><br></div><div>This is an =
ietf last =
call...&nbsp;</div></div></div></blockquote><div><br></div>indeed. =
&nbsp;I just wanted to counter the possibly-implied assertion that v6ops =
rough consensus was sufficient.</div><div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><blockquote =
type=3D"cite"><div>- the criteria for standards track actions (which =
this is, despite the document being labeled as Informational) requires =
both rough consensus and technical =
soundness.<br></div></blockquote><div><br></div><div>Informational =
status was at the behest of the iesg, we have been advised that an =
informational document may confer historical status on a standards track =
document.</div></div></div></blockquote><div><br></div>I don't have a =
problem with the idea that an Informational document can describe the =
consequences of moving something to Historic. &nbsp;I have a serious =
problem with the idea that a standards-track document can be moved off =
of the standards track by less than an IETF Consensus process, or by =
ignoring the criteria for standards-track actions. &nbsp;I haven't seen =
any evidence that IESG is trying to do that - they are doing a Last Call =
after all. &nbsp;But I don't think we want to set a precedent that =
removing something from the standards track is easier or requires less =
scrutiny of the technical criteria than putting something on the =
standards =
track.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-23-762458593--

From moore@network-heretics.com  Thu Jun  9 08:54:24 2011
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 50C0B11E812B; Thu,  9 Jun 2011 08:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.738
X-Spam-Level: 
X-Spam-Status: No, score=-2.738 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_00=-2.599, J_CHICKENPOX_36=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v+DeipEGlx68; Thu,  9 Jun 2011 08:54:22 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 6016211E8132; Thu,  9 Jun 2011 08:54:19 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 016DB20E49; Thu,  9 Jun 2011 11:54:19 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 09 Jun 2011 11:54:19 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=Yw2LxzPjjBK7aY/qZO+ejdrPsm8=; b=V/GrSoEXas67NGGbHn1gnOmjpi9zOFtppkj+MOpuvRS10sHdnAPvbgqxoByO1yIKaJRsHAtFNojob46Ehb3XFsLuTbbk+PsIwmhtpR9986A4jPyzzCe9fT/RJGKGyRF7NPzU5tIcnzW27vDxbr7NsKbxeFQSwFE8nwtSQ0XfuGQ=
X-Sasl-enc: u3RMdmb0p9rUltFsuTl9ahGeccEzuzBE8GvFDyH6ngyp 1307634858
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id D3795441812; Thu,  9 Jun 2011 11:54:17 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move Connection of IPv6 Domains via IPv4Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <BANLkTimCL9NFWOHCQ6ry3MV32PbXPrVZMA@mail.gmail.com>
Date: Thu, 9 Jun 2011 11:54:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF2EC57B-1740-419C-9C24-12D0BB00F701@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com> <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <4269EA985EACD24987D82DAE2FEC62E503D14295@XMB-AMS-101.cisco.com> <A460E821-DB54-4898-8498-FDFFE8FE2432@network-heretics.com> <BANLkTimCL9NFWOHCQ6ry3MV32PbXPrVZMA@mail.gmail.com>
To: =?iso-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>, v6ops@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, 09 Jun 2011 15:54:24 -0000

On Jun 9, 2011, at 11:24 AM, Roger J=F8rgensen wrote:

> I will claim our goal is native IPv6 along IPv4, and in the long run, =
IPv6 only.
> We don't need more tunneling of IPv6 over IPv4, that was okay 10years
> ago, maybe even 5 or 3 years ago.
> Now it is time to actual do the right thing and say "let's do it
> properly, let's do IPv6 native".

The time to actually do the right thing was also 10-15 years ago.  But =
native v6, for the most part, is still not here yet.  At least the ISPs =
are saying Real Soon Now, which is something.  But who knows what "Real =
Soon" means?   Until native IPv6 is actually here, where "here" means =
"everywhere", there is still a need to do tunneling of v6 over v4.

> ...and stop discussing yesterdays technology.

We're always discussing yesterday's technology.   IPv6 was approved in =
1995, if I recall. =20

Keith


From huitema@microsoft.com  Thu Jun  9 09:01:41 2011
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79F0822800B; Thu,  9 Jun 2011 09:01:41 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O4bDriJJV3CF; Thu,  9 Jun 2011 09:01:41 -0700 (PDT)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id DE466228004; Thu,  9 Jun 2011 09:01:40 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 9 Jun 2011 09:01:40 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server (TLS) id 14.1.289.8; Thu, 9 Jun 2011 09:01:40 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.58]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi id 14.01.0289.008; Thu, 9 Jun 2011 09:01:39 -0700
From: Christian Huitema <huitema@microsoft.com>
To: Keith Moore <moore@network-heretics.com>, Philip Homburg <pch-v6ops@u-1.phicoh.com>
Subject: RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds	(6to4) to Historic status) to Informational RFC 
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds	(6to4) to Historic status) to Informational RFC 
Thread-Index: AQHMJrv/oyGIAbwZ4kyG6HE2x5uidpS1K0zA
Date: Thu, 9 Jun 2011 16:01:39 +0000
Message-ID: <22F6318E46E26B498ABC828879B08D4F167D15@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com> <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <m1QUh0G-0001hEC@stereo.hq.phicoh.net> <CCD853BD-A99F-49B5-A168-D396A606E243@network-heretics.com>
In-Reply-To: <CCD853BD-A99F-49B5-A168-D396A606E243@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.43]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "v6ops@ietf.org WG" <v6ops@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, 09 Jun 2011 16:01:41 -0000

Arguably, transitions technologies like 6to4 and Teredo have already achiev=
ed their purpose. My goal at the time, more than 10 years ago, was to break=
 the "chicken and egg" deadlock between application developers and network =
administrators. That's why I spent such energy on making 6to4 easy to deplo=
y, or defining Teredo. Transitions technologies convinced developers that a=
pplications could be developed for IPv6 without waiting for every network t=
o be ready, and applications were indeed developed by Microsoft and others.=
 Network administrators in the meantime started deploying IPv6, and the pre=
sence of applications arguably helped somewhat -- although I am sure networ=
k administrators add many other motivations.

We are now observing a strong pushback, because massive use of tunneling te=
chnologies makes networks harder to manage. Wide scale deployment of self-c=
onfiguring technologies makes levels of services less predictable, and erro=
rs are hard to correct. Self-configuring technologies rely largely on the g=
ood will of others, which is easier to find during a pioneering phase. Argu=
ably, we are beyond the pioneering phase for IPv6.

I understand Keith's point of view, but it is probably time to start progre=
ssively rolling back the transition technologies. 6to4 is the weakest of th=
ese technologies. It does not traverse NAT, it does not include configurati=
on verification tests, and it uses asymmetric paths. It makes sense to star=
t the rollback with 6to4.

-- Christian Huitema




From joelja@bogus.com  Thu Jun  9 09:17:24 2011
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 84E8611E8133; Thu,  9 Jun 2011 09:17:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.699
X-Spam-Level: 
X-Spam-Status: No, score=-101.699 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, J_CHICKENPOX_36=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XMJMd71vTJbV; Thu,  9 Jun 2011 09:17:24 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 147BE11E8144; Thu,  9 Jun 2011 09:17:22 -0700 (PDT)
Received: from 000154tjennings.corp.zynga.com ([12.184.108.202]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p59GHIT3087712 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 9 Jun 2011 16:17:20 GMT (envelope-from joelja@bogus.com)
Subject: Re: [v6ops] Last Call:	<draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move	Connection of IPv6 Domains via IPv4Clouds	(6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4816E77C-C42B-4145-B115-1E6A53AF6002@network-heretics.com>
Date: Thu, 9 Jun 2011 09:17:13 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4C6F2E7-6FD5-49BA-A84E-1E688B5ED333@bogus.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com><B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com><34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com><08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com><34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com><840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com><DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com><677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <4269EA985EACD24987D82DAE2FEC62E503D14295@XMB-AMS-101.cisco.com> <A460E821-DB54-4898-8498-FDFFE8FE2432@network-heretics.com> <86D615E0-AC0B-49C1-8CFB-1E80D261CA62@bogus.com> <4816E77C-C42B-4145-B115-1E6A53AF6002@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 09 Jun 2011 16:17:20 +0000 (UTC)
Cc: "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>, v6ops@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, 09 Jun 2011 16:17:24 -0000

On Jun 9, 2011, at 8:50 AM, Keith Moore wrote:

>=20
>>> - the criteria for standards track actions (which this is, despite =
the document being labeled as Informational) requires both rough =
consensus and technical soundness.
>>=20
>> Informational status was at the behest of the iesg, we have been =
advised that an informational document may confer historical status on a =
standards track document.
>=20
> I don't have a problem with the idea that an Informational document =
can describe the consequences of moving something to Historic.  I have a =
serious problem with the idea that a standards-track document can be =
moved off of the standards track by less than an IETF Consensus process, =
or by ignoring the criteria for standards-track actions.  I haven't seen =
any evidence that IESG is trying to do that - they are doing a Last Call =
after all.  But I don't think we want to set a precedent that removing =
something from the standards track is easier or requires less scrutiny =
of the technical criteria than putting something on the standards track.

The record will show that that the intended status of the document until =
it reached the iegs was standards track. it has been understood from the =
outset that advancement of the document was to obsolete 3056 and 3068. =
revision 4 at the request of the iesg changed th e intented status to =
informational.

> Keith
>=20


From jnc@mercury.lcs.mit.edu  Thu Jun  9 09:25:22 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 557B411E8156; Thu,  9 Jun 2011 09:25:22 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D7WoBJYcy6QX; Thu,  9 Jun 2011 09:25:21 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 36BC511E813E; Thu,  9 Jun 2011 09:25:20 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 06A3D18C0F7; Thu,  9 Jun 2011 12:25:17 -0400 (EDT)
To: ietf@ietf.org, v6ops@ietf.org
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Message-Id: <20110609162517.06A3D18C0F7@mercury.lcs.mit.edu>
Date: Thu,  9 Jun 2011 12:25:17 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 16:25:22 -0000

    > From: Keith Moore <moore@network-heretics.com>

    > Nor do I understand why, in an organization that is supposedly about
    > building consensus, there's such a demand for a divisive ... action. 

Hey, that's been the IPv6 world since day 1. How many leading technical voices
in the community objected vociferoursly to the choice of IPv6 back in the day,
only to be blown off? (The large number of unhappy people have been, I reckon,
a factor in the slow progress of IPv6 since 1995 - although not the larges,
IMO.)

The more things change...

	Noel

From scottr.nist@gmail.com  Wed Jun  8 10:08:03 2011
Return-Path: <scottr.nist@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC1B21F84C3; Wed,  8 Jun 2011 10:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level: 
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7qSiVctsRzpw; Wed,  8 Jun 2011 10:08:02 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3E821F84BF; Wed,  8 Jun 2011 10:08:01 -0700 (PDT)
Received: by wyb29 with SMTP id 29so596238wyb.31 for <multiple recipients>; Wed, 08 Jun 2011 10:08:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=3+nB5MoMzXiCA6EkJpBEqEvHywS5vWis6vkM6lqEUGQ=; b=drPq9LIkW3qDPDxH1gv/WbSZj+SqDT+aAM0IvNyeNlvzfS6tRY+tOZb0SB5pWbeu4x UWFAP2IiRZmNs4Qd6L1+kyAqQbrsOrGqgRc9O8P6lUzadWMt2BSaHMAwPbZ2kDOZtH3R E5fhWffcxQZEmUqGfRO9mDW5TSzn86iy9WzeM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=eLkP0gOVo/3tycYhD8MJ+MRwLlxPnJYnzYJtJl0uQWklm+7tSAcAQt5Da+0xI2CEoy LXXCK/3agHfvBQSnZ0Nv9uz5ZevCB+F+YHhRd9Drk9SJ675/LnEzQZVuwNCk/83PvwiW TO7ERxFsxyIJ8lot+BvelndfGFeIuO5XJUR10=
MIME-Version: 1.0
Received: by 10.216.14.199 with SMTP id d49mr7456449wed.65.1307552880440; Wed, 08 Jun 2011 10:08:00 -0700 (PDT)
Received: by 10.216.87.21 with HTTP; Wed, 8 Jun 2011 10:08:00 -0700 (PDT)
In-Reply-To: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com>
References: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com>
Date: Wed, 8 Jun 2011 13:08:00 -0400
Message-ID: <BANLkTikRmTLjuzUE8_nxMeyrL5sPFppqVg@mail.gmail.com>
Subject: Re: Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
From: Scott Rose <scottr.nist@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=001485f9a7c8f6b71104a5366044
X-Mailman-Approved-At: Thu, 09 Jun 2011 09:27:53 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-ietf-dnsext-rfc2672bis-dname.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: scott.rose@nist.gov
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 17:08:03 -0000

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

Perhaps the document should only update RFC 2672 instead of obsoleting it?

As for the nits:


On Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <ben@nostrum.com> wrote:
>
>  Nits/editorial comments:



 -- IDNits has some comments, please check.



> -- Abstract: "This is a revision of the original specification in RFC 2672,
> also aligning RFC 3363 and RFC 4294 with this revision."
>

The heading says this obsoletes 2672 and updates the other two. It's
> probably worth explicitly using those words here.
>

Will change to say that this doc updates all three RFC's.


>  -- 3.1, 1st paragraph: "Relevant includes the following cases:"


> Awkward sentence. Maybe "Relevant cases include the following:"?
>
>
Will re-write to make it flow better.


>  -- 3.1, 5th paragraph: "is synthesized and included in the answer
> section"



What synthesized it? The server? (passive voice obscures responsibility)
>
> The caching servers in this case.  Will re-write to clarify that.


>  -- ... "The DNAME has an RRSIG"


> A _signed_ DNAME has an RRSIG, right?
>
> Correct, will make more explicit.



> -- 4, 4th paragraph: "...should be revised..."
>
> This document actually executes the revision, right? Better to say "this
> document revises..." rather than "should be revised"
>
>
Yes, will correct.


> -- ..., 7th paragraph: "...replaced with the word "DELETED"."
>
> Won't that just leave the word "deleted" hanging on page without
> explanation? Wouldn't it be better to just simply delete it?
>
>
Maybe, but I think the logic was that if there is some text there (just
something), it can be cleanly referenced (i.e. "DELETED [RFCXXXX]")if
someone is making a revised version of the RFC for some purpose.  Purely
deleting it accomplishes the task, but this provides a good "hook" for a
paper trail.

Scott

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

<div>Perhaps the document should only update RFC 2672 instead of obsoleting=
 it? =A0<br></div><div><br></div><div>As for the nits:<br></div><div><br></=
div><div><br></div><div class=3D"gmail_quote">On Tue, Jun 7, 2011 at 6:35 P=
M, Ben Campbell <span dir=3D"ltr">&lt;<a href=3D"mailto:ben@nostrum.com">be=
n@nostrum.com</a>&gt;</span> wrote: =A0<blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
=A0Nits/editorial comments:=A0</blockquote><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">=
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex;">
=A0-- IDNits has some comments, please check. =A0</blockquote><div>=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex;">
-- Abstract: &quot;This is a revision of the original specification in RFC =
2672, also aligning RFC 3363 and RFC 4294 with this revision.&quot;<br>
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex;">
The heading says this obsoletes 2672 and updates the other two. It&#39;s pr=
obably worth explicitly using those words here.<br></blockquote><div><br></=
div><div>Will change to say that this doc updates all three RFC&#39;s.</div=
>
<div>=A0=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex;">=A0-- 3.1, 1st paragraph: =
&quot;Relevant includes the following cases:&quot;=A0</blockquote><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex;">

<br>
Awkward sentence. Maybe &quot;Relevant cases include the following:&quot;?<=
br>
<br></blockquote><div><br></div><div>Will re-write to make it flow better.<=
/div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">=A0-- 3.1, 5th paragraph=
: &quot;is synthesized and included in the answer section&quot;=A0</blockqu=
ote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">=A0</blockquote><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex;">
What synthesized it? The server? (passive voice obscures responsibility)<br=
>
<br></blockquote><div>The caching servers in this case. =A0Will re-write to=
 clarify that.=A0</div><div>=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">=A0-- =
... &quot;The DNAME has an RRSIG&quot;=A0</blockquote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
<br>
A _signed_ DNAME has an RRSIG, right?<br>
<br></blockquote><div>Correct, will make more explicit.</div><div><br></div=
><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;">
-- 4, 4th paragraph: &quot;...should be revised...&quot;<br>
<br>
This document actually executes the revision, right? Better to say &quot;th=
is document revises...&quot; rather than &quot;should be revised&quot;<br>
<br></blockquote><div><br></div><div>Yes, will correct.</div><div>=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
-- ..., 7th paragraph: &quot;...replaced with the word &quot;DELETED&quot;.=
&quot;<br>
<br>
Won&#39;t that just leave the word &quot;deleted&quot; hanging on page with=
out explanation? Wouldn&#39;t it be better to just simply delete it?<br>
<br>
</blockquote></div><div><br></div><div>Maybe, but I think the logic was tha=
t if there is some text there (just something), it can be cleanly reference=
d (i.e. &quot;DELETED [RFCXXXX]&quot;)if someone is making a revised versio=
n of the RFC for some purpose. =A0Purely deleting it accomplishes the task,=
 but this provides a good &quot;hook&quot; for a paper trail.</div>
<div><br></div><div>Scott</div>

--001485f9a7c8f6b71104a5366044--

From scottr.nist@gmail.com  Wed Jun  8 10:11:14 2011
Return-Path: <scottr.nist@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE11721F8544; Wed,  8 Jun 2011 10:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level: 
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q4joNbc-bneJ; Wed,  8 Jun 2011 10:11:14 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id A361E21F8526; Wed,  8 Jun 2011 10:11:13 -0700 (PDT)
Received: by wyb29 with SMTP id 29so598633wyb.31 for <multiple recipients>; Wed, 08 Jun 2011 10:11:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=8S1qwCCAyHfuiVFf1TRFTj+KDzSg//LFMIIf2z2YWWQ=; b=Ltedcm1PWLFdWg8sEDP5FsyXtp72hvJ8OuohwBLMpjq+fcqwwJ9127n04r9LH50Hjx jgW8uq0RrJm7FFrU9SZqTexp7J4jB6FUS3hDfaQnKQfW0JUngPZEiK+5+AGUDldQo/M5 11swVboFX0BrYIlouvJtwcY694Cgx8VsBeHQM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=T/h2mZHjq/OtQ3rtjZQgqw6Evd1YfXV4Ck8sZgZ11+EN9VN4e0qLTQW+j8zCPdwSfR 2pWN1tEsWzMeCknhyb3AL7Ccs0gyLKe5w/z5/ryhono1uAKeNHWIM4I73SUBKPizB0zy gjY5smQ9aY60esuLD12HKMe6grxAD0oXU+iSc=
MIME-Version: 1.0
Received: by 10.216.145.206 with SMTP id p56mr5225022wej.80.1307553072689; Wed, 08 Jun 2011 10:11:12 -0700 (PDT)
Received: by 10.216.87.21 with HTTP; Wed, 8 Jun 2011 10:11:12 -0700 (PDT)
In-Reply-To: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com>
References: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com>
Date: Wed, 8 Jun 2011 13:11:12 -0400
Message-ID: <BANLkTin0xTnTpA79PL12UcBADQj-A8U_GQ@mail.gmail.com>
Subject: Re: Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
From: Scott Rose <scottr.nist@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=0016e6de04446c33f304a5366cb7
X-Mailman-Approved-At: Thu, 09 Jun 2011 09:27:53 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-ietf-dnsext-rfc2672bis-dname.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: scott.rose@nist.gov
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 17:11:14 -0000

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

Perhaps the document should only update RFC 2672 instead of obsoleting it?

As for the nits:


On Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <ben@nostrum.com> wrote:
>
>  Nits/editorial comments:



 -- IDNits has some comments, please check.



> -- Abstract: "This is a revision of the original specification in RFC 2672,
> also aligning RFC 3363 and RFC 4294 with this revision."
>

The heading says this obsoletes 2672 and updates the other two. It's
> probably worth explicitly using those words here.
>

Will change to say that this doc updates all three RFC's.


>  -- 3.1, 1st paragraph: "Relevant includes the following cases:"


> Awkward sentence. Maybe "Relevant cases include the following:"?
>
>
Will re-write to make it flow better.


>  -- 3.1, 5th paragraph: "is synthesized and included in the answer
> section"



What synthesized it? The server? (passive voice obscures responsibility)
>
> The caching servers in this case.  Will re-write to clarify that.


>  -- ... "The DNAME has an RRSIG"


> A _signed_ DNAME has an RRSIG, right?
>
> Correct, will make more explicit.



> -- 4, 4th paragraph: "...should be revised..."
>
> This document actually executes the revision, right? Better to say "this
> document revises..." rather than "should be revised"
>
>
Yes, will correct.


> -- ..., 7th paragraph: "...replaced with the word "DELETED"."
>
> Won't that just leave the word "deleted" hanging on page without
> explanation? Wouldn't it be better to just simply delete it?
>
>
Maybe, but I think the logic was that if there is some text there (just
something), it can be cleanly referenced (i.e. "DELETED [RFCXXXX]")if
someone is making a revised version of the RFC for some purpose.  Purely
deleting it accomplishes the task, but this provides a good "hook" for a
paper trail.

Scott

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

<div>Perhaps the document should only update RFC 2672 instead of obsoleting=
 it? =A0<br></div><div><br></div><div>As for the nits:<br></div><div><br></=
div><div><br></div><div class=3D"gmail_quote">On Tue, Jun 7, 2011 at 6:35 P=
M, Ben Campbell <span dir=3D"ltr">&lt;<a href=3D"mailto:ben@nostrum.com">be=
n@nostrum.com</a>&gt;</span> wrote: =A0<blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
=A0Nits/editorial comments:=A0</blockquote><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">=
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex;">
=A0-- IDNits has some comments, please check. =A0</blockquote><div>=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex;">
-- Abstract: &quot;This is a revision of the original specification in RFC =
2672, also aligning RFC 3363 and RFC 4294 with this revision.&quot;<br>
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex;">
The heading says this obsoletes 2672 and updates the other two. It&#39;s pr=
obably worth explicitly using those words here.<br></blockquote><div><br></=
div><div>Will change to say that this doc updates all three RFC&#39;s.</div=
>
<div>=A0=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex;">=A0-- 3.1, 1st paragraph: =
&quot;Relevant includes the following cases:&quot;=A0</blockquote><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex;">

<br>
Awkward sentence. Maybe &quot;Relevant cases include the following:&quot;?<=
br>
<br></blockquote><div><br></div><div>Will re-write to make it flow better.<=
/div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">=A0-- 3.1, 5th paragraph=
: &quot;is synthesized and included in the answer section&quot;=A0</blockqu=
ote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">=A0</blockquote><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex;">
What synthesized it? The server? (passive voice obscures responsibility)<br=
>
<br></blockquote><div>The caching servers in this case. =A0Will re-write to=
 clarify that.=A0</div><div>=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">=A0-- =
... &quot;The DNAME has an RRSIG&quot;=A0</blockquote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
<br>
A _signed_ DNAME has an RRSIG, right?<br>
<br></blockquote><div>Correct, will make more explicit.</div><div><br></div=
><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;">
-- 4, 4th paragraph: &quot;...should be revised...&quot;<br>
<br>
This document actually executes the revision, right? Better to say &quot;th=
is document revises...&quot; rather than &quot;should be revised&quot;<br>
<br></blockquote><div><br></div><div>Yes, will correct.</div><div>=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">
-- ..., 7th paragraph: &quot;...replaced with the word &quot;DELETED&quot;.=
&quot;<br>
<br>
Won&#39;t that just leave the word &quot;deleted&quot; hanging on page with=
out explanation? Wouldn&#39;t it be better to just simply delete it?<br>
<br>
</blockquote></div><div><br></div><div>Maybe, but I think the logic was tha=
t if there is some text there (just something), it can be cleanly reference=
d (i.e. &quot;DELETED [RFCXXXX]&quot;)if someone is making a revised versio=
n of the RFC for some purpose. =A0Purely deleting it accomplishes the task,=
 but this provides a good &quot;hook&quot; for a paper trail.</div>
<div><br></div><div>Scott</div>

--0016e6de04446c33f304a5366cb7--

From wesley.george@twcable.com  Wed Jun  8 12:28:39 2011
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC81F11E8174; Wed,  8 Jun 2011 12:28:39 -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=[AWL=-0.833,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, J_CHICKENPOX_32=0.6, J_CHICKENPOX_54=0.6, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pbnj-df0GHQg; Wed,  8 Jun 2011 12:28:31 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 40E0711E8171; Wed,  8 Jun 2011 12:28:30 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.65,339,1304308800";  d="scan'208,217";a="222344242"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 08 Jun 2011 15:28:19 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.29]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Wed, 8 Jun 2011 15:28:13 -0400
From: "George, Wesley" <wesley.george@twcable.com>
To: Keith Moore <moore@network-heretics.com>
Date: Wed, 8 Jun 2011 15:28:09 -0400
Subject: RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Thread-Index: AcwlZPBC7XzsEcC/TfeWF6uzHBmZ5wAigcnA
Message-ID: <34E4F50CAFA10349A41E0756550084FB0690A2B5@PRVPEXVS04.corp.twcable.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com>
In-Reply-To: <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_34E4F50CAFA10349A41E0756550084FB0690A2B5PRVPEXVS04corpt_"
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 09 Jun 2011 09:27:53 -0700
Cc: "v6ops@ietf.org" <v6ops@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, 08 Jun 2011 19:28:40 -0000

--_000_34E4F50CAFA10349A41E0756550084FB0690A2B5PRVPEXVS04corpt_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


From: Keith Moore [mailto:moore@network-heretics.com]
Sent: Tuesday, June 07, 2011 6:48 PM
To: George, Wesley
Cc: ietf@ietf.org; v6ops@ietf.org
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> =
(Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Histo=
ric status) to Informational RFC

KM>I've been using 6to4 on a regular, often daily, basis since the late 199=
0s.   6to4 has allowed me to develop IPv6 applications and test them on rea=
l networks, and deploy them in limited circumstances.  6to4 has also allowe=
d me to remotely access computers on my SOHO networks, using any applicatio=
n protocol that I chose to do so, with out-of-the-box hardware and software=
, without any application-specific proxies, and generally without any appli=
cation-specific configuration.  None of these scenarios required a relay ro=
uter.  All of them were, and continue to be, useful.

KM> Yes, I've experienced on many occasions that using 6to4 to access dual-=
stack web servers doesn't always work so well.  Sometimes it picks a subopt=
imal path because the relay router isn't convenient.  Sometimes the v6 path=
 doesn't work at all and the application has to time out and retry using v4=
.   But this never really bothered me much, because my purpose in using 6to=
4 wasn't to try to access services that I could get to via IPv4 anyway.  An=
d neither, I suggest, is that a reasonable metric for evaluating 6to4 or an=
y other IPv6 transition mechanism.   The metric for evaluating an IPv6 tran=
sition mechanism should be based on its effectiveness in accessing services=
 that are IPv6 only.

WEG> Again, are you or are you not using a relay router? You keep going bac=
k and forth.
Bluntly, this isn't about whether you, or anyone else at IETF use 6to4. We =
are the longest of the long tail; the smallest percentage, the exception to=
 the rule, not the exception that proves the rule. We're network geeks; we'=
re willing to deal with dodgy connectivity or otherwise fiddly methods of d=
oing things to test them and to prove a point. This discussion cannot be ab=
out whether the protocol should be preserved because some marginal percenta=
ge of folks in IETF use 6to4 successfully. I am not disagreeing that for so=
me value of "work" 6to4 works to reach IPv6-only things. What I am saying i=
s that the very things you illustrate here make it only acceptable for test=
ing, and not for any sort of real substitute for IPv6 connectivity. What us=
er is going to accept +100ms in latency due to suboptimal relay choice, or =
waiting multiple seconds for IPv6 to time out because 6to4 didn't work in t=
hat particular network setup? I think that the evidence says that 6to4 is a=
ctually *ineffective* by the evaluation you suggest - a good portion of the=
 time it either utterly fails or provides such degraded service that it may=
 as well not work.

KM> - Enterprises have applications that need to be able to communicate wit=
h large numbers of hosts spread over a diverse area.  IPv6 is clearly the w=
ay that they want to go, but it's not widely available at present.  6to4 pr=
ovides them with a means of routing traffic to their hosts in the interim u=
ntil widespread support for IPv6 exists.

WEG> So do IPv6IP or GRE tunnels. Been using one at home for 3+ years now. =
And honestly, if this type of application is going to be enterprise-class, =
it needs to be in conjunction with ISP deployment of IPv6, not in spite of =
it.

KM> What you're saying is that applications developers shouldn't bother wit=
h actually trying to use IPv6 until the ISPs get their act together and dep=
loy it.  Well guess what?  The ISPs have let us down.  We've been waiting f=
or 15 years for the ISPs to roll out IPv6, and for most of those 15 years t=
hey were all telling us that there were no applications for it.  Now the IS=
Ps are scrambling to get IPv6 into their networks, and they want to sabotag=
e the IPv6 mechanisms that we have in place even before they are actually o=
ffering product.

WEG> Yes, yes, shame on the big, bad ISPs and their lack of deployment. Tru=
st me, I'm as annoyed with the ISPs I've worked for and been a customer of =
that it is taking so long to get IPv6 out there too.
But...6to4 sabotaged itself. This draft is acknowledging reality that it re=
ally didn't work the way we'd hoped. There is no active malevolence here on=
 the part of the ISPs. In fact many of them (us?) have deployed or will be =
deploying 6to4 relays to improve the customer experience until native servi=
ce is available, and are supporting the recommendations to make 6to4 suck l=
ess in draft-carpenter.

KM>Widespread IPv6 support for native IPv6 would be when native IPv6 is ava=
ilable everywhere that IPv4 access is available, from at least one provider=
, with quality (connectivity, reliability, support) approximately as good a=
s IPv4, and at a reasonable price.  In other words, you can't expect applic=
ations to rely on native IPv6 until it's reliably available everywhere that=
 they need to use it.

WEG> So Widespread IPv6 has to have reliability and support equivalent to I=
Pv4, yet you're saying that you can expect applications to rely on 6to4 in =
the meantime despite evidence that it's unreliable, and the virtual guarant=
ee that it won't be supported by the upstream ISP?

KM>There's no such virtual guarantee.
WEG>I should probably have clarified that by "support" I don't mean "will p=
ass protocol 41 IPv4 packets." I mean "can call and yell at someone when it=
 breaks." Make more sense now?
WEG> I am simply saying that I do not for a second believe that those same =
applications that are so important to that user community are at the same t=
ime unimportant enough that they're the sacrificial lamb that has to go IPv=
6-only when the majority of that user community, no matter how small, doesn=
't have native IPv6 access yet.

KM>You have absolutely no idea which applications will be important to the =
user community tomorrow.   Who knows what will be the next netflix, twitter=
, facebook, youtube, ... ?   The Internet is successful not because it supp=
orts some small number of apps that operators think are a good idea; it's s=
uccessful because it (at least as originally architected) can support a wid=
e range of apps without operators having to bless them.
WEG> One of the few places I'm in agreement with you. However, it's not a j=
ustification for 6to4. It's a justification for ubiquitous IPv6. It's not a=
bout whether the operators "bless" an application or not. If those up-and-c=
oming applications are saddled with the performance hit that 6to4 represent=
s, they are unlikely to be successful. In other words, 6to4 will not move t=
he needle on innovative IPv6-only applications, so they're tied to the nati=
ve IPv6 rollout schedule. Sad, but true.

WEG>This is the essence of the IPv6 content vs access chicken/egg problem, =
and 6to4 absolutely will not break the impasse. 6to4 breakage is the most c=
ommon thing that content providers cite as reasons why they don't just go d=
ual-stack. Why would an enterprise application be any different?

KM> It doesn't really matter much whether "content-providers" (as in web si=
te providers) go "dual stack" now.  Sure, they need to be gearing up for it=
, making sure that they understand it, making sure that their networks supp=
ort it.  (Or maybe they'll just install v6-to-v4 proxies at their borders s=
o that they can keep providing good customer service in the face of LSN-ind=
uced brain damage on the public v4 network.)   But assuming their applicati=
ons work through LSN, they're going to keep supporting v4 for a long time a=
nyway, because that's the established base of interoperability for their pr=
oducts and services.   Existing "content providers" are not going to drive =
adoption of IPv6.   They're going to follow it.  Web and email will be the =
last applications to migrate.  New content might appear on v6, and that mig=
ht drive adoption.  But to the extent that it drives adoption, it probably =
won't be from the currently established players that already have plenty of=
 v4 addresses and infrastructure.  It will be from new things that take adv=
antage of the niches created by IPv6 that didn't exist before.
WEG> This is a variant of the old "IPv6 Killer App" discussion. We're still=
 waiting for one, largely because people are afraid of excluding some non-t=
rivial percentage of the populace from being able to use their new, cool th=
ing because it's IPv6-only, and they don't think it will so compelling as t=
o be a justification for people to find a workaround or clamor for IPv6 sup=
port. IMO, IPv4 exhaustion and CGN is the closest thing we have to a Killer=
 App for IPv6. If 6to4 somehow provides an incentive for folks to generate =
IPv6-only applications, and for ordinary users to start using 6to4 to conne=
ct to IPv6, I'm wondering why it hasn't accomplished that goal in the last =
10 years?What would be different all of the sudden?

KM> 6to4 is as reliable as IPv4 is, if it isn't asked to cross a relay rout=
er.
WEG> perhaps (with the exception of MTU issues that plague any tunneled pro=
tocol), but you continue to not provide any examples of this being used any=
where, in the face of significant evidence that 6to4 is horribly unreliable=
 *with* a relay. So this gets filed in the same place as my 100% secure fil=
e server which happens to be unplugged from power and network and encased i=
n 10ft of concrete. Theoretically perfect, but otherwise practically useles=
s.

KM>What is "anywhere" to you?  You seem to have a content-centric view of t=
he Internet.  I do not.   Meanwhile, you persist in saying that something t=
hat I've used regularly for more than 10 years, to do useful work, isn't be=
ing used anywhere.
WEG> No, I'm trying to follow the same distinction you've drawn between 6to=
4 with relays and without and understand how that's being used, since appar=
ently 6to4 without relays is a lot less problematic and you've had such suc=
cess with it. What I've read is multiple people trying to explain to you th=
at non-anycast 6to4 (3056) is not being used, and you continuing to insist =
that it's heavily used by providing examples of 3068.

KM>  I keep seeing figures that 6to4 comprises 40-some-odd percent of IPv6 =
traffic, while native IPv6 is around 10 percent.  By your logic, native v6 =
should be deprecated because it doesn't work reliably and it's not being us=
ed anywhere.
WEG> While my general view is that 40% of less than 1% of Internet traffic =
amounts to a statistical anomaly, citation, please? Assuming that the sourc=
e of your statistic is able to distinguish between types of protocol 41 tra=
ffic, that 40% is almost definitely traffic that is using a relay, BTW.

KM> The disease is the current IPv4 network with NATs and LSNs and a paucit=
y of address space.  6to4 is like a drug that can let some valuable v6 appl=
ications grow (even if a bit stunted) and survive until there's once again =
a network that will support them.  Sure, there are some side effects and co=
ntraindications.  But it's useful when used with awareness of its limitatio=
ns.  You're arguing that it should be discouraged because it causes some pr=
oblems.  Indeed it does.  But LSN also causes problems, and is a bigger dea=
d-end than 6to4, and it's full steam ahead with that.  At least 6to4 is des=
igned to ease transition to a saner world, which is a lot more than I can s=
ay for LSN.
WEG> LSN is a necessary evil brought on by the lack of ubiquitous IPv6 supp=
ort, which has many causes. I don't like it either. The thing you are faili=
ng to realize is that IETF saying that 6to4 use is a bad idea in no way sto=
ps consenting adults from using it in spite of the side effects and contrai=
ndications, but it does put a much finer point on those contraindications.

KM> I have no doubt that many of those "major content providers" are correc=
t when they don't see 6to4 as an acceptable substitute for them.  But the I=
nternet doesn't exist just to support "major content providers".  So stop t=
rying to sabotage something that works well enough for other users.
WEG> Not trying to imply that it does. I'm saying that your definition of "=
works well enough" and the average user's are widely different, making 6to4=
 a no-op for the average user. The content providers' position on end users=
 trying to use 6to4 to reach their content is an example of that point.

WEG> Why are we having a World IPv6 Day? In part to shake loose the broken =
6to4 users that may not even know that 6to4 is enabled/broken so that conte=
nt providers can be more confident that they can dual-stack their websites =
without risk of significant user impact due to breakage.

KM> I'm looking forward to World IPv6 Day, and what will be learned from it=
.   But again, how well 6to4 works with "major content providers" is irrele=
vant.
WEG> I might argue that this is because 6to4 is largely irrelevant and will=
 become increasingly more so as major ISPs roll out IPv6 in the next 12-18 =
months. This is about removing barriers to deployment and use of IPv6 for t=
he increasing population of Native IPv6 users, not trying to buff the turd =
for a tiny (but unfortunately very vocal) minority.

WEG>Finally, we're having problems with equipment that doesn't support IPv6=
 at all. 6to4 is not high on the priority list to implement compared with a=
 functional IPv6 stack, meaning that on new gear, it likely won't get imple=
mented until it's no longer necessary.

KM> Gear that doesn't support IPv6 by now is pretty odd gear.     But I'm n=
ot going to tell you not to use it.  I'm just saying, if you want odd gear =
to work for you in your own specific use cases, don't try to sabotage other=
 odd things that work for other people in their specific use cases.
WEG> No. As have multiple others, you assume that I am talking about the us=
ual suspects in core routing and enterprise-class networking and servers. T=
he consumer electronics space is WOEFULLY behind by comparison. That's not =
"odd" gear. And this isn't about me (for some value of me) wanting that gea=
r to work for some corner case application. This is  about me having to sup=
port millions of customers who want that gear to work because they don't wa=
nt to buy replacements for something that they see as working just fine tod=
ay. See also CGN =3D necessary evil.

Wes George

________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

--_000_34E4F50CAFA10349A41E0756550084FB0690A2B5PRVPEXVS04corpt_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* 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.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{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:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: bre=
ak-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Keith Mo=
ore [mailto:moore@network-heretics.com]
<br>
<b>Sent:</b> Tuesday, June 07, 2011 6:48 PM<br>
<b>To:</b> George, Wesley<br>
<b>Cc:</b> ietf@ietf.org; v6ops@ietf.org<br>
<b>Subject:</b> Re: [v6ops] Last Call: &lt;draft-ietf-v6ops-6to4-to-histori=
c-04.txt&gt; (Request to move Connection of IPv6 Domains via IPv4 Clouds (6=
to4) to Historic status) to Informational RFC<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">KM&gt;</span>I've been=
 using 6to4 on a regular, often daily, basis since the late 1990s. &nbsp; 6=
to4 has allowed me to develop IPv6 applications and test them on real netwo=
rks, and deploy them in limited circumstances.
 &nbsp;6to4 has also allowed me to remotely access computers on my SOHO net=
works, using any application protocol that I chose to do so, with out-of-th=
e-box hardware and software, without any application-specific proxies, and =
generally without any application-specific
 configuration. &nbsp;None of these scenarios required a relay router. &nbs=
p;All of them were, and continue to be, useful.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">KM&gt; </span>Yes, I'v=
e experienced on many occasions that using 6to4 to access dual-stack web se=
rvers doesn't always work so well. &nbsp;Sometimes it picks a suboptimal pa=
th because the relay router isn't convenient.
 &nbsp;Sometimes the v6 path doesn't work at all and the application has to=
 time out and retry using v4. &nbsp; But this never really bothered me much=
, because
<i>my purpose in using 6to4 wasn't to try to access services that I could g=
et to via IPv4 anyway. &nbsp;</i>And neither, I suggest, is that a reasonab=
le metric for evaluating 6to4 or any other IPv6 transition mechanism. &nbsp=
; The metric for evaluating an IPv6 transition
 mechanism should be based on its effectiveness in accessing services that =
are IPv6 only. &nbsp;&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">WEG&gt; Again, are you or=
 are you not using a relay router? You keep going back and forth.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bluntly, this isn&#8217;t=
 about whether you, or anyone else at IETF use 6to4. We are the longest of =
the long tail; the smallest percentage, the exception to the rule,
 not the exception that proves the rule. We&#8217;re network geeks; we&#821=
7;re willing to deal with dodgy connectivity or otherwise fiddly methods of=
 doing things to test them and to prove a point. This discussion cannot be =
about whether the protocol should be preserved
 because some marginal percentage of folks in IETF use 6to4 successfully. I=
 am not disagreeing that for some value of &#8220;work&#8221; 6to4 works to=
 reach IPv6-only things. What I am saying is that the very things you illus=
trate here make it only acceptable for testing,
 and not for any sort of real substitute for IPv6 connectivity. What user i=
s going to accept &#43;100ms in latency due to suboptimal relay choice, or =
waiting multiple seconds for IPv6 to time out because 6to4 didn&#8217;t wor=
k in that particular network setup? I think
 that the evidence says that 6to4 is actually *<b>ineffective</b>* by the e=
valuation you suggest &#8211; a good portion of the time it either utterly =
fails or provides such degraded service that it may as well not work.
</span><br>
<br>
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D"><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">KM&gt; - Enterprises have applications that need to =
be able to communicate with large numbers of hosts spread over a diverse ar=
ea. &nbsp;IPv6 is clearly the way that they want to go, but it's not widely=
 available at present. &nbsp;6to4 provides them
 with a means of routing traffic to their hosts in the interim until widesp=
read support for IPv6 exists.<br>
<br>
WEG&gt; So do IPv6IP or GRE tunnels. Been using one at home for 3&#43; year=
s now. And honestly, if this type of application is going to be enterprise-=
class, it needs to be in conjunction with ISP deployment of IPv6, not in sp=
ite of it.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">KM&gt; </span>What you=
're saying is that applications developers shouldn't bother with actually t=
rying to use IPv6 until the ISPs get their act together and deploy it. &nbs=
p;Well guess what? &nbsp;The ISPs have let us down.
 &nbsp;We've been waiting for 15 years for the ISPs to roll out IPv6, and f=
or most of those 15 years they were all telling us that there were no appli=
cations for it. &nbsp;Now the ISPs are scrambling to get IPv6 into their ne=
tworks, and they want to sabotage the IPv6
 mechanisms that we have in place even before they are actually offering pr=
oduct.<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">WEG&gt; Yes, yes, shame o=
n the big, bad ISPs and their lack of deployment. Trust me, I&#8217;m as an=
noyed with the ISPs I&#8217;ve worked for and been a customer of that it
 is taking so long to get IPv6 out there too. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">But&#8230;6to4 sabotaged =
itself. This draft is acknowledging reality that it really didn&#8217;t wor=
k the way we&#8217;d hoped. There is no active malevolence here on the part
 of the ISPs. In fact many of them (us?) have deployed or will be deploying=
 6to4 relays to improve the customer experience until native service is ava=
ilable, and are supporting the recommendations to make 6to4 suck less in dr=
aft-carpenter.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">KM&gt;Widespread IPv6 support for native IPv6 would =
be when native IPv6 is available everywhere that IPv4 access is available, =
from at least one provider, with quality (connectivity, reliability, suppor=
t) approximately as good as IPv4, and
 at a reasonable price. &nbsp;In other words, you can't expect applications=
 to rely on native IPv6 until it's reliably available everywhere that they =
need to use it.<br>
<br>
WEG&gt; So Widespread IPv6 has to have reliability and support equivalent t=
o IPv4, yet you're saying that you can expect applications to rely on 6to4 =
in the meantime despite evidence that it's unreliable, and the virtual guar=
antee that it won't be supported by
 the upstream ISP?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">KM&gt;</span>There's n=
o such virtual guarantee. &nbsp;&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">WEG&gt;I should probably =
have clarified that by &#8220;support&#8221; I don&#8217;t mean &#8220;will=
 pass protocol 41 IPv4 packets.&#8221; I mean &#8220;can call and yell at s=
omeone when it breaks.&#8221;
 Make more sense now?<o:p></o:p></span></p>
</div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">WEG&gt; </span>I am si=
mply saying that I do not for a second believe that those same applications=
 that are so important to that user community are at the same time unimport=
ant enough that they're the sacrificial
 lamb that has to go IPv6-only when the majority of that user community, no=
 matter how small, doesn't have native IPv6 access yet.
<o:p></o:p></p>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">KM&gt;</span>You have =
absolutely no idea which applications will be important to the user communi=
ty tomorrow. &nbsp; Who knows what will be the next netflix, twitter, faceb=
ook, youtube, ... ? &nbsp; The Internet is successful
 not because it supports some small number of apps that operators think are=
 a good idea; it's successful because it (at least as originally architecte=
d) can support a wide range of apps
<i>without</i> operators having to bless them.&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">WEG&gt; One of the few pl=
aces I&#8217;m in agreement with you. However, it&#8217;s not a justificati=
on for 6to4. It&#8217;s a justification for ubiquitous IPv6. It&#8217;s not=
 about whether
 the operators &#8220;bless&#8221; an application or not. If those up-and-c=
oming applications are saddled with the performance hit that 6to4 represent=
s, they are unlikely to be successful. In other words, 6to4 will not move t=
he needle on innovative IPv6-only applications,
 so they&#8217;re tied to the native IPv6 rollout schedule. Sad, but true.<=
o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">WEG&gt;</span>This is =
the essence of the IPv6 content vs access chicken/egg problem, and 6to4 abs=
olutely will not break the impasse. 6to4 breakage is the most common thing =
that content providers cite as reasons
 why they don't just go dual-stack. Why would an enterprise application be =
any different?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">KM&gt; </span>It doesn=
't really matter much whether &quot;content-providers&quot; (as in web site=
 providers) go &quot;dual stack&quot; now. &nbsp;Sure, they need to be gear=
ing up for it, making sure that they understand it, making sure
 that their networks support it. &nbsp;(Or maybe they'll just install v6-to=
-v4 proxies at their borders so that they can keep providing good customer =
service in the face of LSN-induced brain damage on the public v4 network.) =
&nbsp; But assuming their applications work
 through LSN, they're going to keep supporting v4 for a long time anyway, b=
ecause that's the established base of interoperability for their products a=
nd services. &nbsp; Existing &quot;content providers&quot; are not going to=
 drive adoption of IPv6. &nbsp; They're going to follow
 it. &nbsp;Web and email will be the last applications to migrate. &nbsp;Ne=
w content might appear on v6, and that might drive adoption. &nbsp;But to t=
he extent that it drives adoption, it probably won't be from the currently =
established players that already have plenty of
 v4 addresses and infrastructure. &nbsp;It will be from new things that tak=
e advantage of the niches created by IPv6 that didn't exist before.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">WEG&gt; This is a variant=
 of the old &#8220;IPv6 Killer App&#8221; discussion. We&#8217;re still wai=
ting for one, largely because people are afraid of excluding some non-trivi=
al
 percentage of the populace from being able to use their new, cool thing be=
cause it&#8217;s IPv6-only, and they don&#8217;t think it will so compellin=
g as to be a justification for people to find a workaround or clamor for IP=
v6 support. IMO, IPv4 exhaustion and CGN is
 the closest thing we have to a Killer App for IPv6. If 6to4 somehow provid=
es an incentive for folks to generate IPv6-only applications, and for ordin=
ary users to start using 6to4 to connect to IPv6, I&#8217;m wondering why i=
t hasn&#8217;t accomplished that goal in the
 last 10 years?What would be different all of the sudden? </span><br>
<br>
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">KM&gt; 6to4 is as reliable as IPv4 is, if it isn't a=
sked to cross a relay router.<br>
WEG&gt; perhaps (with the exception of MTU issues that plague any tunneled =
protocol), but you continue to not provide any examples of this being used =
anywhere, in the face of significant evidence that 6to4 is horribly unrelia=
ble *with* a relay. So this gets filed
 in the same place as my 100% secure file server which happens to be unplug=
ged from power and network and encased in 10ft of concrete. Theoretically p=
erfect, but otherwise practically useless.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">KM&gt;</span>What is &=
quot;anywhere&quot; to you? &nbsp;You seem to have a content-centric view o=
f the Internet. &nbsp;I do not. &nbsp; Meanwhile, you persist in saying tha=
t something that I've used regularly for more than 10 years, to
 do useful work, isn't being used anywhere. <span style=3D"color:#1F497D"><=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">WEG&gt; No, I&#8217;m try=
ing to follow the same distinction you&#8217;ve drawn between 6to4 with rel=
ays and without and understand how that&#8217;s being used, since apparentl=
y
 6to4 without relays is a lot less problematic and you&#8217;ve had such su=
ccess with it. What I&#8217;ve read is multiple people trying to explain to=
 you that non-anycast 6to4 (3056) is not being used, and you continuing to =
insist that it&#8217;s heavily used by providing examples
 of 3068. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">KM&gt;</span>&nbsp; I =
keep seeing figures that 6to4 comprises 40-some-odd percent of IPv6 traffic=
, while native IPv6 is around 10 percent. &nbsp;By your logic, native v6 sh=
ould be deprecated because it doesn't work reliably
 and it's not being used anywhere.<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">WEG&gt; While my general =
view is that 40% of less than 1% of Internet traffic amounts to a statistic=
al anomaly, citation, please? Assuming that the source of your
 statistic is able to distinguish between types of protocol 41 traffic, tha=
t 40% is almost definitely traffic that is using a relay, BTW.
<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">KM&gt; </span>The dise=
ase is the current IPv4 network with NATs and LSNs and a paucity of address=
 space. &nbsp;6to4 is like a drug that can let some valuable v6 application=
s grow (even if a bit stunted) and survive until
 there's once again a network that will support them. &nbsp;Sure, there are=
 some side effects and contraindications. &nbsp;But it's useful when used w=
ith awareness of its limitations. &nbsp;You're arguing that it should be di=
scouraged because it causes some problems. &nbsp;Indeed
 it does. &nbsp;But LSN also causes problems, and is a bigger dead-end than=
 6to4, and it's full steam ahead with that. &nbsp;At least 6to4 is designed=
 to ease transition to a saner world, which is a lot more than I can say fo=
r LSN.<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">WEG&gt; LSN is a necessar=
y evil brought on by the lack of ubiquitous IPv6 support, which has many ca=
uses. I don&#8217;t like it either. The thing you are failing to
 realize is that IETF saying that 6to4 use is a bad idea in no way stops co=
nsenting adults from using it in spite of the side effects and contraindica=
tions, but it does put a much finer point on those contraindications.</span=
><br>
<br>
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">KM&gt; </span>I have n=
o doubt that many of those &quot;major content providers&quot; are correct =
when they don't see 6to4 as an acceptable substitute for them. &nbsp;But th=
e Internet doesn't exist just to support &quot;major content
 providers&quot;. &nbsp;So stop trying to sabotage something that works wel=
l enough for other users.<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">WEG&gt; Not trying to =
imply that it does. I&#8217;m saying that your definition of &#8220;works w=
ell enough&#8221; and the average user&#8217;s are widely different, making=
 6to4 a no-op for the average user. The content providers&#8217; position
 on end users trying to use 6to4 to reach their content is an example of th=
at point.
</span><br>
<br>
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">WEG&gt; </span>Why are=
 we having a World IPv6 Day? In part to shake loose the broken 6to4 users t=
hat may not even know that 6to4 is enabled/broken so that content providers=
 can be more confident that they can dual-stack
 their websites without risk of significant user impact due to breakage.<o:=
p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">KM&gt; </span>I'm look=
ing forward to World IPv6 Day, and what will be learned from it. &nbsp; But=
 again, how well 6to4 works with &quot;major content providers&quot; is irr=
elevant.<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">WEG&gt; I might argue tha=
t this is because 6to4 is largely irrelevant and will become increasingly m=
ore so as major ISPs roll out IPv6 in the next 12-18 months.
 This is about removing barriers to deployment and use of IPv6 for the incr=
easing population of Native IPv6 users, not trying to buff the turd for a t=
iny (but unfortunately very vocal) minority.
</span><br>
<br>
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1F497D"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">WEG&gt;</span>Finally,=
 we're having problems with equipment that doesn't support IPv6 at all. 6to=
4 is not high on the priority list to implement compared with a functional =
IPv6 stack, meaning that on new gear, it
 likely won't get implemented until it's no longer necessary.<o:p></o:p></p=
>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">KM&gt; </span>Gear tha=
t doesn't support IPv6 by now is pretty odd gear. &nbsp; &nbsp; But I'm not=
 going to tell you not to use it. &nbsp;I'm just saying, if you want odd ge=
ar to work for you in your own specific use cases, don't
 try to sabotage other odd things that work for other people in their speci=
fic use cases.<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">WEG&gt; No. As have multi=
ple others, you assume that I am talking about the usual suspects in core r=
outing and enterprise-class networking and servers. The consumer
 electronics space is WOEFULLY behind by comparison. That&#8217;s not &#822=
0;odd&#8221; gear. And this isn&#8217;t about me (for some value of me) wan=
ting that gear to work for some corner case application. This is&nbsp; abou=
t me having to support millions of customers who want that gear
 to work because they don&#8217;t want to buy replacements for something th=
at they see as working just fine today. See also CGN =3D necessary evil.
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Wes George</span><o:p>=
</o:p></p>
</div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>

--_000_34E4F50CAFA10349A41E0756550084FB0690A2B5PRVPEXVS04corpt_--

From Dmitry.Anipko@microsoft.com  Wed Jun  8 14:32:33 2011
Return-Path: <Dmitry.Anipko@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60A7411E80A6; Wed,  8 Jun 2011 14:32:33 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZaHoyzB3Sw6; Wed,  8 Jun 2011 14:32:32 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by ietfa.amsl.com (Postfix) with ESMTP id D425D11E807A; Wed,  8 Jun 2011 14:32:32 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 8 Jun 2011 14:32:32 -0700
Received: from tk5-exmlt-s701.segroup.winse.corp.microsoft.com (157.54.90.63) by TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) with Microsoft SMTP Server (TLS) id 14.1.289.8; Wed, 8 Jun 2011 14:32:31 -0700
Received: from NA-EXMSG-S702.segroup.winse.corp.microsoft.com ([157.54.98.201]) by tk5-exmlt-s701.segroup.winse.corp.microsoft.com ([157.54.90.63]) with mapi; Wed, 8 Jun 2011 14:32:13 -0700
From: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 8 Jun 2011 14:32:11 -0700
Subject: RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds	(6to4) to Historic status) to Informational RFC
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds	(6to4) to Historic status) to Informational RFC
Thread-Index: AcwlZVYxaNvHyapZTMGrNtFQ33ZycwAurqpQ
Message-ID: <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com>
In-Reply-To: <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 09 Jun 2011 09:27:53 -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 Jun 2011 21:32:33 -0000

I don't intend to re-spin the discussion that took place in the WG, but I'd=
 like to say I do agree with the concerns raised in the LC threads by Keith=
 and others.=20

If there are 6to4 connectivity issues for some 6to4 clients, in my opinion,=
 those issues would be sufficiently mitigated by RFC 3484/bis. Specifically=
, by changing priority of 6to4-to-6to4 below IPv4 (the 6to4->native IPv6 is=
 already placed below IPv4 by most or all existing implementations of 3484)=
.

Once priority is changed, 6to4 basically would only be used when it is the =
only channel that could work to reach a particular destination. Which means=
 that it could provide connectivity, when there would be no connectivity if=
 6to4 were removed.=20

When native IPv6 is made widely available to users, they just would stop us=
ing 6to4. So, I don't understand concerns regarding "evolutionary future of=
 6to4". And it unclear to me why IETF would want to take away a _transition=
_ technique from people for whom it is working or why there is a need to ta=
ke any action beyond the recommendations along the lines of RFC 3484/bis.=20


From ben@nostrum.com  Wed Jun  8 14:50:44 2011
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 05D3121F8531; Wed,  8 Jun 2011 14:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.016
X-Spam-Level: 
X-Spam-Status: No, score=-102.016 tagged_above=-999 required=5 tests=[AWL=0.583, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v8oMtPCEN4jn; Wed,  8 Jun 2011 14:50:43 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 14C2021F84DB; Wed,  8 Jun 2011 14:50:33 -0700 (PDT)
Received: from [10.0.1.6] (cpe-76-187-75-59.tx.res.rr.com [76.187.75.59]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p58LoRTw089804 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 8 Jun 2011 16:50:28 -0500 (CDT) (envelope-from ben@nostrum.com)
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-8-697628755
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <BANLkTin0xTnTpA79PL12UcBADQj-A8U_GQ@mail.gmail.com>
Date: Wed, 8 Jun 2011 16:50:26 -0500
Message-Id: <42646542-15D4-4ABF-A65F-A0F3361D049A@nostrum.com>
References: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com> <BANLkTin0xTnTpA79PL12UcBADQj-A8U_GQ@mail.gmail.com>
To: scott.rose@nist.gov
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 76.187.75.59 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Thu, 09 Jun 2011 09:27:54 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-ietf-dnsext-rfc2672bis-dname.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: Wed, 08 Jun 2011 21:50:44 -0000

--Apple-Mail-8-697628755
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks for the response! Comments below, eliding the bits I think need =
no further comment.

On Jun 8, 2011, at 12:11 PM, Scott Rose wrote:

> Perhaps the document should only update RFC 2672 instead of obsoleting =
it? =20

That would resolve my concern, if it fits with the intent of the work =
group.


>=20
> As for the nits:
>=20
>=20
> On Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <ben@nostrum.com> wrote: =20=

>=20

[...]

> Yes, will correct.
> =20
> -- ..., 7th paragraph: "...replaced with the word "DELETED"."
>=20
> Won't that just leave the word "deleted" hanging on page without =
explanation? Wouldn't it be better to just simply delete it?
>=20
>=20
> Maybe, but I think the logic was that if there is some text there =
(just something), it can be cleanly referenced (i.e. "DELETED =
[RFCXXXX]")if someone is making a revised version of the RFC for some =
purpose.  Purely deleting it accomplishes the task, but this provides a =
good "hook" for a paper trail.
>=20

Okay. On reflection, it's not like we really render the updates the old =
RFC documents.


> Scott
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail-8-697628755
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Thanks for the response! Comments below, eliding the bits I think =
need no further comment.</div><br><div><div>On Jun 8, 2011, at 12:11 PM, =
Scott Rose wrote:</div><br class=3D"Apple-interchange-newline"><blockquote=
 type=3D"cite"><div>Perhaps the document should only update RFC 2672 =
instead of obsoleting it? =
&nbsp;<br></div></blockquote><div><br></div><div>That would resolve my =
concern, if it fits with the intent of the work =
group.</div><div><br></div><br><blockquote =
type=3D"cite"><div><br></div><div>As for the =
nits:<br></div><div><br></div><div><br></div><div class=3D"gmail_quote">On=
 Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <span dir=3D"ltr">&lt;<a =
href=3D"mailto:ben@nostrum.com">ben@nostrum.com</a>&gt;</span> wrote: =
&nbsp;<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc =
solid;padding-left:1ex;"><br></blockquote></div></blockquote><div><br></di=
v><div>[...]</div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><div>Yes, will =
correct.</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, =
204, 204); border-left-style: solid; padding-left: 1ex; position: =
static; z-index: auto; ">
-- ..., 7th paragraph: "...replaced with the word "DELETED"."<br>
<br>
Won't that just leave the word "deleted" hanging on page without =
explanation? Wouldn't it be better to just simply delete it?<br>
<br>
</blockquote></div><div><br></div><div>Maybe, but I think the logic was =
that if there is some text there (just something), it can be cleanly =
referenced (i.e. "DELETED [RFCXXXX]")if someone is making a revised =
version of the RFC for some purpose. &nbsp;Purely deleting it =
accomplishes the task, but this provides a good "hook" for a paper =
trail.</div>
<div><br></div></blockquote><div><br></div><div>Okay. On reflection, =
it's not like we really render the updates the old RFC =
documents.</div><div><br></div><br><blockquote =
type=3D"cite"><div>Scott</div>
_______________________________________________<br>Gen-art mailing =
list<br><a =
href=3D"mailto:Gen-art@ietf.org">Gen-art@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/gen-art<br></blockquote></div><br></body></html>=

--Apple-Mail-8-697628755--

From gert@space.net  Wed Jun  8 22:54:54 2011
Return-Path: <gert@space.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10B7F11E8084 for <ietf@ietfa.amsl.com>; Wed,  8 Jun 2011 22:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D+uPXHGIymX2 for <ietf@ietfa.amsl.com>; Wed,  8 Jun 2011 22:54:53 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by ietfa.amsl.com (Postfix) with ESMTP id 96BEF22800B for <ietf@ietf.org>; Wed,  8 Jun 2011 22:54:50 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id F0D97F81D7 for <ietf@ietf.org>; Thu,  9 Jun 2011 07:54:47 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id D1F82F816A for <ietf@ietf.org>; Thu,  9 Jun 2011 07:54:47 +0200 (CEST)
Received: (qmail 52803 invoked by uid 1007); 9 Jun 2011 07:54:47 +0200
Date: Thu, 9 Jun 2011 07:54:47 +0200
From: Gert Doering <gert@space.net>
To: james woodyatt <jhw@apple.com>
Subject: Re: [v6ops] Last Call:	<draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move	Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Message-ID: <20110609055447.GJ45955@Space.Net>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com> <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Thu, 09 Jun 2011 09:27:54 -0700
Cc: "v6ops@ietf.org WG" <v6ops@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, 09 Jun 2011 05:54:54 -0000

Hi,

On Wed, Jun 08, 2011 at 04:20:44PM -0700, james woodyatt wrote:
> Publish it.  Publish it now.  Let its authors be free to pursue more useful ends than defending it.

Well said.  +1

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

From gvandeve@cisco.com  Thu Jun  9 07:59:15 2011
Return-Path: <gvandeve@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 4A74A21F850D; Thu,  9 Jun 2011 07:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.399
X-Spam-Level: 
X-Spam-Status: No, score=-9.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uNho5ILohqDq; Thu,  9 Jun 2011 07:59:11 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id F116821F8509; Thu,  9 Jun 2011 07:59:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=gvandeve@cisco.com; l=2568; q=dns/txt; s=iport; t=1307631551; x=1308841151; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=sYqOf4pep999j1eyv8wQtUBJENkYQo8qdgk7H/tLiQM=; b=g9eWVZrVXShVfXsShVghI99RFTCvCDroEr2yAFU8NjXxeV/gq97TgVVA gIQhCUWJRWg7wxGJeMUGMQ+drqXzhiEFI+slqPjhug+irJLBIYXIroyAt PvbaSGfBCXnvTOzYmOWziNVkqAtJ3msr6sM9PGltky7gxQcIf6JMMQwGf 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAFXf8E2Q/khL/2dsb2JhbABTpjp3iHGhJZ4bhiMElgCKfg
X-IronPort-AV: E=Sophos;i="4.65,342,1304294400"; d="scan'208";a="34491362"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 09 Jun 2011 14:59:10 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p59ExAVi029488; Thu, 9 Jun 2011 14:59:10 GMT
Received: from xmb-ams-101.cisco.com ([144.254.74.76]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 9 Jun 2011 16:59:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [v6ops] Last Call:	<draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move	Connection of IPv6 Domains via IPv4Clouds	(6to4) to Historic status) to Informational RFC
Date: Thu, 9 Jun 2011 16:59:09 +0200
Message-ID: <4269EA985EACD24987D82DAE2FEC62E503D14295@XMB-AMS-101.cisco.com>
In-Reply-To: <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] Last Call:	<draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move	Connection of IPv6 Domains via IPv4Clouds	(6to4) to Historic status) to Informational RFC
Thread-Index: Acwmsyf6vb/PehSIRTay9jH3mZgfawAAZNaw
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com><B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com><34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com><08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com><34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com><840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com><DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com><677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com>
From: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
To: "Keith Moore" <moore@network-heretics.com>, "james woodyatt" <jhw@apple.com>
X-OriginalArrivalTime: 09 Jun 2011 14:59:09.0923 (UTC) FILETIME=[C98BF330:01CC26B5]
X-Mailman-Approved-At: Thu, 09 Jun 2011 09:27:54 -0700
Cc: v6ops@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, 09 Jun 2011 14:59:15 -0000

Its 'rough' consensus...
I don't wanna rat-hole here, but imho send the draft onwards for
publication asap please.

G/

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
Of Keith Moore
Sent: 09 June 2011 16:38
To: james woodyatt
Cc: v6ops@ietf.org WG; ietf@ietf.org
Subject: Re: [v6ops] Last Call:
<draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move Connection of
IPv6 Domains via IPv4Clouds (6to4) to Historic status) to Informational
RFC

On Jun 8, 2011, at 7:20 PM, james woodyatt wrote:

> On Jun 8, 2011, at 2:32 PM, Dmitry Anipko wrote:
>>=20
>> [...] And it unclear to me why IETF would want to take away a
_transition_ technique from people for whom it is working...
>=20
> Let's be very clear.  This proposed RFC would not "take away" the 6to4
transition mechanism.  The working group considered and rejected the
idea of publishing a phase-out plan.  This draft sets no new
requirements for most current vendors of 6to4-capable equipment.  It is
a purely procedural bill, not a technical one.  As such, it will damage
no one.

I have also seen those claims in v6ops email (haven't caught up with all
of it, but have seen a few messages).  I don't buy the argument.
Clearly the intent of this draft and protocol action are to discourage
use of 6to4, particularly in new implementations.  You can't discourage
use of 6to4 in new implementations without harming people who are
already using it and depending on it.   =20

(That would be a bit like declaring IPv4 Historic and discouraging new
implementations from supporting it - when we all know that there will be
people using IPv4 in corner cases for many years even after the public
Internet no longer routes it.  Legacy hardware and software that's still
in use, etc.)

When the draft is clearly intended to do harm to 6to4, and there are
clearly people using 6to4 in the Real World, it strikes me as
disingenuous for its proponents to claim that the document will do no
harm.

> Publish it.  Publish it now.  Let its authors be free to pursue more
useful ends than defending it.

The authors are already free to abandon the effort and pursue more
useful ends.  Not only would publishing this do harm to 6to4 and its
users, it would set a bad precedent.   We're supposed to be working
toward consensus, not trying to cause harm to things that people use.

Keith

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

From gert@space.net  Thu Jun  9 08:16:44 2011
Return-Path: <gert@space.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D6E111E80F8 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 08:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_36=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JDFqzfIlR7s0 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 08:16:43 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by ietfa.amsl.com (Postfix) with ESMTP id CEAF211E80DB for <ietf@ietf.org>; Thu,  9 Jun 2011 08:16:41 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 3BFEEF8281 for <ietf@ietf.org>; Thu,  9 Jun 2011 17:16:40 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 22BB6F81DE for <ietf@ietf.org>; Thu,  9 Jun 2011 17:16:40 +0200 (CEST)
Received: (qmail 36484 invoked by uid 1007); 9 Jun 2011 17:16:40 +0200
Date: Thu, 9 Jun 2011 17:16:40 +0200
From: Gert Doering <gert@space.net>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move	Connection of IPv6 Domains via IPv4Clouds	(6to4) to Historic status) to Informational RFC
Message-ID: <20110609151640.GQ45955@Space.Net>
References: <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com> <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <4269EA985EACD24987D82DAE2FEC62E503D14295@XMB-AMS-101.cisco.com> <A460E821-DB54-4898-8498-FDFFE8FE2432@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A460E821-DB54-4898-8498-FDFFE8FE2432@network-heretics.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Thu, 09 Jun 2011 09:27:54 -0700
Cc: "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>, v6ops@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, 09 Jun 2011 15:16:44 -0000

Hi,

On Thu, Jun 09, 2011 at 11:05:29AM -0400, Keith Moore wrote:
> The best way to not rat-hole is just to drop the proposed action.  

One voice doesn't make it "consensus to drop".

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

From pch-b2B3A6689@u-1.phicoh.com  Thu Jun  9 08:18:45 2011
Return-Path: <pch-b2B3A6689@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0480211E8102; Thu,  9 Jun 2011 08:18:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level: 
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n8-CQ+m6Sn66; Thu,  9 Jun 2011 08:18:44 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id AFBE411E80F8; Thu,  9 Jun 2011 08:18:42 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #55) id m1QUh0G-0001hEC; Thu, 9 Jun 2011 17:18:36 +0200
Message-Id: <m1QUh0G-0001hEC@stereo.hq.phicoh.net>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC 
From: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Sender: pch-b2B3A6689@u-1.phicoh.com
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com> <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> 
In-reply-to: Your message of "Thu, 9 Jun 2011 10:37:56 -0400 ." <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> 
Date: Thu, 09 Jun 2011 17:18:25 +0200
X-Mailman-Approved-At: Thu, 09 Jun 2011 09:27:54 -0700
Cc: "v6ops@ietf.org WG" <v6ops@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, 09 Jun 2011 15:18:45 -0000

In your letter dated Thu, 9 Jun 2011 10:37:56 -0400 you wrote:
>I have also seen those claims in v6ops email (haven't caught up with all of it
>, but have seen a few messages).  I don't buy the argument.  Clearly the inten
>t of this draft and protocol action are to discourage use of 6to4, particularl
>y in new implementations.  You can't discourage use of 6to4 in new implementat
>ions without harming people who are already using it and depending on it.    
>
>(That would be a bit like declaring IPv4 Historic and discouraging new impleme
>ntations from supporting it - when we all know that there will be people using
> IPv4 in corner cases for many years even after the public Internet no longer 
>routes it.  Legacy hardware and software that's still in use, etc.)
>
>When the draft is clearly intended to do harm to 6to4, and there are clearly p
>eople using 6to4 in the Real World, it strikes me as disingenuous for its prop
>onents to claim that the document will do no harm.

I think this is likely to happen anyway. In all discussions it has been come
clear that 6to4 has nothing to offer for ordinary users, and that the situation
is going to get worse over time (more NAT, more broken 6to4 installation).

So for any CPE manufacturer is makes perfect sense to start planning on
dropping support for 6to4 in future CPEs, or not add it at all, if they have
yet to release firmware with IPv6 support.

This is independent of whether the protocol is declared historic.

On the other hand, there is no reason why open source distribution would 
have to drop 6to4 support. As long as there are people to maintain it, it
can stay. Also on other operation systems, as long as there is some sort of
tunnel interface, you can implement 6to4. It is just a few lines of code, 
everybody can do it.

So I don't see the big fuzz. If you want to use it, just create a web page
that lists software implementation of 6to4 for every possible platform. And
let the authors of the software know have much their software is appreciated.



From brian.e.carpenter@gmail.com  Thu Jun  9 09:30:33 2011
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 E671711E8188; Thu,  9 Jun 2011 09:30:33 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4dp2Pk2UkM1d; Thu,  9 Jun 2011 09:30:33 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 24B8A11E81AF; Thu,  9 Jun 2011 09:29:51 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1274071fxm.31 for <multiple recipients>; Thu, 09 Jun 2011 09:29:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=e8kCFHcJHyh/7tbVFl51sY1iGx4fc8CwZFceBXMpu+E=; b=Lqj3vAZPz3H8iCzsTsqFWz9/63IvaLnKyHdSzxxcEiRcEYDX9c3QhVY+LlMGKqihfs 2UQQzB90UlhrL4i4nnXiU/giwgTacbAaejRrjCpMlCqL2yU0wCIZCRelwaGqkszLJend A1fI1QW10tgD5vVJ9Zwmxw0gaGONItub6as7E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Ie4P0Dg9u8RUePrs+G0GYRl085VRRK75VbeNTi0r1MA/jVcUO4ronO4GYwEji6bZ6C 57dW92tCChcDbyVCv/mJmcreYbLBDu8KMoluxI9cNMCYh+sw5F930h2p/HjhL0M29B4I 3+UI0cj8+3bvU7WEVV2cbooA6l7Hw3Y9YlaPU=
Received: by 10.223.33.80 with SMTP id g16mr1015159fad.125.1307636991168; Thu, 09 Jun 2011 09:29:51 -0700 (PDT)
Received: from [10.255.25.89] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id o23sm727639faa.9.2011.06.09.09.29.48 (version=SSLv3 cipher=OTHER); Thu, 09 Jun 2011 09:29:50 -0700 (PDT)
Message-ID: <4DF0F4F5.5000308@gmail.com>
Date: Fri, 10 Jun 2011 04:29:41 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com>	<B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com>	<08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com>	<840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com>	<DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com>	<677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com>	<ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <m1QUh0G-0001hEC@stereo.hq.phicoh.net>
In-Reply-To: <m1QUh0G-0001hEC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 16:30:34 -0000

Philip,

On 2011-06-10 03:18, Philip Homburg wrote:
...
> I think this is likely to happen anyway. In all discussions it has been come
> clear that 6to4 has nothing to offer for ordinary users, 

In all fairness, that depends on your definition of "ordinary".
Where I differ from Keith is that I don't think we harm the current
ordinary (or extraordinary) 6to4 users by relabelling the RFCs.

As long as all operators do what draft-ietf-v6ops-6to4-advisory
suggests, of course. I wouldn't support the -historic draft if
the -advisory draft wasn't coming along too.

> and that the situation
> is going to get worse over time (more NAT, more broken 6to4 installation).

More NAT44, yes. But *less* broken 6to4 if operators implement -advisory.

   Brian

From moore@network-heretics.com  Thu Jun  9 10:20:39 2011
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 BB04A11E81D6; Thu,  9 Jun 2011 10:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.185
X-Spam-Level: 
X-Spam-Status: No, score=-3.185 tagged_above=-999 required=5 tests=[AWL=0.414,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vj4ZPxzE77HN; Thu,  9 Jun 2011 10:20:38 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 8C86211E81D0; Thu,  9 Jun 2011 10:20:38 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 2E8B020F33; Thu,  9 Jun 2011 13:20:38 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 09 Jun 2011 13:20:38 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=2CQepiaNOEOUDupWK5KiqeaZ9S8=; b=NdKcwiDGzm7JWsm+gAHRYmf3/fnVH7n1/C3QqnBwKjKk8CTbaKZ8kcnztpK5GpRnKKGWiGHp0rqk8/ML5KxrbfZP1VlhIUZ0u3HQxcyT00eN+uSu1mfyq+t2aXalRBIRKG8jNXEWUrwrrqIohOSFoHU3CKmmZ5o6OfJC23rmEk8=
X-Sasl-enc: YlwFa9CcDF5lqmoleUaRcyvSxARQTid3KC+io18EB6jT 1307640037
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 0D807441ADA; Thu,  9 Jun 2011 13:20:36 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4DF0F4F5.5000308@gmail.com>
Date: Thu, 9 Jun 2011 13:20:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <ADD51B8B-7373-4464-AFE3-0473EB802566@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com>	<B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com>	<08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com>	<34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com>	<840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com>	<DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com>	<677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com>	<ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <m1QUh0G-0001hEC@stereo.hq.phicoh.net> <4DF0F4F5.5000308@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Philip Homburg <pch-v6ops@u-1.phicoh.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, 09 Jun 2011 17:20:40 -0000

> On 2011-06-10 03:18, Philip Homburg wrote:
> ...
>> I think this is likely to happen anyway. In all discussions it has =
been come
>> clear that 6to4 has nothing to offer for ordinary users,=20
>=20
> In all fairness, that depends on your definition of "ordinary".
> Where I differ from Keith is that I don't think we harm the current
> ordinary (or extraordinary) 6to4 users by relabelling the RFCs.

At best, I think it's a waste of time.  At worst, I think it will do =
harm by reducing the number of host implementations that can use 6to4, =
before native IPv6 is widely available.

In between those extremes, I think there's a large potential for =
confusion from the publication of 6to4-advisory along with declaring =
6to4 historic and discouraging new implementations.   On one hand, we're =
telling people how to make 6to4 work better.  On the other hand, we're =
telling people that it's bad and that they shouldn't implement it.  =
While I've long favored the idea that IETF needs a way to say "this =
protocol/practice causes problems and we'd rather you not use it, but if =
you do use it please do it this way", in this case we're trying to do it =
with two different documents that say somewhat contradictory things to =
one another.   =20

Really I think that 6to4-advisory should be sufficient.   That, and it's =
much better written and more balanced.

Keith


From randy_presuhn@mindspring.com  Thu Jun  9 10:26:39 2011
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 0F5B711E81ED for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 10:26:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.373
X-Spam-Level: 
X-Spam-Status: No, score=-102.373 tagged_above=-999 required=5 tests=[AWL=0.226, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6F0P7M9Dm55G for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 10:26:38 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id 54C5411E8180 for <ietf@ietf.org>; Thu,  9 Jun 2011 10:26:38 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=EUabK/aHxxnAMsSCI/QtI12Uv7vvtmGIdq9Cy2V0kgAwmLw2mOmoGAMmjPlbVYwu; 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.30.227.199] (helo=oemcomputer) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1QUj09-0004Xz-Gq for ietf@ietf.org; Thu, 09 Jun 2011 13:26:37 -0400
Message-ID: <006d01cc26ca$ed74b600$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu> <49D685CB-00FD-42E5-9AD8-15E51545D9A2@apple.com> <006601cc260c$4a0c87e0$6801a8c0@oemcomputer> <04A9F777-8C57-4120-9964-CEFFAF0DD7BE@free.fr>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
Date: Thu, 9 Jun 2011 10:30:28 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888cc964a8bf633b3820ecbb732f8fa664504c5f78b1dff3939350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.30.227.199
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 17:26:39 -0000

Hi -

> From: "Rémi Després" <remi.despres@free.fr>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: <ietf@ietf.org>
> Sent: Thursday, June 09, 2011 1:11 AM
> Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
...
> > I'm pretty sure Noel was being scarcastic.  There's clear precedent in the
> > analogous case where RFC 1227 was  declared historic, despite its
> > widespread use for that particular application at the time.
>
> RFC 1227 specified an experimental protocol.
> The 6to4 specification is standard track.
> Declaring historic a standard track specification although it still serves
> legitimate needs would, AFAIK, be a precedent, a regrettable one IMHO.

Consider, then, RFC 1157.

It was, quite rightly, declared historic years ago, even though it
was a full standard and in rather widespread use at the time.
Despite that declaration, it remains in use.  This despite all the
good reasons that its replacement should be used instead.

The point is that the "historic" declaration can be a statement
about how the IETF wants things to be, rather than how they are.
If one happens to be a user or vendor of a "historic" technology,
the declaration might sting a little, but it's really not a big deal, IMO.

Randy



From moore@network-heretics.com  Thu Jun  9 10:26:42 2011
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 519A611E81F3; Thu,  9 Jun 2011 10:26:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.911
X-Spam-Level: 
X-Spam-Status: No, score=-2.911 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nwyK+1YgBBDE; Thu,  9 Jun 2011 10:26:41 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 076C511E81EE; Thu,  9 Jun 2011 10:26:40 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id E4D8A207E3; Thu,  9 Jun 2011 13:26:39 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 09 Jun 2011 13:26:39 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=8tBb7GgYW/97uF7pm3fSu8diHic=; b=EJaD3iMu55G8RmK70GKgHJTtGx0U95UlPRRpQ23cwPduRA7OhTrpBHp7TJkHqkLFpZ2J9Soi7yz0txqojolmvOV8rYp+B0nUlLBtzfxyRfmZx2f2pIY8GqnxuH8NzVUufgtpZdcas0ggBJKE2DGsiQmCu/WSW1YXjLM/lTlN4mo=
X-Sasl-enc: YbJf8ppZyIM79mQ3A2gt4bFLxP0kTI2B6gUGeIFQp3VE 1307640399
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 9DADC443813; Thu,  9 Jun 2011 13:26:38 -0400 (EDT)
Subject: Re: [v6ops] Last Call:	<draft-ietf-v6ops-6to4-to-historic-04.txt>(Request to move	Connection of IPv6 Domains via IPv4Clouds	(6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <B4C6F2E7-6FD5-49BA-A84E-1E688B5ED333@bogus.com>
Date: Thu, 9 Jun 2011 13:26:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6336D4B-5C07-45CD-BD38-FA5966F30BFD@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com><B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com><34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com><08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com><34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com><840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com><DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com><677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <4269EA985EACD24987D82DAE2FEC62E503D14295@XMB-AMS-101.cisco.com> <A460E821-DB54-4898-8498-FDFFE8FE2432@network-heretics.com> <86D615E0-AC0B-49C1-8CFB-1E80D261CA62@bogus.com> <4816E77C-C42B-4145-B115-1E6A53AF6002@network-heretics.com> <B4C6F2E7-6FD5-49BA-A84E-1E688B5ED333@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1084)
Cc: "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>, v6ops@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, 09 Jun 2011 17:26:42 -0000

On Jun 9, 2011, at 12:17 PM, Joel Jaeggli wrote:

>> I don't have a problem with the idea that an Informational document =
can describe the consequences of moving something to Historic.  I have a =
serious problem with the idea that a standards-track document can be =
moved off of the standards track by less than an IETF Consensus process, =
or by ignoring the criteria for standards-track actions.  I haven't seen =
any evidence that IESG is trying to do that - they are doing a Last Call =
after all.  But I don't think we want to set a precedent that removing =
something from the standards track is easier or requires less scrutiny =
of the technical criteria than putting something on the standards track.
>=20
> The record will show that that the intended status of the document =
until it reached the iegs was standards track. it has been understood =
from the outset that advancement of the document was to obsolete 3056 =
and 3068. revision 4 at the request of the iesg changed th e intented =
status to informational.

And Informational status *for the document*, if published, is entirely =
appropriate.  But the *protocol action* is a standards-track protocol =
action.

It used to not be considered necessary to publish an RFC every time the =
IESG approved a protocol action.   Somewhere along the way, having a =
companion document started to be commonplace.  I'm not sure why that got =
to be conventional - maybe it was because of increased use of tracking =
tools that were written with document processing in mind.  And at least =
sometimes it's beneficial to the community to publish an RFC that =
explains why a particular document's status has changed, and how to =
interpret that change in document status.  But RFC 2026 didn't =
anticipate the need for every protocol action to have an associated =
document, and sometimes - as in this case - it causes confusion when =
they are associated.

Process-wise, I think that the protocol action and the document action =
should be separate items.  Though of course it makes no sense for IESG =
to approve the document if it doesn't approve the protocol action.

Keith


From trejrco@gmail.com  Thu Jun  9 10:37:21 2011
Return-Path: <trejrco@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CC0411E8138 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 10:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KbtXkoZqo-LL for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 10:37:20 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9826711E8130 for <ietf@ietf.org>; Thu,  9 Jun 2011 10:37:17 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1276318gxk.31 for <ietf@ietf.org>; Thu, 09 Jun 2011 10:37:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=Cg7V7azJUTMTRmyRWEcI8rhFAu+iczoxrNcOLRAIj04=; b=qNryV9jyxSZyPzuSxiqU9cbtY8LbZVu0OKtIIg2LWQYlqzsQqAByV/WkfolQUgXP4p vBRYXk4V2vasmjXeZDg6hzwKfzAo2NclK4J1ysQ4cEN4m0S8Rr4pWddznC/ILZHSfVK7 cRHXEex0JZYu6/aYNVCB0/ofDsmVH1lKRH0Ic=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; b=wDhdnGjnVdRSdS2PGBlELUOamq8QMP5lTgF6/xKGOuDUB1ThL2RZ8JjWvoHNcREEEW 1geXq22lt2j6sEyRcsGIfop2Y/Ie0GyMIVn8JCc16S/F/kex4zunRT52Ixz010cHm31F 1+B5uMthASVdcxrJdQndql6iHXEL7keOM5MkE=
Received: by 10.91.198.11 with SMTP id a11mr2183624agq.184.1307641037086; Thu, 09 Jun 2011 10:37:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.91.170.3 with HTTP; Thu, 9 Jun 2011 10:36:57 -0700 (PDT)
In-Reply-To: <006d01cc26ca$ed74b600$6801a8c0@oemcomputer>
References: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu> <49D685CB-00FD-42E5-9AD8-15E51545D9A2@apple.com> <006601cc260c$4a0c87e0$6801a8c0@oemcomputer> <04A9F777-8C57-4120-9964-CEFFAF0DD7BE@free.fr> <006d01cc26ca$ed74b600$6801a8c0@oemcomputer>
From: TJ <trejrco@gmail.com>
Date: Thu, 9 Jun 2011 13:36:57 -0400
Message-ID: <BANLkTinRZn9mvf=Rf7TmoB_Q7pp5j6fhyw@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Content-Type: multipart/alternative; boundary=0016367658a3825e4904a54ae79f
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 17:37:21 -0000

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

On Thu, Jun 9, 2011 at 13:30, Randy Presuhn <randy_presuhn@mindspring.com>w=
rote:

> Hi -
>
> > From: "R=E9mi Despr=E9s" <remi.despres@free.fr>
> > To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> > Cc: <ietf@ietf.org>
> > Sent: Thursday, June 09, 2011 1:11 AM
> > Subject: Re: [v6ops] Last Call:
> <draft-ietf-v6ops-6to4-to-historic-04.txt>
> ...
> > > I'm pretty sure Noel was being scarcastic.  There's clear precedent i=
n
> the
> > > analogous case where RFC 1227 was  declared historic, despite its
> > > widespread use for that particular application at the time.
> >
> > RFC 1227 specified an experimental protocol.
> > The 6to4 specification is standard track.
> > Declaring historic a standard track specification although it still
> serves
> > legitimate needs would, AFAIK, be a precedent, a regrettable one IMHO.
>
> Consider, then, RFC 1157.
>
> It was, quite rightly, declared historic years ago, even though it
> was a full standard and in rather widespread use at the time.
> Despite that declaration, it remains in use.  This despite all the
> good reasons that its replacement should be used instead.
>
> The point is that the "historic" declaration can be a statement
> about how the IETF wants things to be, rather than how they are.
> If one happens to be a user or vendor of a "historic" technology,
> the declaration might sting a little, but it's really not a big deal, IMO=
.
>


Although I have already stated my position in this issue (against, for now)=
,
I have a problem with the above logic.
You are effectively arguing that this move won't really impact anything ...
in which case I would ask, why are we doing it?

I suspect that 6to4 is a fairly unique case in that it, as pointed out
earlier, relies on the good nature of others to operate relays "for the
public good".  Marking it as historic would, I imagine, demotivate ISPs to
operate those relays and thus render the connectivity even worse than we ar=
e
fearing.

Please don't confuse my position - I wholeheartedly believe the right answe=
r
is, and am very vocal in promoting, native IPv6 (dual stack) everywhere, fo=
r
everyone.  But we aren't there yet.  Even though my home ISP has done more
IPv6 than many|most, they aren't ready to do native here, yet.  I often rel=
y
on 6to4 is _many) scenarios and simply want something that exists to keep
working until the alternatives are more available.


/TJ

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

<div class=3D"gmail_quote">On Thu, Jun 9, 2011 at 13:30, Randy Presuhn <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:randy_presuhn@mindspring.com">randy_pre=
suhn@mindspring.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;=
">

Hi -<br>
<br>
&gt; From: &quot;R=E9mi Despr=E9s&quot; &lt;<a href=3D"mailto:remi.despres@=
free.fr">remi.despres@free.fr</a>&gt;<br>
&gt; To: &quot;Randy Presuhn&quot; &lt;<a href=3D"mailto:randy_presuhn@mind=
spring.com">randy_presuhn@mindspring.com</a>&gt;<br>
&gt; Cc: &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br>
&gt; Sent: Thursday, June 09, 2011 1:11 AM<br>
<div class=3D"im">&gt; Subject: Re: [v6ops] Last Call: &lt;draft-ietf-v6ops=
-6to4-to-historic-04.txt&gt;<br>
</div>...<br>
<div class=3D"im">&gt; &gt; I&#39;m pretty sure Noel was being scarcastic. =
=A0There&#39;s clear precedent in the<br>
&gt; &gt; analogous case where RFC 1227 was =A0declared historic, despite i=
ts<br>
&gt; &gt; widespread use for that particular application at the time.<br>
&gt;<br>
</div>&gt; RFC 1227 specified an experimental protocol.<br>
&gt; The 6to4 specification is standard track.<br>
&gt; Declaring historic a standard track specification although it still se=
rves<br>
&gt; legitimate needs would, AFAIK, be a precedent, a regrettable one IMHO.=
<br>
<br>
Consider, then, RFC 1157.<br>
<br>
It was, quite rightly, declared historic years ago, even though it<br>
was a full standard and in rather widespread use at the time.<br>
Despite that declaration, it remains in use. =A0This despite all the<br>
good reasons that its replacement should be used instead.<br>
<br>
The point is that the &quot;historic&quot; declaration can be a statement<b=
r>
about how the IETF wants things to be, rather than how they are.<br>
If one happens to be a user or vendor of a &quot;historic&quot; technology,=
<br>
the declaration might sting a little, but it&#39;s really not a big deal, I=
MO.<br>
<div><div></div><div class=3D"h5"></div></div></blockquote></div><br><div><=
br></div><div>Although I have already stated my position in this issue (aga=
inst, for now), I have a problem with the above logic.<br>You are effective=
ly arguing that this move won&#39;t really impact anything ... in which cas=
e I would ask, why are we doing it?<br>

<br></div><div>I suspect that 6to4 is a fairly unique case in that it, as p=
ointed out earlier, relies on the good nature of others to operate relays &=
quot;for the public good&quot;. =A0Marking it as historic would, I imagine,=
 demotivate ISPs to operate those relays and thus render the connectivity e=
ven worse than we are fearing.<br>

<br>Please don&#39;t confuse my position - I wholeheartedly believe the rig=
ht answer is, and am very vocal in promoting, native IPv6 (dual stack) ever=
ywhere, for everyone. =A0But we aren&#39;t there yet. =A0Even though my hom=
e ISP has done more IPv6 than many|most, they aren&#39;t ready to do native=
 here, yet. =A0I often rely on 6to4 is _many) scenarios and simply want som=
ething that exists to keep working until the alternatives are more availabl=
e.<br>

<br><br></div><div>/TJ</div>

--0016367658a3825e4904a54ae79f--

From moore@network-heretics.com  Thu Jun  9 10:39:11 2011
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 22DF711E819A; Thu,  9 Jun 2011 10:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.216
X-Spam-Level: 
X-Spam-Status: No, score=-3.216 tagged_above=-999 required=5 tests=[AWL=0.383,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4st0AYt9K3FF; Thu,  9 Jun 2011 10:39:10 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 13E6211E8130; Thu,  9 Jun 2011 10:39:10 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8FB0B20B34; Thu,  9 Jun 2011 13:39:09 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Thu, 09 Jun 2011 13:39:09 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=U/G5IQbdOm86Bh0lD64qy6v7nsU=; b=rckj6GEvQk7qaoOuOioDzJUmkCExmET7Oab1MLH0pLAvbMc2YOvwkba8rMaY9w0Gq2dCe1bpqnDFvAUlW5tMCgbycXz4YCDU5i0jS4YuQnqFm/wWq4Vz2HozmZKcffaoHSY+aejHLTGpbp1rs8qF+5570T56TYqdDc5TWI2M4os=
X-Sasl-enc: sXmYnMKK1jtM3o81Nu14nyxztt/ybj3bJBvPPIiMezQb 1307641148
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 2B0D3442FBE; Thu,  9 Jun 2011 13:39:08 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds	(6to4) to Historic status) to Informational RFC 
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <22F6318E46E26B498ABC828879B08D4F167D15@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Date: Thu, 9 Jun 2011 13:39:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F2C8463-36AA-41D1-8D3F-735A623F484C@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com> <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <m1QUh0G-0001hEC@stereo.hq.phicoh.net> <CCD853BD-A99F-49B5-A168-D396A606E243@network-heretics.com> <22F6318E46E26B498ABC828879B08D4F167D15@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Philip Homburg <pch-v6ops@u-1.phicoh.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, 09 Jun 2011 17:39:11 -0000

On Jun 9, 2011, at 12:01 PM, Christian Huitema wrote:

> Arguably, transitions technologies like 6to4 and Teredo have already =
achieved their purpose. My goal at the time, more than 10 years ago, was =
to break the "chicken and egg" deadlock between application developers =
and network administrators. That's why I spent such energy on making =
6to4 easy to deploy, or defining Teredo. Transitions technologies =
convinced developers that applications could be developed for IPv6 =
without waiting for every network to be ready, and applications were =
indeed developed by Microsoft and others. Network administrators in the =
meantime started deploying IPv6, and the presence of applications =
arguably helped somewhat -- although I am sure network administrators =
add many other motivations.
>=20
> We are now observing a strong pushback, because massive use of =
tunneling technologies makes networks harder to manage. Wide scale =
deployment of self-configuring technologies makes levels of services =
less predictable, and errors are hard to correct. Self-configuring =
technologies rely largely on the good will of others, which is easier to =
find during a pioneering phase. Arguably, we are beyond the pioneering =
phase for IPv6.

It's hard to argue that we're beyond the pioneering phase of IPv6 when =
native IPv6 is still not widely available.  The pushback was =
predictable, for the very reasons you cite.  But it's premature and =
counterproductive to cave in to it.  If pain associated with 6to4 =
provides an additional incentive for ISPs to deploy native v6, and for =
users to use native v6 when it becomes available, that's a Good Thing.  =
(Not that I want to cause them pain, but neither do I want the Internet =
to be stuck with 6to4 and Teredo forever.)

> I understand Keith's point of view, but it is probably time to start =
progressively rolling back the transition technologies. 6to4 is the =
weakest of these technologies. It does not traverse NAT, it does not =
include configuration verification tests, and it uses asymmetric paths. =
It makes sense to start the rollback with 6to4.

The time to start rolling back the transition technologies is when v6 =
support is available off the shelf.  Because there is some pain =
associated with them, there's a built in incentive to do so.=20

And I disagree that 6to4 is the weakest of the technologies.   They all =
have strengths and weaknesses.  6to4 is very widely implemented, is =
automatically configurable, needs no central server, and routing is =
near-optimal for 6to4-to-6to4 traffic.  But there's a community learning =
curve associated with using anycast addresses for relay routers.  =
Configured tunnels take a latency hit on every packet, no matter where =
it's going.  Teredo works through NATs (good), but also requires routing =
packets through third party servers, with the corresponding implications =
for latency, privacy, etc.  And in practice, it's pretty much a =
Microsoft-only solution - it doesn't ship with either Mac or Linux.

(If we could have developed a universal best-of-breed transition =
technology, I think we would have done so.   But the solution space =
really didn't permit that, so we ended up with a hodgepodge of different =
tools that are applicable in different  situations.)

Keith


From randy_presuhn@mindspring.com  Thu Jun  9 10:55:36 2011
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 A3D1B11E81A5 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 10:55:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7RH8JPtl8por for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 10:55:35 -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 EC86511E8196 for <ietf@ietf.org>; Thu,  9 Jun 2011 10:55:34 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=mV6GNQ/47XH4VqfUtsyxYuW6fSkL5OilbBXJde02y9+BjEta8nKfhLKKd6Gh3tnu; 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.30.227.199] (helo=oemcomputer) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1QUjSA-0007Zk-8S for ietf@ietf.org; Thu, 09 Jun 2011 13:55:34 -0400
Message-ID: <00d001cc26ce$f89a9320$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu><49D685CB-00FD-42E5-9AD8-15E51545D9A2@apple.com><006601cc260c$4a0c87e0$6801a8c0@oemcomputer><04A9F777-8C57-4120-9964-CEFFAF0DD7BE@free.fr><006d01cc26ca$ed74b600$6801a8c0@oemcomputer> <BANLkTinRZn9mvf=Rf7TmoB_Q7pp5j6fhyw@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
Date: Thu, 9 Jun 2011 10:59:24 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888cc964a8bf633b38256a823892514231974d92e51929e718f350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.30.227.199
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 17:55:36 -0000

Hi -

> From: "TJ" <trejrco@gmail.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: <ietf@ietf.org>
> Sent: Thursday, June 09, 2011 10:36 AM
> Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
...
> > The point is that the "historic" declaration can be a statement
> > about how the IETF wants things to be, rather than how they are.
> > If one happens to be a user or vendor of a "historic" technology,
> > the declaration might sting a little, but it's really not a big deal, IMO.
>
> Although I have already stated my position in this issue (against, for now),
> I have a problem with the above logic.
> You are effectively arguing that this move won't really impact anything ...
> in which case I would ask, why are we doing it?

No, what I'm saying is that declaring a technology "historic" does not
make it go away.  If accompanied by strong advice and good alternatives,
it might contribute to a reduced likelihood that one will encounter the
offensive technology, but things rarely disappear completely, nor as
quickly as one might like.

Speaking in horribly general terms, rather than the specifics of 6to4:

The folks who believe they have a legitimate need for a technology will
continue to use it as long as they are able to.  The folks who don't find
it causing problems for them will tend to leave things alone - there's
always the fear that turning something off, even if it appears to be
little-used, might break some critical but low-frequency application
somewhere in the enterprise. The folks for whom the historic
technology has been causing a problem will rejoice and turn it off or
remove it from their products, but will still need to defend against it,
because you never know what's going to come in from the
big bad internet.

Randy


From moore@network-heretics.com  Thu Jun  9 10:58:01 2011
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 2C6A211E81EC; Thu,  9 Jun 2011 10:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.237
X-Spam-Level: 
X-Spam-Status: No, score=-3.237 tagged_above=-999 required=5 tests=[AWL=0.361,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7aPBmbfHALfe; Thu,  9 Jun 2011 10:58:00 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0DE11E8180; Thu,  9 Jun 2011 10:58:00 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id E9F5620733; Thu,  9 Jun 2011 13:57:59 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 09 Jun 2011 13:57:59 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=WYjxSYzdZEgOg/cG/lrjjYY+BFM=; b=o8nJeeNVk8ea4pvTDhpQSEg2WJohlci8gIb25W1UsaUE0o3zK0QLun7eHQQarFEeS0R1nbuKLAO4QRfYk1KjpSdxbm94SOzF/x/X5DGdZ6r3JjErdLc0gb8Gz9uDjwhN/2muSP/fk3rVPqtSivMXutzbyCj+3B93bwsVfR+DMJU=
X-Sasl-enc: +VpHuf6FRZTW7vUwdzN35G5jJW5fTic3O/LCOFktQJk+ 1307642278
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 57514442D5F; Thu,  9 Jun 2011 13:57:58 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-24-770079235
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com>
Date: Thu, 9 Jun 2011 13:57:57 -0400
Message-Id: <BD885BE1-F275-46E9-8122-60E0725F8B86@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org> <ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com> <BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations Working Group <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 17:58:01 -0000

--Apple-Mail-24-770079235
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 9, 2011, at 1:42 PM, Lorenzo Colitti wrote:

> On Tue, Jun 7, 2011 at 11:20 AM, Keith Moore =
<moore@network-heretics.com> wrote:
> Indeed, that is one of its main virtues.  6to4 decouples application =
deployment of v6 from network deployment of v6, and helps reduce the =
"chicken or egg" problem.
>=20
> No, it does not - in fact, it is the opposite.
>=20
> Geoff has presented data that shows that anycasted 6to4 as a =
connectivity mechanism has a failure rate of the order of 20-30%.

I don't dispute that data.  I just disagree with the notion of =
discouraging 6to4 in its entirety because of the current problems with =
advertising 6to4 relay routers using anycast addresses.

I suspect that the anycast issues will largely be sorted out before this =
document can have much of an effect.  But nevertheless, I don't have a =
problem with discouraging this use of anycast.  I think it was a noble =
experiment, and we learned something valuable:  Don't use anycast to =
advertise a service that is provided by a wide range of players, at =
least not without having some fairly clear guidelines about how to =
monitor them and weed out the broken ones.

> We have data that clearly shows that Mac OS 10.6.4, which uses 6to4 by =
default, has a ~50x greater failure rate when connecting to dual-stack =
servers than Mac OS 10.6.5 - and the only change is to not use 6to4 by =
default. Search the list archives for details.

Again, I have no problem with implementations disabling 6to4 by default. =
 Especially given the looming threat of LSN, I became convinced that it =
was the right thing to do.

> So the existence of 6to4 is in itself a significant barrier for IPv6 =
deployment for server operators and content providers.

non sequitur.   Existing server operators and content providers can =
easily provide 6to4 addresses for their servers and content, which will =
be used in preference to native v6 addresses.

> Application developers should develop using manually configured =
tunnels, not 6to4. At least they don't have a 20% failure rate.

How do you know?  How do you even measure the failure rate of manually =
configured tunnels in the aggregate?  I don't think you can monitor that =
kind of traffic the way you can 6to4, because the traffic patterns are =
much more constrained.   It's been awhile since I used manually =
configured tunnels (from a well-known tunnel broker).  But the one time =
I did try them, 6to4 worked better overall - lower latency and lower =
failure rate.

Keith


--Apple-Mail-24-770079235
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 9, 2011, at 1:42 PM, Lorenzo Colitti wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
class=3D"gmail_quote">On Tue, Jun 7, 2011 at 11:20 AM, Keith Moore <span =
dir=3D"ltr">&lt;<a =
href=3D"mailto:moore@network-heretics.com">moore@network-heretics.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">Indeed, that is one of its main virtues. &nbsp;6to4 =
decouples application deployment of v6 from network deployment of v6, =
and helps reduce the "chicken or egg" =
problem.</div></blockquote><div><br></div>

<div>No, it does not - in fact, it is the =
opposite.</div><div><br></div><div>Geoff has presented data that shows =
that anycasted 6to4 as a connectivity mechanism has a failure rate of =
the order of 20-30%. </div></div></blockquote><div><br></div><div>I =
don't dispute that data. &nbsp;I just disagree with the notion of =
discouraging 6to4 in its entirety because of the current problems with =
advertising 6to4 relay routers using anycast =
addresses.</div><div><br></div><div>I suspect that the anycast issues =
will largely be sorted out before this document can have much of an =
effect. &nbsp;But nevertheless, I don't have a problem with discouraging =
this use of anycast. &nbsp;I think it was a noble experiment, and we =
learned something valuable: &nbsp;Don't use anycast to advertise a =
service that is provided by a wide range of players, at least not =
without having some fairly clear guidelines about how to monitor them =
and weed out the broken ones.</div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><div>We have data that clearly shows that Mac OS =
10.6.4, which uses 6to4 by default, has a ~50x greater failure rate when =
connecting to dual-stack servers than Mac OS 10.6.5 - and the only =
change is to not use 6to4 by default. Search the list archives for =
details.</div></div></blockquote><div><br></div><div>Again, I have no =
problem with implementations disabling 6to4 by default. &nbsp;Especially =
given the looming threat of LSN, I became convinced that it was the =
right thing to do.</div></div><div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote">

<div><div>So the existence of 6to4 is in itself a significant barrier =
for IPv6 deployment for server operators and content =
providers.</div></div></div></blockquote><div><br></div>non sequitur. =
&nbsp; Existing server operators and content providers can easily =
provide 6to4 addresses for their servers and content, which will be used =
in preference to native v6 addresses.<br><div><br></div><blockquote =
type=3D"cite"><div class=3D"gmail_quote"><div>

<div>Application developers should develop using manually configured =
tunnels, not 6to4. At least they don't have a 20% failure =
rate.</div></div></div>
</blockquote></div><br><div>How do you know? &nbsp;How do you even =
measure the failure rate of manually configured tunnels in the =
aggregate? &nbsp;I don't think you can monitor that kind of traffic the =
way you can 6to4, because the traffic patterns are much more =
constrained. &nbsp; It's been awhile since I used manually configured =
tunnels (from a well-known tunnel broker). &nbsp;But the one time I did =
try them, 6to4 worked better overall - lower latency and lower failure =
rate.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-24-770079235--

From jhw@apple.com  Thu Jun  9 11:01:25 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5643E11E8205; Thu,  9 Jun 2011 11:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level: 
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5DJ7A1+e7dvD; Thu,  9 Jun 2011 11:01:24 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 353A911E8162; Thu,  9 Jun 2011 11:01:22 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LMJ007VQBBAOH50@mail-out.apple.com>; Thu, 09 Jun 2011 11:01:21 -0700 (PDT)
X-AuditID: 11807137-b7cd4ae000003108-9b-4df10a710113
Received: from kencur (kencur.apple.com [17.151.62.38]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay16.apple.com (Apple SCV relay) with SMTP id C9.3E.12552.17A01FD4; Thu, 09 Jun 2011 11:01:21 -0700 (PDT)
Received: from event-10-2-63-213.venue.apple.com (unknown [192.42.249.191]) by kencur.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LMJ00J3EBE8V210@kencur.apple.com>; Thu, 09 Jun 2011 11:01:20 -0700 (PDT)
Subject: Re: [v6ops] Last Call:	<draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move	Connection of IPv6 Domains via IPv4 Clouds	(6to4) to Historic status) to Informational RFC
From: james woodyatt <jhw@apple.com>
In-reply-to: <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com>
Date: Thu, 09 Jun 2011 11:01:22 -0700
Message-id: <056CE2B5-5DE5-4B0D-B38B-569C011B2733@apple.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com> <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1237.1)
X-Brightmail-Tracker: AAAAAA==
Cc: "v6ops@ietf.org WG" <v6ops@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, 09 Jun 2011 18:01:25 -0000

On Jun 9, 2011, at 7:37 AM, Keith Moore wrote:
> 
>  Clearly the intent of this draft and protocol action are to discourage use of 6to4, particularly in new implementations.  You can't discourage use of 6to4 in new implementations without harming people who are already using it and depending on it.

After it became clear to me that IETF will not be issuing a phase-out plan for 6to4, I recommended to all the relevant product managers at Apple that we should continue supporting 6to4 in new implementations for the foreseeable future (despite the non-RFC2119 'not recommended' line in section 1).

I don't see why this draft should discourage anyone from continuing to support 6to4, which as you point out is a *uniquely* useful protocol that people depend on and find *irreplaceable*.  Reclassifying it as Historic simply allows IETF working groups to operate on the fiction that 6to4 will eventually disappear someday in the indefinite and vaguely hopeful future.  While I don't think that self-delusion will be a good thing for IETF in the long run, I have a hard time getting too bummed out about it.  Pragmatism will find its way into deliberations.

Yes, I think this draft is a pointless waste of time.  The reason I support publishing it, however, is that I disagree with your assessment of the harm it could do.  Also, it enjoys widespread support in the V6OPS working group and the opposition, while vocal, seems quite small.  That looks like rough consensus to me, and if I can help get it off our agenda sooner by supporting it rather than opposing it, then I say let's print it.

I confidently predict the reclassification to Historic will be roundly ignored not just by Apple product engineering but by the entire industry.  We're smart enough to recognize that we're not the target audience for the RFC.  The draft that matters is the companion advisory draft.  It would be nice if the 6to4-to-historic draft could be spiked so as not to distract from its companion, but I don't see that as a likely outcome.  Alas and alack.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From moore@network-heretics.com  Thu Jun  9 11:24:48 2011
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 B961A11E8163 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 11:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.256
X-Spam-Level: 
X-Spam-Status: No, score=-3.256 tagged_above=-999 required=5 tests=[AWL=0.343,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LtHnsjgmFga7 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 11:24:47 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 866E911E80F3 for <ietf@ietf.org>; Thu,  9 Jun 2011 11:24:47 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id E86DC20FA9 for <ietf@ietf.org>; Thu,  9 Jun 2011 14:24:46 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Thu, 09 Jun 2011 14:24:46 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=from:content-type:content-transfer-encoding:date:subject:to:message-id:mime-version; s=smtpout; bh=JJegyYz5DuxgMPg5Oq0jpMOXeYM=; b=p0dq1yldPZNRdrDLOAahfqt+P8wIxru/e5tGJlmpn0aJvU2co9WO9ZrhFUTx3mQt7RdIMythkA8A+LB3hIQNBGzL7+VKCSh/jCwWJclsZA36HKXUPACdi1gi98KlWdQTvL4qFo7Vv509i5akFFFB9iasa09g1EuhnrNAZjszn9k=
X-Sasl-enc: ehWZ670JZcnh+Bzaxp0mgMpBdTqtP3tcw5nQBc/xGriV 1307643886
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 1DAAE441773; Thu,  9 Jun 2011 14:24:45 -0400 (EDT)
From: Keith Moore <moore@network-heretics.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 9 Jun 2011 14:24:45 -0400
Subject: one data point regarding native IPv6 support
To: IETF Discussion <ietf@ietf.org>
Message-Id: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 18:24:48 -0000

I just called my ISP to ask about availability of IPv6 at my home.

Me:  "I'm a current customer, and I'm just calling to ask if you support =
Internet Protocol Version 6."

First person: "Yes, we do support Internet.  We support DSL at 3 =
megabits and 6 megabits."

Me: "I understand that, but I'm asking about Internet Protocol version =
6, IPv6.  The Internet has been using IP version 4 since the early =
1980s, but that's running out.  IPv6 is the new version."

First person: "Let me transfer you to support."

Second person: "Hi, this is support.  How may I help you?"

Me: "I'm a current customer, and I'm just calling to ask if you support =
Internet Protocol Version 6."

Second person: "IP version what?"

Me: "Internet protocol version 6".

Second person: "I have no idea.  Let me transfer you to someone else."

(places me on hold for 15 minutes)

Second person: "I'm sorry for the wait time.  I've been trying to find =
the answer to your question, but nobody here seems to know anything =
about it.  We're trying to get in touch with people who run the network =
to ask them.   Can I get your number and call you back?"

Granted, this is just one ISP.  The other ISP that offers service in my =
area put me on hold for an hour and a half *before anyone ever talked to =
me* when I tried to get a quote from them, so I concluded that they =
wouldn't be a good choice.  And these guys have been good about support =
in general.  They seem to know their stuff, which is more than I can say =
for some ISPs I've dealt with in the past.

I live in a well-settled urban area, three miles from the center of the =
city (and sadly, four miles from my CO, which means my DSL circuit gets =
around 380kbits/sec).  It's not a backwater, there's plenty of lit fiber =
running through town.  But when the support people for a fairly =
well-established telco haven't even heard of IPv6, it's hard to believe =
that it's going to be available anytime soon.

Meanwhile, 6to4 continues to work just fine for me.

So please explain again why it isn't premature to discourage a valuable =
transition mechanism?

Keith


From moore@network-heretics.com  Thu Jun  9 11:37:44 2011
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 92E0B11E8126; Thu,  9 Jun 2011 11:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.273
X-Spam-Level: 
X-Spam-Status: No, score=-3.273 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VDO3oSJ7MoAL; Thu,  9 Jun 2011 11:37:43 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id E0D1811E8106; Thu,  9 Jun 2011 11:37:42 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8D7A320D4F; Thu,  9 Jun 2011 14:37:42 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 09 Jun 2011 14:37:42 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=HHlX9GldpM7wHuM3Xub7w7FjAMk=; b=pdT5Fc2xmPtkQCZCD12d88PTJT2s+P5lSvDwwgTmEyINCH/LZgMAebgjH2voPl8488TQdGTH/R1ibUHSSiSjLKsK9IMwWO+AWL0HOcgd6PeeH/32qxkQY0qfKDMEH4A2CM8r5m6QMx6Is/MrspY9yUIj/6tQxNai5erBYaV4iD4=
X-Sasl-enc: CgmxgZ8cG0Ub9WfkCnakyJKqsKGDFSw4CbD0pwQUZalo 1307644661
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id EF61E445597; Thu,  9 Jun 2011 14:37:40 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-25-772461679
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <BANLkTi=3LxgdDSe=rE7PPW6uFWPmQvfNUDr6JiSbZ07Zmb6LTw@mail.gmail.com>
Date: Thu, 9 Jun 2011 14:37:39 -0400
Message-Id: <E197F05C-BE22-4431-897B-FFE2E2CB1F0E@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org> <ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com> <BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com> <BD885BE1-F275-46E9-8122-60E0725F8B86@network-heretics.com> <BANLkTi=3LxgdDSe=rE7PPW6uFWPmQvfNUDr6JiSbZ07Zmb6LTw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations Working Group <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 18:37:44 -0000

--Apple-Mail-25-772461679
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 9, 2011, at 2:20 PM, Lorenzo Colitti wrote:

> On Thu, Jun 9, 2011 at 10:57 AM, Keith Moore =
<moore@network-heretics.com> wrote:
>> So the existence of 6to4 is in itself a significant barrier for IPv6 =
deployment for server operators and content providers.
> non sequitur.   Existing server operators and content providers can =
easily provide 6to4 addresses for their servers and content, which will =
be used in preference to native v6 addresses.
>=20
> No. According to Geoff's data, one of the main reasons 6to4 fails is a =
firewall that blocks IPv4 protocol 41 traffic. Even if content providers =
published 6to4 addresses, those connections would still fail.

I suppose we should just tunnel the whole IPv6 network over IPv4 + HTTP =
then.

Seriously, the argument that 6to4 should be trashed because ISPs are =
blocking tunnels has the flavor of "don't solve the problem, but rather, =
stamp out the solution".=20

(And of course if the ISPs block protocol 41, that will also kill =
configured tunnels that happen to transit their networks.  The overall =
failure rate will be the same, but the granularity of failure will be =
higher for the configured tunnels.)

>> Application developers should develop using manually configured =
tunnels, not 6to4. At least they don't have a 20% failure rate.
>=20
> How do you know?  How do you even measure the failure rate of manually =
configured tunnels in the aggregate?
>=20
> In a similar way as Geoff measured 6to4 - looking at SYNs.

=46rom where?   Again, the tunnels aren't taking the variety of paths =
that 6to4 connections are.  It's that variety that makes measurements =
such as Geoff's at all useful - it's what lets you at least believe that =
the measurements made at a few points are representative of the whole.
=20
>  I don't think you can monitor that kind of traffic the way you can =
6to4, because the traffic patterns are much more constrained.   It's =
been awhile since I used manually configured tunnels (from a well-known =
tunnel broker).  But the one time I did try them, 6to4 worked better =
overall - lower latency and lower failure rate.
>=20
> Please try again. You will be pleasantly surprised.=20

A few months ago I was trying to set one up, but I ran out of time.   =
I'm really busy these days, and it's nowhere nearly as easy to set up a =
configured tunnel as it is to set up 6to4.

Keith


--Apple-Mail-25-772461679
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 9, 2011, at 2:20 PM, Lorenzo Colitti wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
class=3D"gmail_quote">On Thu, Jun 9, 2011 at 10:57 AM, Keith Moore <span =
dir=3D"ltr">&lt;<a =
href=3D"mailto:moore@network-heretics.com">moore@network-heretics.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, =
204, 204); border-left-style: solid; padding-left: 1ex; position: =
static; z-index: auto; ">

<div style=3D"word-wrap:break-word"><div><div class=3D"im"><blockquote =
type=3D"cite"><div class=3D"gmail_quote"><div><div>So the existence of =
6to4 is in itself a significant barrier for IPv6 deployment for server =
operators and content providers.</div>

</div></div></blockquote></div>non sequitur. &nbsp; Existing server =
operators and content providers can easily provide 6to4 addresses for =
their servers and content, which will be used in preference to native v6 =
addresses.</div>

</div></blockquote><div><br></div><div>No. According to Geoff's data, =
one of the main reasons 6to4 fails is a firewall that blocks IPv4 =
protocol 41 traffic. Even if content providers published 6to4 addresses, =
those connections would still =
fail.</div></div></blockquote><br></div><div>I suppose we should just =
tunnel the whole IPv6 network over IPv4 + HTTP =
then.</div><div><br></div><div>Seriously, the argument that 6to4 should =
be trashed because ISPs are blocking tunnels has the flavor of "don't =
solve the problem, but rather, stamp out the =
solution".&nbsp;</div><div><br></div><div>(And of course if the ISPs =
block protocol 41, that will also kill configured tunnels that happen to =
transit their networks. &nbsp;The overall failure rate will be the same, =
but the granularity of failure will be higher for the configured =
tunnels.)</div><div><br></div><div><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div =
style=3D"word-wrap:break-word"><div><div class=3D"im"><blockquote =
type=3D"cite"><div class=3D"gmail_quote"><div>

<div>Application developers should develop using manually configured =
tunnels, not 6to4. At least they don't have a 20% failure =
rate.</div></div></div></blockquote></div></div><div>How do you know? =
&nbsp;How do you even measure the failure rate of manually configured =
tunnels in the aggregate?</div>

</div></blockquote><div><br></div><div>In a similar way as Geoff =
measured 6to4 - looking at =
SYNs.</div></div></blockquote><div><br></div><div>=46rom where? &nbsp; =
Again, the tunnels aren't taking the variety of paths that 6to4 =
connections are. &nbsp;It's that variety that makes measurements such as =
Geoff's at all useful - it's what lets you at least believe that the =
measurements made at a few points are representative of the =
whole.</div><div>&nbsp;</div><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, =
204, 204); border-left-style: solid; padding-left: 1ex; position: =
static; z-index: auto; "><div style=3D"word-wrap:break-word"><div> =
&nbsp;I don't think you can monitor that kind of traffic the way you can =
6to4, because the traffic patterns are much more constrained. &nbsp; =
It's been awhile since I used manually configured tunnels (from a =
well-known tunnel broker). &nbsp;But the one time I did try them, 6to4 =
worked better overall - lower latency and lower failure rate.</div>

</div></blockquote><div><br></div><div>Please try again. You will be =
pleasantly surprised.&nbsp;</div></div>
</blockquote></div><br><div>A few months ago I was trying to set one up, =
but I ran out of time. &nbsp; I'm really busy these days, and it's =
nowhere nearly as easy to set up a configured tunnel as it is to set up =
6to4.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-25-772461679--

From moore@network-heretics.com  Thu Jun  9 11:53:23 2011
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 D0F8C11E80FE; Thu,  9 Jun 2011 11:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.288
X-Spam-Level: 
X-Spam-Status: No, score=-3.288 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OozQLMkgw3NU; Thu,  9 Jun 2011 11:53:22 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id A78A611E8089; Thu,  9 Jun 2011 11:53:22 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 5608C209C8; Thu,  9 Jun 2011 14:53:22 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 09 Jun 2011 14:53:22 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=0LlyWP1/G2CgRG9r57vaAAxX6wg=; b=Z5zvSazZpdE8G4dIsS5ZXswIaAKgreWRsWQe/KUS8CbRONdxr10J5a08tcipJP9FcQCXlVJM3BJrTLJNGZnWyffHyNyCpWkPpIks1N5yW5ij9CoUrEI8u0kQrLKJTg42LmGHgSp7HFvSlTs1eBCU/3q/A8vdhA+0rrif4PXAz2U=
X-Sasl-enc: y1L8I6EHE1AbF3KhTL46iAPRLaHY3iNk+2bQYHLRrhaA 1307645601
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id D1CF244046C; Thu,  9 Jun 2011 14:53:20 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-26-773401850
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <BANLkTi=_bGLqAWZ+EBGV75Exv2v0PNpNzpf6Ofhx=EiShC7zcQ@mail.gmail.com>
Date: Thu, 9 Jun 2011 14:53:19 -0400
Message-Id: <0AFB3478-E7AD-41B7-A1E7-88479D37BE93@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org> <ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com> <BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com> <BD885BE1-F275-46E9-8122-60E0725F8B86@network-heretics.com> <BANLkTi=3LxgdDSe=rE7PPW6uFWPmQvfNUDr6JiSbZ07Zmb6LTw@mail.gmail.com> <E197F05C-BE22-4431-897B-FFE2E2CB1F0E@network-heretics.com> <BANLkTi=_bGLqAWZ+EBGV75Exv2v0PNpNzpf6Ofhx=EiShC7zcQ@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations Working Group <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 18:53:23 -0000

--Apple-Mail-26-773401850
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 9, 2011, at 2:45 PM, Lorenzo Colitti wrote:

> On Thu, Jun 9, 2011 at 11:37 AM, Keith Moore =
<moore@network-heretics.com> wrote:
> I suppose we should just tunnel the whole IPv6 network over IPv4 + =
HTTP then.
>=20
> Seriously, the argument that 6to4 should be trashed because ISPs are =
blocking tunnels has the flavor of "don't solve the problem, but rather, =
stamp out the solution".=20
>=20
> Actually, this mostly happens in enterprise networks and universities. =
I don't see why they would want to change this compared to, say, =
actually deploying native IPv6.

Well if an enterprise network wants to firewall certain kinds of =
traffic, that's its own business.  The fact that some enterprises =
firewall ip-over-ip tunnels is not a justification for IETF trashing one =
particular kind of ip tunnel.

>> In a similar way as Geoff measured 6to4 - looking at SYNs.
>=20
> =46rom where?   Again, the tunnels aren't taking the variety of paths =
that 6to4 connections are.  It's that variety that makes measurements =
such as Geoff's at all useful - it's what lets you at least believe that =
the measurements made at a few points are representative of the whole.
>=20
> =46rom the same place that he ran the 6to4 measurements from?

See above.  It's not a valid measurement.   Or the measurement is fine, =
but comparisons between configured tunnels and 6to4 on the basis of such =
measurements are not valid.
=20
> A few months ago I was trying to set one up, but I ran out of time.   =
I'm really busy these days, and it's nowhere nearly as easy to set up a =
configured tunnel as it is to set up 6to4.
>=20
> Go to http://tunnelbroker.net/ . I'm willing to bet that it will take =
a lot less time than you have spent writing email on this thread. :-)

That's who I was using before.

Keith


--Apple-Mail-26-773401850
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 9, 2011, at 2:45 PM, Lorenzo Colitti wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Thu, Jun 9, 2011 at 11:37 AM, Keith Moore <span dir="ltr">&lt;<a href="mailto:moore@network-heretics.com">moore@network-heretics.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">

<div style="word-wrap:break-word"><div class="im"><div><div>I suppose we should just tunnel the whole IPv6 network over IPv4 + HTTP then.</div></div></div><div><br></div><div>Seriously, the argument that 6to4 should be trashed because ISPs are blocking tunnels has the flavor of "don't solve the problem, but rather, stamp out the solution".&nbsp;</div>

</div></blockquote><div><br></div><div>Actually, this mostly happens in enterprise networks and universities. I don't see why they would want to change this compared to, say, actually deploying native IPv6.</div></div></blockquote><div><br></div>Well if an enterprise network wants to firewall certain kinds of traffic, that's its own business. &nbsp;The fact that some enterprises firewall ip-over-ip tunnels is not a justification for IETF trashing one particular kind of ip tunnel.</div><div><br><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><div style="word-wrap:break-word"><div><div class="im"><blockquote type="cite"><div class="gmail_quote"><div>

In a similar way as Geoff measured 6to4 - looking at SYNs.</div></div></blockquote><div><br></div></div><div>From where? &nbsp; Again, the tunnels aren't taking the variety of paths that 6to4 connections are. &nbsp;It's that variety that makes measurements such as Geoff's at all useful - it's what lets you at least believe that the measurements made at a few points are representative of the whole.</div>

</div></div></blockquote><div><br></div><div>From the same place that he ran the 6to4 measurements from?</div></div></blockquote><div><br></div>See above. &nbsp;It's not a valid measurement. &nbsp; Or the measurement is fine, but comparisons between configured tunnels and 6to4 on the basis of such measurements are not valid.</div><div>&nbsp;</div><div><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style="word-wrap:break-word"><div><div class="im"><div>A few months ago I was trying to set one up, but I ran out of time. &nbsp; I'm really busy these days, and it's nowhere nearly as easy to set up a configured tunnel as it is to set up 6to4.</div>

</div></div></div></blockquote><div><br></div><div>Go to <a href="http://tunnelbroker.net/">http://tunnelbroker.net/</a> . I'm willing to bet that it will take a lot less time than you have spent writing email on this thread. :-)</div>

</div>
</blockquote></div><br><div>That's who I was using before.</div><div><br></div><div>Keith</div><div><br></div></body></html>
--Apple-Mail-26-773401850--

From jhw@apple.com  Thu Jun  9 11:56:02 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 122FD11E819B for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 11:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.499
X-Spam-Level: 
X-Spam-Status: No, score=-106.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BMCy0YKxtQdm for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 11:56:01 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7137911E817A for <ietf@ietf.org>; Thu,  9 Jun 2011 11:56:01 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LMJ007L3DX9OHF0@mail-out.apple.com> for ietf@ietf.org; Thu, 09 Jun 2011 11:56:01 -0700 (PDT)
X-AuditID: 1180711d-b7c70ae00000719a-08-4df1174059a5
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id 2D.56.29082.14711FD4; Thu, 09 Jun 2011 11:56:01 -0700 (PDT)
Received: from event-10-2-63-213.venue.apple.com (unknown [192.42.249.191]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LMJ00HABDXC9T10@cardamom.apple.com> for ietf@ietf.org; Thu, 09 Jun 2011 11:56:00 -0700 (PDT)
Subject: Re: one data point regarding native IPv6 support
From: james woodyatt <jhw@apple.com>
In-reply-to: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>
Date: Thu, 09 Jun 2011 11:56:00 -0700
Message-id: <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1237.1)
X-Brightmail-Tracker: AAAAAA==
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, 09 Jun 2011 18:56:02 -0000

On Jun 9, 2011, at 11:24 AM, Keith Moore wrote:
> 
> [...] But when the support people for a fairly well-established telco haven't even heard of IPv6, it's hard to believe that it's going to be available anytime soon.

I have another anecdote to relate.

When I contacted the support staff at the moderately sized regional ISP I use at home, to ask about whether they might move to providing native IPv6 service instead of their subscribers-only IPv6-in-IPv4 tunnel service, the support person was knowledgeable about IPv6, but unhelpful.

I explained who I am, and what I do at Apple, and tried very hard without disclosing Apple Confidential information to explain that it's not just a hobby for me... I need *native* IPv6 into my home in San Francisco for my day job, and that I want to stay with my current provider rather than move to one of its competitors, which I named, and which I know to be rolling out native IPv6 service in my area in the immediate future.  I hoped that might jog something loose.  I'm quite willing and able to help them conduct a native IPv6 trial.

The support person said, "Let me pass along your information to our chief of network operations."

A couple days later, I heard back from the support person.  "We have no plans to offer native IPv6."

Meanwhile, 6to4 works fine on their network so long as remote IPv6 destinations have a working return path route to 2002::/16, i.e. they are complying with I-D.ietf-v6ops-6to4-advisory now.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From brian.e.carpenter@gmail.com  Thu Jun  9 12:01:50 2011
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 13CB11F0C5D; Thu,  9 Jun 2011 12:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.299
X-Spam-Level: 
X-Spam-Status: No, score=-103.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iVdJXJKV4MXM; Thu,  9 Jun 2011 12:01:49 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1AE361F0C64; Thu,  9 Jun 2011 12:01:11 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1362674fxm.31 for <multiple recipients>; Thu, 09 Jun 2011 12:01:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=U9hn4RpC0/pc8TTWX/ov5ZUz0Mp+9axMFUIMeH5eDek=; b=bSp89EAED+fuq5nR1TuVSW5jjoejfEwTG9t+IDA5GRNqN0+EQlkMerFJn44vtD9t2+ MLP+VJmwc0Mkx9epNv/Y35KreWa9LKEA+1sSCFUOHQmOlm/qS3SKiNAdE/Bb3lkKj1GB 2XKEg/ozCQ+XPqUplBOApGVPVd895wrbMJfL0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=u+aPA208nMw2eW6cIKeJHzaZVn1fiwSAaty8bDRUqvzngfSMgDb8ple8/YLWnuKMsI oERTTY1b6R91N3CvkTx6w7//OZr0uHCmCymIHsildBQVYXrygm0ubGSK9kIitomm7ZS1 KKmPxUGxmTBrKMbDehZQ4g/OvvG5DPjmcn+SA=
Received: by 10.223.102.131 with SMTP id g3mr1154816fao.68.1307646069483; Thu, 09 Jun 2011 12:01:09 -0700 (PDT)
Received: from [10.255.25.89] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id g7sm769891fac.15.2011.06.09.12.01.06 (version=SSLv3 cipher=OTHER); Thu, 09 Jun 2011 12:01:08 -0700 (PDT)
Message-ID: <4DF1186E.7080902@gmail.com>
Date: Fri, 10 Jun 2011 07:01:02 +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: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com>	<B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>	<B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org>	<ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com>	<BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com>	<BD885BE1-F275-46E9-8122-60E0725F8B86@network-heretics.com> <BANLkTi=3LxgdDSe=rE7PPW6uFWPmQvfNUDr6JiSbZ07Zmb6LTw@mail.gmail.com>
In-Reply-To: <BANLkTi=3LxgdDSe=rE7PPW6uFWPmQvfNUDr6JiSbZ07Zmb6LTw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations Working Group <v6ops@ietf.org>, Keith Moore <moore@network-heretics.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 19:01:50 -0000

Hi Lorenzo,

On 2011-06-10 06:20, Lorenzo Colitti wrote:
> On Thu, Jun 9, 2011 at 10:57 AM, Keith Moore <moore@network-heretics.com>wrote:
> 
>> So the existence of 6to4 is in itself a significant barrier for IPv6
>> deployment for server operators and content providers.
>>
>> non sequitur.   Existing server operators and content providers can easily
>> provide 6to4 addresses for their servers and content, which will be used in
>> preference to native v6 addresses.
>>
> 
> No. According to Geoff's data, one of the main reasons 6to4 fails is a
> firewall that blocks IPv4 protocol 41 traffic. Even if content providers
> published 6to4 addresses, those connections would still fail.

To be clear, that statistic applies to clients whose SYN packet reaches
the server, but who never respond to SYN/ACK. It's a presumption that
the problem is Protocol 41 filtering - probably correct, but there are
other possible causes.

Also, we have no possible way of knowing how many clients send SYN packets
towards a 6to4 anycast relay, but those packets are blackholed and never
reach the intended server. From the client's viewpoint, this also looks
like a missing SYN/ACK, leading to retries and eventual fallback to IPv4.

In other words, the real failure rate may be much worse than Geoff reports,
but we have no way of measuring it.
> 
> 
>> Application developers should develop using manually configured tunnels,
>> not 6to4. At least they don't have a 20% failure rate.
>>
>> How do you know?  How do you even measure the failure rate of manually
>> configured tunnels in the aggregate?
>>
> 
> In a similar way as Geoff measured 6to4 - looking at SYNs. I suspect that
> the answer will be that much fewer users have configured tunnels than 6to4,
> and that the failure rate is much lower.

Er, I'm currently on 2001:388:f000::xxxx
Do you have an algorithm that will tell you whether that is native
or a configured tunnel?

    Brian
> 
> 
>>  I don't think you can monitor that kind of traffic the way you can 6to4,
>> because the traffic patterns are much more constrained.   It's been awhile
>> since I used manually configured tunnels (from a well-known tunnel broker).
>>  But the one time I did try them, 6to4 worked better overall - lower latency
>> and lower failure rate.
>>
> 
> Please try again. You will be pleasantly surprised.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From tjc@ecs.soton.ac.uk  Thu Jun  9 12:35:14 2011
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 04F3511E80D8; Thu,  9 Jun 2011 12:35: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.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21ZwsFGSyIHL; Thu,  9 Jun 2011 12:35:12 -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 06C3011E8089; Thu,  9 Jun 2011 12:35:07 -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 p59JZ2Yv032395; Thu, 9 Jun 2011 20:35:02 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p59JZ2Yv032395
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1307648103; bh=q7D7VI6mRvCeXGgGN7BwWF8uSLo=; h=From:Mime-Version:Subject:Date:In-Reply-To:To:References; b=0GKdPR8HfOD/Ce7mLFjMNBqri5hpzqk3Bl9Lj/8KnsygDo648X1Cj1DY4jmUMWO5o 3FI6DXg6Wkh0pv99afwumcgV1rqDYjOzZRX3/j1n40u/e9jTaDAaem5P+eK0lp5YkG KXtSqC51GuYRDChkhwoG8vX6+o9XrP5/q8DAXABs=
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 id n58KZ20035665161xU ret-id none; Thu, 09 Jun 2011 20:35:02 +0100
Received: from [192.168.1.14] (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 p59JYuVH015531 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 9 Jun 2011 20:34:57 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-1-775898431
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>	(Request to move Connection of IPv6 Domains via IPv4	Clouds	(6to4) to Historic status) to Informational RFC
Date: Thu, 9 Jun 2011 20:34:56 +0100
In-Reply-To: <0F2C8463-36AA-41D1-8D3F-735A623F484C@network-heretics.com>
To: "v6ops@ietf.org WG" <v6ops@ietf.org>, ietf@ietf.org
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <DD1A73D9E9C89144A927C5080F70285A01A7675A98FD@NA-EXMSG-S702.segroup.winse.corp.microsoft.com> <677F8425-F710-403E-B59B-F3CCEBF711C7@apple.com> <ABDDAB5E-40CA-4097-86EC-FAA1D93F6CC9@network-heretics.com> <m1QUh0G-0001hEC@stereo.hq.phicoh.net> <CCD853BD-A99F-49B5-A168-D396A606E243@network-heretics.com> <22F6318E46E26B498ABC828879B08D4F167D15@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <0F2C8463-36AA-41D1-8D3F-735A623F484C@network-heretics.com> <F376F804-0F19-461A-B1F0-967C2C4F2EE0@ecs.soton.ac.uk>
Message-ID: <EMEW3|5a4519def70ee3ecffb36e29bb7a53b0n58KZ203tjc|ecs.soton.ac.uk|F376F804-0F19-461A-B1F0-967C2C4F2EE0@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n58KZ2003566516100; tid=n58KZ20035665161xU; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p59JZ2Yv032395
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 19:35:14 -0000

--Apple-Mail-1-775898431
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I agree the draft should be progressed, so add another +1 to the 'just =
ship it' people.

On 9 Jun 2011, at 18:39, Keith Moore wrote:
>  If pain associated with 6to4 provides an additional incentive for =
ISPs to deploy native v6, and for users to use native v6 when it becomes =
available, that's a Good Thing.=20

The pain though is felt by the content providers, who still see too much =
brokenness. =20

On 9 Jun 2011, at 19:01, james woodyatt wrote:
> I confidently predict the reclassification to Historic will be roundly =
ignored not just by Apple product engineering but by the entire =
industry.  We're smart enough to recognize that we're not the target =
audience for the RFC.  The draft that matters is the companion advisory =
draft.  It would be nice if the 6to4-to-historic draft could be spiked =
so as not to distract from its companion, but I don't see that as a =
likely outcome.  Alas and alack.

Well, the most important point in this is that 6to4 is disabled by =
default in every device.  Apple did that already, which is good. What is =
unclear to me though is whether deprecating 2002::/16 means that prefix =
would no longer be routed, as per 3ffe::/16, or just 'reserved' so it's =
not reallocated later.

On 9 Jun 2011, at 19:53, Keith Moore wrote:
> On Jun 9, 2011, at 2:45 PM, Lorenzo Colitti wrote:
>> Go to http://tunnelbroker.net/ . I'm willing to bet that it will take =
a lot less time than you have spent writing email on this thread. :-)
>=20
> That's who I was using before.

Our staff and students find the HE broker easy to use, though I believe =
some also use other brokers.  One student did a final year project this =
year developing a Linux home router which included HE broker support.  =
It was simple to use/integrate.

On 9 Jun 2011, at 19:56, james woodyatt wrote:
> I need *native* IPv6 into my home in San Francisco for my day job

Have you considered deploying/adding IPv6 VPN support at your day job?  =
So your VPN from home to work gives you IPv4 and IPv6?  This is quite a =
nice model, and is starting to appear in UK universities, and I use it =
myself for IPv6 training. At least one big vendor offers this today. =
Users are familiar with VPN use, so adding IPv6 with that comes =
naturally, and $dayjob provides the support, so you're in control.

> Meanwhile, 6to4 works fine on their network so long as remote IPv6 =
destinations have a working return path route to 2002::/16, i.e. they =
are complying with I-D.ietf-v6ops-6to4-advisory now.

That 'so long as' is the crux though.

Tim=

--Apple-Mail-1-775898431
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I =
agree the draft should be progressed, so add another +1 to the 'just =
ship it' people.<div><br><div><div>On 9 Jun 2011, at 18:39, Keith Moore =
wrote:</div><div><blockquote type=3D"cite"><div>&nbsp;If pain associated =
with 6to4 provides an additional incentive for ISPs to deploy native v6, =
and for users to use native v6 when it becomes available, that's a Good =
Thing.&nbsp;</div></blockquote></div><br></div><div>The pain though is =
felt by the content providers, who still see too much brokenness. =
&nbsp;</div><br><div><div>On 9 Jun 2011, at 19:01, james woodyatt =
wrote:</div><blockquote type=3D"cite"><div>I confidently predict the =
reclassification to Historic will be roundly ignored not just by Apple =
product engineering but by the entire industry. &nbsp;We're smart enough =
to recognize that we're not the target audience for the RFC. &nbsp;The =
draft that matters is the companion advisory draft. &nbsp;It would be =
nice if the 6to4-to-historic draft could be spiked so as not to distract =
from its companion, but I don't see that as a likely outcome. &nbsp;Alas =
and alack.</div></blockquote><br></div><div>Well, the most important =
point in this is that 6to4 is&nbsp;disabled by default in every device. =
&nbsp;Apple did that already, which is good.&nbsp;What is unclear to me =
though is whether deprecating 2002::/16 means that prefix would no =
longer be routed, as per 3ffe::/16, or just 'reserved' so it's not =
reallocated later.</div><div><br></div><div><div>On 9 Jun 2011, at =
19:53, Keith Moore wrote:</div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>On Jun 9, 2011, at =
2:45 PM, Lorenzo Colitti wrote:</div></div><div><blockquote =
type=3D"cite"><div class=3D"gmail_quote"><div>Go to&nbsp;<a =
href=3D"http://tunnelbroker.net/">http://tunnelbroker.net/</a>&nbsp;. =
I'm willing to bet that it will take a lot less time than you have spent =
writing email on this thread. =
:-)</div></div></blockquote></div><div>That's who I was using =
before.</div></div></blockquote><br></div><div>Our staff and students =
find the HE broker easy to use, though I believe some also use other =
brokers. &nbsp;One student did a final year project this year developing =
a Linux home router which included HE broker support. &nbsp;It was =
simple to use/integrate.</div><div><br></div><div><div>On 9 Jun 2011, at =
19:56, james woodyatt wrote:</div><blockquote type=3D"cite"><div>I need =
*native* IPv6 into my home in San Francisco for my day =
job<br></div></blockquote><div><br></div>Have you considered =
deploying/adding IPv6 VPN support at your day job? &nbsp;So your VPN =
from home to work gives you IPv4 and IPv6? &nbsp;This is quite a nice =
model, and is starting to appear in UK universities, and I use it myself =
for IPv6 training. At least one big vendor offers this today. Users are =
familiar with VPN use, so adding IPv6 with that comes naturally, and =
$dayjob provides the support, so you're in =
control.</div><div><br></div><div><blockquote =
type=3D"cite"><div>Meanwhile, 6to4 works fine on their network so long =
as remote IPv6 destinations have a working return path route to =
2002::/16, i.e. they are complying with I-D.ietf-v6ops-6to4-advisory =
now.</div></blockquote><br></div><div>That 'so long as' is the crux =
though.</div><div><br></div><div>Tim</div></div></body></html>=

--Apple-Mail-1-775898431--

From mrex@sap.com  Thu Jun  9 14:31:13 2011
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 3F55611E8142; Thu,  9 Jun 2011 14:31:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.337
X-Spam-Level: 
X-Spam-Status: No, score=-9.337 tagged_above=-999 required=5 tests=[AWL=0.913,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RWP44Ytajygo; Thu,  9 Jun 2011 14:31:12 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id E498B11E813A; Thu,  9 Jun 2011 14:31:11 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p59LV6T3023993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Jun 2011 23:31:06 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201106092131.p59LV5cZ003693@fs4113.wdf.sap.corp>
Subject: Re: [v6ops] Last Call:
To: gert@space.net (Gert Doering)
Date: Thu, 9 Jun 2011 23:31:05 +0200 (MEST)
In-Reply-To: <20110609151640.GQ45955@Space.Net> from "Gert Doering" at Jun 9, 11 05:16:40 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: gvandeve@cisco.com, ietf@ietf.org, moore@network-heretics.com, v6ops@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 Jun 2011 21:31:13 -0000

Gert Doering wrote:
> 
> On Thu, Jun 09, 2011 at 11:05:29AM -0400, Keith Moore wrote:
> > The best way to not rat-hole is just to drop the proposed action.  
> 
> One voice doesn't make it "consensus to drop".

In the IETF, that is supposed to be possible.

A single technical or procedural issue that is raised before or
during Last Call and not resolved precludes  IETF rough consensus.

intention behind this include (using words from rfc2418):
   good working group consensus about a bad design.

While the Tao (rfc-4677) is only informational, it seems to capture
the IETF spirit quite good:

   "We reject kings, presidents and voting.
   We believe in rough consensus and running code".

   The lack of formal voting has caused some very long delays for some
   proposals, but most IETF participants who have witnessed rough
   consensus after acrimonious debates feel that the delays often result
   in better protocols.  (And, if you think about it, how could you have
   "voting" in a group that anyone can join, and when it's impossible to
   count the participants?)  Rough consensus has been defined in many
   ways; a simple version is that it means that strongly held objections
   must be debated until most people are satisfied that these objections
   are wrong.

or look at rfc-4858, later parts of section 3.2, another Informational
but valuable document.

e.g. if an implementor raises an issue, one should carefully listen
and talk about it, even if it is just one single implementor.
The opposite, an implementor that does not see a problem is not
proof of anything (as we can see from regular interop problems
showing up only during interop tests).  Reading specs correctly
(and carefully) seems to be less common than is desirable.


The purpose of the discussion is to seperate issues of taste (where
significant majority decisions are OK) from technical&procedural
issues and resolving all of the latter categorie(s) or determining
technical issues to be out-of-scope.


WG chairs and ADs have a significant discretion, and I've seen it
happening that they got too personally involved, inducing a non-marginal
bias on the issue resolution process in situations where this was
unnecessary and not appropriate.  That may or may not result in
worse decision.  But it is conceived as unfair by those holding
the objections and a problem by itself because it regularly
taints other discussions on other work items.


-Martin

From ned+ietf@mauve.mrochek.com  Thu Jun  9 15:28:58 2011
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 A93591F0C50 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 15:28: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0AQlzeG2J5Df for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 15:28:57 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 9AA8F1F0C4A for <ietf@ietf.org>; Thu,  9 Jun 2011 15:28:57 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O2A8KVUAF400VYUB@mauve.mrochek.com> for ietf@ietf.org; Thu, 9 Jun 2011 15:28:33 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O28N39BBNK00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 9 Jun 2011 15:28:28 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O2A8KT5RZ600VHKR@mauve.mrochek.com>
Date: Thu, 09 Jun 2011 15:13:00 -0700 (PDT)
Subject: Re: one data point regarding native IPv6 support
In-reply-to: "Your message dated Thu, 09 Jun 2011 11:56:00 -0700" <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com>
To: james woodyatt <jhw@apple.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1307658339; i=@mrochek.com; bh=g+EHuGM3uU35583hS22ytJNpN71IJhIZIRc1VeJB8wo=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=SPcee7oM2bM29jHAujocFyCDvhJCYusR6Lh+tF3IZG+Il0bzvoX5wHp+6yYr4RYxJ RmLV7zOSQ1b0I4f+jtRcjQ9eDvkUv8Zwm37rnowH6mXoJ1Lbd10GZfnWM9DzP2aZPf 0JjYcSQqutSbbTLGPBpcGEQoC5J1UB+Tifk/ynCQ=
Cc: Keith Moore <moore@network-heretics.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 22:28:58 -0000

You folks have had it easy in your interactions with ISPs. When I tried not too
long ago with various ISPs in my area, I was unable to reach anyone at either
of the big ISPs who knew what "IPv6" even meant. Both promised callbacks,
neither did.

The more interesting response was from a small ISP. They knew exactly what I
was talking about, and told me (a) The IPv4 address shortage is nothing but a
"scare tactic", (b) They currently have no plans to offer IPv6, and (c) If they
ever did offer it "would only be with T1/T3 services, Colocation, and Managed
Servers and not DSL".

Those are verbatim quotes from their response.

And here's another data point, this time in the SOHO router space. My new
router is advertised as being "IPv6 ready", but the firmware it came with has
no IPv6 support whatsoever. When I contacted the vendor about this, I was
informed that I could get a special firmware build that supports IPv6, but it
would be an "as-is" thing based on an earlier release so there may be some loss
of functionality in other areas.

I then asked why they don't have support in their current product, I was told
it's because they are worried about their support staff being inundated with
questions and problems. Given the dearth of IPv6 support from other vendors in
this product area, I can't say I blame them.

Anyone who doesn't believe we have a major marketing problem here isn't paying
attention.

				Ned

From moore@network-heretics.com  Thu Jun  9 17:49:58 2011
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 AA0A21F0C34 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 17:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.303
X-Spam-Level: 
X-Spam-Status: No, score=-3.303 tagged_above=-999 required=5 tests=[AWL=0.296,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fWq8U-mryzBT for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 17:49:58 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id B0FB411E8076 for <ietf@ietf.org>; Thu,  9 Jun 2011 17:49:46 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 3C4882097D; Thu,  9 Jun 2011 20:49:46 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 09 Jun 2011 20:49:46 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=uoo7WiCDdpZimKvtGBomTXF5k/s=; b=sEuATtT0nyDoieMjmgEpIUvhVmV30Z4p8qnAciE3aBqHuZoa0TYBs9ArbmFZyE62x/aVQEE3U49d3sbVVCaxMnvU9xGWK+XP1NbDGt/h8YPtF1ywJ4mcSgGUGrnnNZE85E4/qkwMilhtN+Wam4l4Q0Ue+Mm757kxsR7LkoAw7vY=
X-Sasl-enc: nP81SKFbX2xTEWSbEFHns/oyMQ3tSvsfBgD6xuBKPWyv 1307666985
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 54CF14413A5; Thu,  9 Jun 2011 20:49:45 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
X-Priority: 3
In-Reply-To: <006d01cc26ca$ed74b600$6801a8c0@oemcomputer>
Date: Thu, 9 Jun 2011 20:49:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F7E4C3A-8912-40AC-BF8F-E4D171B6864E@network-heretics.com>
References: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu> <49D685CB-00FD-42E5-9AD8-15E51545D9A2@apple.com> <006601cc260c$4a0c87e0$6801a8c0@oemcomputer> <04A9F777-8C57-4120-9964-CEFFAF0DD7BE@free.fr> <006d01cc26ca$ed74b600$6801a8c0@oemcomputer>
To: Randy Presuhn <randy_presuhn@mindspring.com>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 00:49:58 -0000

On Jun 9, 2011, at 1:30 PM, Randy Presuhn wrote:

>>> I'm pretty sure Noel was being scarcastic.  There's clear precedent =
in the
>>> analogous case where RFC 1227 was  declared historic, despite its
>>> widespread use for that particular application at the time.
>>=20
>> RFC 1227 specified an experimental protocol.
>> The 6to4 specification is standard track.
>> Declaring historic a standard track specification although it still =
serves
>> legitimate needs would, AFAIK, be a precedent, a regrettable one =
IMHO.
>=20
> Consider, then, RFC 1157.
>=20
> It was, quite rightly, declared historic years ago, even though it
> was a full standard and in rather widespread use at the time.

Was there a replacement for RFC 1157 (presumably, a new version of SNMP) =
generally available at the time that document was moved to Historic?=20

I mean, it would make perfect sense to want to declare 1157 historic if =
there were a new version available that clearly worked better.  Right =
now, there's not a readily available replacement for 6to4 that is =
clearly better.

So I think the comparison is not valid.  SNMP (of whatever version) is a =
protocol that you can use on your own network if you want to, and that's =
where most of its utility is.  You don't have to get your ISP to support =
it before it's significantly useful to you.  By contrast, the very =
purpose of 6to4 is to communicate with peers over someone else's =
network(s).  If you want to run IPv6 over your own IPv4 network, 6rd or =
maybe 6over4 are better suited to that.

Keith


From marka@isc.org  Thu Jun  9 17:58:22 2011
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 4003011E80A3 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 17:58: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.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xzlhjGl3Kj9f for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 17:58: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 8F12D11E8076 for <ietf@ietf.org>; Thu,  9 Jun 2011 17:58: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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 019D95F98ED; Fri, 10 Jun 2011 00:58:04 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 4299A216C7B; Fri, 10 Jun 2011 00:58:02 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id BC2D110ABF81; Fri, 10 Jun 2011 10:57:58 +1000 (EST)
To: ned+ietf@mauve.mrochek.com
From: Mark Andrews <marka@isc.org>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com>
Subject: Re: one data point regarding native IPv6 support
In-reply-to: Your message of "Thu, 09 Jun 2011 15:13:00 MST." <01O2A8KT5RZ600VHKR@mauve.mrochek.com>
Date: Fri, 10 Jun 2011 10:57:58 +1000
Message-Id: <20110610005758.BC2D110ABF81@drugs.dv.isc.org>
Cc: IETF Discussion <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 00:58:22 -0000

And from Optus a similar response to a recent request.

Subject IPv6 support
Â 
Discussion ThreadÂ Response Via Email (Russell)
07/02/2011 02.04 PM
Dear Mark, 
Thank you for your email.

IPv6 deployment within Optus has not been broadly discussed.

At this point in time Optus has no immediate plans for implementation. 

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

From randy_presuhn@mindspring.com  Thu Jun  9 18:21:30 2011
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 A5EF921F8460 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 18:21:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.516
X-Spam-Level: 
X-Spam-Status: No, score=-101.516 tagged_above=-999 required=5 tests=[AWL=1.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id czPuU1Lyfn9J for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 18:21:29 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id 2C46F21F845F for <ietf@ietf.org>; Thu,  9 Jun 2011 18:21:28 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=OsEqg77lRpXkd3rj6jrAJCnUPr5b6rS5KsA4JbGQBaC7AlSEkLL19mujhn7Abgd9; 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.23.161.222] (helo=oemcomputer) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1QUqPf-0000t7-Hl for ietf@ietf.org; Thu, 09 Jun 2011 21:21:27 -0400
Message-ID: <000901cc270d$430ec000$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu> <49D685CB-00FD-42E5-9AD8-15E51545D9A2@apple.com> <006601cc260c$4a0c87e0$6801a8c0@oemcomputer> <04A9F777-8C57-4120-9964-CEFFAF0DD7BE@free.fr> <006d01cc26ca$ed74b600$6801a8c0@oemcomputer> <1F7E4C3A-8912-40AC-BF8F-E4D171B6864E@network-heretics.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
Date: Thu, 9 Jun 2011 18:25:18 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888cc964a8bf633b3827fb13d8416999686c2435cdbc1353bc9350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.23.161.222
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 01:21:30 -0000

Hi -

> From: "Keith Moore" <moore@network-heretics.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: <ietf@ietf.org>
> Sent: Thursday, June 09, 2011 5:49 PM
> Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
...
> > Consider, then, RFC 1157.
> > 
> > It was, quite rightly, declared historic years ago, even though it
> > was a full standard and in rather widespread use at the time.
>
> Was there a replacement for RFC 1157 (presumably, a new version
> of SNMP) generally available at the time that document was moved to Historic? 

Yes, with some arguments about "generally".

> I mean, it would make perfect sense to want to declare 1157 historic
> if there were a new version available that clearly worked better.  Right
> now, there's not a readily available replacement for 6to4 that is clearly better.
>
> So I think the comparison is not valid.  SNMP (of whatever version) is a
> protocol that you can use on your own network if you want to, and that's
> where most of its utility is.  You don't have to get your ISP to support it
> before it's significantly useful to you.  By contrast, the very purpose
> of 6to4 is to communicate with peers over someone else's network(s).
>  If you want to run IPv6 over your own IPv4 network, 6rd or maybe
> 6over4 are better suited to that.

There appears to be some dispute about whether the functionality of 6to4 is
really needed.  I take no sides in that part of the debate.

My comment was in response to the claim (which you have not made, AFAIK)
that it was inappropriate to declare a standards-track protocol historic while
still in widespread use, for reasonable interpretations of "widespread". 
I was making no claims about 6to4's (de)merits.

Your argument seems to be that the peculiar operational characteristics of 6to4
should give it additional immunity to being declared historic. I don't find that
argument persuasive.  The history of multiple protocols that have been
declared "historic" shows that vendors seem to care about that designation
only when it is convenient for them to do so.  Installed base, customer
demand, operational considerations and so on all trump whatever the IETF
might say about a "historic" protocol.  This works both ways: folks might
decide to kill something before it becomes historic, or support it long after.
We can't compel people to continue supporting it any more than we can
make them stop.  At most, we can give them (hopefully convincing) reasons
to change.  If the SNMP experience shows anything, it shows that even
that isn't enough.  For that reason, I find it amusing when others write of 
"killing" 6to4.  We don't have that kind of power.

Randy


From mohta@necom830.hpcl.titech.ac.jp  Thu Jun  9 18:49:02 2011
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 751F411E813F for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 18:49:02 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDIetxZSM3qL for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 18:49:02 -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 B191811E80AF for <ietf@ietf.org>; Thu,  9 Jun 2011 18:49:01 -0700 (PDT)
Received: (qmail 62081 invoked from network); 10 Jun 2011 01:55:18 -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; 10 Jun 2011 01:55:18 -0000
Message-ID: <4DF177B0.4080303@necom830.hpcl.titech.ac.jp>
Date: Fri, 10 Jun 2011 10:47:28 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com>
In-Reply-To: <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com>
Content-Type: text/plain; charset=ISO-2022-JP
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, 10 Jun 2011 01:49:02 -0000

james woodyatt wrote:

> I need *native* IPv6 into my home in San Francisco for my day job,

Really?

I wonder why some people are arguing against to kill 6to4 along
with IPv6.

						Masataka Ohta

From marka@isc.org  Thu Jun  9 18:59:57 2011
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 D454111E80CD for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 18:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79unD+2XfHUd for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 18:59:54 -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 F100B11E8073 for <ietf@ietf.org>; Thu,  9 Jun 2011 18:59:44 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 40C2EC94B8; Fri, 10 Jun 2011 01:59:35 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 D1974216C80; Fri, 10 Jun 2011 01:59:34 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 437AF10AD2E7; Fri, 10 Jun 2011 11:59:31 +1000 (EST)
To: "Randy Presuhn" <randy_presuhn@mindspring.com>
From: Mark Andrews <marka@isc.org>
References: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu> <49D685CB-00FD-42E5-9AD8-15E51545D9A2@apple.com> <006601cc260c$4a0c87e0$6801a8c0@oemcomputer> <04A9F777-8C57-4120-9964-CEFFAF0DD7BE@free.fr> <006d01cc26ca$ed74b600$6801a8c0@oemcomputer> <1F7E4C3A-8912-40AC-BF8F-E4D171B6864E@network-heretics.com> <000901cc270d$430ec000$6801a8c0@oemcomputer>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
In-reply-to: Your message of "Thu, 09 Jun 2011 18:25:18 MST." <000901cc270d$430ec000$6801a8c0@oemcomputer>
Date: Fri, 10 Jun 2011 11:59:31 +1000
Message-Id: <20110610015931.437AF10AD2E7@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: Fri, 10 Jun 2011 01:59:58 -0000

In message <000901cc270d$430ec000$6801a8c0@oemcomputer>, "Randy Presuhn" writes
:
> We can't compel people to continue supporting it any more than we can
> make them stop.  At most, we can give them (hopefully convincing) reasons
> to change.  If the SNMP experience shows anything, it shows that even
> that isn't enough.  For that reason, I find it amusing when others write of 
> "killing" 6to4.  We don't have that kind of power.

But you can give them a big excuse not to support it.

Customer: "Where did the 6to4 support go?"
Vendor: "The IETF declared it historic so we removed it."
Customer: "I was using it, can you put it back?"
Vendor: "I repeat the IETF declared it historic."

6to4 on by default is wrong. 

However if a user/site turns 6to4 on they do that with the full
knowledge that it will add delays and it does use third party relays.
As to those that say users won't accept 100ms delays many actually
will accept the delay and it does not impact on what they do. The
tunnel I use adds +300ms to some IPv6 sites compared to IPv4 but
unless I explicitly measure it I don't notice it.

Making 6to4 historic is a knee jerk reaction to a bad default setting.
Fix the default.  Don't make 6to4 historic.

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

From mrex@sap.com  Thu Jun  9 19:40:49 2011
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 AA17411E813D for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 19:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.397
X-Spam-Level: 
X-Spam-Status: No, score=-9.397 tagged_above=-999 required=5 tests=[AWL=0.852,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AEQZQy2Odsku for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 19:40:49 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id C640B11E8150 for <ietf@ietf.org>; Thu,  9 Jun 2011 19:40:47 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p5A2ej42005860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 10 Jun 2011 04:40:46 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201106100240.p5A2ejRj021475@fs4113.wdf.sap.corp>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
To: marka@isc.org (Mark Andrews)
Date: Fri, 10 Jun 2011 04:40:45 +0200 (MEST)
In-Reply-To: <20110610015931.437AF10AD2E7@drugs.dv.isc.org> from "Mark Andrews" at Jun 10, 11 11:59:31 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: randy_presuhn@mindspring.com, 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: Fri, 10 Jun 2011 02:40:49 -0000

Mark Andrews wrote:
> 
> In message "Randy Presuhn" writes:
> >
> > We can't compel people to continue supporting it any more than we can
> > make them stop.  At most, we can give them (hopefully convincing) reasons
> > to change.  If the SNMP experience shows anything, it shows that even
> > that isn't enough.  For that reason, I find it amusing when others write of 
> > "killing" 6to4.  We don't have that kind of power.
> 
> But you can give them a big excuse not to support it.
> 
> Customer: "Where did the 6to4 support go?"
> Vendor: "The IETF declared it historic so we removed it."

> Vendor: "I repeat the IETF declared it historic."
> 
> 6to4 on by default is wrong. 
> 
> Making 6to4 historic is a knee jerk reaction to a bad default setting.
> Fix the default.  Don't make 6to4 historic.

I fully agree about your description of the purpose of "historic"
for vendor and its usage by vendors.

The only sensible use of historic is to promote active de-support
on the part of vendors -- literally for "ripping things out".


I just did that myself 4 weeks ago, justifying the complete removal
of support for MD2-based digital signatures from our PKI software
with a pointer to

  http://tools.ietf.org/html/rfc6149   "MD2 to Historic Status"

Moving 6to4 seems premature by several years.

-Martin

From michel@arneill-py.sacramento.ca.us  Thu Jun  9 20:38:41 2011
Return-Path: <michel@arneill-py.sacramento.ca.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 7DEC111E8096 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 20:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZEWkAuY3pa7i for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 20:38:41 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [69.12.226.219]) by ietfa.amsl.com (Postfix) with ESMTP id C96CF11E8076 for <ietf@ietf.org>; Thu,  9 Jun 2011 20:38:40 -0700 (PDT)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: one data point regarding native IPv6 support
Date: Thu, 9 Jun 2011 20:38:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local>
In-Reply-To: <20110610005758.BC2D110ABF81@drugs.dv.isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: one data point regarding native IPv6 support
Thread-Index: AcwnCYAV3hDXGO8IQU+mc/djkc+6AwADnaMg
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com><BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com><01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Mark Andrews" <marka@isc.org>, <ned+ietf@mauve.mrochek.com>
Cc: IETF Discussion <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 03:38:41 -0000

> Keith Moore wrote:
> ... when the support people for a fairly well-established telco
> haven't even heard of IPv6, it's hard to believe that it's going
> to be available anytime soon.

> [multiple people essentially reporting the same]
> At this point in time $ISP has no immediate plans for implementation.

I would say it's about time reality finally settles in.


> Keith Moore wrote:
> Meanwhile, 6to4 continues to work just fine for me.
> So please explain again why it isn't premature to
> discourage a valuable transition mechanism?

On that one I agree with Keith; where's the rush? Although imperfect,
6to4 was an obvious path and its demise would be the failure of the
IETF, following a long list of things that have been killed prematurely.


> Ned wrote:
> Anyone who doesn't believe we have a major marketing
> problem here isn't paying attention.

Hmm that is a point of view. You think you have a solution (IPv6) to
what you perceive to be a problem (shortage of IPv4 addresses).

However, some ISPs (and some other companies) do not consider it a
problem, but a blessing. What the IPv4 shortage does is that it prevents
new large players to enter the field, while allowing existing players to
continue to do business as usual.

As the shortage as been predicted for a decade, some (not all) have
stockpiled addresses and are now reaping the benefits. In business, this
situation is worth solid gold: it's called a monopoly. I'm fat and
happy, and I want it to continue. In this case, it's even better:
companies who benefit from it can argue that they are not the ones who
created the monopoly, it was a built-in limitation of the system as
created.

Some may not like the parallel, but we have failed the IPv6 migration
the same way we have failed the war on drugs. A while ago, there was
this thing called the Tier-1 cartel. As originally designed, a very
elusive club, with almost no way in and absolutely no tears when a
member gets de-peered.

Some have said that the cartel has failed as a system (due to a large
number of multilateral peering agreements and other factors). But now
what we have is a much larger number of largely unorganized but sharing
the same goals entities: those who already have IPv4 addresses. It's
even worse.

When a resource becomes scare or limited, the big picture is not how
much of it is available, or how much it costs. The big picture is how
much of the market one does control. Now we are in the situation where
everyone and their sister own a piece of the pie, and as long as the
price of the pie keeps going up, they're going to cling to it.

=20
On top of the marketing problem you mentioned, you have a bigger one:
there are many, many organizations out there that, even if you paid them
to deploy IPv6, would not. Because IPv6 is a territorial threat to them.

While the new or wannabe players would like the extra address space, the
sad truth is that the already establish players don't like newly open
spaces and prefer the territory control that comes with owning a piece
of a limited land space.

Michel.


From narten@us.ibm.com  Thu Jun  9 21:53:15 2011
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 0041411E80BB for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 21:53:14 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tLbnMSq8V7YA for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 21:53:13 -0700 (PDT)
Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) by ietfa.amsl.com (Postfix) with ESMTP id 4403911E8078 for <ietf@ietf.org>; Thu,  9 Jun 2011 21:53:11 -0700 (PDT)
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by e35.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p5A4ZKsK011481 for <ietf@ietf.org>; Thu, 9 Jun 2011 22:35:20 -0600
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p5A4r45a356434 for <ietf@ietf.org>; Thu, 9 Jun 2011 22:53:04 -0600
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 p5A4r3km024698 for <ietf@ietf.org>; Thu, 9 Jun 2011 22:53:03 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.176.22]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p5A4r3P3024686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 9 Jun 2011 22:53:03 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p5A4r2nn007984 for <ietf@ietf.org>; Fri, 10 Jun 2011 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p5A4r2B7007960 for ietf@ietf.org; Fri, 10 Jun 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201106100453.p5A4r2B7007960@rotala.raleigh.ibm.com>
Date: Fri, 10 Jun 2011 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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 04:53:15 -0000

Total of 129 messages in the last 7 days.
 
script run at: Fri Jun 10 00:53:02 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 17.05% |   22 | 29.39% |   331489 | moore@network-heretics.com
  3.10% |    4 |  6.83% |    77083 | wesley.george@twcable.com
  4.65% |    6 |  3.56% |    40198 | alexey.melnikov@isode.com
  3.88% |    5 |  2.51% |    28274 | john-ietf@jck.com
  3.88% |    5 |  2.20% |    24760 | mrex@sap.com
  3.10% |    4 |  2.94% |    33207 | trejrco@gmail.com
  3.10% |    4 |  2.25% |    25365 | brian.e.carpenter@gmail.com
  3.10% |    4 |  2.23% |    25112 | jhw@apple.com
  3.10% |    4 |  2.14% |    24158 | randy_presuhn@mindspring.com
  3.10% |    4 |  2.00% |    22568 | paul.hoffman@vpnc.org
  3.10% |    4 |  2.00% |    22513 | marka@isc.org
  2.33% |    3 |  2.59% |    29221 | scottr.nist@gmail.com
  2.33% |    3 |  2.42% |    27317 | tjc@ecs.soton.ac.uk
  2.33% |    3 |  1.98% |    22320 | joelja@bogus.com
  2.33% |    3 |  1.97% |    22250 | ben@nostrum.com
  2.33% |    3 |  1.38% |    15605 | gert@space.net
  1.55% |    2 |  1.81% |    20447 | presnick@qualcomm.com
  1.55% |    2 |  1.48% |    16650 | evnikita2@gmail.com
  0.78% |    1 |  2.08% |    23517 | stpeter@stpeter.im
  1.55% |    2 |  1.29% |    14592 | ron.even.tlv@gmail.com
  1.55% |    2 |  1.23% |    13841 | nishida@sfc.wide.ad.jp
  1.55% |    2 |  1.01% |    11338 | barryleiba@computer.org
  1.55% |    2 |  0.98% |    11071 | krishnabirth@gmail.com
  1.55% |    2 |  0.80% |     9015 | msk@cloudmark.com
  1.55% |    2 |  0.66% |     7400 | jnc@mercury.lcs.mit.edu
  0.78% |    1 |  1.20% |    13489 | yaronf.ietf@gmail.com
  0.78% |    1 |  1.11% |    12553 | lars.eggert@nokia.com
  0.78% |    1 |  1.09% |    12284 | vint@google.com
  0.78% |    1 |  1.03% |    11611 | jari.arkko@piuha.net
  0.78% |    1 |  0.86% |     9672 | yaojk@cnnic.cn
  0.78% |    1 |  0.82% |     9232 | mail@sabahattin-gucukoglu.com
  0.78% |    1 |  0.82% |     9230 | otroan@employees.org
  0.78% |    1 |  0.78% |     8810 | fernando@gont.com.ar
  0.78% |    1 |  0.75% |     8504 | cb.list6@gmail.com
  0.78% |    1 |  0.72% |     8129 | gvandeve@cisco.com
  0.78% |    1 |  0.67% |     7575 | kathleen.moriarty@emc.com
  0.78% |    1 |  0.65% |     7345 | yoshihiro.ohba@toshiba.co.jp
  0.78% |    1 |  0.63% |     7082 | rogerj@gmail.com
  0.78% |    1 |  0.62% |     7029 | fred@cisco.com
  0.78% |    1 |  0.61% |     6902 | michel@arneill-py.sacramento.ca.us
  0.78% |    1 |  0.61% |     6900 | dave@cridland.net
  0.78% |    1 |  0.61% |     6897 | alexandru.petrescu@gmail.com
  0.78% |    1 |  0.59% |     6686 | huitema@microsoft.com
  0.78% |    1 |  0.58% |     6548 | narten@us.ibm.com
  0.78% |    1 |  0.56% |     6278 | pch-v6ops@u-1.phicoh.com
  0.78% |    1 |  0.52% |     5916 | rdroms.ietf@gmail.com
  0.78% |    1 |  0.52% |     5869 | dmitry.anipko@microsoft.com
  0.78% |    1 |  0.50% |     5657 | ned+ietf@mauve.mrochek.com
  0.78% |    1 |  0.48% |     5373 | housley@vigilsec.com
  0.78% |    1 |  0.47% |     5292 | ajs@anvilwalrusden.com
  0.78% |    1 |  0.46% |     5181 | iljitsch@muada.com
  0.78% |    1 |  0.44% |     4981 | johnl@iecc.com
  0.78% |    1 |  0.42% |     4714 | cheshire@apple.com
  0.78% |    1 |  0.41% |     4634 | dlb@interlinux.org.uk
  0.78% |    1 |  0.38% |     4308 | bortzmeyer@nic.fr
  0.78% |    1 |  0.35% |     3941 | mohta@necom830.hpcl.titech.ac.jp
--------+------+--------+----------+------------------------
100.00% |  129 |100.00% |  1127933 | Total

From hsantos@isdg.net  Thu Jun  9 22:34:52 2011
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 A182021F84FB for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 22:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.284
X-Spam-Level: 
X-Spam-Status: No, score=-2.284 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GkKcb1QS5xZj for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 22:34:51 -0700 (PDT)
Received: from secure.winserver.com (dkim.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 079C621F84FA for <ietf@ietf.org>; Thu,  9 Jun 2011 22:34:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=isdg.net; s=tms1; l=3938; t=1307684087; h=Message-ID:Date:From:Organization:To: Subject; bh=nk2PokIsV/EQK2PJBNKLJeIYSrE=; b=rAmRT6fbyODf7gQJ32tM b2mzha+HRr1I3QDkUUw72S5iUJ2EWDh5l+m/wOLtlBT9U/682IgvdyY+FawK+kHT RoVdzF9+wzkTS6xiu363Y94tZ3KKjFf1oj1XqDNh21vYukk5+9C9K3FchTCZx/nN 6IHoV0igdiJN48AMdndFWLs=
Received: by winserver.com (Wildcat! SMTP Router v6.3.453.5) for ietf@ietf.org; Fri, 10 Jun 2011 01:34:47 -0400
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.3.453.5) with ESMTP id 434593126.9781.2636; Fri, 10 Jun 2011 01:34:46 -0400
Received: by beta.winserver.com (Wildcat! SMTP Router v6.3.453.2) for ietf@ietf.org; Fri, 10 Jun 2011 01:31:41 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.3.453.2) with ESMTP id 1405907548; Fri, 10 Jun 2011 01:31:41 -0400
Message-ID: <4DF1AD04.2090402@isdg.net>
Date: Fri, 10 Jun 2011 01:35:00 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>
In-Reply-To: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 05:34:52 -0000

Unless you are elevated to higher level networking people who are 
normally not part of the support process, what 1st/2nd support feeds 
end-users should be taken very lightly.

This is all very simple - economics.  Its not just about end-users, 
but major operations who are IPv4 dependent and as scary it may sound, 
its going probably going to take some major conjones, i.e. arm 
twisting and an act by congress similar to HDTV to force "everyone" to 
switch by so and so date, which is the only way the IPS (Telecos) will 
break business contracts with their business tiers.  Its more 
complicated than people having legacy TVs and wires to it.  We are 
talking major operations for millions of companies, small to large, 
who simply can't "afford" to close the door on IPv4.

I personally understand the draft's attempt to begin "closing" the 
mentality of sticking with IPv4.  As long as there a fallback, the 
urgency to move towards IPv6 is minimized.   At some point, some hard 
decisions will need to be made. Which takes be back to the HDTV 
analogy - only a government mandate made that happen.   But its not 
the same because its not just a relative few networks or broadband 
providers, but there are many software vendors, free, commercial or 
otherwise that need to change their software across the board; SMTP, 
FTP, NNTP, IMAP, POP3 etc.

The bottom line: unless I am force to support IPv6, stack or no stack, 
the investment required isn't going to happen soon.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com

Keith Moore wrote:
> I just called my ISP to ask about availability of IPv6 at my home.
> 
> Me:  "I'm a current customer, and I'm just calling to ask if you support Internet Protocol Version 6."
> 
> First person: "Yes, we do support Internet.  We support DSL at 3 megabits and 6 megabits."
> 
> Me: "I understand that, but I'm asking about Internet Protocol version 6, IPv6.  The Internet has been using IP version 4 since the early 1980s, but that's running out.  IPv6 is the new version."
> 
> First person: "Let me transfer you to support."
> 
> Second person: "Hi, this is support.  How may I help you?"
> 
> Me: "I'm a current customer, and I'm just calling to ask if you support Internet Protocol Version 6."
> 
> Second person: "IP version what?"
> 
> Me: "Internet protocol version 6".
> 
> Second person: "I have no idea.  Let me transfer you to someone else."
> 
> (places me on hold for 15 minutes)
> 
> Second person: "I'm sorry for the wait time.  I've been trying to find the answer to your question, but nobody here seems to know anything about it.  We're trying to get in touch with people who run the network to ask them.   Can I get your number and call you back?"
> 
> Granted, this is just one ISP.  The other ISP that offers service in my area put me on hold for an hour and a half *before anyone ever talked to me* when I tried to get a quote from them, so I concluded that they wouldn't be a good choice.  And these guys have been good about support in general.  They seem to know their stuff, which is more than I can say for some ISPs I've dealt with in the past.
> 
> I live in a well-settled urban area, three miles from the center of the city (and sadly, four miles from my CO, which means my DSL circuit gets around 380kbits/sec).  It's not a backwater, there's plenty of lit fiber running through town.  But when the support people for a fairly well-established telco haven't even heard of IPv6, it's hard to believe that it's going to be available anytime soon.
> 
> Meanwhile, 6to4 continues to work just fine for me.
> 
> So please explain again why it isn't premature to discourage a valuable transition mechanism?
> 
> Keith
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 





From rogerj@gmail.com  Thu Jun  9 23:15:18 2011
Return-Path: <rogerj@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E036A11E80A1 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 23:15:18 -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.600,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qi7oRYKMRjuq for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 23:15:17 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id B2D1011E80A0 for <ietf@ietf.org>; Thu,  9 Jun 2011 23:15:16 -0700 (PDT)
Received: by wyb29 with SMTP id 29so1819156wyb.31 for <ietf@ietf.org>; Thu, 09 Jun 2011 23:15:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=acd1dSQBXrVVLzgfce7xPFOGRXi3gjgl/peoW03vhtI=; b=BPGy5CYAP0nWzioLpeDULuQVcvLxTUQwajYSn928HwYcrlbx9Basyftz5xDfffMHv9 GzmWc+1mfyRGTyBPH5x1jnNWxP5zKFGfpQ5vvjbQ8ZY/HJEHcXqiOoexYKRXNLdPj3d9 zkG0JmtmslzCN2izEwpLT56PlkrHCGCejPi9M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=XHV27G2RLci4/KO6xUZ3ApBjdXD3muQdMIuM+OWmkNceI6oMvq3Vl8OfFWSmAW6nai eMhxMWGdX4Zc9t2PK1czMydrNqSaFHsdrviO7wq64PKZf4RmyjM6KfeYBj9+4BqmKvSO 9Ir6idJyO0j+Mh/59d97a4NCHMD8bePvaxEiE=
MIME-Version: 1.0
Received: by 10.227.199.19 with SMTP id eq19mr1705340wbb.75.1307686515428; Thu, 09 Jun 2011 23:15:15 -0700 (PDT)
Received: by 10.227.132.142 with HTTP; Thu, 9 Jun 2011 23:15:15 -0700 (PDT)
In-Reply-To: <4DF1AD04.2090402@isdg.net>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <4DF1AD04.2090402@isdg.net>
Date: Fri, 10 Jun 2011 08:15:15 +0200
Message-ID: <BANLkTindzHSXX_4KZe4O_VT+X4jrN=pB-Q@mail.gmail.com>
Subject: Re: one data point regarding native IPv6 support
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Hector Santos <hsantos@isdg.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 06:15:19 -0000

On Fri, Jun 10, 2011 at 7:35 AM, Hector Santos <hsantos@isdg.net> wrote:
<snip>
> The bottom line: unless I am force to support IPv6, stack or no stack, th=
e
> investment required isn't going to happen soon.

You got an options now, how, when and where you want to go with IPv6,
wait a few years until all you communicate with in Asia demand IPv6
connectivity, it's the only way to reach them.

and it isn't that hard, just make sure all equipment you buy/invest
into now can or have a plan to support IPv6, if you start with it now,
or started with it ~2-3 years ago you are pretty much safe.
(not all edge equipment are ready at that time but that's another story rea=
lly)


--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From stefan.winter@restena.lu  Thu Jun  9 23:33:00 2011
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7D9621F853E for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 23:33: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]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cp5s11S4EbEm for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 23:33:00 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 0318521F853C for <ietf@ietf.org>; Thu,  9 Jun 2011 23:32:59 -0700 (PDT)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id A0FF310590 for <ietf@ietf.org>; Fri, 10 Jun 2011 08:32:55 +0200 (CEST)
Received: from [IPv6:2001:a18:1:8::155] (unknown [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 631BC10582 for <ietf@ietf.org>; Fri, 10 Jun 2011 08:32:55 +0200 (CEST)
Message-ID: <4DF1BA93.5070105@restena.lu>
Date: Fri, 10 Jun 2011 08:32:51 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com><BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com><01O2A8KT5RZ600VHKR@mauve.mrochek.com>	<20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5501663B17FE80CA4ACF9E5B"
X-Virus-Scanned: ClamAV
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 06:33:01 -0000

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

Hi,

>> ... when the support people for a fairly well-established telco
>> haven't even heard of IPv6, it's hard to believe that it's going
>> to be available anytime soon.
>> [multiple people essentially reporting the same]
>> At this point in time $ISP has no immediate plans for implementation.
> I would say it's about time reality finally settles in.

My reality is that I switched to an ISP who openly announced native IPv6
support in their offering in 2007. Up and running since then, and when I
had trouble setting up the IPCP+IP6CP in the same PPP channel in IOS, I
wrote them an email on a Saturday, and got a config snippet back an hour
later, as part of their standard customer service. That ISP operates
nation-wide and uses IPv6 as a marketing instrument to get techies to
subscribe. For a price of converted 15 USD per month. That's in Germany
though. Apparently, realities differ depending on where you are.

Greetings,

Stefan Winter

>
>> Keith Moore wrote:
>> Meanwhile, 6to4 continues to work just fine for me.
>> So please explain again why it isn't premature to
>> discourage a valuable transition mechanism?
> On that one I agree with Keith; where's the rush? Although imperfect,
> 6to4 was an obvious path and its demise would be the failure of the
> IETF, following a long list of things that have been killed prematurely=
=2E
>
>
>> Ned wrote:
>> Anyone who doesn't believe we have a major marketing
>> problem here isn't paying attention.
> Hmm that is a point of view. You think you have a solution (IPv6) to
> what you perceive to be a problem (shortage of IPv4 addresses).
>
> However, some ISPs (and some other companies) do not consider it a
> problem, but a blessing. What the IPv4 shortage does is that it prevent=
s
> new large players to enter the field, while allowing existing players t=
o
> continue to do business as usual.
>
> As the shortage as been predicted for a decade, some (not all) have
> stockpiled addresses and are now reaping the benefits. In business, thi=
s
> situation is worth solid gold: it's called a monopoly. I'm fat and
> happy, and I want it to continue. In this case, it's even better:
> companies who benefit from it can argue that they are not the ones who
> created the monopoly, it was a built-in limitation of the system as
> created.
>
> Some may not like the parallel, but we have failed the IPv6 migration
> the same way we have failed the war on drugs. A while ago, there was
> this thing called the Tier-1 cartel. As originally designed, a very
> elusive club, with almost no way in and absolutely no tears when a
> member gets de-peered.
>
> Some have said that the cartel has failed as a system (due to a large
> number of multilateral peering agreements and other factors). But now
> what we have is a much larger number of largely unorganized but sharing=

> the same goals entities: those who already have IPv4 addresses. It's
> even worse.
>
> When a resource becomes scare or limited, the big picture is not how
> much of it is available, or how much it costs. The big picture is how
> much of the market one does control. Now we are in the situation where
> everyone and their sister own a piece of the pie, and as long as the
> price of the pie keeps going up, they're going to cling to it.
>
> =20
> On top of the marketing problem you mentioned, you have a bigger one:
> there are many, many organizations out there that, even if you paid the=
m
> to deploy IPv6, would not. Because IPv6 is a territorial threat to them=
=2E
>
> While the new or wannabe players would like the extra address space, th=
e
> sad truth is that the already establish players don't like newly open
> spaces and prefer the territory control that comes with owning a piece
> of a limited land space.
>
> Michel.
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473



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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3xupcACgkQ+jm90f8eFWYh+QCeJEvfvXQN/wg8rCuVRXUQQeeE
xE8An20Zqf1aSdNElFm3KxlaWLh+Fju2
=nH67
-----END PGP SIGNATURE-----

--------------enig5501663B17FE80CA4ACF9E5B--

From mail@sabahattin-gucukoglu.com  Fri Jun 10 00:49:05 2011
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDB3D11E80A9 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 00:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.962
X-Spam-Level: 
X-Spam-Status: No, score=0.962 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HOST_MISMATCH_COM=0.311, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7tqWrjBNOM3v for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 00:49:05 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com (sgucukoglu-2-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:7ef::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8CDD811E809E for <ietf@ietf.org>; Fri, 10 Jun 2011 00:49:03 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:42301) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S35DB5> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Fri, 10 Jun 2011 08:49:00 +0100
Received: from [192.168.1.20] (cpc2-dals7-0-0-cust570.hari.cable.virginmedia.com [82.35.114.59]) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Fri, 10 Jun 2011 08:48:59 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: one data point regarding native IPv6 support
In-Reply-To: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>
Date: Fri, 10 Jun 2011 08:48:57 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C55A72CD-091E-4484-848C-78C37C20BD68@sabahattin-gucukoglu.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-Delivery-Agent: TMDA/1.1.12-kg3 (Haumea)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1310284140.4d8a77@sabahattin-gucukoglu.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, 10 Jun 2011 07:49:05 -0000

The situation in the UK appears similar to the US, with the exception of =
some really tech-friendly, passionate and clueful ISPs: either flat-out =
denial that IPv6 is important, in the smaller and well-off case, or else =
complete cluelessness, in the larger case.  For larger ISPs, especially =
the resident cable pigopolist, you have to go to their user support =
forums to read the staff opinion, i.e., IPv6 is alarmist tripe and it'll =
wait, no plans to support, etc.  My personal opinion is that they are =
simply afraid; they have too much invested in a young market, and now =
they're overpowered by the changes required, but without progress made =
or anticipated, it's a vicious circle, with investors in the lead.

Cheers,
Sabahattin

From otuenehoj@gmail.com  Fri Jun 10 00:51:10 2011
Return-Path: <otuenehoj@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B58A011E809E for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 00:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.732
X-Spam-Level: 
X-Spam-Status: No, score=-2.732 tagged_above=-999 required=5 tests=[AWL=0.866,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XFhL3VfRemvh for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 00:51:09 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1B67911E8070 for <ietf@ietf.org>; Fri, 10 Jun 2011 00:51:09 -0700 (PDT)
Received: by iwn39 with SMTP id 39so2642319iwn.31 for <ietf@ietf.org>; Fri, 10 Jun 2011 00:51:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=1gMpHoAfH92n/7pTpeLi8UZ8AKqE2+UwNUJQXc8PoUc=; b=vOshZvc3gT62AXE0UVRm+eC7t/ILA6OyLJa2PRXvl+ekdthU6jz2gu3EdPO/rqDAaF 83+dUQ0rqK/3tjRpOuOYMbnnq5Xc/ZC9gMQOiE9ldz052Edaa9zzRheymJMOdcczsqXz NtBZ6JFzB0z0+Yp+Q9cao9RARC3ck9QOIRQlw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LP0EzuLKJKXPGmd3lLoybD+gfaUhj54aDUxr0h+bbm1RJongBNeMC43XewEzmwjlXl ZEdQfyKfx8F+XS/zfPZzDPVn4/HiEzsXKD4+x+SxtrZiyjKkQQVYLbT2e0oRlvNdwnu+ 18iEhUmyWCWeUzVIxdde8bZFacmN+O8Yjd2mI=
MIME-Version: 1.0
Received: by 10.231.122.30 with SMTP id j30mr2263906ibr.37.1307692268786; Fri, 10 Jun 2011 00:51:08 -0700 (PDT)
Received: by 10.231.5.147 with HTTP; Fri, 10 Jun 2011 00:51:08 -0700 (PDT)
In-Reply-To: <4DF1BA93.5070105@restena.lu>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF1BA93.5070105@restena.lu>
Date: Fri, 10 Jun 2011 08:51:08 +0100
Message-ID: <BANLkTinJSLjbqxM-OzLN-JOK3==3rRgiOA@mail.gmail.com>
Subject: Re: one data point regarding native IPv6 support
From: otunte otueneh <otuenehoj@gmail.com>
To: Stefan Winter <stefan.winter@restena.lu>
Content-Type: multipart/alternative; boundary=0016e6471a2c2813a304a556d58b
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 07:51:10 -0000

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

Hello all,

I visited *http://www.worldipv6day.org/* which is an Internet Society
website and clicked on *test* which took me to http://test-ipv6.com/# to do
a test online for IPv6.

When *http://test-ipv6.com/#*  opened for me to run a test, part of the
results says:
"You appear to be able to browse the IPv4 Internet only. You will not be
able to reach IPv6-only sites."

Please can some one visit http://test-ipv6.com/# and give me more
explanation on the displayed result?

Kind regards,

Otunte Otueneh
ISOC Nigeria Chapter


On Fri, Jun 10, 2011 at 7:32 AM, Stefan Winter <stefan.winter@restena.lu>wr=
ote:

> Hi,
>
> >> ... when the support people for a fairly well-established telco
> >> haven't even heard of IPv6, it's hard to believe that it's going
> >> to be available anytime soon.
> >> [multiple people essentially reporting the same]
> >> At this point in time $ISP has no immediate plans for implementation.
> > I would say it's about time reality finally settles in.
>
> My reality is that I switched to an ISP who openly announced native IPv6
> support in their offering in 2007. Up and running since then, and when I
> had trouble setting up the IPCP+IP6CP in the same PPP channel in IOS, I
> wrote them an email on a Saturday, and got a config snippet back an hour
> later, as part of their standard customer service. That ISP operates
> nation-wide and uses IPv6 as a marketing instrument to get techies to
> subscribe. For a price of converted 15 USD per month. That's in Germany
> though. Apparently, realities differ depending on where you are.
>
> Greetings,
>
> Stefan Winter
>
> >
> >> Keith Moore wrote:
> >> Meanwhile, 6to4 continues to work just fine for me.
> >> So please explain again why it isn't premature to
> >> discourage a valuable transition mechanism?
> > On that one I agree with Keith; where's the rush? Although imperfect,
> > 6to4 was an obvious path and its demise would be the failure of the
> > IETF, following a long list of things that have been killed prematurely=
.
> >
> >
> >> Ned wrote:
> >> Anyone who doesn't believe we have a major marketing
> >> problem here isn't paying attention.
> > Hmm that is a point of view. You think you have a solution (IPv6) to
> > what you perceive to be a problem (shortage of IPv4 addresses).
> >
> > However, some ISPs (and some other companies) do not consider it a
> > problem, but a blessing. What the IPv4 shortage does is that it prevent=
s
> > new large players to enter the field, while allowing existing players t=
o
> > continue to do business as usual.
> >
> > As the shortage as been predicted for a decade, some (not all) have
> > stockpiled addresses and are now reaping the benefits. In business, thi=
s
> > situation is worth solid gold: it's called a monopoly. I'm fat and
> > happy, and I want it to continue. In this case, it's even better:
> > companies who benefit from it can argue that they are not the ones who
> > created the monopoly, it was a built-in limitation of the system as
> > created.
> >
> > Some may not like the parallel, but we have failed the IPv6 migration
> > the same way we have failed the war on drugs. A while ago, there was
> > this thing called the Tier-1 cartel. As originally designed, a very
> > elusive club, with almost no way in and absolutely no tears when a
> > member gets de-peered.
> >
> > Some have said that the cartel has failed as a system (due to a large
> > number of multilateral peering agreements and other factors). But now
> > what we have is a much larger number of largely unorganized but sharing
> > the same goals entities: those who already have IPv4 addresses. It's
> > even worse.
> >
> > When a resource becomes scare or limited, the big picture is not how
> > much of it is available, or how much it costs. The big picture is how
> > much of the market one does control. Now we are in the situation where
> > everyone and their sister own a piece of the pie, and as long as the
> > price of the pie keeps going up, they're going to cling to it.
> >
> >
> > On top of the marketing problem you mentioned, you have a bigger one:
> > there are many, many organizations out there that, even if you paid the=
m
> > to deploy IPv6, would not. Because IPv6 is a territorial threat to them=
.
> >
> > While the new or wannabe players would like the extra address space, th=
e
> > sad truth is that the already establish players don't like newly open
> > spaces and prefer the territory control that comes with owning a piece
> > of a limited land space.
> >
> > Michel.
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>
>
> --
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et de
> la Recherche
> 6, rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>
> Tel: +352 424409 1
> Fax: +352 422473
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>

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

Hello all, <br><br>I visited <b><a href=3D"http://www.worldipv6day.org/">ht=
tp://www.worldipv6day.org/</a></b> which is an Internet Society website and=
 clicked on <b>test</b> which took me to <a href=3D"http://test-ipv6.com/#"=
>http://test-ipv6.com/#</a> to do a test online for IPv6.<br>
<br>When <b><a href=3D"http://test-ipv6.com/#">http://test-ipv6.com/#</a></=
b>=A0 opened for me to run a test, part of the results says:<br>&quot;You a=
ppear to be able to browse the IPv4 Internet only.  You will not be able to=
 reach IPv6-only sites.&quot;<br>
<br>Please can some one visit <a href=3D"http://test-ipv6.com/#">http://tes=
t-ipv6.com/#</a> and give me more explanation on the displayed result?<br><=
br>Kind regards,<br><br>Otunte Otueneh<br>ISOC Nigeria Chapter<br><br><br>
<div class=3D"gmail_quote">On Fri, Jun 10, 2011 at 7:32 AM, Stefan Winter <=
span dir=3D"ltr">&lt;<a href=3D"mailto:stefan.winter@restena.lu">stefan.win=
ter@restena.lu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<div class=3D"im"><br>
&gt;&gt; ... when the support people for a fairly well-established telco<br=
>
&gt;&gt; haven&#39;t even heard of IPv6, it&#39;s hard to believe that it&#=
39;s going<br>
&gt;&gt; to be available anytime soon.<br>
&gt;&gt; [multiple people essentially reporting the same]<br>
&gt;&gt; At this point in time $ISP has no immediate plans for implementati=
on.<br>
&gt; I would say it&#39;s about time reality finally settles in.<br>
<br>
</div>My reality is that I switched to an ISP who openly announced native I=
Pv6<br>
support in their offering in 2007. Up and running since then, and when I<br=
>
had trouble setting up the IPCP+IP6CP in the same PPP channel in IOS, I<br>
wrote them an email on a Saturday, and got a config snippet back an hour<br=
>
later, as part of their standard customer service. That ISP operates<br>
nation-wide and uses IPv6 as a marketing instrument to get techies to<br>
subscribe. For a price of converted 15 USD per month. That&#39;s in Germany=
<br>
though. Apparently, realities differ depending on where you are.<br>
<br>
Greetings,<br>
<br>
Stefan Winter<br>
<div><div></div><div class=3D"h5"><br>
&gt;<br>
&gt;&gt; Keith Moore wrote:<br>
&gt;&gt; Meanwhile, 6to4 continues to work just fine for me.<br>
&gt;&gt; So please explain again why it isn&#39;t premature to<br>
&gt;&gt; discourage a valuable transition mechanism?<br>
&gt; On that one I agree with Keith; where&#39;s the rush? Although imperfe=
ct,<br>
&gt; 6to4 was an obvious path and its demise would be the failure of the<br=
>
&gt; IETF, following a long list of things that have been killed prematurel=
y.<br>
&gt;<br>
&gt;<br>
&gt;&gt; Ned wrote:<br>
&gt;&gt; Anyone who doesn&#39;t believe we have a major marketing<br>
&gt;&gt; problem here isn&#39;t paying attention.<br>
&gt; Hmm that is a point of view. You think you have a solution (IPv6) to<b=
r>
&gt; what you perceive to be a problem (shortage of IPv4 addresses).<br>
&gt;<br>
&gt; However, some ISPs (and some other companies) do not consider it a<br>
&gt; problem, but a blessing. What the IPv4 shortage does is that it preven=
ts<br>
&gt; new large players to enter the field, while allowing existing players =
to<br>
&gt; continue to do business as usual.<br>
&gt;<br>
&gt; As the shortage as been predicted for a decade, some (not all) have<br=
>
&gt; stockpiled addresses and are now reaping the benefits. In business, th=
is<br>
&gt; situation is worth solid gold: it&#39;s called a monopoly. I&#39;m fat=
 and<br>
&gt; happy, and I want it to continue. In this case, it&#39;s even better:<=
br>
&gt; companies who benefit from it can argue that they are not the ones who=
<br>
&gt; created the monopoly, it was a built-in limitation of the system as<br=
>
&gt; created.<br>
&gt;<br>
&gt; Some may not like the parallel, but we have failed the IPv6 migration<=
br>
&gt; the same way we have failed the war on drugs. A while ago, there was<b=
r>
&gt; this thing called the Tier-1 cartel. As originally designed, a very<br=
>
&gt; elusive club, with almost no way in and absolutely no tears when a<br>
&gt; member gets de-peered.<br>
&gt;<br>
&gt; Some have said that the cartel has failed as a system (due to a large<=
br>
&gt; number of multilateral peering agreements and other factors). But now<=
br>
&gt; what we have is a much larger number of largely unorganized but sharin=
g<br>
&gt; the same goals entities: those who already have IPv4 addresses. It&#39=
;s<br>
&gt; even worse.<br>
&gt;<br>
&gt; When a resource becomes scare or limited, the big picture is not how<b=
r>
&gt; much of it is available, or how much it costs. The big picture is how<=
br>
&gt; much of the market one does control. Now we are in the situation where=
<br>
&gt; everyone and their sister own a piece of the pie, and as long as the<b=
r>
&gt; price of the pie keeps going up, they&#39;re going to cling to it.<br>
&gt;<br>
&gt;<br>
&gt; On top of the marketing problem you mentioned, you have a bigger one:<=
br>
&gt; there are many, many organizations out there that, even if you paid th=
em<br>
&gt; to deploy IPv6, would not. Because IPv6 is a territorial threat to the=
m.<br>
&gt;<br>
&gt; While the new or wannabe players would like the extra address space, t=
he<br>
&gt; sad truth is that the already establish players don&#39;t like newly o=
pen<br>
&gt; spaces and prefer the territory control that comes with owning a piece=
<br>
&gt; of a limited land space.<br>
&gt;<br>
&gt; Michel.<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Ietf mailing list<br>
&gt; <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ietf</a><br>
<br>
<br>
</div></div>--<br>
Stefan WINTER<br>
Ingenieur de Recherche<br>
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l&#39;Education Nation=
ale et de la Recherche<br>
6, rue Richard Coudenhove-Kalergi<br>
L-1359 Luxembourg<br>
<br>
Tel: +352 424409 1<br>
Fax: +352 422473<br>
<br>
<br>
<br>_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
<br></blockquote></div><br>

--0016e6471a2c2813a304a556d58b--

From stefan.winter@restena.lu  Fri Jun 10 02:09:25 2011
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FFE711E8082 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 02:09: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l4NDYqZw6KiC for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 02:09:24 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 3F1FD11E807D for <ietf@ietf.org>; Fri, 10 Jun 2011 02:09:23 -0700 (PDT)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 8139410590; Fri, 10 Jun 2011 11:09:20 +0200 (CEST)
Received: from [IPv6:2001:a18:1:8::155] (unknown [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 677C510584; Fri, 10 Jun 2011 11:09:20 +0200 (CEST)
Message-ID: <4DF1DF3B.2020408@restena.lu>
Date: Fri, 10 Jun 2011 11:09:15 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: otunte otueneh <otuenehoj@gmail.com>
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>	<BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com>	<01O2A8KT5RZ600VHKR@mauve.mrochek.com>	<20110610005758.BC2D110ABF81@drugs.dv.isc.org>	<392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local>	<4DF1BA93.5070105@restena.lu> <BANLkTinJSLjbqxM-OzLN-JOK3==3rRgiOA@mail.gmail.com>
In-Reply-To: <BANLkTinJSLjbqxM-OzLN-JOK3==3rRgiOA@mail.gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8652D502717D398734D4715F"
X-Virus-Scanned: ClamAV
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 09:09:25 -0000

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

Hello,

> "You appear to be able to browse the IPv4 Internet only. You will not
> be able to reach IPv6-only sites."
>
> Please can some one visit http://test-ipv6.com/# and give me more
> explanation on the displayed result?

That message is quite clear, isn't it? You use an Internet Service
Provider which only supplies you with IPv4 connectivity. If you want to
visit a website which only supports IPv6, it will not work.

The test website can be reached on both IPv4 and IPv6. So it can tell
you: you came here via IPv4, and didn't manage to get here via IPv6. So
there is no working IPv6 for you.

Stefan

>
> Kind regards,
>
> Otunte Otueneh
> ISOC Nigeria Chapter
>
>
> On Fri, Jun 10, 2011 at 7:32 AM, Stefan Winter
> <stefan.winter@restena.lu <mailto:stefan.winter@restena.lu>> wrote:
>
>     Hi,
>
>     >> ... when the support people for a fairly well-established telco
>     >> haven't even heard of IPv6, it's hard to believe that it's going=

>     >> to be available anytime soon.
>     >> [multiple people essentially reporting the same]
>     >> At this point in time $ISP has no immediate plans for
>     implementation.
>     > I would say it's about time reality finally settles in.
>
>     My reality is that I switched to an ISP who openly announced
>     native IPv6
>     support in their offering in 2007. Up and running since then, and
>     when I
>     had trouble setting up the IPCP+IP6CP in the same PPP channel in
>     IOS, I
>     wrote them an email on a Saturday, and got a config snippet back
>     an hour
>     later, as part of their standard customer service. That ISP operate=
s
>     nation-wide and uses IPv6 as a marketing instrument to get techies =
to
>     subscribe. For a price of converted 15 USD per month. That's in
>     Germany
>     though. Apparently, realities differ depending on where you are.
>
>     Greetings,
>
>     Stefan Winter
>
>     >
>     >> Keith Moore wrote:
>     >> Meanwhile, 6to4 continues to work just fine for me.
>     >> So please explain again why it isn't premature to
>     >> discourage a valuable transition mechanism?
>     > On that one I agree with Keith; where's the rush? Although
>     imperfect,
>     > 6to4 was an obvious path and its demise would be the failure of t=
he
>     > IETF, following a long list of things that have been killed
>     prematurely.
>     >
>     >
>     >> Ned wrote:
>     >> Anyone who doesn't believe we have a major marketing
>     >> problem here isn't paying attention.
>     > Hmm that is a point of view. You think you have a solution (IPv6)=
 to
>     > what you perceive to be a problem (shortage of IPv4 addresses).
>     >
>     > However, some ISPs (and some other companies) do not consider it =
a
>     > problem, but a blessing. What the IPv4 shortage does is that it
>     prevents
>     > new large players to enter the field, while allowing existing
>     players to
>     > continue to do business as usual.
>     >
>     > As the shortage as been predicted for a decade, some (not all) ha=
ve
>     > stockpiled addresses and are now reaping the benefits. In
>     business, this
>     > situation is worth solid gold: it's called a monopoly. I'm fat an=
d
>     > happy, and I want it to continue. In this case, it's even better:=

>     > companies who benefit from it can argue that they are not the
>     ones who
>     > created the monopoly, it was a built-in limitation of the system =
as
>     > created.
>     >
>     > Some may not like the parallel, but we have failed the IPv6
>     migration
>     > the same way we have failed the war on drugs. A while ago, there =
was
>     > this thing called the Tier-1 cartel. As originally designed, a ve=
ry
>     > elusive club, with almost no way in and absolutely no tears when =
a
>     > member gets de-peered.
>     >
>     > Some have said that the cartel has failed as a system (due to a
>     large
>     > number of multilateral peering agreements and other factors).
>     But now
>     > what we have is a much larger number of largely unorganized but
>     sharing
>     > the same goals entities: those who already have IPv4 addresses. I=
t's
>     > even worse.
>     >
>     > When a resource becomes scare or limited, the big picture is not =
how
>     > much of it is available, or how much it costs. The big picture
>     is how
>     > much of the market one does control. Now we are in the situation
>     where
>     > everyone and their sister own a piece of the pie, and as long as =
the
>     > price of the pie keeps going up, they're going to cling to it.
>     >
>     >
>     > On top of the marketing problem you mentioned, you have a bigger
>     one:
>     > there are many, many organizations out there that, even if you
>     paid them
>     > to deploy IPv6, would not. Because IPv6 is a territorial threat
>     to them.
>     >
>     > While the new or wannabe players would like the extra address
>     space, the
>     > sad truth is that the already establish players don't like newly
>     open
>     > spaces and prefer the territory control that comes with owning a
>     piece
>     > of a limited land space.
>     >
>     > Michel.
>     >
>     > _______________________________________________
>     > Ietf mailing list
>     > Ietf@ietf.org <mailto:Ietf@ietf.org>
>     > https://www.ietf.org/mailman/listinfo/ietf
>
>
>     --
>     Stefan WINTER
>     Ingenieur de Recherche
>     Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education
>     Nationale et de la Recherche
>     6, rue Richard Coudenhove-Kalergi
>     L-1359 Luxembourg
>
>     Tel: +352 424409 1
>     Fax: +352 422473
>
>
>
>     _______________________________________________
>     Ietf mailing list
>     Ietf@ietf.org <mailto:Ietf@ietf.org>
>     https://www.ietf.org/mailman/listinfo/ietf
>
>


--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473



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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3x3z8ACgkQ+jm90f8eFWYZcACaA0aK39nh+0YecQOI3MtXkP8I
NQcAoIIjPuC+dWxr/POJIST/tnOUJtPv
=BwPL
-----END PGP SIGNATURE-----

--------------enig8652D502717D398734D4715F--

From otuenehoj@gmail.com  Fri Jun 10 02:55:39 2011
Return-Path: <otuenehoj@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDCE611E80D9 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 02:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.021
X-Spam-Level: 
X-Spam-Status: No, score=-3.021 tagged_above=-999 required=5 tests=[AWL=0.577,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8NHxezZAKudL for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 02:55:38 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id EA1F911E807E for <ietf@ietf.org>; Fri, 10 Jun 2011 02:55:37 -0700 (PDT)
Received: by iwn39 with SMTP id 39so2728746iwn.31 for <ietf@ietf.org>; Fri, 10 Jun 2011 02:55:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Jf9o8PFgbHik1zCAGvBPOxkTLsC3LdeLAbPrGo0RAdQ=; b=gPYcBAsXiA5qLBfGXMdXhfxzQVU/nsqND4gPJK4IDwElUbYGcPk1ET2YCBLTl/wFGd t4MNG1I/CmDR0WsT7BTK7Hl086Vszp60JLVmTEfhGDZdTiBwF6TylCsYIq8xP0H//0bW U+77x69hbgOlNXwQxoLMRFjz/KWt+oInBOI6o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Ph/gv+lJ78P+hEHPgLX19n1FO72MWvSM2EHmdn9jLzyEYNC+Q3blJ+GzwLrlzdZmEK M1S5jUIQ4Tj9Ib3VfeBxcIruqBUh9G3Y0ehTCmL4C2QlNmymSesnCo/Yiqwn56d9c1AN pDXB+qSnKxCr6+VZwUWGmg06CUV/tp0HCsoxI=
MIME-Version: 1.0
Received: by 10.231.60.68 with SMTP id o4mr2368394ibh.12.1307699737277; Fri, 10 Jun 2011 02:55:37 -0700 (PDT)
Received: by 10.231.5.147 with HTTP; Fri, 10 Jun 2011 02:55:37 -0700 (PDT)
In-Reply-To: <4DF1DF3B.2020408@restena.lu>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF1BA93.5070105@restena.lu> <BANLkTinJSLjbqxM-OzLN-JOK3==3rRgiOA@mail.gmail.com> <4DF1DF3B.2020408@restena.lu>
Date: Fri, 10 Jun 2011 10:55:37 +0100
Message-ID: <BANLkTim4arExNBHV5r=iZHdUHdxqvcuhpw@mail.gmail.com>
Subject: Re: one data point regarding native IPv6 support
From: otunte otueneh <otuenehoj@gmail.com>
To: Stefan Winter <stefan.winter@restena.lu>
Content-Type: multipart/alternative; boundary=0015176f195050363004a5589277
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 09:55:39 -0000

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

Dear Stefan,
Thank you for the reply.
I think there should be a platform where IPv4 users and IPv6 users can
interface. If this link is missing then there will be problem.

Otueneh

On Fri, Jun 10, 2011 at 10:09 AM, Stefan Winter <stefan.winter@restena.lu>w=
rote:

> Hello,
>
> > "You appear to be able to browse the IPv4 Internet only. You will not
> > be able to reach IPv6-only sites."
> >
> > Please can some one visit http://test-ipv6.com/# and give me more
> > explanation on the displayed result?
>
> That message is quite clear, isn't it? You use an Internet Service
> Provider which only supplies you with IPv4 connectivity. If you want to
> visit a website which only supports IPv6, it will not work.
>
> The test website can be reached on both IPv4 and IPv6. So it can tell
> you: you came here via IPv4, and didn't manage to get here via IPv6. So
> there is no working IPv6 for you.
>
> Stefan
>
> >
> > Kind regards,
> >
> > Otunte Otueneh
> > ISOC Nigeria Chapter
> >
> >
> > On Fri, Jun 10, 2011 at 7:32 AM, Stefan Winter
> > <stefan.winter@restena.lu <mailto:stefan.winter@restena.lu>> wrote:
> >
> >     Hi,
> >
> >     >> ... when the support people for a fairly well-established telco
> >     >> haven't even heard of IPv6, it's hard to believe that it's going
> >     >> to be available anytime soon.
> >     >> [multiple people essentially reporting the same]
> >     >> At this point in time $ISP has no immediate plans for
> >     implementation.
> >     > I would say it's about time reality finally settles in.
> >
> >     My reality is that I switched to an ISP who openly announced
> >     native IPv6
> >     support in their offering in 2007. Up and running since then, and
> >     when I
> >     had trouble setting up the IPCP+IP6CP in the same PPP channel in
> >     IOS, I
> >     wrote them an email on a Saturday, and got a config snippet back
> >     an hour
> >     later, as part of their standard customer service. That ISP operate=
s
> >     nation-wide and uses IPv6 as a marketing instrument to get techies =
to
> >     subscribe. For a price of converted 15 USD per month. That's in
> >     Germany
> >     though. Apparently, realities differ depending on where you are.
> >
> >     Greetings,
> >
> >     Stefan Winter
> >
> >     >
> >     >> Keith Moore wrote:
> >     >> Meanwhile, 6to4 continues to work just fine for me.
> >     >> So please explain again why it isn't premature to
> >     >> discourage a valuable transition mechanism?
> >     > On that one I agree with Keith; where's the rush? Although
> >     imperfect,
> >     > 6to4 was an obvious path and its demise would be the failure of t=
he
> >     > IETF, following a long list of things that have been killed
> >     prematurely.
> >     >
> >     >
> >     >> Ned wrote:
> >     >> Anyone who doesn't believe we have a major marketing
> >     >> problem here isn't paying attention.
> >     > Hmm that is a point of view. You think you have a solution (IPv6)
> to
> >     > what you perceive to be a problem (shortage of IPv4 addresses).
> >     >
> >     > However, some ISPs (and some other companies) do not consider it =
a
> >     > problem, but a blessing. What the IPv4 shortage does is that it
> >     prevents
> >     > new large players to enter the field, while allowing existing
> >     players to
> >     > continue to do business as usual.
> >     >
> >     > As the shortage as been predicted for a decade, some (not all) ha=
ve
> >     > stockpiled addresses and are now reaping the benefits. In
> >     business, this
> >     > situation is worth solid gold: it's called a monopoly. I'm fat an=
d
> >     > happy, and I want it to continue. In this case, it's even better:
> >     > companies who benefit from it can argue that they are not the
> >     ones who
> >     > created the monopoly, it was a built-in limitation of the system =
as
> >     > created.
> >     >
> >     > Some may not like the parallel, but we have failed the IPv6
> >     migration
> >     > the same way we have failed the war on drugs. A while ago, there
> was
> >     > this thing called the Tier-1 cartel. As originally designed, a ve=
ry
> >     > elusive club, with almost no way in and absolutely no tears when =
a
> >     > member gets de-peered.
> >     >
> >     > Some have said that the cartel has failed as a system (due to a
> >     large
> >     > number of multilateral peering agreements and other factors).
> >     But now
> >     > what we have is a much larger number of largely unorganized but
> >     sharing
> >     > the same goals entities: those who already have IPv4 addresses.
> It's
> >     > even worse.
> >     >
> >     > When a resource becomes scare or limited, the big picture is not
> how
> >     > much of it is available, or how much it costs. The big picture
> >     is how
> >     > much of the market one does control. Now we are in the situation
> >     where
> >     > everyone and their sister own a piece of the pie, and as long as
> the
> >     > price of the pie keeps going up, they're going to cling to it.
> >     >
> >     >
> >     > On top of the marketing problem you mentioned, you have a bigger
> >     one:
> >     > there are many, many organizations out there that, even if you
> >     paid them
> >     > to deploy IPv6, would not. Because IPv6 is a territorial threat
> >     to them.
> >     >
> >     > While the new or wannabe players would like the extra address
> >     space, the
> >     > sad truth is that the already establish players don't like newly
> >     open
> >     > spaces and prefer the territory control that comes with owning a
> >     piece
> >     > of a limited land space.
> >     >
> >     > Michel.
> >     >
> >     > _______________________________________________
> >     > Ietf mailing list
> >     > Ietf@ietf.org <mailto:Ietf@ietf.org>
> >     > https://www.ietf.org/mailman/listinfo/ietf
> >
> >
> >     --
> >     Stefan WINTER
> >     Ingenieur de Recherche
> >     Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education
> >     Nationale et de la Recherche
> >     6, rue Richard Coudenhove-Kalergi
> >     L-1359 Luxembourg
> >
> >     Tel: +352 424409 1
> >     Fax: +352 422473
> >
> >
> >
> >     _______________________________________________
> >     Ietf mailing list
> >     Ietf@ietf.org <mailto:Ietf@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/ietf
> >
> >
>
>
> --
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et de
> la Recherche
> 6, rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>
> Tel: +352 424409 1
> Fax: +352 422473
>
>
>

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

Dear Stefan,<br>Thank you for the reply.<br>I think there should be a platf=
orm where IPv4 users and IPv6 users can interface. If this link is missing =
then there will be problem.<br><br>Otueneh <br><br><div class=3D"gmail_quot=
e">
On Fri, Jun 10, 2011 at 10:09 AM, Stefan Winter <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:stefan.winter@restena.lu">stefan.winter@restena.lu</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;">
Hello,<br>
<div class=3D"im"><br>
&gt; &quot;You appear to be able to browse the IPv4 Internet only. You will=
 not<br>
&gt; be able to reach IPv6-only sites.&quot;<br>
&gt;<br>
&gt; Please can some one visit <a href=3D"http://test-ipv6.com/#" target=3D=
"_blank">http://test-ipv6.com/#</a> and give me more<br>
&gt; explanation on the displayed result?<br>
<br>
</div>That message is quite clear, isn&#39;t it? You use an Internet Servic=
e<br>
Provider which only supplies you with IPv4 connectivity. If you want to<br>
visit a website which only supports IPv6, it will not work.<br>
<br>
The test website can be reached on both IPv4 and IPv6. So it can tell<br>
you: you came here via IPv4, and didn&#39;t manage to get here via IPv6. So=
<br>
there is no working IPv6 for you.<br>
<br>
Stefan<br>
<div class=3D"im"><br>
&gt;<br>
&gt; Kind regards,<br>
&gt;<br>
&gt; Otunte Otueneh<br>
&gt; ISOC Nigeria Chapter<br>
&gt;<br>
&gt;<br>
&gt; On Fri, Jun 10, 2011 at 7:32 AM, Stefan Winter<br>
</div><div><div></div><div class=3D"h5">&gt; &lt;<a href=3D"mailto:stefan.w=
inter@restena.lu">stefan.winter@restena.lu</a> &lt;mailto:<a href=3D"mailto=
:stefan.winter@restena.lu">stefan.winter@restena.lu</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt; =A0 =A0 Hi,<br>
&gt;<br>
&gt; =A0 =A0 &gt;&gt; ... when the support people for a fairly well-establi=
shed telco<br>
&gt; =A0 =A0 &gt;&gt; haven&#39;t even heard of IPv6, it&#39;s hard to beli=
eve that it&#39;s going<br>
&gt; =A0 =A0 &gt;&gt; to be available anytime soon.<br>
&gt; =A0 =A0 &gt;&gt; [multiple people essentially reporting the same]<br>
&gt; =A0 =A0 &gt;&gt; At this point in time $ISP has no immediate plans for=
<br>
&gt; =A0 =A0 implementation.<br>
&gt; =A0 =A0 &gt; I would say it&#39;s about time reality finally settles i=
n.<br>
&gt;<br>
&gt; =A0 =A0 My reality is that I switched to an ISP who openly announced<b=
r>
&gt; =A0 =A0 native IPv6<br>
&gt; =A0 =A0 support in their offering in 2007. Up and running since then, =
and<br>
&gt; =A0 =A0 when I<br>
&gt; =A0 =A0 had trouble setting up the IPCP+IP6CP in the same PPP channel =
in<br>
&gt; =A0 =A0 IOS, I<br>
&gt; =A0 =A0 wrote them an email on a Saturday, and got a config snippet ba=
ck<br>
&gt; =A0 =A0 an hour<br>
&gt; =A0 =A0 later, as part of their standard customer service. That ISP op=
erates<br>
&gt; =A0 =A0 nation-wide and uses IPv6 as a marketing instrument to get tec=
hies to<br>
&gt; =A0 =A0 subscribe. For a price of converted 15 USD per month. That&#39=
;s in<br>
&gt; =A0 =A0 Germany<br>
&gt; =A0 =A0 though. Apparently, realities differ depending on where you ar=
e.<br>
&gt;<br>
&gt; =A0 =A0 Greetings,<br>
&gt;<br>
&gt; =A0 =A0 Stefan Winter<br>
&gt;<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt;&gt; Keith Moore wrote:<br>
&gt; =A0 =A0 &gt;&gt; Meanwhile, 6to4 continues to work just fine for me.<b=
r>
&gt; =A0 =A0 &gt;&gt; So please explain again why it isn&#39;t premature to=
<br>
&gt; =A0 =A0 &gt;&gt; discourage a valuable transition mechanism?<br>
&gt; =A0 =A0 &gt; On that one I agree with Keith; where&#39;s the rush? Alt=
hough<br>
&gt; =A0 =A0 imperfect,<br>
&gt; =A0 =A0 &gt; 6to4 was an obvious path and its demise would be the fail=
ure of the<br>
&gt; =A0 =A0 &gt; IETF, following a long list of things that have been kill=
ed<br>
&gt; =A0 =A0 prematurely.<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt;&gt; Ned wrote:<br>
&gt; =A0 =A0 &gt;&gt; Anyone who doesn&#39;t believe we have a major market=
ing<br>
&gt; =A0 =A0 &gt;&gt; problem here isn&#39;t paying attention.<br>
&gt; =A0 =A0 &gt; Hmm that is a point of view. You think you have a solutio=
n (IPv6) to<br>
&gt; =A0 =A0 &gt; what you perceive to be a problem (shortage of IPv4 addre=
sses).<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; However, some ISPs (and some other companies) do not cons=
ider it a<br>
&gt; =A0 =A0 &gt; problem, but a blessing. What the IPv4 shortage does is t=
hat it<br>
&gt; =A0 =A0 prevents<br>
&gt; =A0 =A0 &gt; new large players to enter the field, while allowing exis=
ting<br>
&gt; =A0 =A0 players to<br>
&gt; =A0 =A0 &gt; continue to do business as usual.<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; As the shortage as been predicted for a decade, some (not=
 all) have<br>
&gt; =A0 =A0 &gt; stockpiled addresses and are now reaping the benefits. In=
<br>
&gt; =A0 =A0 business, this<br>
&gt; =A0 =A0 &gt; situation is worth solid gold: it&#39;s called a monopoly=
. I&#39;m fat and<br>
&gt; =A0 =A0 &gt; happy, and I want it to continue. In this case, it&#39;s =
even better:<br>
&gt; =A0 =A0 &gt; companies who benefit from it can argue that they are not=
 the<br>
&gt; =A0 =A0 ones who<br>
&gt; =A0 =A0 &gt; created the monopoly, it was a built-in limitation of the=
 system as<br>
&gt; =A0 =A0 &gt; created.<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; Some may not like the parallel, but we have failed the IP=
v6<br>
&gt; =A0 =A0 migration<br>
&gt; =A0 =A0 &gt; the same way we have failed the war on drugs. A while ago=
, there was<br>
&gt; =A0 =A0 &gt; this thing called the Tier-1 cartel. As originally design=
ed, a very<br>
&gt; =A0 =A0 &gt; elusive club, with almost no way in and absolutely no tea=
rs when a<br>
&gt; =A0 =A0 &gt; member gets de-peered.<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; Some have said that the cartel has failed as a system (du=
e to a<br>
&gt; =A0 =A0 large<br>
&gt; =A0 =A0 &gt; number of multilateral peering agreements and other facto=
rs).<br>
&gt; =A0 =A0 But now<br>
&gt; =A0 =A0 &gt; what we have is a much larger number of largely unorganiz=
ed but<br>
&gt; =A0 =A0 sharing<br>
&gt; =A0 =A0 &gt; the same goals entities: those who already have IPv4 addr=
esses. It&#39;s<br>
&gt; =A0 =A0 &gt; even worse.<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; When a resource becomes scare or limited, the big picture=
 is not how<br>
&gt; =A0 =A0 &gt; much of it is available, or how much it costs. The big pi=
cture<br>
&gt; =A0 =A0 is how<br>
&gt; =A0 =A0 &gt; much of the market one does control. Now we are in the si=
tuation<br>
&gt; =A0 =A0 where<br>
&gt; =A0 =A0 &gt; everyone and their sister own a piece of the pie, and as =
long as the<br>
&gt; =A0 =A0 &gt; price of the pie keeps going up, they&#39;re going to cli=
ng to it.<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; On top of the marketing problem you mentioned, you have a=
 bigger<br>
&gt; =A0 =A0 one:<br>
&gt; =A0 =A0 &gt; there are many, many organizations out there that, even i=
f you<br>
&gt; =A0 =A0 paid them<br>
&gt; =A0 =A0 &gt; to deploy IPv6, would not. Because IPv6 is a territorial =
threat<br>
&gt; =A0 =A0 to them.<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; While the new or wannabe players would like the extra add=
ress<br>
&gt; =A0 =A0 space, the<br>
&gt; =A0 =A0 &gt; sad truth is that the already establish players don&#39;t=
 like newly<br>
&gt; =A0 =A0 open<br>
&gt; =A0 =A0 &gt; spaces and prefer the territory control that comes with o=
wning a<br>
&gt; =A0 =A0 piece<br>
&gt; =A0 =A0 &gt; of a limited land space.<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; Michel.<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; _______________________________________________<br>
&gt; =A0 =A0 &gt; Ietf mailing list<br>
</div></div>&gt; =A0 =A0 &gt; <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.or=
g</a> &lt;mailto:<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a>&gt;<br>
<div class=3D"im">&gt; =A0 =A0 &gt; <a href=3D"https://www.ietf.org/mailman=
/listinfo/ietf" target=3D"_blank">https://www.ietf.org/mailman/listinfo/iet=
f</a><br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 --<br>
&gt; =A0 =A0 Stefan WINTER<br>
&gt; =A0 =A0 Ingenieur de Recherche<br>
&gt; =A0 =A0 Fondation RESTENA - R=E9seau T=E9l=E9informatique de l&#39;Edu=
cation<br>
&gt; =A0 =A0 Nationale et de la Recherche<br>
&gt; =A0 =A0 6, rue Richard Coudenhove-Kalergi<br>
&gt; =A0 =A0 L-1359 Luxembourg<br>
&gt;<br>
&gt; =A0 =A0 Tel: +352 424409 1<br>
&gt; =A0 =A0 Fax: +352 422473<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 _______________________________________________<br>
&gt; =A0 =A0 Ietf mailing list<br>
</div>&gt; =A0 =A0 <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a> &lt;m=
ailto:<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a>&gt;<br>
<div><div></div><div class=3D"h5">&gt; =A0 =A0 <a href=3D"https://www.ietf.=
org/mailman/listinfo/ietf" target=3D"_blank">https://www.ietf.org/mailman/l=
istinfo/ietf</a><br>
&gt;<br>
&gt;<br>
<br>
<br>
--<br>
Stefan WINTER<br>
Ingenieur de Recherche<br>
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l&#39;Education Nation=
ale et de la Recherche<br>
6, rue Richard Coudenhove-Kalergi<br>
L-1359 Luxembourg<br>
<br>
Tel: +352 424409 1<br>
Fax: +352 422473<br>
<br>
<br>
</div></div></blockquote></div><br>

--0015176f195050363004a5589277--

From trejrco@gmail.com  Fri Jun 10 04:36:58 2011
Return-Path: <trejrco@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B946C11E809C for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 04:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.523
X-Spam-Level: 
X-Spam-Status: No, score=-3.523 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G+0WyVnmcLxH for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 04:36:57 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id C990811E8083 for <ietf@ietf.org>; Fri, 10 Jun 2011 04:36:57 -0700 (PDT)
Received: by gxk19 with SMTP id 19so2267991gxk.31 for <ietf@ietf.org>; Fri, 10 Jun 2011 04:36:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=LaConfT6Xo67Mltu9JDcnBMPWxjM8rHCvyl+qEpjU2E=; b=IH2DNW2ZR+mLML5h1o29h5WKQz/isctfvGRQVbmkhzO+UFyrayrlwNyI24Rb+3zAyc sLZlYK5joh+trxGrfHBhkfXShV/XyF25dN6Wh7PadKE/4evg0Y5Q4AnBtHPnVEcfl8Vq Clp3B2xjxNrXuDfnSK+uPK/wpF+z3LjDieUc4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; b=DpF73HSUYhrSNBXsOs5AdCuzOSlEBjqHLr29LorOKbwDVBbweUydHdx521Ng8ciODa xb689+d4rwgnhpcrQm6nrgYC7QJSZmFWKAFmz5v6x3fPKVX5kKgFtJqF9RcPfOdjQFGw UQ0cWAgeknoRJrv+9ZwwwSucbmVHy/pv2JzK0=
Received: by 10.91.153.7 with SMTP id f7mr1741162ago.36.1307705817080; Fri, 10 Jun 2011 04:36:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.91.170.3 with HTTP; Fri, 10 Jun 2011 04:36:37 -0700 (PDT)
In-Reply-To: <BANLkTim4arExNBHV5r=iZHdUHdxqvcuhpw@mail.gmail.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF1BA93.5070105@restena.lu> <BANLkTinJSLjbqxM-OzLN-JOK3==3rRgiOA@mail.gmail.com> <4DF1DF3B.2020408@restena.lu> <BANLkTim4arExNBHV5r=iZHdUHdxqvcuhpw@mail.gmail.com>
From: TJ <trejrco@gmail.com>
Date: Fri, 10 Jun 2011 07:36:37 -0400
Message-ID: <BANLkTi=WKMfvYQgkgQp4-sOJUbOdiKK8Uw@mail.gmail.com>
Subject: Re: one data point regarding native IPv6 support
To: The IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=0016e644ccbeb2a22604a559fce4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 11:36:58 -0000

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

On Fri, Jun 10, 2011 at 05:55, otunte otueneh <otuenehoj@gmail.com> wrote:

> Dear Stefan,
> Thank you for the reply.
> I think there should be a platform where IPv4 users and IPv6 users can
> interface. If this link is missing then there will be problem.
>
>
That kind of thing can be done - Google NAT64/DNS64 or how proxies work.,
 However, this is *not* the ideal state.  Ideally, you would be provisioned
with both IPv4 and IPv6 ("dual stack")  and thus be able to connect to
content reachable over either.

Call your ISP, ask them when they will be entering the right decade (read:
How soon will they offer IPv6).  This may not be a "critical" feature right
now, but if your ISP hasn't even started they probably won't be ready when
you start to need it.  Or they will break things trying to get there
rapidly, that is fun.


/TJ

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

<div class=3D"gmail_quote">On Fri, Jun 10, 2011 at 05:55, otunte otueneh <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:otuenehoj@gmail.com">otuenehoj@gmail.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

Dear Stefan,<br>Thank you for the reply.<br>I think there should be a platf=
orm where IPv4 users and IPv6 users can interface. If this link is missing =
then there will be problem.<br><br></blockquote><div><br></div><div>That ki=
nd of thing can be done - Google NAT64/DNS64 or how proxies work., =A0Howev=
er, this is *not* the ideal state. =A0Ideally, you would be provisioned wit=
h both IPv4 and IPv6 (&quot;dual stack&quot;) =A0and thus be able to connec=
t to content reachable over either. =A0<br>

<br>Call your ISP, ask them when they will be entering the right decade (re=
ad: How soon will they offer IPv6). =A0This may not be a &quot;critical&quo=
t; feature right now, but if your ISP hasn&#39;t even started they probably=
 won&#39;t be ready when you start to need it. =A0Or they will break things=
 trying to get there rapidly, that is fun.</div>

</div><div><br></div><br><div>/TJ</div>

--0016e644ccbeb2a22604a559fce4--

From tnadeau@lucidvision.com  Fri Jun 10 06:04:07 2011
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 3EE3D11E8123 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 06:04: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]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hJ6Uhsxqh77V for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 06:04:06 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 46F1811E80F8 for <ietf@ietf.org>; Fri, 10 Jun 2011 06:04:06 -0700 (PDT)
Received: from [10.100.68.148] (unknown [141.202.11.155]) by lucidvision.com (Postfix) with ESMTP id 42D441BCCE3F; Fri, 10 Jun 2011 09:04:05 -0400 (EDT)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>
Date: Fri, 10 Jun 2011 09:04:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7640580D-6DC7-4FD6-A981-22FF58113177@lucidvision.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
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, 10 Jun 2011 13:04:07 -0000

	Sadly this is more common than it should be these days. I've =
been begging Fairpoint for IPv6 for the past 3 years, from which people =
in NH/VT/ME now have been subjected to as Verizon sold off FIOS/dsl in =
those areas to them a while back. I have "business" service from them =
with static IPs and the whole 9 yards, and they still insist that I am =
mad when I call to ask for IPv6 siting the same reasons you are being =
given.

	--Tom

=09
> I just called my ISP to ask about availability of IPv6 at my home.
>=20
> Me:  "I'm a current customer, and I'm just calling to ask if you =
support Internet Protocol Version 6."
>=20
> First person: "Yes, we do support Internet.  We support DSL at 3 =
megabits and 6 megabits."
>=20
> Me: "I understand that, but I'm asking about Internet Protocol version =
6, IPv6.  The Internet has been using IP version 4 since the early =
1980s, but that's running out.  IPv6 is the new version."
>=20
> First person: "Let me transfer you to support."
>=20
> Second person: "Hi, this is support.  How may I help you?"
>=20
> Me: "I'm a current customer, and I'm just calling to ask if you =
support Internet Protocol Version 6."
>=20
> Second person: "IP version what?"
>=20
> Me: "Internet protocol version 6".
>=20
> Second person: "I have no idea.  Let me transfer you to someone else."
>=20
> (places me on hold for 15 minutes)
>=20
> Second person: "I'm sorry for the wait time.  I've been trying to find =
the answer to your question, but nobody here seems to know anything =
about it.  We're trying to get in touch with people who run the network =
to ask them.   Can I get your number and call you back?"
>=20
> Granted, this is just one ISP.  The other ISP that offers service in =
my area put me on hold for an hour and a half *before anyone ever talked =
to me* when I tried to get a quote from them, so I concluded that they =
wouldn't be a good choice.  And these guys have been good about support =
in general.  They seem to know their stuff, which is more than I can say =
for some ISPs I've dealt with in the past.
>=20
> I live in a well-settled urban area, three miles from the center of =
the city (and sadly, four miles from my CO, which means my DSL circuit =
gets around 380kbits/sec).  It's not a backwater, there's plenty of lit =
fiber running through town.  But when the support people for a fairly =
well-established telco haven't even heard of IPv6, it's hard to believe =
that it's going to be available anytime soon.
>=20
> Meanwhile, 6to4 continues to work just fine for me.
>=20
> So please explain again why it isn't premature to discourage a =
valuable transition mechanism?
>=20
> Keith
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From bertietf@bwijnen.net  Fri Jun 10 06:11:01 2011
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7E0E11E814C for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 06:11: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E-ZgAQOkMznI for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 06:11:01 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id 2CD1C11E80F8 for <ietf@ietf.org>; Fri, 10 Jun 2011 06:11:00 -0700 (PDT)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1QV1UA-0003hr-Gt; Fri, 10 Jun 2011 15:10:56 +0200
Received: from dog.ripe.net ([193.0.1.217] helo=guest178.guestnet.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1QV1UA-00038d-Ax; Fri, 10 Jun 2011 15:10:50 +0200
Message-ID: <4DF217DA.9010501@bwijnen.net>
Date: Fri, 10 Jun 2011 15:10:50 +0200
From: "Bert (IETF) Wijnen" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Thomas Nadeau <tnadeau@lucidvision.com>
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <7640580D-6DC7-4FD6-A981-22FF58113177@lucidvision.com>
In-Reply-To: <7640580D-6DC7-4FD6-A981-22FF58113177@lucidvision.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4f9e0bd309cdaf34e1e6a5d537b1f95cb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 13:11:01 -0000

I have a "Business service" from my ISP too. They told me that somewhere in 2012 they would look into IPv6.
So I have threatened to move to another provider. But we do not have much choice in NL at the moment
I believe. Although I have to re-checked recently.

Bert

On 6/10/11 3:04 PM, Thomas Nadeau wrote:
> 	Sadly this is more common than it should be these days. I've been begging Fairpoint for IPv6 for the past 3 years, from which people in NH/VT/ME now have been subjected to as Verizon sold off FIOS/dsl in those areas to them a while back. I have "business" service from them with static IPs and the whole 9 yards, and they still insist that I am mad when I call to ask for IPv6 siting the same reasons you are being given.
>
> 	--Tom
>
> 	
>> I just called my ISP to ask about availability of IPv6 at my home.
>>
>> Me:  "I'm a current customer, and I'm just calling to ask if you support Internet Protocol Version 6."
>>
>> First person: "Yes, we do support Internet.  We support DSL at 3 megabits and 6 megabits."
>>
>> Me: "I understand that, but I'm asking about Internet Protocol version 6, IPv6.  The Internet has been using IP version 4 since the early 1980s, but that's running out.  IPv6 is the new version."
>>
>> First person: "Let me transfer you to support."
>>
>> Second person: "Hi, this is support.  How may I help you?"
>>
>> Me: "I'm a current customer, and I'm just calling to ask if you support Internet Protocol Version 6."
>>
>> Second person: "IP version what?"
>>
>> Me: "Internet protocol version 6".
>>
>> Second person: "I have no idea.  Let me transfer you to someone else."
>>
>> (places me on hold for 15 minutes)
>>
>> Second person: "I'm sorry for the wait time.  I've been trying to find the answer to your question, but nobody here seems to know anything about it.  We're trying to get in touch with people who run the network to ask them.   Can I get your number and call you back?"
>>
>> Granted, this is just one ISP.  The other ISP that offers service in my area put me on hold for an hour and a half *before anyone ever talked to me* when I tried to get a quote from them, so I concluded that they wouldn't be a good choice.  And these guys have been good about support in general.  They seem to know their stuff, which is more than I can say for some ISPs I've dealt with in the past.
>>
>> I live in a well-settled urban area, three miles from the center of the city (and sadly, four miles from my CO, which means my DSL circuit gets around 380kbits/sec).  It's not a backwater, there's plenty of lit fiber running through town.  But when the support people for a fairly well-established telco haven't even heard of IPv6, it's hard to believe that it's going to be available anytime soon.
>>
>> Meanwhile, 6to4 continues to work just fine for me.
>>
>> So please explain again why it isn't premature to discourage a valuable transition mechanism?
>>
>> Keith
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From brian.e.carpenter@gmail.com  Fri Jun 10 06:35:01 2011
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 067AD1F0C61 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 06:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.539
X-Spam-Level: 
X-Spam-Status: No, score=-103.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JIfFZzJ5Esnp for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 06:35:00 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3AA971F0C60 for <ietf@ietf.org>; Fri, 10 Jun 2011 06:35:00 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1850663fxm.31 for <ietf@ietf.org>; Fri, 10 Jun 2011 06:34:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZuK98PkZQg38zAOV7T9sNRihFDMvcC9mrJheWRN1ny0=; b=RK+hS7HaiRAlLi/sQvZsDjs5o5z/6l7YWdptYPVPz8tksVrV1KKRix876ZLImk9Tpq 0Cw52LwLRND792agV6cII2TsQLTJoYBdTGUpEViasJKoASer5JsRUjTUBVAbPos8Uaqq CK27jHYXDfBpAfY28bHb5q9BHEaD2YNGt2TxU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=LDnXgJb4agQRxpcvj+EMFsXfzgH8bNzmF57nMoe9lsjLidfbH4Beuy+xc6s/45OShy wr1uk4CM9q0vLVGxEI79wj53d+y31WnuGitr1B4Sap2oEQ4T+4QoR7QjLYZUwSb/WwKc F93Et96tdFK+ISwHwPfbGIaC9aj57meAQy2Bg=
Received: by 10.223.55.27 with SMTP id s27mr2062709fag.121.1307712895832; Fri, 10 Jun 2011 06:34:55 -0700 (PDT)
Received: from [10.255.25.89] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id n13sm108005fab.22.2011.06.10.06.34.53 (version=SSLv3 cipher=OTHER); Fri, 10 Jun 2011 06:34:54 -0700 (PDT)
Message-ID: <4DF21D7B.7040103@gmail.com>
Date: Sat, 11 Jun 2011 01:34:51 +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: Michel Py <michel@arneill-py.sacramento.ca.us>
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com><BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com><01O2A8KT5RZ600VHKR@mauve.mrochek.com>	<20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ned+ietf@mauve.mrochek.com, IETF Discussion <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 13:35:01 -0000

Michel,

On 2011-06-10 15:38, Michel Py wrote:
...
> On that one I agree with Keith; where's the rush? Although imperfect,
> 6to4 was an obvious path and its demise would be the failure of the
> IETF, following a long list of things that have been killed prematurely.

Who's talking about its demise? Really all that the 6to4-historic draft
does is say that it should no longer be considered as a default solution
to the problem of ISPs that don't support IPv6. Changing the formal
status of the RFCs is a symbolic step, but the real point is that it's
now time for the reluctant ISPs to get their heads out of the sand.

You're correct that some ISPs will try to get monopoly rents out of
the IPv4 shortage, and use CGN to capture customers in walled gardens,
but fortunately capitalism provides a solution to such misbehaviour:
other ISPs can deploy IPv6 as a competitive advantage.

    Brian

From moore@network-heretics.com  Fri Jun 10 06:49:30 2011
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 7543D11E8181 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 06:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.316
X-Spam-Level: 
X-Spam-Status: No, score=-3.316 tagged_above=-999 required=5 tests=[AWL=0.283,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DsijJtsYSt36 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 06:49:29 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 66A8111E817F for <ietf@ietf.org>; Fri, 10 Jun 2011 06:49:29 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 7CA78203AF; Fri, 10 Jun 2011 09:49:28 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Fri, 10 Jun 2011 09:49:28 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=yG2uebKsmRW/MVJBZdGbxF32z+E=; b=qN29baevN3hRQ0OY8abKm8d9TRV2kAz+Bk9+UQ9Qg9vHreyRAIFpgEpxfB6vZj5ktC4Ca4Z3PcVn7TLkRIqTXnt/CgzoKGj3yUHMxNaBHZHZuP/Gq58qtvBH+LB+dEnUJw0OQtzakptAMGewKAUnqa8FocB1jbGCwPGM8xapb6Q=
X-Sasl-enc: kgp/iI41V276dyQJyo1K22wPG5mF0DJfEHX/5kvJaZc0 1307713767
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 34DA1400EE9; Fri, 10 Jun 2011 09:49:27 -0400 (EDT)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4DF21D7B.7040103@gmail.com>
Date: Fri, 10 Jun 2011 09:49:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F76AB59-2F72-437C-A3C8-D6341BB46719@network-heretics.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com><BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com><01O2A8KT5RZ600VHKR@mauve.mrochek.com>	<20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, ned+ietf@mauve.mrochek.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: Fri, 10 Jun 2011 13:49:30 -0000

On Jun 10, 2011, at 9:34 AM, Brian E Carpenter wrote:

> Michel,
>=20
> On 2011-06-10 15:38, Michel Py wrote:
> ...
>> On that one I agree with Keith; where's the rush? Although imperfect,
>> 6to4 was an obvious path and its demise would be the failure of the
>> IETF, following a long list of things that have been killed =
prematurely.
>=20
> Who's talking about its demise? Really all that the 6to4-historic =
draft
> does is say that it should no longer be considered as a default =
solution
> to the problem of ISPs that don't support IPv6.

Actually it says more than that.  For instance, it specifically says =
that new implementations shouldn't support 6to4.

That, and if passed, this would be the first time I can recall that IETF =
has taken the "symbolic" step of declaring something Historic that =
people actually use, and for which there is not a readily available =
replacement that works better.  Historic has historically been used for =
things that aren't used anymore, or for things for which there's an =
obvious and readily available replacement.

That, and the 'no compromise' position of this draft's proponents - =
their unwillingness to try to build a strong consensus position - makes =
this look suspiciously like a denial-of-service attack.

> Changing the formal status of the RFCs is a symbolic step, but the =
real point is that it's now time for the reluctant ISPs to get their =
heads out of the sand.

It's a step in the wrong direction.  Not only does this "symbolic step" =
bring with it the potential for harm to current users of 6to4, it =
actually takes away some of the incentive for ISPs to get their heads =
out of the sand.  Meanwhile, it discourages the development of =
IPv6-based applications.

> You're correct that some ISPs will try to get monopoly rents out of
> the IPv4 shortage, and use CGN to capture customers in walled gardens,
> but fortunately capitalism provides a solution to such misbehaviour:
> other ISPs can deploy IPv6 as a competitive advantage.

Last mile (kilometer?) problems limit the ability of other ISPs to =
compete with established players, especially for consumer services.  But =
IETF can't do much about that.

Keith


From john-ietf@jck.com  Fri Jun 10 07:43:33 2011
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 A575911E80B9 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 07:43:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cdTvlkQp5TP9 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 07:43:32 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 4624311E80B7 for <ietf@ietf.org>; Fri, 10 Jun 2011 07:43:32 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QV2vr-000Ih3-G1; Fri, 10 Jun 2011 10:43:31 -0400
Date: Fri, 10 Jun 2011 10:43:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: one data point regarding native IPv6 support
Message-ID: <52581FF9790F6D396FB93E09@PST.JCK.COM>
In-Reply-To: <4DF21D7B.7040103@gmail.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@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: Fri, 10 Jun 2011 14:43:33 -0000

--On Saturday, June 11, 2011 01:34 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>...
> You're correct that some ISPs will try to get monopoly rents
> out of the IPv4 shortage, and use CGN to capture customers in
> walled gardens, but fortunately capitalism provides a solution
> to such misbehaviour: other ISPs can deploy IPv6 as a
> competitive advantage.

Sure.  Assuming that there is realistic competition, or a
realistic possibility of competition, in the relevant market.
Keith, Ned, and others have described a situation in which there
are few realistic choices of ISPs and the attitude of all of
them toward getting IPv6 deployed to endpoints runs from bad to
worse.  In that marketplace situation, capitalism is as likely
to predict a "no one goes first" outcome as it is to predict
that one of the ISPs will suddenly decide that deploying IPv6
will give them a competitive advantage... and give that
competitive advantage even after the additional training costs
for their own staffs, support costs for customers, equipment and
software, etc., are considered.

That situation really isn't much different than it was several
years ago.  If I'm in an area where competition is permitted,
I'm a large enough customer to be talking about dedicated fiber
to my premises in the multiple DS3 range or above, and I call up
my ISP (or my router vendors, or...) and say "sell me IPv6 or
I'm going to find it somewhere else", the threat is credible and
I'll probably set either them or their competitors scrambling.
If I'm in a situation that is closer to a SOHO one, in much of
the world there is no effective competition, I'm not seen as
having much leverage, and the scenario for my getting native
IPv6 is a lot more dependent on internal strategic decisions (or
wishful thinking) in those ISPs and not on competition issues
except very indirectly or at all.

   john


     john


From evnikita2@gmail.com  Fri Jun 10 07:46:17 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D56D211E80D6; Fri, 10 Jun 2011 07:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.438
X-Spam-Level: 
X-Spam-Status: No, score=-3.438 tagged_above=-999 required=5 tests=[AWL=0.161,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id poAr4y9mEmcF; Fri, 10 Jun 2011 07:46:17 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id D48B411E80B3; Fri, 10 Jun 2011 07:46:16 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1899435fxm.31 for <multiple recipients>; Fri, 10 Jun 2011 07:46:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bn555MlE8hADJqkrmlvg4GpDPC83OvLyPhggKCIYg5U=; b=IdVH27QkWlsYALKreAZDnDMZieXDrZzTBHWIlphK59OZCvD5GxB7KaFh/erAxcuqAW XqIj+XIv/PhUNSGnYAdZ90jH70Jr9f/p4Nu7yEctE7+RLxV3hVm3r9/Ihca0WM/44SwV 1XhUClK9dMfid58e66ZUcfoFNDa5fQuB7P3Cs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=X7tny8hUC4QmmC/THlHApLzntb5BcxuXj14Q6AuUnhIgLSe9kNm3M6yhYnKCyirXsv SEs7FQ3Bwzx2Et6PvXcEUaXz3UZrXnTG2I3syJFtLZc99eZ4GqUzylTC+S1kqyP65ShD n2cPwnQpNN5crQAz6pyPsPRbY+zdDH/xkli4A=
Received: by 10.223.143.20 with SMTP id s20mr2136733fau.10.1307717176001; Fri, 10 Jun 2011 07:46:16 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id l26sm1091043fah.14.2011.06.10.07.46.14 (version=SSLv3 cipher=OTHER); Fri, 10 Jun 2011 07:46:15 -0700 (PDT)
Message-ID: <4DF22E64.8030401@gmail.com>
Date: Fri, 10 Jun 2011 17:47:00 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-iesg-rfc1150bis-01.txt> (Conclusion of FYI RFC	Sub-series) to Informational RFC
References: <20110610131840.26851.83855.idtracker@ietfa.amsl.com>
In-Reply-To: <20110610131840.26851.83855.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg-secretary@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 14:46:18 -0000

Please consider these: 
http://www.rfc-editor.org/pipermail/rfc-interest/2011-June/002518.html 
and 
http://www.rfc-editor.org/pipermail/rfc-interest/2011-June/002519.html 
as Last Call comments.  Mykyta.

10.06.2011 16:18, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Conclusion of FYI RFC Sub-series'
>    <draft-iesg-rfc1150bis-01.txt>  as an Informational RFC
>
> [ . . . ]
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>


From alh-ietf@tndh.net  Fri Jun 10 09:03:57 2011
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 4AC6911E81FF for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 09:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.045
X-Spam-Level: *
X-Spam-Status: No, score=1.045 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YmGyS+CVKt1Y for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 09:03:56 -0700 (PDT)
Received: from tndh.net (unknown [50.46.43.186]) by ietfa.amsl.com (Postfix) with ESMTP id 8CDDE11E811E for <ietf@ietf.org>; Fri, 10 Jun 2011 09:03:56 -0700 (PDT)
X-AuthUser: alh-ietf@tndh.net
Received: from ahainW7 ([192.168.112.18]:36323) by tndh.net with [XMail 1.27 ESMTP Server] id <S18E5FAA> for <ietf@ietf.org> from <alh-ietf@tndh.net>; Fri, 10 Jun 2011 09:03:52 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'John C Klensin'" <john-ietf@jck.com>, "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>	<BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com>	<01O2A8KT5RZ600VHKR@mauve.mrochek.com>	<20110610005758.BC2D110ABF81@drugs.dv.isc.org>	<392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local>	<4DF21D7B.7040103@gmail.com> <52581FF9790F6D396FB93E09@PST.JCK.COM>
In-Reply-To: <52581FF9790F6D396FB93E09@PST.JCK.COM>
Subject: RE: one data point regarding native IPv6 support
Date: Fri, 10 Jun 2011 09:03:50 -0700
Message-ID: <117501cc2787$feb51410$fc1f3c30$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwnfNiV7A3q4dCMTV2c1uIxV2rOEAACHeoQ
Content-Language: en-us
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, 10 Jun 2011 16:03:57 -0000

Keith & John are hitting the crux of the issue here. The entire point of the
automated tunneling technologies was to enable application development and
deployment in the face of lethargic ISPs, that will refuse to move until
they see a set of credible applications running in the wild. None of them
will take the risk that the leap-of-faith requires without serious
competitive threat, and that simply doesn't exist. 

I am in the 'enviable' position where both ISP options available to me are
clueful and actually actively working on IPv6 deployments. That said, I am
still stuck with tunneling because the one option that could get me service
today can't keep their basic access network running (the other
work-from-home neighbors around me struggle with it regularly for IPv4), and
the one I use for service has decided to start their deployment of IPv6 in
larger markets (imagine that). 6to4 continues to serve me well for all but
the bone-headed places that have decided to boycott that prefix.

There is no real problem with 6to4, despite the BS being propagated about
failure rates. The fundamental problem is that those complaining have their
heads firmly stuck in IPv4-think, and are refusing to add a second 6to4
prefix to their service. If they would simply install their own 6to4 router
and be the tunnel endpoint, there would be no 3rd party in the path for
either direction. The technology is simply creating an opportunity. Those
complaining about it are refusing to take advantage of it because that would
be a different operational practice than they do for IPv4.

The herd mentality of kill-what-we-don't-like is not helping with
deployment. In fact the ability to document which ISPs have customers that
are trying to use IPv6 despite the edge lethargy is a very useful thing to
drive deployment through blame-&-shame. Put the 6to4-to-historic effort on
the shelf for at least 5 years. Then it will be time to talk.

Tony



> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> John C Klensin
> Sent: Friday, June 10, 2011 7:44 AM
> To: Brian E Carpenter
> Cc: IETF Discussion
> Subject: Re: one data point regarding native IPv6 support
> 
> 
> 
> --On Saturday, June 11, 2011 01:34 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
> >...
> > You're correct that some ISPs will try to get monopoly rents
> > out of the IPv4 shortage, and use CGN to capture customers in
> > walled gardens, but fortunately capitalism provides a solution
> > to such misbehaviour: other ISPs can deploy IPv6 as a
> > competitive advantage.
> 
> Sure.  Assuming that there is realistic competition, or a
> realistic possibility of competition, in the relevant market.
> Keith, Ned, and others have described a situation in which there
> are few realistic choices of ISPs and the attitude of all of
> them toward getting IPv6 deployed to endpoints runs from bad to
> worse.  In that marketplace situation, capitalism is as likely
> to predict a "no one goes first" outcome as it is to predict
> that one of the ISPs will suddenly decide that deploying IPv6
> will give them a competitive advantage... and give that
> competitive advantage even after the additional training costs
> for their own staffs, support costs for customers, equipment and
> software, etc., are considered.
> 
> That situation really isn't much different than it was several
> years ago.  If I'm in an area where competition is permitted,
> I'm a large enough customer to be talking about dedicated fiber
> to my premises in the multiple DS3 range or above, and I call up
> my ISP (or my router vendors, or...) and say "sell me IPv6 or
> I'm going to find it somewhere else", the threat is credible and
> I'll probably set either them or their competitors scrambling.
> If I'm in a situation that is closer to a SOHO one, in much of
> the world there is no effective competition, I'm not seen as
> having much leverage, and the scenario for my getting native
> IPv6 is a lot more dependent on internal strategic decisions (or
> wishful thinking) in those ISPs and not on competition issues
> except very indirectly or at all.
> 
>    john
> 
> 
>      john
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From lorenzo@google.com  Thu Jun  9 10:42:40 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB27811E812C for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 10:42:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S0IxwJP08IRo for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 10:42:40 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6550411E81BE for <ietf@ietf.org>; Thu,  9 Jun 2011 10:42:40 -0700 (PDT)
Received: from hpaq12.eem.corp.google.com (hpaq12.eem.corp.google.com [172.25.149.12]) by smtp-out.google.com with ESMTP id p59Hgd4A023173 for <ietf@ietf.org>; Thu, 9 Jun 2011 10:42:39 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1307641360; bh=T6MkxhKlW7q5q3R4HYlW74XmKl0=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=HRU89YyPjdPzipZCJnV1unhVROiEAAluO8/v6aaWHDnIrC6om6mzgIcjEhoED0fbD SEYJbx+1IUobOEx2rWCwA==
Received: from ywl2 (ywl2.prod.google.com [10.192.12.2]) by hpaq12.eem.corp.google.com with ESMTP id p59Heqc7008743 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 9 Jun 2011 10:42:37 -0700
Received: by ywl2 with SMTP id 2so1189252ywl.12 for <ietf@ietf.org>; Thu, 09 Jun 2011 10:42:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=TTa49wQJwHsNiTIedUP96nZM+KJ2gEy/spcn0oX02No=; b=uKkj3hzXdMt1OV2ZC/WkM/flBGGe0ZS3Q6FoCLKqc3t8AShokQu6nC7RMYKoHz474J AEGJguE3dOQVyX39bYuA==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=SzPsvbQYIZhI0g212YycmV4NjqSyDHnY8u5ZAOe21VQ1z7heNlNHVZ6FCUof3L+b8W DChiFIXVpwDc+3kZ6IiA==
Received: by 10.151.86.3 with SMTP id o3mr2376293ybl.150.1307641357160; Thu, 09 Jun 2011 10:42:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.95.20 with HTTP; Thu, 9 Jun 2011 10:42:17 -0700 (PDT)
In-Reply-To: <ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org> <ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Jun 2011 10:42:17 -0700
Message-ID: <BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=000e0cd28fee96504804a54afa79
X-System-Of-Record: true
X-Mailman-Approved-At: Fri, 10 Jun 2011 09:11:39 -0700
Cc: IPv6 Operations Working Group <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 17:42:40 -0000

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

On Tue, Jun 7, 2011 at 11:20 AM, Keith Moore <moore@network-heretics.com>wrote:

> Indeed, that is one of its main virtues.  6to4 decouples application
> deployment of v6 from network deployment of v6, and helps reduce the
> "chicken or egg" problem.
>

No, it does not - in fact, it is the opposite.

Geoff has presented data that shows that anycasted 6to4 as a connectivity
mechanism has a failure rate of the order of 20-30%. We have data that
clearly shows that Mac OS 10.6.4, which uses 6to4 by default, has a ~50x
greater failure rate when connecting to dual-stack servers than Mac OS
10.6.5 - and the only change is to not use 6to4 by default. Search the list
archives for details.

So the existence of 6to4 is in itself a significant barrier for IPv6
deployment for server operators and content providers. And if you believe
the access networks, the lack of IPv6 content is one of the most significant
barriers to IPv6 deployment in access networks.

Application developers should develop using manually configured tunnels, not
6to4. At least they don't have a 20% failure rate.

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

<div class=3D"gmail_quote">On Tue, Jun 7, 2011 at 11:20 AM, Keith Moore <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com">moore@netw=
ork-heretics.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">Indeed, that is one of its main virtues. =A06to4 decouple=
s application deployment of v6 from network deployment of v6, and helps red=
uce the &quot;chicken or egg&quot; problem.</div></blockquote><div><br></di=
v>

<div>No, it does not - in fact, it is the opposite.</div><div><br></div><di=
v>Geoff has presented data that shows that anycasted 6to4 as a connectivity=
 mechanism has a failure rate of the order of 20-30%. We have data that cle=
arly shows that Mac OS 10.6.4, which uses 6to4 by default, has a ~50x great=
er failure rate when connecting to dual-stack servers than Mac OS 10.6.5 - =
and the only change is to not use 6to4 by default. Search the list archives=
 for details.</div>

<div><br></div><div><meta http-equiv=3D"content-type" content=3D"text/html;=
 charset=3Dutf-8"><div>So the existence of 6to4 is in itself a significant =
barrier for IPv6 deployment for server operators and content providers. And=
 if you believe the access networks, the lack of IPv6 content is one of the=
 most significant barriers to IPv6 deployment in access networks.</div>

<div><br></div><div>Application developers should develop using manually co=
nfigured tunnels, not 6to4. At least they don&#39;t have a 20% failure rate=
.</div></div></div>

--000e0cd28fee96504804a54afa79--

From lorenzo@google.com  Thu Jun  9 11:00:29 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9EBC11E81E5 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 11:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mObbDeN3kU2w for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 11:00:29 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 13E1F11E81FB for <ietf@ietf.org>; Thu,  9 Jun 2011 11:00:06 -0700 (PDT)
Received: from wpaz21.hot.corp.google.com (wpaz21.hot.corp.google.com [172.24.198.85]) by smtp-out.google.com with ESMTP id p59I05ii019557 for <ietf@ietf.org>; Thu, 9 Jun 2011 11:00:05 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1307642405; bh=GGEIZvHkvdC1lTwVtd1ona/is/Y=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=dRUFuRCeGDYJVLojdU8MoeTvyywHaEajehE+j3nbIWsypMbbWPJJyw0ZWr+pJjX8+ 5vrVFK/ISDg8ObV/KpVTg==
Received: from yie19 (yie19.prod.google.com [10.243.66.19]) by wpaz21.hot.corp.google.com with ESMTP id p59Hth2b007527 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 9 Jun 2011 11:00:03 -0700
Received: by yie19 with SMTP id 19so1323673yie.2 for <ietf@ietf.org>; Thu, 09 Jun 2011 11:00:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=8aubcWvimXpHlG20i/IcdVljNEnI6GWfGWGL7dtVh08=; b=kmrIUr/x3jWpVby3SNzGP0gf0o45mt6FS08Nzr/wRFXUX0zs1T8IydmrJj6w8NFQTr +XrZcRFzqsgMrrdafB5w==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=JJqR1LSha5illt6wpYAdRV1tNPSml5F8DenZL6GsPQNEmupjbPcbjkC3+xyibsXMoq RjcbypB9Md9h2QhP0WIg==
Received: by 10.150.7.15 with SMTP id 15mr2184378ybg.378.1307642403106; Thu, 09 Jun 2011 11:00:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.95.20 with HTTP; Thu, 9 Jun 2011 10:59:42 -0700 (PDT)
In-Reply-To: <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Jun 2011 10:59:42 -0700
Message-ID: <BANLkTik8s9PHbPi-5rvB=xaCJG+BnrQXrgGh+cZGOp-ZVnYMzw@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=000e0cd28788ee2fb204a54b38c7
X-System-Of-Record: true
X-Mailman-Approved-At: Fri, 10 Jun 2011 09:11:39 -0700
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "George, Wesley" <wesley.george@twcable.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, 09 Jun 2011 18:00:29 -0000

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

On Tue, Jun 7, 2011 at 3:47 PM, Keith Moore <moore@network-heretics.com>wrote:

> Why are you trying to make life harder for developers of IPv6 applications?
>  There's no reason at all that an application developer should have to set
> up a special-purpose network just to test an IPv6 application.
>

No, we're trying to make their lives easier, by suggesting they use
something that actually *works*.


> Realistic testing of applications needs to be done on real networks, or a
> least an approximation to real networks.  Testing IPv6 using 6to4 over
> public IPv4 obviously isn't perfect, but it's a hell of a lot more realistic
> than setting up a lab network and confining one's testing to that.
>

So use a tunnel broker.


> You're missing something.   I can connect directly from my mobile laptop to
> a machine in my home network using 6to4.
>

Really? From where? On none of the networks my laptop connects to do I get a
public IPv4 address. Some of them do give me have native IPv6 or
manually-tunneled IPv6 though.

We can disagree about the meaning of the word "widespread", but the
> practical fact is that you can't expect people to give up something that
> works for them until you can provide them something that works better *for
> them.  "Available to 50% of Internet service customers" is equivalent to a
> very small percent probability of native connectivity being able to replace
> 6to4 connectivity in a scenario where 6to4 is currently working.  And the
> more hosts involved, the smaller that probability is. *
>

You cannot claim that 6to4 is "working" when there is data that shows that
it has a 20% failure rate. If we had that sort of connectivity in IPv4, we
wouldn't have an Internet.


> Existing "content providers" are not going to drive adoption of IPv6.
> They're going to follow it.
>

Nope. Look at World IPv6 day. If you look at the list of participaints, I'd
say that probably more than 10% of Internet content, either by bits or by
query volume, is ready for IPv6 now. Our data shows that access is at 0.3%.
So you could say that in fact content *is* driving adoption of IPv6. We just
need to get unreliable tunneled connectivity out of the way so we can turn
it on for real.


>  Web and email will be the last applications to migrate.
>

Um, no. See above.

> WEG> Well, it'd be more harmful if there weren't alternatives.
>
>
> There aren't any good ones.  Teredo and configured tunnels are worse in
> many ways; though they each have their use cases.
>

Actually, configured tunnels are much better. They have a much lower failure
rate and lower latency. We published data that shows the latency impact in
our PAM 2009 paper.

Regards,
Lorenzo

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

<div class=3D"gmail_quote">On Tue, Jun 7, 2011 at 3:47 PM, Keith Moore <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com" target=3D"_=
blank">moore@network-heretics.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">


<div style=3D"word-wrap:break-word"><div>Why are you trying to make life ha=
rder for developers of IPv6 applications? =A0There&#39;s no reason at all t=
hat an application developer should have to set up a special-purpose networ=
k just to test an IPv6 application.=A0</div>


</div></blockquote><div><br></div><div>No, we&#39;re trying to make their l=
ives easier, by suggesting they use something that actually *works*.</div><=
div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">


<div style=3D"word-wrap:break-word"><div><div>Realistic testing of applicat=
ions needs to be done on real networks, or a least an approximation to real=
 networks. =A0Testing IPv6 using 6to4 over public IPv4 obviously isn&#39;t =
perfect, but it&#39;s a hell of a lot more realistic than setting up a lab =
network and confining one&#39;s testing to that.</div>


</div></div></blockquote><div><br></div><div>So use a tunnel broker.</div><=
div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-w=
ord">


<div>You&#39;re missing something. =A0 I can connect directly from my mobil=
e laptop to a machine in my home network using 6to4.</div></div></blockquot=
e><div><br></div><div>Really? From where? On none of the networks my laptop=
 connects to do I get a public IPv4 address. Some of them do give me have n=
ative IPv6 or manually-tunneled IPv6 though.</div>


<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break=
-word"><div>We can disagree about the meaning of the word &quot;widespread&=
quot;, but the practical fact is that you can&#39;t expect people to give u=
p something that works for them until you can provide them something that w=
orks better <i>for them. =A0&quot;<span style=3D"font-style:normal">Availab=
le to 50% of Internet service customers&quot; is equivalent to a very small=
 percent probability of native connectivity being able to replace 6to4 conn=
ectivity in a scenario where 6to4 is currently working. =A0And the more hos=
ts involved, the smaller that probability is.=A0</span></i></div>


</div></blockquote><div><br></div><div>You cannot claim that 6to4 is &quot;=
working&quot; when there is data that shows that it has a 20% failure rate.=
 If we had that sort of connectivity in IPv4, we wouldn&#39;t have an Inter=
net.</div>


<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-=
word"><div>Existing &quot;content providers&quot; are not going to drive ad=
option of IPv6. =A0 They&#39;re going to follow it.</div>


</div></blockquote><div><br></div><div>Nope. Look at World IPv6 day. If you=
 look at the list of participaints, I&#39;d say that probably more than 10%=
 of Internet content, either by bits or by query volume, is ready for IPv6 =
now. Our data shows that access is at 0.3%. So you could say that in fact c=
ontent *is* driving adoption of IPv6. We just need to get unreliable tunnel=
ed connectivity out of the way so we can turn it on for real.</div>


<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-=
word"><div> =A0Web and email will be the last applications to migrate.</div=
></div>


</blockquote><div><br></div><div>Um, no. See above.</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div style=3D"word-wrap:break-word"><div><div><blockquote typ=
e=3D"cite">


<div>WEG&gt; Well, it&#39;d be more harmful if there weren&#39;t alternativ=
es.</div></blockquote></div></div><div><div><div><br></div></div><div>There=
 aren&#39;t any good ones. =A0Teredo and configured tunnels are worse in ma=
ny ways; though they each have their use cases. =A0=A0</div>


</div></div></blockquote><div><br></div><div>Actually, configured tunnels a=
re much better. They have a much lower failure rate and lower latency. We p=
ublished data that shows the latency impact in our PAM 2009 paper.</div>

<div><br></div><div>Regards,</div><div>Lorenzo</div>
</div>

--000e0cd28788ee2fb204a54b38c7--

From lorenzo@google.com  Thu Jun  9 11:11:18 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9CA11E80D3 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 11:11:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fqjKA8qMWS2M for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 11:10:52 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 31EDE11E8130 for <ietf@ietf.org>; Thu,  9 Jun 2011 11:10:51 -0700 (PDT)
Received: from wpaz29.hot.corp.google.com (wpaz29.hot.corp.google.com [172.24.198.93]) by smtp-out.google.com with ESMTP id p59IAcaJ005537 for <ietf@ietf.org>; Thu, 9 Jun 2011 11:10:38 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1307643038; bh=Td5nNzknJeZhpOaY7uSrKSDeaPw=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=haJKokUQnIWLVxowhSct5TEcb39BMlhgyFwItMoBmxudMb/CiYKYv9jpaOBmFsglU nHvCOBclBvZiVFmWo7byQ==
Received: from yib17 (yib17.prod.google.com [10.243.65.81]) by wpaz29.hot.corp.google.com with ESMTP id p59IAbo5003707 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 9 Jun 2011 11:10:37 -0700
Received: by yib17 with SMTP id 17so1269707yib.8 for <ietf@ietf.org>; Thu, 09 Jun 2011 11:10:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=T/0mwUxCnSFBcwdprxowvsMq/uvHysIXYXl2nkndiYA=; b=hqeOSIE1aAYw58m3vxWm4qmKwFzi+U3Eu05EZ6nnG2Xg9cwn/PQrZynE6BnPJdAyAF njZmeLtnhk+DbeiU9nlg==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=F/9LoErnd0Oq4ZU+ebG6HnmksVWt0LQtH77Tgi4AG+kqLdSI7kNfZUnYizAk2U3BVI BU36rDe3UO4DeB4OangA==
Received: by 10.150.195.18 with SMTP id s18mr2211619ybf.207.1307643037121; Thu, 09 Jun 2011 11:10:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.95.20 with HTTP; Thu, 9 Jun 2011 11:10:17 -0700 (PDT)
In-Reply-To: <C58AF2D7-C362-4A76-BD59-F6B78C6746B0@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB0690A2B5@PRVPEXVS04.corp.twcable.com> <C58AF2D7-C362-4A76-BD59-F6B78C6746B0@network-heretics.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Jun 2011 11:10:17 -0700
Message-ID: <BANLkTi=ds=7bAhUMD+vY_d0AQ1uOS2X+v+iXBBknD_ZDfWCpjQ@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=000e0cd4d83cb87ba304a54b5eb5
X-System-Of-Record: true
X-Mailman-Approved-At: Fri, 10 Jun 2011 09:11:39 -0700
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "George, Wesley" <wesley.george@twcable.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, 09 Jun 2011 18:11:24 -0000

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

On Wed, Jun 8, 2011 at 1:19 PM, Keith Moore <moore@network-heretics.com>wrote:

> Again, 40-something percent of the IPv6 traffic that is observed on the net
> today uses 6to4.
>

Please point at the data behind that assertion. In many cases in the past,
such assertions have comes from networks that do not have the hardware
capabilities to monitor native IPv6 traffic. I remember one case at the RIPE
meeting where someone from AMS-IX observed about one of these presentations,
"I have more native IPv6 traffic on my exchange point than you have observed
in the entire Internet. How is that possible?" Needless to say, that
presentation did not go well.

Look at http://www.google.com/intl/en/ipv6/statistics/ That obviously does
not see peer-to-peer traffic, but it does see IPv6 web clients, and just
under 90% of those are native.

The evidence is that people are using it.  You're trying to subject it to
> test cases that are largely meaningless - because in those cases IPv6 (of
> any kind) provides no marginal value in the near term.
>

So far, you have provided solid evidence that *you* use it, but not solid
evidence that "people" are using it. Can you point to that evidence?


> Almost all usage of IPv6 today is in spite of ISPs.   For that matter, a
> great many successful IPv4 applications today are deployed in spite of ISPs.
>  Again, ISPs in general have let us down, and 6to4 and Teredo are carrying
> ~90% of IPv6 traffic.   ISPs are not in a good position to demand that 6to4
> be deprecated.
>

Nope. As before, 90% of IPv6 is native, and it comes from a small number of
large deployments. Maybe your ISP doesn't support it, but other ISPs do.


> It's not one versus the other.   6to4 is helping to promote ubiquitous
> IPv6.
>

No, it is a barrier to ubiquitous IPv6 adoption.

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

<div class=3D"gmail_quote">On Wed, Jun 8, 2011 at 1:19 PM, Keith Moore <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com">moore@netwo=
rk-heretics.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style=3D"word-wrap:break-word"><div>Again, 40-something percent of the=
 IPv6 traffic that is observed on the net today uses 6to4.</div></div></blo=
ckquote><div><br></div><div>Please point at the data behind that assertion.=
 In many cases in the past, such assertions have comes from networks that d=
o not have the hardware capabilities to monitor native IPv6 traffic. I reme=
mber one case at the RIPE meeting where someone from AMS-IX observed about =
one of these presentations, &quot;I have more native IPv6 traffic on my exc=
hange point than you have observed in the entire Internet. How is that poss=
ible?&quot; Needless to say, that presentation did not go well.</div>

<div><br></div><div>Look at <a href=3D"http://www.google.com/intl/en/ipv6/s=
tatistics/">http://www.google.com/intl/en/ipv6/statistics/</a> That obvious=
ly does not see peer-to-peer traffic, but it does see IPv6 web clients, and=
 just under 90% of those are native.</div>

<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;"><div style=3D"word-wrap:brea=
k-word"><div>The evidence is that people are using it. =A0You&#39;re trying=
 to subject it to test cases that are largely meaningless - because in thos=
e cases IPv6 (of any kind) provides no marginal value in the near term.</di=
v>

</div></blockquote><div><br></div><div>So far, you have provided solid evid=
ence that *you* use it, but not solid evidence that &quot;people&quot; are =
using it. Can you point to that evidence?</div><div>=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex;">

<div style=3D"word-wrap:break-word"><div><div class=3D"im">Almost all usage=
 of IPv6 today is in spite of ISPs. =A0 For that matter, a great many succe=
ssful IPv4 applications today are deployed in spite of ISPs. =A0Again, ISPs=
 in general have let us down, and 6to4 and Teredo are carrying ~90% of IPv6=
 traffic. =A0 ISPs are not in a good position to demand that 6to4 be deprec=
ated. =A0</div>

</div></div></blockquote><div><br></div><div>Nope. As before, 90% of IPv6 i=
s native, and it comes from a small number of large deployments. Maybe your=
 ISP doesn&#39;t support it, but other ISPs do.</div><div>=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex;">

<div style=3D"word-wrap:break-word"><div>It&#39;s not one versus the other.=
 =A0 6to4 is helping to promote ubiquitous IPv6.</div></div></blockquote><d=
iv><br></div><div>No, it is a barrier to ubiquitous IPv6 adoption.</div></d=
iv>


--000e0cd4d83cb87ba304a54b5eb5--

From lorenzo@google.com  Thu Jun  9 11:20:30 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D2AD11E8130 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 11:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TTdqmI8aXxTC for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 11:20:30 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id E647A11E81C8 for <ietf@ietf.org>; Thu,  9 Jun 2011 11:20:29 -0700 (PDT)
Received: from kpbe20.cbf.corp.google.com (kpbe20.cbf.corp.google.com [172.25.105.84]) by smtp-out.google.com with ESMTP id p59IKNSW023154 for <ietf@ietf.org>; Thu, 9 Jun 2011 11:20:24 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1307643624; bh=1VesNEVkML4j63VbRAi5728Ppv0=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=CeqZPwu+YpQkjs9CbOim3bShiHWEdvTt+5IwyS1Erx+Y87593E7c3c2ahvF6xFgxG 4htw3lxQFTtjZ129OXe2g==
Received: from ywo7 (ywo7.prod.google.com [10.192.15.7]) by kpbe20.cbf.corp.google.com with ESMTP id p59IJBs0028782 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 9 Jun 2011 11:20:22 -0700
Received: by ywo7 with SMTP id 7so1974336ywo.25 for <ietf@ietf.org>; Thu, 09 Jun 2011 11:20:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=br6F0TJ2UVxjNzX64Aity0SMmDbtqwSnX3X6/QUO2oQ=; b=h/GqfzTe8XlNo9N5DnszA7nbemEIOh1yCFE08Vp+twWHvIexTStrzdCqC7dd5qxJL+ ALteWlTjZr71mR1lc01A==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=mHbY5Aqu5z7CJayKJY8Qt6ViW3iNCL91o9M2yQvY0P13xQ+DHG3WbOp2rMwao0wdiw UagyMtzeYz7nK/e7TV8g==
Received: by 10.151.86.3 with SMTP id o3mr2419927ybl.150.1307643622102; Thu, 09 Jun 2011 11:20:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.95.20 with HTTP; Thu, 9 Jun 2011 11:20:02 -0700 (PDT)
In-Reply-To: <BD885BE1-F275-46E9-8122-60E0725F8B86@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org> <ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com> <BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com> <BD885BE1-F275-46E9-8122-60E0725F8B86@network-heretics.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Jun 2011 11:20:02 -0700
Message-ID: <BANLkTi=3LxgdDSe=rE7PPW6uFWPmQvfNUDr6JiSbZ07Zmb6LTw@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=000e0cd28fee9695e404a54b81e8
X-System-Of-Record: true
X-Mailman-Approved-At: Fri, 10 Jun 2011 09:11:39 -0700
Cc: IPv6 Operations Working Group <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 18:20:30 -0000

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

On Thu, Jun 9, 2011 at 10:57 AM, Keith Moore <moore@network-heretics.com>wrote:

> So the existence of 6to4 is in itself a significant barrier for IPv6
> deployment for server operators and content providers.
>
> non sequitur.   Existing server operators and content providers can easily
> provide 6to4 addresses for their servers and content, which will be used in
> preference to native v6 addresses.
>

No. According to Geoff's data, one of the main reasons 6to4 fails is a
firewall that blocks IPv4 protocol 41 traffic. Even if content providers
published 6to4 addresses, those connections would still fail.


> Application developers should develop using manually configured tunnels,
> not 6to4. At least they don't have a 20% failure rate.
>
> How do you know?  How do you even measure the failure rate of manually
> configured tunnels in the aggregate?
>

In a similar way as Geoff measured 6to4 - looking at SYNs. I suspect that
the answer will be that much fewer users have configured tunnels than 6to4,
and that the failure rate is much lower.


>  I don't think you can monitor that kind of traffic the way you can 6to4,
> because the traffic patterns are much more constrained.   It's been awhile
> since I used manually configured tunnels (from a well-known tunnel broker).
>  But the one time I did try them, 6to4 worked better overall - lower latency
> and lower failure rate.
>

Please try again. You will be pleasantly surprised.

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

<div class=3D"gmail_quote">On Thu, Jun 9, 2011 at 10:57 AM, Keith Moore <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com">moore@netw=
ork-heretics.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style=3D"word-wrap:break-word"><div><div class=3D"im"><blockquote type=
=3D"cite"><div class=3D"gmail_quote"><div><div>So the existence of 6to4 is =
in itself a significant barrier for IPv6 deployment for server operators an=
d content providers.</div>

</div></div></blockquote></div>non sequitur. =A0 Existing server operators =
and content providers can easily provide 6to4 addresses for their servers a=
nd content, which will be used in preference to native v6 addresses.</div>

</div></blockquote><div><br></div><div>No. According to Geoff&#39;s data, o=
ne of the main reasons 6to4 fails is a firewall that blocks IPv4 protocol 4=
1 traffic. Even if content providers published 6to4 addresses, those connec=
tions would still fail.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div style=3D"word-wrap:break=
-word"><div><div class=3D"im"><blockquote type=3D"cite"><div class=3D"gmail=
_quote"><div>

<div>Application developers should develop using manually configured tunnel=
s, not 6to4. At least they don&#39;t have a 20% failure rate.</div></div></=
div></blockquote></div></div><div>How do you know? =A0How do you even measu=
re the failure rate of manually configured tunnels in the aggregate?</div>

</div></blockquote><div><br></div><div>In a similar way as Geoff measured 6=
to4 - looking at SYNs. I suspect that the answer will be that much fewer us=
ers have configured tunnels than 6to4, and that the failure rate is much lo=
wer.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;"><div style=3D"word-wrap:break=
-word"><div> =A0I don&#39;t think you can monitor that kind of traffic the =
way you can 6to4, because the traffic patterns are much more constrained. =
=A0 It&#39;s been awhile since I used manually configured tunnels (from a w=
ell-known tunnel broker). =A0But the one time I did try them, 6to4 worked b=
etter overall - lower latency and lower failure rate.</div>

</div></blockquote><div><br></div><div>Please try again. You will be pleasa=
ntly surprised.=A0</div></div>

--000e0cd28fee9695e404a54b81e8--

From lorenzo@google.com  Thu Jun  9 11:46:17 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4E8E11E8106 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 11:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6YEx6c0y7Sto for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 11:46:16 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2D67511E8089 for <ietf@ietf.org>; Thu,  9 Jun 2011 11:46:15 -0700 (PDT)
Received: from kpbe17.cbf.corp.google.com (kpbe17.cbf.corp.google.com [172.25.105.81]) by smtp-out.google.com with ESMTP id p59IkFu7000742 for <ietf@ietf.org>; Thu, 9 Jun 2011 11:46:15 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1307645175; bh=2d8jA+tnkAxaFNA0UFhm/qtqx9A=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=patYUy5mgXnVkCe22He70lU+y9fhkLC0AP+ZaX7TkyN2kuPnAbZudtY3Z1lZhtKgA 8g9v6WR0qj5Q56wQkzvog==
Received: from gxk19 (gxk19.prod.google.com [10.202.11.19]) by kpbe17.cbf.corp.google.com with ESMTP id p59IjmYk013964 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 9 Jun 2011 11:46:14 -0700
Received: by gxk19 with SMTP id 19so1499303gxk.17 for <ietf@ietf.org>; Thu, 09 Jun 2011 11:46:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=yDkAjAygetx1YZoAXnJH4TxFkKVgKswkNI0Uqc122Hg=; b=tnhCNo972Pl0Ji4snwub+5Y14F5v+lj98Y3RnC35aGY4xcVxrM7F4/8poZjij+R7Nz ZhgjJXw7N6mc2EjUzsIQ==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=BGxgIbkuwROW/5zvOQjXaEmDkhLCbMt7iLz0I//yTMUqLPRV8OPGHluqxN577yAFWG 46XI/t5oqBPQI9mLLddQ==
Received: by 10.150.7.15 with SMTP id 15mr2232992ybg.378.1307645174110; Thu, 09 Jun 2011 11:46:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.95.20 with HTTP; Thu, 9 Jun 2011 11:45:54 -0700 (PDT)
In-Reply-To: <E197F05C-BE22-4431-897B-FFE2E2CB1F0E@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org> <ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com> <BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com> <BD885BE1-F275-46E9-8122-60E0725F8B86@network-heretics.com> <BANLkTi=3LxgdDSe=rE7PPW6uFWPmQvfNUDr6JiSbZ07Zmb6LTw@mail.gmail.com> <E197F05C-BE22-4431-897B-FFE2E2CB1F0E@network-heretics.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Jun 2011 11:45:54 -0700
Message-ID: <BANLkTi=_bGLqAWZ+EBGV75Exv2v0PNpNzpf6Ofhx=EiShC7zcQ@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=000e0cd28788185ae104a54bde25
X-System-Of-Record: true
X-Mailman-Approved-At: Fri, 10 Jun 2011 09:11:39 -0700
Cc: IPv6 Operations Working Group <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 18:46:18 -0000

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

On Thu, Jun 9, 2011 at 11:37 AM, Keith Moore <moore@network-heretics.com>wrote:

> I suppose we should just tunnel the whole IPv6 network over IPv4 + HTTP
> then.
>
> Seriously, the argument that 6to4 should be trashed because ISPs are
> blocking tunnels has the flavor of "don't solve the problem, but rather,
> stamp out the solution".
>

Actually, this mostly happens in enterprise networks and universities. I
don't see why they would want to change this compared to, say, actually
deploying native IPv6.

In a similar way as Geoff measured 6to4 - looking at SYNs.
>
>
> From where?   Again, the tunnels aren't taking the variety of paths that
> 6to4 connections are.  It's that variety that makes measurements such as
> Geoff's at all useful - it's what lets you at least believe that the
> measurements made at a few points are representative of the whole.
>

>From the same place that he ran the 6to4 measurements from?


> A few months ago I was trying to set one up, but I ran out of time.   I'm
> really busy these days, and it's nowhere nearly as easy to set up a
> configured tunnel as it is to set up 6to4.
>

Go to http://tunnelbroker.net/ . I'm willing to bet that it will take a lot
less time than you have spent writing email on this thread. :-)

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

<div class=3D"gmail_quote">On Thu, Jun 9, 2011 at 11:37 AM, Keith Moore <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com">moore@netw=
ork-heretics.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style=3D"word-wrap:break-word"><div class=3D"im"><div><div>I suppose w=
e should just tunnel the whole IPv6 network over IPv4 + HTTP then.</div></d=
iv></div><div><br></div><div>Seriously, the argument that 6to4 should be tr=
ashed because ISPs are blocking tunnels has the flavor of &quot;don&#39;t s=
olve the problem, but rather, stamp out the solution&quot;.=A0</div>

</div></blockquote><div><br></div><div>Actually, this mostly happens in ent=
erprise networks and universities. I don&#39;t see why they would want to c=
hange this compared to, say, actually deploying native IPv6.</div><div>

<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex;"><div style=3D"word-wrap:break-wor=
d"><div><div class=3D"im"><blockquote type=3D"cite"><div class=3D"gmail_quo=
te"><div>

In a similar way as Geoff measured 6to4 - looking at SYNs.</div></div></blo=
ckquote><div><br></div></div><div>From where? =A0 Again, the tunnels aren&#=
39;t taking the variety of paths that 6to4 connections are. =A0It&#39;s tha=
t variety that makes measurements such as Geoff&#39;s at all useful - it&#3=
9;s what lets you at least believe that the measurements made at a few poin=
ts are representative of the whole.</div>

</div></div></blockquote><div><br></div><div>From the same place that he ra=
n the 6to4 measurements from?</div><div>=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex;">

<div style=3D"word-wrap:break-word"><div><div class=3D"im"><div>A few month=
s ago I was trying to set one up, but I ran out of time. =A0 I&#39;m really=
 busy these days, and it&#39;s nowhere nearly as easy to set up a configure=
d tunnel as it is to set up 6to4.</div>

</div></div></div></blockquote><div><br></div><div>Go to <a href=3D"http://=
tunnelbroker.net/">http://tunnelbroker.net/</a> . I&#39;m willing to bet th=
at it will take a lot less time than you have spent writing email on this t=
hread. :-)</div>

</div>

--000e0cd28788185ae104a54bde25--

From lorenzo@google.com  Thu Jun  9 12:04:18 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4FC211E8213 for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 12:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6ZfBoQzHoQc for <ietf@ietfa.amsl.com>; Thu,  9 Jun 2011 12:04:18 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id C5B5B11E8199 for <ietf@ietf.org>; Thu,  9 Jun 2011 12:04:17 -0700 (PDT)
Received: from hpaq5.eem.corp.google.com (hpaq5.eem.corp.google.com [172.25.149.5]) by smtp-out.google.com with ESMTP id p59J4GhR023358 for <ietf@ietf.org>; Thu, 9 Jun 2011 12:04:16 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1307646256; bh=vceBpKhIZ/wiky+RonlHf55viM8=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=EFguA/psVaDWaS/qXafexdg8zLx04jbNIVgJ4kOi6+ymKueV10N6B40nTZb8QrR5x r4zsrJxgJGcuM7sbRo1zg==
Received: from gxk7 (gxk7.prod.google.com [10.202.11.7]) by hpaq5.eem.corp.google.com with ESMTP id p59J3r3E022239 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 9 Jun 2011 12:04:15 -0700
Received: by gxk7 with SMTP id 7so1410536gxk.7 for <ietf@ietf.org>; Thu, 09 Jun 2011 12:04:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=2YDh8vN1YHly0VfHteGcU6qgSouyrkrpxLSnsTtn3wU=; b=QW0ktBOXMg+gGoqZ1Kv3LNXmkXMEV/YNQ+MbCvPeP/QQ0APe89DdQ0bFLHtXPQFJfe z2qjufO6VONvlelPr5Wg==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=kIQJqe7AcnNrKg8igpU0ZQ2xNnuQudV8TWrAaGnHQ5nWPAEZdopZ3tvoCrsnDuxaJi zU5NymZBnlDXjnRjp7AA==
Received: by 10.151.86.3 with SMTP id o3mr2469788ybl.150.1307646255347; Thu, 09 Jun 2011 12:04:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.95.20 with HTTP; Thu, 9 Jun 2011 12:03:55 -0700 (PDT)
In-Reply-To: <4DF1186E.7080902@gmail.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org> <ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com> <BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com> <BD885BE1-F275-46E9-8122-60E0725F8B86@network-heretics.com> <BANLkTi=3LxgdDSe=rE7PPW6uFWPmQvfNUDr6JiSbZ07Zmb6LTw@mail.gmail.com> <4DF1186E.7080902@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Jun 2011 12:03:55 -0700
Message-ID: <BANLkTimeYWS8m=+eOObo21GUbaWvQLdAoQSNU8MAA6V3J1UPaQ@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=000e0cd28fee8ab81d04a54c1e60
X-System-Of-Record: true
X-Mailman-Approved-At: Fri, 10 Jun 2011 09:11:39 -0700
Cc: IPv6 Operations Working Group <v6ops@ietf.org>, Keith Moore <moore@network-heretics.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2011 19:04:18 -0000

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

On Thu, Jun 9, 2011 at 12:01 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> > In a similar way as Geoff measured 6to4 - looking at SYNs. I suspect that
> > the answer will be that much fewer users have configured tunnels than
> 6to4,
> > and that the failure rate is much lower.
>
> Er, I'm currently on 2001:388:f000::xxxx
> Do you have an algorithm that will tell you whether that is native
> or a configured tunnel?


Not perfectly. But you can look at things like MSS and MTU.

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

<div class=3D"gmail_quote">On Thu, Jun 9, 2011 at 12:01 PM, Brian E Carpent=
er <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">bri=
an.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex;">

<div class=3D"im">&gt; In a similar way as Geoff measured 6to4 - looking at=
 SYNs. I suspect that<br>
&gt; the answer will be that much fewer users have configured tunnels than =
6to4,<br>
&gt; and that the failure rate is much lower.<br>
<br>
</div>Er, I&#39;m currently on 2001:388:f000::xxxx<br>
Do you have an algorithm that will tell you whether that is native<br>
or a configured tunnel?</blockquote><div><br></div><div>Not perfectly. But =
you can look at things like MSS and MTU.=A0</div></div>

--000e0cd28fee8ab81d04a54c1e60--

From dworley@avaya.com  Fri Jun 10 09:12:08 2011
Return-Path: <dworley@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 EB6941F0C6E for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 09:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.549
X-Spam-Level: 
X-Spam-Status: No, score=-103.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LTZcttfTkgd2 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 09:12:07 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 05D081F0C74 for <ietf@ietf.org>; Fri, 10 Jun 2011 09:12:04 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAJNA8k2HCzI1/2dsb2JhbABSpkV3qjMCm0GGIwSWFosI
X-IronPort-AV: E=Sophos;i="4.65,348,1304308800"; d="scan'208";a="250791272"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 10 Jun 2011 12:12:03 -0400
X-IronPort-AV: E=Sophos;i="4.65,348,1304308800"; d="scan'208";a="661849859"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 10 Jun 2011 12:12:02 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.192]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Fri, 10 Jun 2011 12:12:01 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: John C Klensin <john-ietf@jck.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Fri, 10 Jun 2011 12:10:21 -0400
Subject: RE: one data point regarding native IPv6 support
Thread-Topic: one data point regarding native IPv6 support
Thread-Index: AcwnfNtJg5zm/TX7TryA3wPwJDSfTAADAp/e
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222907E9C2@DC-US1MBEX4.global.avaya.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@gmail.com>,<52581FF9790F6D396FB93E09@PST.JCK.COM>
In-Reply-To: <52581FF9790F6D396FB93E09@PST.JCK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 10 Jun 2011 16:12:08 -0000

OTOH, my cable ISP provider has an "Expected IPv6 Transition Phases" chart,=
 in which Phase 3 says, "Customer Premesis Equipment (CPE) IP addressing:  =
IPv6 only".  And they've started trials of IPv6 already.

Dale

From nsb@guppylake.com  Fri Jun 10 09:16:18 2011
Return-Path: <nsb@guppylake.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 060C81F0C59 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 09:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o0ERzCAZ9di0 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 09:16:17 -0700 (PDT)
Received: from server1.netnutz.com (server1.netnutz.com [72.233.90.3]) by ietfa.amsl.com (Postfix) with ESMTP id 5AA5A1F0C80 for <ietf@ietf.org>; Fri, 10 Jun 2011 09:16:10 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=guppylake.com; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer; b=g0947VoEL19LyVBxGhEto9RuEJukTiO1aM7TSzfJvNaz6x16vAd7P0qBY3AoMsv+Ok2fqVYezbp25Nk1P7e2i9Ba4OWXWf4ATgIeL/22yVQAfjWX3NBgRNWPxaQxZRFC;
Received: from c-68-42-65-200.hsd1.mi.comcast.net ([68.42.65.200] helo=[192.168.2.8]) by server1.netnutz.com with esmtpa (Exim 4.69) (envelope-from <nsb@guppylake.com>) id 1QV4NP-00030B-AB; Fri, 10 Jun 2011 12:16:03 -0400
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <01O2A8KT5RZ600VHKR@mauve.mrochek.com>
Date: Fri, 10 Jun 2011 12:15:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1BE11D6-DDD3-4D23-BC28-9501E4AF1372@guppylake.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com>
To: ned+ietf@mauve.mrochek.com
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server1.netnutz.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - guppylake.com
Cc: IETF Discussion <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 16:16:18 -0000

At the risk of piling on, I can't resist the opportunity to try to =
one-up Ned's story.

While in the UK this year, I had the misfortune to need to call BT for =
support on my broken home Internet connection.  In the middle of the =
usual mind-numbing "we will force you to walk through every idiotic step =
that you already know is irrelevant after thirty years in the business," =
 the phone support guy told me to "Click on the pulldown for 'Configure =
one-pee-vee-six' and set it to Off."  Not only was this totally =
irrelevant, and not only did he routinely make me turn off the very =
protocol we want to enable, but he called that protocol "one pee v6" =
instead of "eye pee v6."   And when I was stupid enough to correct him, =
he wouldn't go any further until I admitted that he knew best, and that =
I should call it "one pee v6" rather than "eye pee v6."    Needless to =
say, I didn't bother asking about BT's plans to support IPv6 -- oops, I =
mean 1Pv6.

No need to ask.  If BT can't even spell IP, we are a11 d00med.  -- =
Nathaniel


On Jun 9, 2011, at 6:13 PM, ned+ietf@mauve.mrochek.com wrote:

> You folks have had it easy in your interactions with ISPs. When I =
tried not too
> long ago with various ISPs in my area, I was unable to reach anyone at =
either
> of the big ISPs who knew what "IPv6" even meant. Both promised =
callbacks,
> neither did.
>=20
> The more interesting response was from a small ISP. They knew exactly =
what I
> was talking about, and told me (a) The IPv4 address shortage is =
nothing but a
> "scare tactic", (b) They currently have no plans to offer IPv6, and =
(c) If they
> ever did offer it "would only be with T1/T3 services, Colocation, and =
Managed
> Servers and not DSL".
>=20
> Those are verbatim quotes from their response.
>=20
> And here's another data point, this time in the SOHO router space. My =
new
> router is advertised as being "IPv6 ready", but the firmware it came =
with has
> no IPv6 support whatsoever. When I contacted the vendor about this, I =
was
> informed that I could get a special firmware build that supports IPv6, =
but it
> would be an "as-is" thing based on an earlier release so there may be =
some loss
> of functionality in other areas.
>=20
> I then asked why they don't have support in their current product, I =
was told
> it's because they are worried about their support staff being =
inundated with
> questions and problems. Given the dearth of IPv6 support from other =
vendors in
> this product area, I can't say I blame them.
>=20
> Anyone who doesn't believe we have a major marketing problem here =
isn't paying
> attention.
>=20
> 				Ned
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From jnc@mercury.lcs.mit.edu  Fri Jun 10 09:18:18 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3AFA1F0C88; Fri, 10 Jun 2011 09:18:17 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NzldUS8B1Fqy; Fri, 10 Jun 2011 09:18:16 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 70B281F0C89; Fri, 10 Jun 2011 09:18:07 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 99D1618C0F6; Fri, 10 Jun 2011 12:18:06 -0400 (EDT)
To: ietf@ietf.org, v6ops@ietf.org
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Message-Id: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu>
Date: Fri, 10 Jun 2011 12:18:06 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 16:18:18 -0000

    > From: Lorenzo Colitti <lorenzo@google.com>

    > Mac OS 10.6.4, which uses 6to4 by default, has a ~50x greater failure
    > rate when connecting to dual-stack servers than Mac OS 10.6.5 - and the
    > only change is to not use 6to4 by default.
    > ...
    > So the existence of 6to4 is in itself a significant barrier for IPv6
    > deployment

Surely you meant to say "the _incorrect configuration_ of 6to4 is in itself a
significant barrier"?

I get the impression that the problem comes in when 6to4 is configured on by
default, and too high in the priority list (as opposed to native, other
methods, etc). So fix the real issue, don't try and prematurely kill off
something that's being used by lots of people.

	Noel

From brian.e.carpenter@gmail.com  Fri Jun 10 10:05:06 2011
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 4487D11E80BD for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 10:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.549
X-Spam-Level: 
X-Spam-Status: No, score=-103.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gV2sQ6WG2u9t for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 10:05:05 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8171B11E80E0 for <ietf@ietf.org>; Fri, 10 Jun 2011 10:05:02 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1986245fxm.31 for <ietf@ietf.org>; Fri, 10 Jun 2011 10:05:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lpt2aOHyD4kK1jbMzOAI7UZEsuk7HhW9O5+l7nbQCy8=; b=dHqygU99M4zs7fgZdpd7eAcxopk2itGdCrn64T0zEMvAHdNBmNMJcogXz9Rj+Rj4PJ QV6U0nGAoEu4IB9K3fXpo8TwM9VgHg8YhtDZ2r0dxVYc9/QMeeWJcYdsyOrkt6De3nl6 YEEMITiKo+LiC1/pDjwtUu+hWOdFj0uq95zgs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=nIPKBssdUTtTu/G+5jBYpglJTlJnrrRVOkN+hw9L6H9BOUGpXGJixd2s41r9zVAmUo SY8mfTm64tHft1B0squOHmmAq3No3ai+vVa7mGcIaH3B2DI+VjAN6gsZbXUin4YxROki 6nnLBPWYSmsi1uo7IbCjBMa4TfjxP4fhmYK6k=
Received: by 10.223.38.149 with SMTP id b21mr2277252fae.18.1307725501623; Fri, 10 Jun 2011 10:05:01 -0700 (PDT)
Received: from [10.255.25.89] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id q14sm1134608faa.27.2011.06.10.10.04.59 (version=SSLv3 cipher=OTHER); Fri, 10 Jun 2011 10:05:00 -0700 (PDT)
Message-ID: <4DF24EB9.5000508@gmail.com>
Date: Sat, 11 Jun 2011 05:04:57 +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: Tony Hain <alh-ietf@tndh.net>
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>	<BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com>	<01O2A8KT5RZ600VHKR@mauve.mrochek.com>	<20110610005758.BC2D110ABF81@drugs.dv.isc.org>	<392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local>	<4DF21D7B.7040103@gmail.com> <52581FF9790F6D396FB93E09@PST.JCK.COM> <117501cc2787$feb51410$fc1f3c30$@net>
In-Reply-To: <117501cc2787$feb51410$fc1f3c30$@net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'IETF Discussion' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 17:05:06 -0000

On 2011-06-11 04:03, Tony Hain wrote:
...
> There is no real problem with 6to4, despite the BS being propagated about
> failure rates. 

That's no BS, unfortunately. Have you studied the careful reports at
https://labs.ripe.net/Members/emileaben/6to4-how-bad-is-it-really
and http://www.potaroo.net/ispcol/2010-12/6to4fail.html ?

The operational fixes for 6to4 are also essential, and documented
in my draft, but how do you propose we get them implemented
by the 1PV6 deniers among ISPs?

   Brian

From john-ietf@jck.com  Fri Jun 10 10:05:17 2011
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 BD2CC11E80BD for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 10:05:17 -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_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MO24tb8-fl3E for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 10:05:17 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 9A6E511E807C for <ietf@ietf.org>; Fri, 10 Jun 2011 10:05:16 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QV58z-000M46-MW; Fri, 10 Jun 2011 13:05:13 -0400
Date: Fri, 10 Jun 2011 13:05:12 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: one data point regarding native IPv6 support
Message-ID: <B8755BDFE9F2DA066529DC12@PST.JCK.COM>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222907E9C2@DC-US1MBEX4.global.avaya.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@gmail.com> ,<52581FF9790F6D396FB93E09@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222907E9C2@DC-US1MBEX4.global.avaya.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: Fri, 10 Jun 2011 17:05:17 -0000

--On Friday, June 10, 2011 12:10 -0400 "Worley, Dale R (Dale)"
<dworley@avaya.com> wrote:

> OTOH, my cable ISP provider has an "Expected IPv6 Transition
> Phases" chart, in which Phase 3 says, "Customer Premesis
> Equipment (CPE) IP addressing:  IPv6 only".  And they've
> started trials of IPv6 already.

Dale,

I think that is part of the (rather specific) point I was trying
to make.  When one gets to the SOHO and small business markets,
there are ISPs who have gotten with the program and are making
commitments or actually deploying.  Some have not, don't intend
to, and don't have a clue.   A few are issuing press releases
about their commitment to IPv6, but have no actual deployment
plan to end users.   In none of the cases that are moving
forward have I seen anything that can be best explained by a
desire for competitive advantage.

For several years, I went through the exercise that, every time
one particular ISP issued a press release or make a presentation
about their IPv6 efforts, I'd call their local office and say
"ok, I'd like IPv6 here.  What is the schedule for your turning
service on here and how do I get an order in?"   Despite all the
hype, the answers I got were a lot more similar to what Keith,
Ned, and Nathaniel have reported than they were to handing out
charts and making commitments.

YMMD... and obviously does.

I think the question for the IETF is whether it is desirable to
move 6to4 to historic at a time when it is the only path to IPv6
for some users in spite of whatever recognition there is that it
is no longer a mechanism we want to encourage people to design
into new installations or systems.  

Personally, I'd rather see us publish an A/S that just says
"generally Not Recommended any more because..." than have the
debate about the surface and deep semantics of "Historic".  Most
of the text for that document could be appropriated from the
current V6OPS WG draft.  Much of the rest could be drawn from
Tony Hain's recent note in this thread.  

But, to the extent to which the motivation for moving 6to4 to
Historic is what Tony describes as "kill-what-we-don't-like",
let me suggest that we need to realize that a good fraction of
the reason we have as little deployed and
used-routinely-in-production IPv6 as we do is not technical
issues but that the IETF and some related communities have
consistently gotten deployment scenarios, schedules, and plans
wrong... and then made promises based on those wrong guesses.  I
think a little modest realism about our predictive abilities and
a willingness to understand that different situations call for
different scenarios would help a lot.  It would help even more
if our documents ran a little more in the direction of
reflective and emotionally neutral scenario analysis and a
little less in the direction of "praise what you like and damn
what you don't".

    john


From jhw@apple.com  Fri Jun 10 10:15:21 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAD1611E8090; Fri, 10 Jun 2011 10:15:21 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jNsHeZNxDi9D; Fri, 10 Jun 2011 10:15:20 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 571A811E8077; Fri, 10 Jun 2011 10:15:20 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LML004753J5DN80@mail-out.apple.com>; Fri, 10 Jun 2011 10:15:19 -0700 (PDT)
X-AuditID: 11807130-b7c15ae000005aca-28-4df251260234
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay11.apple.com (Apple SCV relay) with SMTP id 12.2C.23242.72152FD4; Fri, 10 Jun 2011 10:15:19 -0700 (PDT)
Received: from 67-218-102-220.cust.layer42.net (67-218-102-220.cust.layer42.net [67.218.102.220]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LML008VE3XIEA00@koseret.apple.com>; Fri, 10 Jun 2011 10:15:18 -0700 (PDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to	Historic status) to Informational RFC
From: james woodyatt <jhw@apple.com>
In-reply-to: <BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com>
Date: Fri, 10 Jun 2011 10:15:19 -0700
Message-id: <3B25F81A-89D1-4272-942C-A699C8593099@apple.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org> <ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com> <BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1237.1)
X-Brightmail-Tracker: AAAAAA==
Cc: IPv6 Operations Working Group <v6ops@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 17:15:21 -0000

On Jun 9, 2011, at 10:42 AM, Lorenzo Colitti wrote:
> 
>  We have data that clearly shows that Mac OS 10.6.4, which uses 6to4 by default...

I don't want anybody to be misled by this statement.  I think what Lorenzo meant to say is that Mac OS X 10.6.4 and earlier doesn't implement the policy table in I-D.ietf-6man-rfc3484-revise, which prefers IPv4 source addresses over 2002::/16 IPv6 source addresses.

Mac OS X has *never* used 6to4 by default.  The scenario Lorenzo is talking about is where a router is advertising a 6to4 prefix onto a native IPv6 link.  On those links, Mac OS X 10.6.4 and earlier will treat 6to4 prefixes equivalently to any other IPv6 prefix when making address selection decisions.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From brian.e.carpenter@gmail.com  Fri Jun 10 10:28:14 2011
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 6B87A11E818B for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 10:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.556
X-Spam-Level: 
X-Spam-Status: No, score=-103.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BA0ZgdpQk0MQ for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 10:28:13 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 502DA11E8183 for <ietf@ietf.org>; Fri, 10 Jun 2011 10:28:13 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1998418fxm.31 for <ietf@ietf.org>; Fri, 10 Jun 2011 10:28:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Y2HVb8mLa4NpGkZaX531J2UsvcVTStC39a044mO30gE=; b=vKwvKRdwAedpaSRc/kuMcXv21iKHIlnlc4J+ln7DO7KwrfWwSzYcCqXVWr2fN3OzjU YS8YCdvzWO5geU1sCsqFdyRkYZptFFWAp3znEesZoqN8iFS2gOiEN8Nlg1D2/dUVpZN6 T7sZx7xIrTxYg5JDGgwnfM2dRm+tfHGvuywuc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=bC7J6Bz4c1/FzjiqtQwXfJT9S/CcfcCgrU19dUjoHL8ObEA4hGk1MoLxQpBUZVNaIF ZJ4jMM3LdH6v1zZUh+69gACPykaNyhCJmebCt84+xV+A6vqrD+O/DmHquFqy++Z4RFM+ qjU++ELsTnooWa+AGDdlCN1zX1h9FnntWzyYc=
Received: by 10.223.48.139 with SMTP id r11mr2314422faf.63.1307726892250; Fri, 10 Jun 2011 10:28:12 -0700 (PDT)
Received: from [10.255.25.89] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id 11sm1139948fax.36.2011.06.10.10.28.10 (version=SSLv3 cipher=OTHER); Fri, 10 Jun 2011 10:28:11 -0700 (PDT)
Message-ID: <4DF25429.2070601@gmail.com>
Date: Sat, 11 Jun 2011 05:28: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: John C Klensin <john-ietf@jck.com>
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@gmail.com> , <52581FF9790F6D396FB93E09@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222907E9C2@DC-US1MBEX4.global.avaya.com> <B8755BDFE9F2DA066529DC12@PST.JCK.COM>
In-Reply-To: <B8755BDFE9F2DA066529DC12@PST.JCK.COM>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 17:28:14 -0000

John,

On 2011-06-11 05:05, John C Klensin wrote:

...
> But, to the extent to which the motivation for moving 6to4 to
> Historic is what Tony describes as "kill-what-we-don't-like",

Unfortunately, as I know from the enormous amount of technical
feedback I got from living, breathing operators while drafting
draft-ietf-v6ops-advisory, the motivation is "kill something
that is causing real operational problems and failure modes."
I wouldn't be endorsing draft-ietf-v6ops-6to4-to-historic if
there wasn't a very sound operational argument for it.

I think nobody wants to kill the successful use of 6to4, but
we need to stop the operational problems getting worse. It
appears that the default help desk advice to disable 1PV6 is
generally an echo of problems caused by on-by-default 6to4.

    Brian

From mcr@sandelman.ca  Fri Jun 10 10:38:23 2011
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 D8B5511E812D for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 10:38: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=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LjZg+xRhESWv for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 10:38:22 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 64F3611E80B1 for <ietf@ietf.org>; Fri, 10 Jun 2011 10:38:17 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 63EAA3416C for <ietf@ietf.org>; Fri, 10 Jun 2011 13:38:16 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id A53B298A11 for <ietf@ietf.org>; Fri, 10 Jun 2011 13:39:58 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: one data point regarding native IPv6 support
In-Reply-To: <117501cc2787$feb51410$fc1f3c30$@net>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@gmail.com> <52581FF9790F6D396FB93E09@PST.JCK.COM> <117501cc2787$feb51410$fc1f3c30$@net>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Fri, 10 Jun 2011 13:39:58 -0400
Message-ID: <11761.1307727598@marajade.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, 10 Jun 2011 17:38:24 -0000

>>>>> "Tony" == Tony Hain <alh-ietf@tndh.net> writes:
    Tony> There is no real problem with 6to4, despite the BS being
    Tony> propagated about failure rates. The fundamental problem is
    Tony> that those complaining have their heads firmly stuck in
    Tony> IPv4-think, and are refusing to add a second 6to4 prefix to
    Tony> their service. If they would simply install their own 6to4
    Tony> router and be the tunnel endpoint, there would be no 3rd party
    Tony> in the path for either direction. The technology is simply
    Tony> creating an opportunity. Those complaining about it are
    Tony> refusing to take advantage of it because that would be a
    Tony> different operational practice than they do for IPv4.

+1
I have native IPv6 at home.
I have multiple other sites that I work with that can only get tunnels.
6to4 (on BSD. Linux has a design bug) lets me do this to shortcut things:
   route add -net -inet6 2001:4830:116e:: -prefixlen 48    2002:84d5:ee07::1
 
IPv4 is my NBMA LAN :-)


    Tony> The herd mentality of kill-what-we-don't-like is not helping
    Tony> with deployment. In fact the ability to document which ISPs
    Tony> have customers that are trying to use IPv6 despite the edge
    Tony> lethargy is a very useful thing to drive deployment through
    Tony> blame-&-shame. Put the 6to4-to-historic effort on the shelf
    Tony> for at least 5 years. Then it will be time to talk.

The funny part is that removing 6to4 won't reduce any code, as the 6rd
code is often identical...

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From mcr@sandelman.ca  Fri Jun 10 10:42:16 2011
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 0431C11E816F; Fri, 10 Jun 2011 10:42:16 -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=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 045LQpIQsAp9; Fri, 10 Jun 2011 10:42:15 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 423B211E80B7; Fri, 10 Jun 2011 10:42:15 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 0D64A3414F; Fri, 10 Jun 2011 13:42:15 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 535AC98A11; Fri, 10 Jun 2011 13:43:57 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: "v6ops@ietf.org" <v6ops@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
In-Reply-To: <BANLkTik8s9PHbPi-5rvB=xaCJG+BnrQXrgGh+cZGOp-ZVnYMzw@mail.gmail.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <BANLkTik8s9PHbPi-5rvB=xaCJG+BnrQXrgGh+cZGOp-ZVnYMzw@mail.gmail.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Fri, 10 Jun 2011 13:43:57 -0400
Message-ID: <12313.1307727837@marajade.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, 10 Jun 2011 17:42:16 -0000

>>>>> "Lorenzo" == Lorenzo Colitti <lorenzo@google.com> writes:
    >> Why are you trying to make life harder for developers of IPv6
    >> applications?  There's no reason at all that an application
    >> developer should have to set up a special-purpose network just to
    >> test an IPv6 application.
    >> 

    Lorenzo> No, we're trying to make their lives easier, by suggesting
    Lorenzo> they use something that actually *works*.


    >> Realistic testing of applications needs to be done on real
    >> networks, or a least an approximation to real networks.  Testing
    >> IPv6 using 6to4 over public IPv4 obviously isn't perfect, but
    >> it's a hell of a lot more realistic than setting up a lab network
    >> and confining one's testing to that.

    Lorenzo> So use a tunnel broker.

My tunnel broker has a machine with broken IPv4 routing, which they
can't fix.   It's been down for a week+ now.   We had to renumber that
location in time for World IPv6 day.  We only had 6 machines that were
using their non-autoconfigured addresses, so the rest was just a s///g
in the DNS zone file.

6to4 would have turned this into my problem (which I could have fixed),
but since some places like google refuse to run their own 6to4 relay, I
can't really use 6to4 to talk to.  Thanks.

This all reminds of how killing the mbone killed multicast.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From joelja@bogus.com  Fri Jun 10 10:57:00 2011
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 C2DBC11E81D1; Fri, 10 Jun 2011 10:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.298
X-Spam-Level: 
X-Spam-Status: No, score=-102.298 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4N3Dw0HvDIUC; Fri, 10 Jun 2011 10:57:00 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id C8DA711E81A0; Fri, 10 Jun 2011 10:56:59 -0700 (PDT)
Received: from 000154tjennings.corp.zynga.com ([12.184.108.202]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5AHutTS018327 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 10 Jun 2011 17:56:57 GMT (envelope-from joelja@bogus.com)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-1-856412113
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <12313.1307727837@marajade.sandelman.ca>
Date: Fri, 10 Jun 2011 10:56:50 -0700
Message-Id: <950C6940-C1C2-4AA5-AB32-621B3150682D@bogus.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7388@PRVPEXVS04.corp.twcable.com> <08CD7CDC-E67F-4A59-9035-6D4C8C92BAB6@network-heretics.com> <34E4F50CAFA10349A41E0756550084FB067B7752@PRVPEXVS04.corp.twcable.com> <840209E6-606E-4823-8E6B-43D7C8EDE84D@network-heretics.com> <BANLkTik8s9PHbPi-5rvB=xaCJG+BnrQXrgGh+cZGOp-ZVnYMzw@mail.gmail.com> <12313.1307727837@marajade.sandelman.ca>
To: Michael Richardson <mcr@sandelman.ca>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 10 Jun 2011 17:56:58 +0000 (UTC)
Cc: "v6ops@ietf.org" <v6ops@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 Jun 2011 17:57:00 -0000

--Apple-Mail-1-856412113
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jun 10, 2011, at 10:43 AM, Michael Richardson wrote:
>=20
> This all reminds of how killing the mbone killed multicast.

Getting grumpy email from van because I sourced more than 128Kb/s killed =
the mbone, it was a toy.=20

joel=

--Apple-Mail-1-856412113
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 10, 2011, at 10:43 AM, Michael Richardson wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>This all reminds of how killing the mbone killed multicast.<br></div></blockquote></div><br><div>Getting grumpy email from van because I sourced more than 128Kb/s killed the mbone, it was a toy.&nbsp;</div><div><br></div><div>joel</div></body></html>
--Apple-Mail-1-856412113--

From elwynd@dial.pipex.com  Fri Jun 10 10:58:04 2011
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 4649311E81D0; Fri, 10 Jun 2011 10:58: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 34ROB+yfNq0H; Fri, 10 Jun 2011 10:58:03 -0700 (PDT)
Received: from b.painless.aaisp.net.uk (b.painless.aaisp.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 02A2211E810F; Fri, 10 Jun 2011 10:58:02 -0700 (PDT)
Received: from 250.254.187.81.in-addr.arpa ([81.187.254.250]) by b.painless.aaisp.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1QV5y2-0007mN-1f; Fri, 10 Jun 2011 18:57:58 +0100
Subject: Gen-art LC review of draft-ietf-pcn-cl-edge-behaviour-08
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Fri, 10 Jun 2011 19:01:54 +0100
Message-Id: <1307728914.22973.2654.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-pcn-cl-edge-behaviour.all@tools.ietf.org, "A. Jean Mahoney" <mahoney@nostrum.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, 10 Jun 2011 17:58:04 -0000

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

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

Document: draft-ietf-pcn-cl-edge-behaviour-08 
Reviewer: Elwyn Davies
Review Date: 10 June 2011
IETF LC End Date: 10 June 2011
IESG Telechat date: (if known) -

Summary:
In my opinion, there are a number of areas that need significant work
and at least one open issue (the stability question from s3.3.1) that
needs to be addressed before this document is ready for the IESG.

Major issues:
The draft contains partial definitions of two control protocols (egress
-> decision point; decision point -> ingress).  It does not make it
clear whether the reader is expected to get full definitions of these
protocols here or whether there will be another document that specifies
these protocols completely.  As is stands one could build the protocols
and pretty much guarantee that they would not be interoperable with
other implementations since message formats are not included although
high level specs are.  The document needs to be much clearer about what
is expected to happen here.
 
Use of EXP codepoint: My understanding of what is said in RFC 5696 is
that EXP is supposed to be left for other (non=PCN) systems to use.
This draft uses it.  Is this sensible? Is this whole draft experimental
really?

s3.3.1:
> [CL-specific] The outcome of the comparison is not very sensitive
>       to the value of the CLE-limit in practice, because when threshold-
>       marking occurs it tends to persist long enough that threshold-
>       marked traffic becomes a large proportion of the received traffic
>       in a given interval.
This statement worries me.  It sounds like a characteristic of an
unstable system.  If the value is that non-critical why are we
bothering?

Minor issues:
s1.1: definition of PCN-Traffic etc:  
> The same network will carry traffic of other Diffserv BAs.
Just to be sure: Does this or does this not imply that *all* traffic in
a PCN network must have a non-empty DSCP marking, i.e. that *all*
traffic must be attached to some specific Diffserv BA? This should be
clarified whichever is true. 

s1.1: T-fail:  I notice from s3.1 that PCN-ingress nodes also have to
make reports on request.  Should T-fail or some other timer apply to
non-return of info from ingress points?  What would a (probably
non-colocated) decision point do if it lost contact with the ingress? 

s2/s3.2.1: The use of PM and EXP codepoints for ThM and ETM appear to be
reversed in these two sections!!  Which way round is intended?

s3.2.1/s3.2.2:  Neither section mentions T-meas but I assume that this
is supposed to be (either or both) the sampling period in the egress
node or the period between reports.  It is unclear if they are allowed
to be different and if they are which one is T-meas.  However s3.2.3
appears to imply that T-meas is probably the time between reports.  This
all needs to be much clearer.

s3.2.1/3.2.2: In s3.2.2, para 2:
> If so configured (e.g., because multipath routing is
>    being used, as explained in the previous section), the PCN-egress-
>    node MUST also report the set of flow identifiers of PCN-flows for
>    which excess-traffic-marking was observed in the most recent
>    measurement interval.
This is a requirement for a protocol that you may or may not be
defining. Confusing.

s3.2.3/s3.2.2: The first paragraph of s3.2.3 suggests that the report
from an egress may not always contain the calculated value of the CLE,
but s3.2.2 has a MUST for the report to contain this value.
Consistency!!!

s6:  The potential introduction of a centralized decision point appears
to provide additional attack points beyond the architecture in RFC 5559.
It appears to me that the requests for information about specific flows
to the ingress are ighly vulnerable as they (probably) contain all the
information needed to craft a DoS attack on the flow.

Nits/editorial comments:
General: Consistency of naming for timing paramters t-meas/T-meas, etc.

s1.1: I think it would be worth reproducing the CL-specific definitions:
PCN-threshold-rate and threshold-marked since they are specific.

s1.1: 
> Congestion level estimate (CLE)
>       A value derived from the measurement of PCN-packets received at a
>       PCN-egress-node for a given ingress-egress-aggregate, representing
>       the ratio of marked to total PCN-traffic (measured in octets)
            ^^^^^                                 ^^^^^^^^^^^^^^^^^^
>       received over a short period.
The ratio is (hopefully) dimensionless.  Maybe '(each measured in octets)' ?

s2:
> the PCN-domain satisfies the conditions specified in [RFC5696];
This may be a bit pedantic but I am not sure that RFC 5696 actually sets
out conditions for the domain.  It sets out rules for encoding markings
and allowed transitions.  Maybe s/conditions/packet markings and allowed
transitions/.

s3.1, para 1 and several other instances: s/collocated/co(-)located/

s3.2.1, para 5: s/statistical variance/statistical variation/





From Fred.L.Templin@boeing.com  Fri Jun 10 11:15:48 2011
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5688E9E800B; Fri, 10 Jun 2011 11:15:48 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pqd-9vw1qD8h; Fri, 10 Jun 2011 11:15:47 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by ietfa.amsl.com (Postfix) with ESMTP id B56969E8004; Fri, 10 Jun 2011 11:15:47 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p5AIFeXS013921 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 10 Jun 2011 11:15:41 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p5AIFe3N023116; Fri, 10 Jun 2011 11:15:40 -0700 (PDT)
Received: from XCH-NWHT-03.nw.nos.boeing.com (xch-nwht-03.nw.nos.boeing.com [130.247.71.23]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p5AIFelN023098 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 10 Jun 2011 11:15:40 -0700 (PDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-03.nw.nos.boeing.com ([130.247.71.23]) with mapi; Fri, 10 Jun 2011 11:15:40 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Lorenzo Colitti <lorenzo@google.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Date: Fri, 10 Jun 2011 11:15:39 -0700
Subject: RE: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Thread-Index: AcwnjPOsyFstRw0iRie7BDfF+VdQ/gADQvSA
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C6A7E6A9A@XCH-NW-01V.nw.nos.boeing.com>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com>
In-Reply-To: <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_E1829B60731D1740BB7A0626B4FAF0A65C6A7E6A9AXCHNW01Vnwnos_"
MIME-Version: 1.0
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 18:15:48 -0000

--_000_E1829B60731D1740BB7A0626B4FAF0A65C6A7E6A9AXCHNW01Vnwnos_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


You cannot expect something to be configured correctly if it is simply turn=
ed on without a) being managed by someone or b) detection mechanisms to see=
 if it's working. Sadly, anycasted 6to4 meets neither of these conditions.
ISATAP meets both of these conditions:

http://tools.ietf.org/html/draft-templin-v6ops-isops

Fred



--_000_E1829B60731D1740BB7A0626B4FAF0A65C6A7E6A9AXCHNW01Vnwnos_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.6082" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3Dgmail_quote>
  <DIV>You cannot expect something to be configured correctly if it is simp=
ly=20
  turned on without a) being managed by someone or b) detection mechanisms =
to=20
  see if it's working. Sadly, anycasted 6to4 meets neither of these=20
  conditions.<SPAN class=3D671451218-10062011><FONT face=3DArial color=3D#0=
000ff=20
  size=3D2>&nbsp;&nbsp;</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV dir=3Dltr><SPAN class=3D671451218-10062011><FONT face=3DArial size=3D2=
>ISATAP meets=20
both of these conditions:</FONT></SPAN></DIV>
<DIV dir=3Dltr><SPAN class=3D671451218-10062011><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr><SPAN class=3D671451218-10062011><FONT face=3DArial color=3D=
#0000ff=20
size=3D2><A=20
href=3D"http://tools.ietf.org/html/draft-templin-v6ops-isops">http://tools.=
ietf.org/html/draft-templin-v6ops-isops</A></FONT></SPAN></DIV>
<DIV dir=3Dltr><SPAN class=3D671451218-10062011><FONT face=3DArial color=3D=
#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr><SPAN class=3D671451218-10062011><FONT face=3DArial=20
size=3D2>Fred</FONT></SPAN></DIV>
<DIV dir=3Dltr><SPAN class=3D671451218-10062011><FONT face=3DArial color=3D=
#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr><SPAN class=3D671451218-10062011><FONT face=3DArial color=3D=
#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV></BODY></HTML>

--_000_E1829B60731D1740BB7A0626B4FAF0A65C6A7E6A9AXCHNW01Vnwnos_--

From moore@network-heretics.com  Fri Jun 10 11:20:45 2011
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 EDF3A9E8022 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 11:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.328
X-Spam-Level: 
X-Spam-Status: No, score=-3.328 tagged_above=-999 required=5 tests=[AWL=0.271,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGpOnLYTqqEa for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 11:20:44 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 05BB29E8020 for <ietf@ietf.org>; Fri, 10 Jun 2011 11:20:44 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 5C64221CA2; Fri, 10 Jun 2011 14:20:43 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Fri, 10 Jun 2011 14:20:43 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=ICloSTq4T4E6IAUxLmvbnPix64U=; b=EQx1GZU68zHRViXvsBCsmfyofFLqtcPb7fQi+4JTWHzEvd7EwB7iZhk+Jn3LXGgAvQ3cGLtuQbFmri5ToDR/jxVtu3HBiNzTt9acsFARCLM/V+RP+gXXkOTldvvizlR9JrFi5IPLYdPCAKFNm5+iR+qr0fjzJja3ibl4KhC4ua4=
X-Sasl-enc: YnjnzICP9FMkNT6S+T6I7jAr72PmewiIbIoeVBYprpRC 1307730042
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 526F64077E9; Fri, 10 Jun 2011 14:20:42 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
X-Priority: 3
In-Reply-To: <000901cc270d$430ec000$6801a8c0@oemcomputer>
Date: Fri, 10 Jun 2011 14:20:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6538E2D1-6CAD-44E0-97EB-21A0F2A1EDAA@network-heretics.com>
References: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu> <49D685CB-00FD-42E5-9AD8-15E51545D9A2@apple.com> <006601cc260c$4a0c87e0$6801a8c0@oemcomputer> <04A9F777-8C57-4120-9964-CEFFAF0DD7BE@free.fr> <006d01cc26ca$ed74b600$6801a8c0@oemcomputer> <1F7E4C3A-8912-40AC-BF8F-E4D171B6864E@network-heretics.com> <000901cc270d$430ec000$6801a8c0@oemcomputer>
To: Randy Presuhn <randy_presuhn@mindspring.com>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 18:20:45 -0000

On Jun 9, 2011, at 9:25 PM, Randy Presuhn wrote:

> Your argument seems to be that the peculiar operational =
characteristics of 6to4
> should give it additional immunity to being declared historic. I don't =
find that
> argument persuasive. =20

That's not my argument.  My argument is that declaring 6to4 Historic is =
inconsistent with the way we've used Historic in the past - namely to =
label something that either 'hardly anybody uses anymore' or something =
that should be abandoned because a better alternative is now generally =
available.

> The history of multiple protocols that have been
> declared "historic" shows that vendors seem to care about that =
designation
> only when it is convenient for them to do so.  Installed base, =
customer
> demand, operational considerations and so on all trump whatever the =
IETF
> might say about a "historic" protocol.  This works both ways: folks =
might
> decide to kill something before it becomes historic, or support it =
long after.
> We can't compel people to continue supporting it any more than we can
> make them stop.  At most, we can give them (hopefully convincing) =
reasons
> to change.  If the SNMP experience shows anything, it shows that even
> that isn't enough.  For that reason, I find it amusing when others =
write of=20
> "killing" 6to4.  We don't have that kind of power.

Declaring 6to4 Historic certainly won't prevent people from implementing =
it.  But the proposed action is clearly intended to discourage =
implementation of 6to4.  It says so explicitly.  Of course some vendors =
will ignore it, but some vendors will probably not ignore it.

Keith


From jhw@apple.com  Fri Jun 10 11:27:32 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6131111E80B1 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 11:27:32 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3hdoqVF82kUK for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 11:27:31 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 513B511E8075 for <ietf@ietf.org>; Fri, 10 Jun 2011 11:27:29 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=iso-2022-jp
Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LML00F8S6GT1A61@mail-out.apple.com> for ietf@ietf.org; Fri, 10 Jun 2011 11:25:42 -0700 (PDT)
X-AuditID: 11807134-b7c00ae0000074fb-05-4df261a50fe5
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay14.apple.com (Apple SCV relay) with SMTP id 36.38.29947.6A162FD4; Fri, 10 Jun 2011 11:25:42 -0700 (PDT)
Received: from [17.193.13.64] (unknown [17.193.13.64]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LML008VL76TEA10@koseret.apple.com> for ietf@ietf.org; Fri, 10 Jun 2011 11:25:41 -0700 (PDT)
Subject: Re: one data point regarding native IPv6 support
From: james woodyatt <jhw@apple.com>
In-reply-to: <4DF177B0.4080303@necom830.hpcl.titech.ac.jp>
Date: Fri, 10 Jun 2011 11:25:41 -0700
Message-id: <318019AA-C0F3-4D25-B60E-034DD248D3E7@apple.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <4DF177B0.4080303@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
X-Mailer: Apple Mail (2.1237.1)
X-Brightmail-Tracker: AAAAAA==
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, 10 Jun 2011 18:27:32 -0000

On Jun 9, 2011, at 18:47 , Masataka Ohta wrote:
> james woodyatt wrote:
>> 
>> I need *native* IPv6 into my home in San Francisco for my day job,
> 
> Really?

Very very very few people have day jobs that require native IPv6 service to their home network today.

I'm an exception because I have a requirement that IPv6 and IPv4 provide more or less *equivalent* performance characteristics.  The extra 20 milliseconds of queuing delay caused by the 6over4 tunnel endpoint should be acceptable to almost everyone else, but it's a deal-breaker for me.  For reasons I'm not going to discuss here, I need IPv6 to be at least as good if not better than IPv4-- today, not three years from now--- and I'm forced to leave my ISP over it.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From moore@network-heretics.com  Fri Jun 10 11:29:01 2011
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 B7C2811E8119; Fri, 10 Jun 2011 11:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.339
X-Spam-Level: 
X-Spam-Status: No, score=-3.339 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8b4SpRxxY8-C; Fri, 10 Jun 2011 11:29:00 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id B718111E80FF; Fri, 10 Jun 2011 11:29:00 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 61FDB20D87; Fri, 10 Jun 2011 14:29:00 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Fri, 10 Jun 2011 14:29:00 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=DPjzCqFhLzX5/QmpXY9vhLngf5w=; b=bM+xYZksZ0iVbGVB6J4jwHmmzyaTlHNJM5iHkyOH6T+vFXgQWFz0CdL/bstNjCJwy9ho+CcpHcy/OOBqdZF890u0uODpHYjNaeLp7kbVNPJLPL8NSA1ye3ksj2PyfypJeH9Sg9vSvEa7Lri2HduximfRLY/gdSJTmhUqOMJugFU=
X-Sasl-enc: SR7dJPTU35esJmbJBBZq3w4FpJZreaaESap45owLQIlu 1307730539
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 579E840727F; Fri, 10 Jun 2011 14:28:59 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to	Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <3B25F81A-89D1-4272-942C-A699C8593099@apple.com>
Date: Fri, 10 Jun 2011 14:28:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C6D95F6-49D3-49CD-A737-D24138DC631F@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org> <ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com> <BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com> <3B25F81A-89D1-4272-942C-A699C8593099@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Operations Working Group <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 18:29:01 -0000

On Jun 10, 2011, at 1:15 PM, james woodyatt wrote:

> On Jun 9, 2011, at 10:42 AM, Lorenzo Colitti wrote:
>>=20
>> We have data that clearly shows that Mac OS 10.6.4, which uses 6to4 =
by default...
>=20
> I don't want anybody to be misled by this statement.  I think what =
Lorenzo meant to say is that Mac OS X 10.6.4 and earlier doesn't =
implement the policy table in I-D.ietf-6man-rfc3484-revise, which =
prefers IPv4 source addresses over 2002::/16 IPv6 source addresses.
>=20
> Mac OS X has *never* used 6to4 by default.  The scenario Lorenzo is =
talking about is where a router is advertising a 6to4 prefix onto a =
native IPv6 link.  On those links, Mac OS X 10.6.4 and earlier will =
treat 6to4 prefixes equivalently to any other IPv6 prefix when making =
address selection decisions.

thanks for clearing that up.  I was pretty sure it wasn't true, but you =
saved me the trouble of reinstalling 10.6.4 to prove it.

Keith


From jhw@apple.com  Fri Jun 10 11:41:24 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6CF211E8114 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 11:41:24 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I3otbw4qkTwj for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 11:41:24 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1657311E80B7 for <ietf@ietf.org>; Fri, 10 Jun 2011 11:41:24 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LML00DJ87W4ZD20@mail-out.apple.com> for ietf@ietf.org; Fri, 10 Jun 2011 11:41:23 -0700 (PDT)
X-AuditID: 11807130-b7c15ae000005aca-90-4df26553afa0
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay11.apple.com (Apple SCV relay) with SMTP id 4B.8E.23242.35562FD4; Fri, 10 Jun 2011 11:41:23 -0700 (PDT)
Received: from [17.193.13.64] (unknown [17.193.13.64]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LML008SR7WZYJ20@cardamom.apple.com> for ietf@ietf.org; Fri, 10 Jun 2011 11:41:23 -0700 (PDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt>
From: james woodyatt <jhw@apple.com>
X-Priority: 3
In-reply-to: <6538E2D1-6CAD-44E0-97EB-21A0F2A1EDAA@network-heretics.com>
Date: Fri, 10 Jun 2011 11:41:23 -0700
Message-id: <306454C6-FD0D-4532-9B3A-A7AE7320E77D@apple.com>
References: <20110608160415.1F8CF18C121@mercury.lcs.mit.edu> <49D685CB-00FD-42E5-9AD8-15E51545D9A2@apple.com> <006601cc260c$4a0c87e0$6801a8c0@oemcomputer> <04A9F777-8C57-4120-9964-CEFFAF0DD7BE@free.fr> <006d01cc26ca$ed74b600$6801a8c0@oemcomputer> <1F7E4C3A-8912-40AC-BF8F-E4D171B6864E@network-heretics.com> <000901cc270d$430ec000$6801a8c0@oemcomputer> <6538E2D1-6CAD-44E0-97EB-21A0F2A1EDAA@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1237.1)
X-Brightmail-Tracker: AAAAAA==
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, 10 Jun 2011 18:41:25 -0000

On Jun 10, 2011, at 11:20 , Keith Moore wrote:
> 
> Declaring 6to4 Historic certainly won't prevent people from implementing it.  But the proposed action is clearly intended to discourage implementation of 6to4.  It says so explicitly.  Of course some vendors will ignore it, but some vendors will probably not ignore it.

I would absolutely agree that the document would be improved if this pointless recommendation were removed.  I expect some perfectly reasonable people will still oppose it with understandable concerns.  Nevertheless, I do think this particular recommendation is inconsistent with the consensus in IETF that a phase-out plan for 6to4 is unwarranted.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From wwwrun@ietfa.amsl.com  Fri Jun 10 11:42:02 2011
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id F000811E8075; Fri, 10 Jun 2011 11:42:01 -0700 (PDT)
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: RFP for Secretariat Services 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110610184201.F000811E8075@ietfa.amsl.com>
Date: Fri, 10 Jun 2011 11:42:01 -0700 (PDT)
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 18:42:02 -0000

The IETF Administrative Oversight Committee (IAOC) on behalf of the IETF announces this
Request for Proposal for Secretariat Services.

The Internet Society (ISOC) is the contractor.

The Secretariat performs the following three types of services in support of the IETF:
1. Meeting Services
2. Clerical Support Services
3. IT Support Services

Supported Organizations include the Working Groups, Internet Engineering Steering Group 
(IESG), Internet Architecture Board (IAB), IETF Administrative Oversight Committee (IAOC), 
Internet Research Task Force (IRTF), Internet Research Steering Group (IRSG), RFC Series 
Oversight Committee (RSOC), RFC Series Editor (RSE), Independent Submissions Editor (ISE)
and the Nominating Committee (NomCom).

The RFP is located at: <http://iaoc.ietf.org/rfpsrfis.html>

The initial contract term will be for two (2) years, commencing on 1 February 2012, with an option
on the part of the parties for two renewals of up to two (2) additional years each for a possible
total of six years.

It is the intent of the IAOC to obtain the best combination of performance and cost for the benefit
of the IETF. A contract may be awarded to an Offeror providing all services, or a Prime 
Contractor, with subcontractors, providing all services.

 The closing date for submission of proposals to ietf-rfp@isoc.org is Monday, August 8, 2011 not 
later than 5:00 P.M. ET. It is expected that a contract or contracts will be completed by September 2012.

The sole point of contact regarding this RFP is the IETF Administrative Director (IAD). All 
questions or inquiries must be submitted in writing and must be received no later than midnight 
ET, June 17, 2011. Questions or inquiries will be accepted by email at ietf-rfp@isoc.org. 
Responses to questions plus any changes to the RFP shall be posted on the IETF Administrative
Support Activity (IASA) website at <http://iaoc.ietf.org/rfpsrfis.html>  no later than June 24, 2011.

Ray Pelletier
IETF Administrative Director 

From john-ietf@jck.com  Fri Jun 10 14:06:03 2011
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 C60199E8011 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 14:06:03 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WVMLhLWKZaRU for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 14:06:02 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id F24EE9E800D for <ietf@ietf.org>; Fri, 10 Jun 2011 14:06:01 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QV8tw-0000kL-Qp; Fri, 10 Jun 2011 17:05:57 -0400
Date: Fri, 10 Jun 2011 17:05:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: one data point regarding native IPv6 support
Message-ID: <081D65448E2ECBE519C21C55@PST.JCK.COM>
In-Reply-To: <4DF25429.2070601@gmail.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@gmail.com> ,<52581FF9790F6D396FB93E09@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222907E9C2@DC-US1MBEX4.global.avaya.com> <B8755BDFE9F2DA066529DC12@PST.JCK.COM> <4DF25429.2070601@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: Fri, 10 Jun 2011 21:06:03 -0000

--On Saturday, June 11, 2011 05:28 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> John,
> 
> On 2011-06-11 05:05, John C Klensin wrote:
> 
> ...
>> But, to the extent to which the motivation for moving 6to4 to
>> Historic is what Tony describes as "kill-what-we-don't-like",
> 
> Unfortunately, as I know from the enormous amount of technical
> feedback I got from living, breathing operators while drafting
> draft-ietf-v6ops-advisory, the motivation is "kill something
> that is causing real operational problems and failure modes."
> I wouldn't be endorsing draft-ietf-v6ops-6to4-to-historic if
> there wasn't a very sound operational argument for it.
> 
> I think nobody wants to kill the successful use of 6to4, but
> we need to stop the operational problems getting worse. It
> appears that the default help desk advice to disable 1PV6 is
> generally an echo of problems caused by on-by-default 6to4.

Brian,

This is not in my primary area of expertise and I am painfully
aware that it has been almost a decade since I have been able to
look in on these things from the viewpoint of an ISP with
default-free backbone arrangements, small end-site customers,
and almost everything in between.

>From the above and other comments you have made, I don't think
we disagree very much on the substance here.  I'm certainly not
about to try to make the case that 6to4 is a wonderful option to
be widely preferred.  As a variation on your comment above, I
don't want to see the IETF denounce or kill the successful use
of 6to4 and don't believe anyone else does either (or at least
should).

Where we disagree is about a procedural matter and the stance
the IETF takes formally and, perhaps still, about where the
motivations to deploy IPv6 "for real" comes from.

Let me see if I can describe my position and recommendation in
another way:

Even among those of us who believe that IPv6 conversion has
ceased being optional and has to be considered the only option
at this stage, we really have few clues about what is going to
cause a given ISP, or a given end-node customer, to switch over.
Most of our arguments are faulty, at least for some particular
set of cases.  Your capitalism/competition one is an example --
there are places where it will work and places where it won't.
The applications support and availability of IPv6-capable (and
IPv6-native) servers is another -- sometimes ISPs are waiting
for customer demand and/or enough deployment on customer sites
before they think about making the switch and the customers are
waiting for more evidence that the applications issues are
sorted out and will work reliably.  We talk about the advantages
to the folks who switch early, but we are aware that some folks
don't want to be the first to switch.   And so on, for a rather
long list.

Part of this adds up to a conclusion that we are lots better at
protocol design than we are at predicting the future or gaming
out the decision processes under various circumstances.  We had
better be -- our track record for those predictions is bad
enough that, if our protocol design and engineering were worse,
we should all find other occupations.

At the same time, my very limited and quite anecdotal experience
suggests that the decision in several dual-stack setups to
automatically prefer IPv6 when it is available (following IETF
advice if I recall) combines with sometimes-sketchy IPv6
connections and routing to cause connectivity problems that can
overwhelm the sorts of folks who staff first-level help desks.
6to4 is certainly part of that problem --and a little worse if
it is set up without user or ISP knowledge-- but the implicit
argument in both ..-6to4-advice and 6to4-historic that 6to4 is
the dominant cause of those problems isn't convincing.  Maybe it
is the case, maybe it is the dominant case (and, again, I don't
have enough firsthand experience in recent years to claim to
know) but certainly it is not the only one.  

I accept the claim that it can easily be misconfigured, but that
may not be sufficient to demonize it.

I don't think the technical content of either
draft-ietf-v6ops-6to4-to-historic or
draft-ietf-v6ops-6to4-advisory is especially bad.   Indeed, the
analysis in ...-6to4-advisory seems quite good to me -- the sort
of thing the IETF should, IMO, be doing a lot more often.  I'm
just suggesting that we should not write off _any_ option that
has proven useful to folks in preparing to transition, planning
for transitions, or actually transitioning.    To that end, the
abstract of ...6to4-advisory is just the right think to do.
Advising that 6to4 is a really lousy default, that
implementations should allow it to be turned on only after
appropriate warnings and only if the advice in Section 4 of
..-6to4-advice is followed _really_ carefully may be entirely
appropriate.  Put differently, your analysis appears good enough
that I can see no argument against branding 6to4 as "really
dangerous -- use only if actually understood and needed, then
with great caution, and then only if there is some reason why
6rd is inappropriate or unavailable".

But "Historic" is a really blunt instrument, especially since we
use it primarily for protocols that are no longer in use and/or
that have been demonstrated to be of no redeeming value.  This
situation is, IMO, an almost perfect example of why 2026 permits
us to identify a protocol specification as "NOT RECOMMENDED"
(yes, I think 2119 is defective in listing the conformance
language (MUST/ SHOULD/ MAY/...) but not the recommendation
terminology, but that is another topic).

So my personal preference, in a more perfect world, would be to
fold these two drafts together, drop "Historic" and any even
slightly hyperbolic language, issue the combination as a
standards-track A/S that updates 3056 and 3068 and makes a clear
and carefully explained "NOT RECOMMENDED" statement.   If, in
conjunction with that move, you or others see value in
downgrading 3056 and 3068 to Experimental and including comments
to the effect that they are normally useful only for
exploratory/experimental use, I wouldn't have any problem with
that at all.

I actually don't feel very strongly about the above.  I probably
would not have said anything in this thread if you hadn't raised
the capitalism/competition argument.  But, if there is a
situation where 6to4 really is appropriate and the IETF makes
what appears to be a strong statement deprecating it, we either
convince someone to further defer thinking through and migrating
to IPv6 or we help contribute to the impression that the IETF is
out of touch with real world realities.  I don't consider either
of those outcomes desirable and presume you don't either.   On
the other hand, my impression from conversations with operations
is that it certainly would not be either the first or the most
extreme case in which we've shown the IETF to be out of touch
and at least some users and implementers who find value in 6to4
are likely to continue doing whatever they think it is
appropriate to do regardless of what labels the IETF decided to
put on the specs.

best,
   john


p.s. Editorial nit: I'd love to know what a "domestic customer"
in Sections 2 and 4.2.4 of ...-6to4-advice is.  The term is as
likely to be construed as "within a particular country" (New
Zealand?) as "residential" (which I'm guessing is what you
mean).  As far as I can tell from skimming the document
"residential, small office, or home office (SOHO)" would be more
appropriate and consistent with terminology in common use.


From dave@cridland.net  Fri Jun 10 14:11:30 2011
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 C40359E8009 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 14:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.229
X-Spam-Level: 
X-Spam-Status: No, score=-2.229 tagged_above=-999 required=5 tests=[AWL=0.370,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XwqAn2mfPM0U for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 14:11:29 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [IPv6:2001:470:1f09:882:2e0:81ff:fe29:d16a]) by ietfa.amsl.com (Postfix) with ESMTP id 108269E8007 for <ietf@ietf.org>; Fri, 10 Jun 2011 14:11:29 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 0C5EC1168087; Fri, 10 Jun 2011 22:11:26 +0100 (BST)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (peirce.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gSPh8GHRGahF; Fri, 10 Jun 2011 22:11:22 +0100 (BST)
Received: from puncture (puncture.dave.cridland.net [IPv6:2001:470:1f09:882:221:85ff:fe3f:1696]) by peirce.dave.cridland.net (Postfix) with ESMTPA id 9B2851168067; Fri, 10 Jun 2011 22:11:22 +0100 (BST)
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <C1BE11D6-DDD3-4D23-BC28-9501E4AF1372@guppylake.com>
In-Reply-To: <C1BE11D6-DDD3-4D23-BC28-9501E4AF1372@guppylake.com>
MIME-Version: 1.0
Message-Id: <2961.1307740282.616986@puncture>
Date: Fri, 10 Jun 2011 22:11:22 +0100
From: Dave Cridland <dave@cridland.net>
To: Nathaniel Borenstein <nsb@guppylake.com>, IETF-Discussion <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>, "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
Content-Type: text/plain; delsp="yes"; 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 Jun 2011 21:11:31 -0000

On Fri Jun 10 17:15:55 2011, Nathaniel Borenstein wrote:
> At the risk of piling on, I can't resist the opportunity to try to  
> one-up Ned's story.
> 
> While in the UK this year, I had the misfortune to need to call BT  
> for support on my broken home Internet connection.  In the middle  
> of the usual mind-numbing "we will force you to walk through every  
> idiotic step that you already know is irrelevant after thirty years  
> in the business,"  the phone support guy told me to "Click on the  
> pulldown for 'Configure one-pee-vee-six' and set it to Off."  Not  
> only was this totally irrelevant, and not only did he routinely  
> make me turn off the very protocol we want to enable, but he called  
> that protocol "one pee v6" instead of "eye pee v6."   And when I  
> was stupid enough to correct him, he wouldn't go any further until  
> I admitted that he knew best, and that I should call it "one pee  
> v6" rather than "eye pee v6."    Needless to say, I didn't bother  
> asking about BT's plans to support IPv6 -- oops, I mean 1Pv6.
> 
> No need to ask.  If BT can't even spell IP, we are a11 d00med.  --  
> Nathaniel
> 
> 
Particularly poor as BT are actually quite clued up on IPv6:

http://www.ipv6.bt.com/

(And I don't work for BT, have never worked for BT, have been in  
competition with BT, and I don't use their service)

I would *never* judge an ISP by the clueless nature of their scripted  
first-line suppor, at least not beyond their existence. (The ISP I  
use does not have clueless script monkeys, but smart and helpful  
people who craft their response to fit your ability, not theirs).

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From brian.e.carpenter@gmail.com  Fri Jun 10 14:32:11 2011
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 4DEFE11E8105 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 14:32:11 -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.038, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4XUU7jfiPZ3 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 14:32:10 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id D89A011E80EC for <ietf@ietf.org>; Fri, 10 Jun 2011 14:32:09 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2109946fxm.31 for <ietf@ietf.org>; Fri, 10 Jun 2011 14:32:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5jd5NN3AkEMzrjimACv/PKx4Ftp3UejO2lYCI2O/pdE=; b=AwiBRpjJii7PJV7MY6sgxsubWdqVwltkVXogEoCVSD6412cb9NHyq/mWF/fWJtvP2X PRNAjaOEhNYIJjvfo/KciK90b0S97G84T520LzxDRJRxsChuaycDWo3NN14m4FYNGZbb 3OZmOay4RMG7hmlqsp0+KCWfK7PmU7AnG/CCE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=nFNMJcVUu6k9ZsD1UfsELwO3Tq5V7VySYPyDSnEAtvtXvz3FvdnTbQM2bPEUBXdlkF MQuExisgiCTsbRrNZ2IeZbIOsM+hC3aZB4d5EjVgbSMm/9O6iBEF4vv4y/BW0C2iSaUu wVl6FMEoAPLD1qRIX8MhHa+urqtUnCKmPn92g=
Received: by 10.223.98.5 with SMTP id o5mr2529556fan.33.1307741528934; Fri, 10 Jun 2011 14:32:08 -0700 (PDT)
Received: from [10.255.25.89] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id o23sm1200203faa.9.2011.06.10.14.32.06 (version=SSLv3 cipher=OTHER); Fri, 10 Jun 2011 14:32:08 -0700 (PDT)
Message-ID: <4DF28D54.5010008@gmail.com>
Date: Sat, 11 Jun 2011 09:32:04 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@gmail.com> , <52581FF9790F6D396FB93E09@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222907E9C2@DC-US1MBEX4.global.avaya.com> <B8755BDFE9F2DA066529DC12@PST.JCK.COM> <4DF25429.2070601@gmail.com> <081D65448E2ECBE519C21C55@PST.JCK.COM>
In-Reply-To: <081D65448E2ECBE519C21C55@PST.JCK.COM>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 21:32:11 -0000

John,

On one specific point:

>> So my personal preference, in a more perfect world, would be to
>> fold these two drafts together, 

I specifically pushed for the -advisory draft to be kept separate
and Informational in order to get it out ASAP (in my dreams, before
IPv6 Day, but that didn't prove possible). I still think that is the
correct approach - decouple the practical advice from the admittedly
political debate.

I'm not dismissing the rest of your points - clearly there are
varied opinions and "Historic" is, as you say, a blunt instrument.

Regards
   Brian

On 2011-06-11 09:05, John C Klensin wrote:
> 
> --On Saturday, June 11, 2011 05:28 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>> John,
>>
>> On 2011-06-11 05:05, John C Klensin wrote:
>>
>> ...
>>> But, to the extent to which the motivation for moving 6to4 to
>>> Historic is what Tony describes as "kill-what-we-don't-like",
>> Unfortunately, as I know from the enormous amount of technical
>> feedback I got from living, breathing operators while drafting
>> draft-ietf-v6ops-advisory, the motivation is "kill something
>> that is causing real operational problems and failure modes."
>> I wouldn't be endorsing draft-ietf-v6ops-6to4-to-historic if
>> there wasn't a very sound operational argument for it.
>>
>> I think nobody wants to kill the successful use of 6to4, but
>> we need to stop the operational problems getting worse. It
>> appears that the default help desk advice to disable 1PV6 is
>> generally an echo of problems caused by on-by-default 6to4.
> 
> Brian,
> 
> This is not in my primary area of expertise and I am painfully
> aware that it has been almost a decade since I have been able to
> look in on these things from the viewpoint of an ISP with
> default-free backbone arrangements, small end-site customers,
> and almost everything in between.
> 
>>From the above and other comments you have made, I don't think
> we disagree very much on the substance here.  I'm certainly not
> about to try to make the case that 6to4 is a wonderful option to
> be widely preferred.  As a variation on your comment above, I
> don't want to see the IETF denounce or kill the successful use
> of 6to4 and don't believe anyone else does either (or at least
> should).
> 
> Where we disagree is about a procedural matter and the stance
> the IETF takes formally and, perhaps still, about where the
> motivations to deploy IPv6 "for real" comes from.
> 
> Let me see if I can describe my position and recommendation in
> another way:
> 
> Even among those of us who believe that IPv6 conversion has
> ceased being optional and has to be considered the only option
> at this stage, we really have few clues about what is going to
> cause a given ISP, or a given end-node customer, to switch over.
> Most of our arguments are faulty, at least for some particular
> set of cases.  Your capitalism/competition one is an example --
> there are places where it will work and places where it won't.
> The applications support and availability of IPv6-capable (and
> IPv6-native) servers is another -- sometimes ISPs are waiting
> for customer demand and/or enough deployment on customer sites
> before they think about making the switch and the customers are
> waiting for more evidence that the applications issues are
> sorted out and will work reliably.  We talk about the advantages
> to the folks who switch early, but we are aware that some folks
> don't want to be the first to switch.   And so on, for a rather
> long list.
> 
> Part of this adds up to a conclusion that we are lots better at
> protocol design than we are at predicting the future or gaming
> out the decision processes under various circumstances.  We had
> better be -- our track record for those predictions is bad
> enough that, if our protocol design and engineering were worse,
> we should all find other occupations.
> 
> At the same time, my very limited and quite anecdotal experience
> suggests that the decision in several dual-stack setups to
> automatically prefer IPv6 when it is available (following IETF
> advice if I recall) combines with sometimes-sketchy IPv6
> connections and routing to cause connectivity problems that can
> overwhelm the sorts of folks who staff first-level help desks.
> 6to4 is certainly part of that problem --and a little worse if
> it is set up without user or ISP knowledge-- but the implicit
> argument in both ..-6to4-advice and 6to4-historic that 6to4 is
> the dominant cause of those problems isn't convincing.  Maybe it
> is the case, maybe it is the dominant case (and, again, I don't
> have enough firsthand experience in recent years to claim to
> know) but certainly it is not the only one.  
> 
> I accept the claim that it can easily be misconfigured, but that
> may not be sufficient to demonize it.
> 
> I don't think the technical content of either
> draft-ietf-v6ops-6to4-to-historic or
> draft-ietf-v6ops-6to4-advisory is especially bad.   Indeed, the
> analysis in ...-6to4-advisory seems quite good to me -- the sort
> of thing the IETF should, IMO, be doing a lot more often.  I'm
> just suggesting that we should not write off _any_ option that
> has proven useful to folks in preparing to transition, planning
> for transitions, or actually transitioning.    To that end, the
> abstract of ...6to4-advisory is just the right think to do.
> Advising that 6to4 is a really lousy default, that
> implementations should allow it to be turned on only after
> appropriate warnings and only if the advice in Section 4 of
> ..-6to4-advice is followed _really_ carefully may be entirely
> appropriate.  Put differently, your analysis appears good enough
> that I can see no argument against branding 6to4 as "really
> dangerous -- use only if actually understood and needed, then
> with great caution, and then only if there is some reason why
> 6rd is inappropriate or unavailable".
> 
> But "Historic" is a really blunt instrument, especially since we
> use it primarily for protocols that are no longer in use and/or
> that have been demonstrated to be of no redeeming value.  This
> situation is, IMO, an almost perfect example of why 2026 permits
> us to identify a protocol specification as "NOT RECOMMENDED"
> (yes, I think 2119 is defective in listing the conformance
> language (MUST/ SHOULD/ MAY/...) but not the recommendation
> terminology, but that is another topic).
> 
> So my personal preference, in a more perfect world, would be to
> fold these two drafts together, drop "Historic" and any even
> slightly hyperbolic language, issue the combination as a
> standards-track A/S that updates 3056 and 3068 and makes a clear
> and carefully explained "NOT RECOMMENDED" statement.   If, in
> conjunction with that move, you or others see value in
> downgrading 3056 and 3068 to Experimental and including comments
> to the effect that they are normally useful only for
> exploratory/experimental use, I wouldn't have any problem with
> that at all.
> 
> I actually don't feel very strongly about the above.  I probably
> would not have said anything in this thread if you hadn't raised
> the capitalism/competition argument.  But, if there is a
> situation where 6to4 really is appropriate and the IETF makes
> what appears to be a strong statement deprecating it, we either
> convince someone to further defer thinking through and migrating
> to IPv6 or we help contribute to the impression that the IETF is
> out of touch with real world realities.  I don't consider either
> of those outcomes desirable and presume you don't either.   On
> the other hand, my impression from conversations with operations
> is that it certainly would not be either the first or the most
> extreme case in which we've shown the IETF to be out of touch
> and at least some users and implementers who find value in 6to4
> are likely to continue doing whatever they think it is
> appropriate to do regardless of what labels the IETF decided to
> put on the specs.
> 
> best,
>    john
> 
> 
> p.s. Editorial nit: I'd love to know what a "domestic customer"
> in Sections 2 and 4.2.4 of ...-6to4-advice is.  The term is as
> likely to be construed as "within a particular country" (New
> Zealand?) as "residential" (which I'm guessing is what you
> mean).  As far as I can tell from skimming the document
> "residential, small office, or home office (SOHO)" would be more
> appropriate and consistent with terminology in common use.
> 
> 

From mohta@necom830.hpcl.titech.ac.jp  Fri Jun 10 14:45:13 2011
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 483B111E8197 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 14:45:13 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zhOLJtMjEMwC for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 14:45:12 -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 665AB11E8159 for <ietf@ietf.org>; Fri, 10 Jun 2011 14:45:10 -0700 (PDT)
Received: (qmail 78159 invoked from network); 10 Jun 2011 21:51:33 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 10 Jun 2011 21:51:33 -0000
Message-ID: <4DF29010.5070201@necom830.hpcl.titech.ac.jp>
Date: Sat, 11 Jun 2011 06:43:44 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <4DF177B0.4080303@necom830.hpcl.titech.ac.jp> <318019AA-C0F3-4D25-B60E-034DD248D3E7@apple.com>
In-Reply-To: <318019AA-C0F3-4D25-B60E-034DD248D3E7@apple.com>
Content-Type: text/plain; charset=ISO-2022-JP
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, 10 Jun 2011 21:45:13 -0000

james woodyatt wrote:

> Very very very few people have day jobs that require native IPv6
> service to their home network today.
> 
> I'm an exception because I have a requirement that IPv6 and IPv4
> provide more or less *equivalent* performance characteristics.

Use 4 over 4 in addition to 6 over 4.

I think you are not saying mobile IPv4 with 4 over 4 is not
acceptable IPv4.

PS

If you mind performance, you should better learn how to type
e-mails not to use lines longer than 72 characters.

From brian.e.carpenter@gmail.com  Fri Jun 10 14:45:26 2011
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 8207111E81A7 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 14:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.566
X-Spam-Level: 
X-Spam-Status: No, score=-103.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sq9o-fm5EQHk for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 14:45:25 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9CFCA11E81A0 for <ietf@ietf.org>; Fri, 10 Jun 2011 14:45:25 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2114500fxm.31 for <ietf@ietf.org>; Fri, 10 Jun 2011 14:45:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=6s4TBJnxk5j8yzzO7oZxlOj5PNYEQJFZWFd8o3mY9cg=; b=o0UYYgiR3rQHNGpoFCL8YXPT6fqDnmsKO9ITWMJRNBwX1EO5wO4691o9Vhe1fjH8/y iAaU1YKj0B1oil0ioTJ5wqk6K6HANZH9edTCwDTnymMJSm6nIuAQo5rrxJMh9sDaqmvX kMMAtzrFoyZobQ0n/I9JpCoT2z1fqxHOKgggk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=JyY64YR3IvK5eRkX5R2QPoS3G+UHtj+MtQHH3PYveKTIhlBaKHGIcjB2a3l21gjQAR cN5Tm/0oCFqr93gm0m5OKVepgoKGzRMM5/eJvT0T2LV/JznTHUFWNGl6sIPYyOpnDUlB LHOoLt1O6+ysB+FmvS2Wvv0amxSjYkI5YcaXw=
Received: by 10.223.73.199 with SMTP id r7mr2492832faj.118.1307742324673; Fri, 10 Jun 2011 14:45:24 -0700 (PDT)
Received: from [10.255.25.89] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id q21sm1201571fan.40.2011.06.10.14.45.22 (version=SSLv3 cipher=OTHER); Fri, 10 Jun 2011 14:45:23 -0700 (PDT)
Message-ID: <4DF2906F.9000607@gmail.com>
Date: Sat, 11 Jun 2011 09:45:19 +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: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: Liaison and request for review of ITU-T document
References: <666AC2E8-ECF9-4C64-98B3-839315ED56C3@gmail.com>
In-Reply-To: <666AC2E8-ECF9-4C64-98B3-839315ED56C3@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 21:45:26 -0000

Ralph,

As far as I can tell this seems to describe some sort of a Layer 2 stateful
per-flow QoS mechanism using new Ethertype headers. As such I don't see why
the IETF would care. The point of it escapes me, since we have plenty of reason
to believe that such solutions are impractical and do not scale, but that doesn't
seem like our problem.

I only looked at this to check if it impacted current work in 6MAN on
the IPv6 Flow Label, and there doesn't appear to be any impact or relevance.

Regards
   Brian Carpenter

On 2011-06-08 08:27, Ralph Droms wrote:
> The IETF has recently received a liaison from ITU-T Q5/SG-11 regarding a Draft Recommendation.  That liaison is available as https://datatracker.ietf.org/liaison/1054/.  The official liaison is available at https://datatracker.ietf.org/documents/LIAISON/file1232.pdf.
> 
> The liaison asks for IETF review of Draft Recommendation "Signalling protocols and procedures relating to Flow State Aware QoS control in a bounded sub-network of a NGN", which is available at https://datatracker.ietf.org/documents/LIAISON/file1231.pdf.  This note opens an IETF comment period on the document, ending midnight, anywhere on earth, 2011/7/5.  After the comment period, a summary will be prepared and returned in a liaison to ITU-T Q5/SG-11.
> 
> Of specific interest to the IETF are any ways in which the "signalling protocols and procedures" defined in the Draft Recommendation might interact with existing IETF Internet protocols.  We are especially interested in potential adverse interactions or interference with IETF Internet protocols.  The technical merits of the "signalling protocols and procedures" defined in the Draft Recommendation are of interest inasmuch as the IETF community might provide technical advice and recommendations to improve the Draft Recommendation itself.
> 
> Please respond with any comments on the Draft Recommendation to ietf@ietf.org.  Thanks in advance for your review of the Draft Recommendation.
> 
> - Ralph Droms, Internet Area Director
>   for the IESG
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From joelja@bogus.com  Fri Jun 10 15:11:17 2011
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 6DBDB21F846A for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 15:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.374
X-Spam-Level: 
X-Spam-Status: No, score=-102.374 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PYEAIPZuPJHb for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 15:11:17 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id B88C021F8457 for <ietf@ietf.org>; Fri, 10 Jun 2011 15:10:59 -0700 (PDT)
Received: from 000154tjennings.corp.zynga.com ([12.184.108.202]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5AMArhi023381 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 10 Jun 2011 22:10:55 GMT (envelope-from joelja@bogus.com)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4DF25429.2070601@gmail.com>
Date: Fri, 10 Jun 2011 15:10:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <92F90CDD-6DA4-4B7F-BBCC-5DA43A43AF0B@bogus.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@gmail.com> , <52581FF9790F6D396FB93E09@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222907E9C2@DC-US1MBEX4.global.avaya.com> <B8755BDFE9F2DA066529DC12@PST.JCK.COM> <4DF25429.2070601@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 10 Jun 2011 22:10:55 +0000 (UTC)
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: Fri, 10 Jun 2011 22:11:17 -0000

On Jun 10, 2011, at 10:28 AM, Brian E Carpenter wrote:

> John,
>=20
> On 2011-06-11 05:05, John C Klensin wrote:
>=20
> ...
>> But, to the extent to which the motivation for moving 6to4 to
>> Historic is what Tony describes as "kill-what-we-don't-like",
>=20
> Unfortunately, as I know from the enormous amount of technical
> feedback I got from living, breathing operators while drafting
> draft-ietf-v6ops-advisory, the motivation is "kill something
> that is causing real operational problems and failure modes."
> I wouldn't be endorsing draft-ietf-v6ops-6to4-to-historic if
> there wasn't a very sound operational argument for it.

I'm a content provider. I'm am prepared to turn on more ipv6 services =
that are visible to consumers. 6to4 is a visible and measurable source =
of collateral damage. If consenting adults want to use it that's fine, I =
would greatly appreciate it if the facility were:=20

* off by default

* considered harmful when not deliberately used.

The gradually declining determinism that we fully expect to experience =
from ipv4 access networks and mobile broadband in particular we expect =
to be hard enough to manage without those users riding in over 6to4.

I think the two documents at present encourage:=20

* vendors an implementors to consider not using or a least disabling by =
default 6to4 auto-tunneling in existing and future implementations.

* the deployment of additional 6to4 anycast relays which if done would =
help address issue that existing users of 6to4 who will be with us for a =
while as well as those who would prefer to use it would benefit from.=20

> I think nobody wants to kill the successful use of 6to4, but
> we need to stop the operational problems getting worse. It
> appears that the default help desk advice to disable 1PV6 is
> generally an echo of problems caused by on-by-default 6to4.
>=20
>    Brian
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From jhw@apple.com  Fri Jun 10 15:33:40 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 784ED228011 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 15:33:40 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K7pNru-N-CvV for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 15:33:39 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id CA2AB228010 for <ietf@ietf.org>; Fri, 10 Jun 2011 15:33:39 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LML004G7IO0DNW0@mail-out.apple.com> for ietf@ietf.org; Fri, 10 Jun 2011 15:33:39 -0700 (PDT)
X-AuditID: 11807130-b7c15ae000005aca-6d-4df29bc394e1
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay11.apple.com (Apple SCV relay) with SMTP id 2F.11.23242.3CB92FD4; Fri, 10 Jun 2011 15:33:39 -0700 (PDT)
Received: from [17.193.13.64] (unknown [17.193.13.64]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LML00M4TIO2U680@koseret.apple.com> for ietf@ietf.org; Fri, 10 Jun 2011 15:33:39 -0700 (PDT)
Subject: Re: one data point regarding native IPv6 support
From: james woodyatt <jhw@apple.com>
In-reply-to: <92F90CDD-6DA4-4B7F-BBCC-5DA43A43AF0B@bogus.com>
Date: Fri, 10 Jun 2011 15:33:38 -0700
Message-id: <50A0FF4A-DB27-44FB-89A9-738EBD6F47FC@apple.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@gmail.com> <52581FF9790F6D396FB93E09@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222907E9C2@DC-US1MBEX4.global.avaya.com> <B8755BDFE9F2DA066529DC12@PST.JCK.COM> <4DF25429.2070601@gmail.com> <92F90CDD-6DA4-4B7F-BBCC-5DA43A43AF0B@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1237.1)
X-Brightmail-Tracker: AAAAAA==
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, 10 Jun 2011 22:33:40 -0000

On Jun 10, 2011, at 15:10 , Joel Jaeggli wrote:
> 
> I think the two documents at present encourage: 
> 
> * vendors an implementors to consider not using or a least disabling by default 6to4 auto-tunneling in existing and future implementations.
> 
> * the deployment of additional 6to4 anycast relays which if done would help address issue that existing users of 6to4 who will be with us for a while as well as those who would prefer to use it would benefit from. 

I would say that I-D.ietf-v6ops-6to4-advisory suffices to encourage both those things with more precision and clarity than I-D.ietf-v6ops-6to4-to-historic does.

In fact, I-D.ietf-v6ops-6to4-to-historic makes a more aggressive point on the first item, and sends, at best, a very mixed message about the second.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From john-ietf@jck.com  Fri Jun 10 15:43:18 2011
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 5048E11E80EF for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 15:43:18 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G3Kim5lBY0RD for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 15:43:15 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id C0CCD11E80BF for <ietf@ietf.org>; Fri, 10 Jun 2011 15:42:51 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QVAPh-0002EK-OS; Fri, 10 Jun 2011 18:42:49 -0400
Date: Fri, 10 Jun 2011 18:42:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joel Jaeggli <joelja@bogus.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: one data point regarding native IPv6 support
Message-ID: <5F274DD088279612B40C3B5E@PST.JCK.COM>
In-Reply-To: <92F90CDD-6DA4-4B7F-BBCC-5DA43A43AF0B@bogus.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@gmail.com> , <52581FF9790F6D396FB93E09@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222907E9C2@DC-US1MBEX4.global.avaya.com> <B8755BDFE9F2DA066529DC12@PST.JCK.COM> <4DF25429.2070601@gmail.com> <92F90CDD-6DA4-4B7F-BBCC-5DA43A43AF0B@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 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, 10 Jun 2011 22:43:18 -0000

--On Friday, June 10, 2011 15:10 -0700 Joel Jaeggli
<joelja@bogus.com> wrote:

> I'm a content provider. I'm am prepared to turn on more ipv6
> services that are visible to consumers. 6to4 is a visible and
> measurable source of collateral damage. If consenting adults
> want to use it that's fine, I would greatly appreciate it if
> the facility were: 
> 
> * off by default
> 
> * considered harmful when not deliberately used.

ok

> The gradually declining determinism that we fully expect to
> experience from ipv4 access networks and mobile broadband in
> particular we expect to be hard enough to manage without those
> users riding in over 6to4.
> 
> I think the two documents at present encourage: 
> 
> * vendors an implementors to consider not using or a least
> disabling by default 6to4 auto-tunneling in existing and
> future implementations.
> 
> * the deployment of additional 6to4 anycast relays which if
> done would help address issue that existing users of 6to4 who
> will be with us for a while as well as those who would prefer
> to use it would benefit from. 

Actually not.  That is certainly what the "advice" document
encourages.  But "Historic" is a sufficiently blunt instrument
that moving the base 6to4 specs to Historic could be interpreted
by either vendors or operators as "if you had a transition
strategy based on using 6to4, or are using it today, 6to4 is
sufficiently bad news that it is reasonable to just disable it,
and IPv6 along with it, instead until some unspecified magical
event occurs".  I know that isn't what you intend or how you
would read it, but it is a reading of "Historic" that is
perfectly consistent with things we have used Historic for in
the past.

   john


From marka@isc.org  Fri Jun 10 16:40:59 2011
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 C3EA59E8009 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 16:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XxbzYoJJDCXK for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 16:40:59 -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 E36E29E8005 for <ietf@ietf.org>; Fri, 10 Jun 2011 16:40:58 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 2583BC94AD for <ietf@ietf.org>; Fri, 10 Jun 2011 23:40:48 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 B46F4216C7B for <ietf@ietf.org>; Fri, 10 Jun 2011 23:40:47 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 0E85B10B30A2 for <ietf@ietf.org>; Sat, 11 Jun 2011 09:40:44 +1000 (EST)
To: The IETF <ietf@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF1BA93.5070105@restena.lu> <BANLkTinJSLjbqxM-OzLN-JOK3==3rRgiOA@mail.gmail.com> <4DF1DF3B.2020408@restena.lu> <BANLkTim4arExNBHV5r=iZHdUHdxqvcuhpw@mail.gmail.com> <BANLkTi=WKMfvYQgkgQp4-sOJUbOdiKK8Uw@mail.gmail.com>
Subject: Re: one data point regarding native IPv6 support
In-reply-to: Your message of "Fri, 10 Jun 2011 07:36:37 -0400." <BANLkTi=WKMfvYQgkgQp4-sOJUbOdiKK8Uw@mail.gmail.com>
Date: Sat, 11 Jun 2011 09:40:44 +1000
Message-Id: <20110610234044.0E85B10B30A2@drugs.dv.isc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 23:40:59 -0000

As for Geoff figures.  No one as far as I know has done measurements
of 6to4 failure of explictly enabled 6to4.  Yes Geoff figures seem
scary but if vendors were to make 6to4 users do something to turn
it on I truly think the failure rate would be in the noise.

Lots of the perceived issues with broken 6to4 go away with reasonable
application support for multi-homed servers.  Just yesterday I had
a dual homed site that was reachable over IPv4 but not over IPv6,
routing SNAFU in Canada.  Safari made me wait 30 odd seconds to
connect.  With Chrome I couldn't tell the site was not reachable
over IPv6.  This wasn't a 6to4 issue as neither end was running
6to4.

However it is this delay, which is completely avoidable on the
applications part, that is partially driving this push to move 6to4
to historic.

Also the kill 6to4 crowd push back on anything that would make 6to4
work better for those that can't get native IPv6, whether there is
a technical problem in the proposal or not.  If there is not a
technical problem then shut up.  You may not want to work on it but
others might.

Making 6to4 historic will also stop us working on things that make
6to4 behave better.  Whenever something is proposed in the future
you will hear the kill 6to4 crowd say "6to4 is historic, we can't
work on that."

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  Fri Jun 10 16:51:37 2011
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 72EB99E8009 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 16:51:37 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9qeb8WQZ6-VA for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 16:51:36 -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 B67BD9E8005 for <ietf@ietf.org>; Fri, 10 Jun 2011 16:51:36 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 0ECE9C949D; Fri, 10 Jun 2011 23:51:25 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 9BADB216C7B; Fri, 10 Jun 2011 23:51:24 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id AEECC10B3161; Sat, 11 Jun 2011 09:51:22 +1000 (EST)
To: Joel Jaeggli <joelja@bogus.com>
From: Mark Andrews <marka@isc.org>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@gmail.com> , <52581FF9790F6D396FB93E09@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B222907E9C2@DC-US1MBEX4.global.avaya.com> <B8755BDFE9F2DA066529DC12@PST.JCK.COM> <4DF25429.2070601@gmail.com> <92F90CDD-6DA4-4B7F-BBCC-5DA43A43AF0B@bogus.com>
Subject: Re: one data point regarding native IPv6 support
In-reply-to: Your message of "Fri, 10 Jun 2011 15:10:48 MST." <92F90CDD-6DA4-4B7F-BBCC-5DA43A43AF0B@bogus.com>
Date: Sat, 11 Jun 2011 09:51:22 +1000
Message-Id: <20110610235122.AEECC10B3161@drugs.dv.isc.org>
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: Fri, 10 Jun 2011 23:51:37 -0000

In message <92F90CDD-6DA4-4B7F-BBCC-5DA43A43AF0B@bogus.com>, Joel Jaeggli write
s:
> 
> On Jun 10, 2011, at 10:28 AM, Brian E Carpenter wrote:
> 
> > John,
> > 
> > On 2011-06-11 05:05, John C Klensin wrote:
> > 
> > ...
> >> But, to the extent to which the motivation for moving 6to4 to
> >> Historic is what Tony describes as "kill-what-we-don't-like",
> > 
> > Unfortunately, as I know from the enormous amount of technical
> > feedback I got from living, breathing operators while drafting
> > draft-ietf-v6ops-advisory, the motivation is "kill something
> > that is causing real operational problems and failure modes."
> > I wouldn't be endorsing draft-ietf-v6ops-6to4-to-historic if
> > there wasn't a very sound operational argument for it.
> 
> I'm a content provider. I'm am prepared to turn on more ipv6 services that ar
> e visible to consumers. 6to4 is a visible and measurable source of collateral
>  damage. If consenting adults want to use it that's fine, I would greatly app
> reciate it if the facility were: 
> 
> * off by default
> 
> * considered harmful when not deliberately used.

You don't need to make the protocol historic to achieve this.
 
> The gradually declining determinism that we fully expect to experience from i
> pv4 access networks and mobile broadband in particular we expect to be hard e
> nough to manage without those users riding in over 6to4.
> 
> I think the two documents at present encourage: 

There are at least 4 documents that address aspects of this issue.

You need to add "happy eyeballs" to the mix (which works, see Google
Chrome) and my 6to4 DHCP option draft.

> * vendors an implementors to consider not using or a least disabling by defau
> lt 6to4 auto-tunneling in existing and future implementations.

We don't need vendors to stop implementing (historic).  We just need it
turned off by default (advisary).

> * the deployment of additional 6to4 anycast relays which if done would help a
> ddress issue that existing users of 6to4 who will be with us for a while as w
> ell as those who would prefer to use it would benefit from. 

* the ability to signal that 6to4 will not work with the address you are
  being give.

* the ability to signal that there is a managed 6to4 relay at this address.

> > I think nobody wants to kill the successful use of 6to4, but
> > we need to stop the operational problems getting worse. It
> > appears that the default help desk advice to disable 1PV6 is
> > generally an echo of problems caused by on-by-default 6to4.
> > 
> >    Brian
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> > 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From mohta@necom830.hpcl.titech.ac.jp  Fri Jun 10 17:45:58 2011
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 E420911E8094 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 17:45:58 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W6356rtAkrmr for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 17:45:58 -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 19C249E8027 for <ietf@ietf.org>; Fri, 10 Jun 2011 17:45:57 -0700 (PDT)
Received: (qmail 80208 invoked from network); 11 Jun 2011 00:52:23 -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; 11 Jun 2011 00:52:23 -0000
Message-ID: <4DF2BA67.9080400@necom830.hpcl.titech.ac.jp>
Date: Sat, 11 Jun 2011 09:44:23 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>	<BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com>	<01O2A8KT5RZ600VHKR@mauve.mrochek.com>	<20110610005758.BC2D110ABF81@drugs.dv.isc.org>	<392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local>	<4DF1BA93.5070105@restena.lu>	<BANLkTinJSLjbqxM-OzLN-JOK3==3rRgiOA@mail.gmail.com>	<4DF1DF3B.2020408@restena.lu>	<BANLkTim4arExNBHV5r=iZHdUHdxqvcuhpw@mail.gmail.com>	<BANLkTi=WKMfvYQgkgQp4-sOJUbOdiKK8Uw@mail.gmail.com> <20110610234044.0E85B10B30A2@drugs.dv.isc.org>
In-Reply-To: <20110610234044.0E85B10B30A2@drugs.dv.isc.org>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: The 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, 11 Jun 2011 00:45:59 -0000

Mark Andrews wrote:

> Lots of the perceived issues with broken 6to4 go away with reasonable
> application support for multi-homed servers.

True.

A major design flaw of IPv6 is half hearted support for multihoming
with multiple addresses by broken address selection architecture,
which causes a lot of operational problems, which is partly why
IPv6 is unusable.

Disabling 6to4 and/or improving applications may work for some
faulty cases, but it's not enough at all.

							Masataka Ohta

From marka@isc.org  Fri Jun 10 18:07:17 2011
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 EB39B9E803B for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 18:07:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id POg+loI1KLTE for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 18:07:17 -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 6D2AA9E803A for <ietf@ietf.org>; Fri, 10 Jun 2011 18:07:17 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 23EBDC94BC; Sat, 11 Jun 2011 01:07:05 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 B2BA3216C81; Sat, 11 Jun 2011 01:07:04 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id C2EF510B4484; Sat, 11 Jun 2011 11:06:51 +1000 (EST)
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
From: Mark Andrews <marka@isc.org>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF1BA93.5070105@restena.lu> <BANLkTinJSLjbqxM-OzLN-JOK3==3rRgiOA@mail.gmail.com> <4DF1DF3B.2020408@restena.lu> <BANLkTim4arExNBHV5r=iZHdUHdxqvcuhpw@mail.gmail.com> <BANLkTi=WKMfvYQgkgQp4-sOJUbOdiKK8Uw@mail.gmail.com> <20110610234044.0E85B10B30A2@drugs.dv.isc.org> <4DF2BA67.9080400@necom830.hpcl.titech.ac.jp>
Subject: Re: one data point regarding native IPv6 support
In-reply-to: Your message of "Sat, 11 Jun 2011 09:44:23 +0900." <4DF2BA67.9080400@necom830.hpcl.titech.ac.jp>
Date: Sat, 11 Jun 2011 11:06:51 +1000
Message-Id: <20110611010651.C2EF510B4484@drugs.dv.isc.org>
Cc: The 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, 11 Jun 2011 01:07:18 -0000

In message <4DF2BA67.9080400@necom830.hpcl.titech.ac.jp>, Masataka Ohta writes:
> Mark Andrews wrote:
> 
> > Lots of the perceived issues with broken 6to4 go away with reasonable
> > application support for multi-homed servers.
> 
> True.
> 
> A major design flaw of IPv6 is half hearted support for multihoming
> with multiple addresses by broken address selection architecture,
> which causes a lot of operational problems, which is partly why
> IPv6 is unusable.
> 
> Disabling 6to4 and/or improving applications may work for some
> faulty cases, but it's not enough at all.

The next step is to make multi-homed clients also work well.

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

From shimshamshimmy@gmail.com  Fri Jun 10 18:43:50 2011
Return-Path: <shimshamshimmy@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A62711E80DF; Fri, 10 Jun 2011 18:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tp6VLj13DpDI; Fri, 10 Jun 2011 18:43:49 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 04BC211E80A3; Fri, 10 Jun 2011 18:43:48 -0700 (PDT)
Received: by vws12 with SMTP id 12so3650651vws.31 for <multiple recipients>; Fri, 10 Jun 2011 18:43:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=UNzsMVr7Co3a09/x1txwdZY6Xw3NCl9rL7+dF5nzKvo=; b=VfdH/jK4go4GmPhm6kY8lSLMJT/QFFPXUI4JoyL5kk4bOX1RuBbMW9bkT0TxcIyjhZ GTYBOFYLr9vBE87YGqQH0cPE3IqSpJknWujmar5PYLR/6IhTbeBaoenCs9eg5HuKKjDI TMBQHsAaQnX/mekw090bhcCgmL4dzToB1joMA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type; b=XoDHOUC9VAWVc6Yc2TKRMk/vPxqCP26hSetIR7HxmH2IoZWl3dDBDPrHnH6yVEyOwB KiBvkbCrI7S973QXtdwvM4RCJFUMzap1ipuwTnJkbHpZ/cCaOX+GOFEw8/FHAl/1ZCCn FQx2UGwl3mMr06Fo8v9YZt6BQH6gd8znAUack=
Received: by 10.52.100.7 with SMTP id eu7mr3672074vdb.296.1307756627123; Fri, 10 Jun 2011 18:43:47 -0700 (PDT)
MIME-Version: 1.0
Sender: shimshamshimmy@gmail.com
Received: by 10.52.160.233 with HTTP; Fri, 10 Jun 2011 18:43:27 -0700 (PDT)
From: Jun Murai <jun@wide.ad.jp>
Date: Sat, 11 Jun 2011 10:43:27 +0900
X-Google-Sender-Auth: FzeXOcjgxrnlb4Vqb6QGjlWCBZg
Message-ID: <BANLkTinHsOFgk4Fsac3MQa6LfMjtrNgxcQ@mail.gmail.com>
Subject: Itojun Service Award Announcement
To: "ietf@ietf. org" <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "chair@ietf. org" <chair@ietf.org>, "Lynn St. Amour" <st.amour@isoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2011 01:43:50 -0000

Dear IETFers,
Please note below regarding the Itojun Service Award.
The deadline is July 15.
Thanks in advance,
Jun Murai
===
ANNOUNCING: CALL FOR CANDIDATES FOR ITOJUN SERVICE AWARD

The Itojun Service Award is presented every year to an individual or a
group who has made outstanding contributions in service to the IPv6
community.   The deadline for nominations for this year's award is 15
July 2011.  The award will be presented at the 82nd meeting of the
IETF to be held in November 2011 in Taipei, Taiwan.

About the Award

The Itojun Service Award was established by the friends of Itojun and
administered by the Internet Society (ISOC), recognises and
commemorates the extraordinary dedication exercised by Itojun over the
course of IPv6 development.  The award includes a presentation
crystal, a US$3,000 honorarium, and a travel grant.

The award is focused on pragmatic technical contributions, especially
through development or operation, with the spirit of servicing the
Internet.  With respect to the spirit, the selection committee seeks
contributors to the Internet as a whole; open source developers are a
common example of such contributors, although this is not a
requirement for expected nominees.  While the committee primarily
consider practical contributions such as software development or
network operation, higher level efforts that help those direct
contributions will also be appreciated in this regard.  The
contribution should be substantial, but could be immature or ongoing;
this award aims to encourage the contributor to keep their efforts,
rather than just recognizing well established work.  Finally,
contributions of a group of individuals will be accepted as deployment
work is often done by a large project, not just a single outstanding
individual.

The award is named after Dr. Jun-ichiro "Itojun" Hagino, who passed
away in 2007, aged just 37.  Itojun worked as a Senior Researcher at
Internet Initiative Japan Inc. (IIJ), was a member of the board of the
Widely Integrated Distributed Environment (WIDE) project, and from
1998 to 2006 served on the groundbreaking KAME project in Japan as the
"IPv6 samurai". He was also a member of the Internet Architecture
Board (IAB) from 2003 to 2005.

For additional information on the award, please visit
http://www.isoc.org/awards/itojun/

Award Nomination Procedure

Neither the nominee nor nominator needs to be a member of ISOC.
Nominate via email to <itojun-award at elists.isoc.org> and include the
following details:
1. Name and Email address of nominee (in case of a group nominee,
 names and Email addresses of representative persons of that group)
2. CV/Bio of nominee (in case of a group nominee, a summary of the
 group's achievements)
3. Statement of recommendation including specific acts, works,
 contributions, and other criteria that would show the nominee to
 fit the standard set by Itojun.  Please include corroborating
 references with their name, email address, and telephone
 number. Conclude with your affiliation, postal address, and
 telephone number as well as the postal address, telephone and fax
 number of the nominee.

Thank you in advance for your support,

Jun Murai
Itojun Service Award Selection Committee

From johnl@iecc.com  Fri Jun 10 20:31:28 2011
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 6817C9E800D for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 20:31:28 -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.650, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O8o3tWcGkiGR for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 20:31:28 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id ABC399E8009 for <ietf@ietf.org>; Fri, 10 Jun 2011 20:31:27 -0700 (PDT)
Received: (qmail 67208 invoked from network); 11 Jun 2011 03:31:26 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 11 Jun 2011 03:31:26 -0000
Date: 11 Jun 2011 03:31:04 -0000
Message-ID: <20110611033104.2492.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: one data point regarding native IPv6 support
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: michel@arneill-py.sacramento.ca.us
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2011 03:31:28 -0000

>I would say it's about time reality finally settles in.

The reality is that for now and for the next several years, anyone who
wants to communicate with "the Internet" had better figure out how to
get their packets back and forth to the IPv4 Internet.  This is
totally unfair to new entrants who don't have a source of cheap IPv4
space.  Tough.

I'm all in favor of doing IPv6 experiments and opportunistically using
it when you notice that a remote party supports it, but the urgency of
doing so has been greatly overstated.

R's,
John

From michel@arneill-py.sacramento.ca.us  Fri Jun 10 20:40:34 2011
Return-Path: <michel@arneill-py.sacramento.ca.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 D33F711E808D for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 20:40:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZuhwLoRi-udi for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 20:40:34 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [69.12.226.219]) by ietfa.amsl.com (Postfix) with ESMTP id 4F95B228007 for <ietf@ietf.org>; Fri, 10 Jun 2011 20:40:34 -0700 (PDT)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: one data point regarding native IPv6 support
Date: Fri, 10 Jun 2011 20:40:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF58E@newserver.arneill-py.local>
In-Reply-To: <4DF21D7B.7040103@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: one data point regarding native IPv6 support
Thread-Index: AcwnczOYqODoM2R8Qb2P0vl+jRuAuwAbR3Eg
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com><BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com><01O2A8KT5RZ600VHKR@mauve.mrochek.com>	<20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF21D7B.7040103@gmail.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
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 Jun 2011 03:40:34 -0000

Brian,

>> Michel Py wrote:
>> On that one I agree with Keith; where's the rush? Although
>> imperfect, 6to4 was an obvious path and its demise would be
>> the failure of the IETF, following a long list of things
>> that have been killed prematurely.

> Brian E Carpenter wrote:
> Who's talking about its demise? Really all that the 6to4
> historic draft does is say that it should no longer be
> considered as a default solution to the problem of ISPs
> that don't support IPv6.

I'm not qualified to debate procedural issues, but I will say that, from
a distance, this does smell like a kill-what-we-don't-like. As you have
undoubtedly felt the irony of me defending Keith on this kind of issue,
I will confess that there is a little part of me that did not mind a bit
seeing him getting a taste of his own food in that matter, but I still
think this is premature.


> but the real point is that it's now time for the
> reluctant ISPs to get their heads out of the sand.

I don't think making 6-to-4 historic will change anything in that
regard, which is why I said above that it did look like a
kill-what-we-don't-like.


> You're correct that some ISPs will try to get monopoly
> rents out of the IPv4 shortage, and use CGN to capture
> customers in walled gardens, but fortunately capitalism
> provides a solution to such misbehaviour: other ISPs can
> deploy IPv6 as a competitive advantage.

It does not matter, as long as the core of the "haves" don't do anything
about it, as they command a big enough market share. Besides, you have
not convinced me and not many ISPs either.

I understand what you are trying to do here; nevertheless, 1Pv6 has not
reached critical mass; although I do understand the "disable 1Pv6" issue
(probably better than most) and I do indeed recognize that some of the
brokenness comes from 6to4, it does not change the fact that deprecating
6to4 will reduce the sub-critical mass before it starts chain reaction,
if it ever does.


Michel.


From evnikita2@gmail.com  Fri Jun 10 21:36:04 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD48311E807D for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 21:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.508
X-Spam-Level: 
X-Spam-Status: No, score=-3.508 tagged_above=-999 required=5 tests=[AWL=0.091,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0KF6qbar+3y for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 21:36:04 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id F309611E8075 for <ietf@ietf.org>; Fri, 10 Jun 2011 21:36:03 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2214814fxm.31 for <ietf@ietf.org>; Fri, 10 Jun 2011 21:36:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=IlKpj6LUo/dfhtzE3gfKivFBDnP/2064esRQraeqZdE=; b=f1NU16Lrt3l/7/pUNEutARv7o186mpHekap0IyhJpJt9T+TJUW0mRxeLpIw35OLTzm R1PXKK0ejeyvZkMFuXLznKClJ0OrZ/M9y0G+Q+QKYIESFGZfF9BUlonBG8L7qauMeXIc TffDwMqV8N328SUxJQXGRDP4Onwe5IsHwb2Ec=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=psv6gCSc2CQafGPi92eUhOwWbGG8u02+M/YExZC0EUCE6Y39iEGMakRXYUxWAealCV mfY3Olvi5lLsyBflyLAX1f7BUgyOdgjuXGQsrTd3+pDd+s3U8V3tADbvaIHsqqrISady wvplLvRy4xetGEtY8l+GWzi4aULqi2plFfucI=
Received: by 10.223.24.134 with SMTP id v6mr2784797fab.146.1307766963149; Fri, 10 Jun 2011 21:36:03 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id q21sm1278862fan.16.2011.06.10.21.36.00 (version=SSLv3 cipher=OTHER); Fri, 10 Jun 2011 21:36:01 -0700 (PDT)
Message-ID: <4DF2F0DE.2090704@gmail.com>
Date: Sat, 11 Jun 2011 07:36:46 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-housley-two-maturity-levels-06.txt>	(Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110505161306.3291.13078.idtracker@ietfa.amsl.com>	<4DE42639.5060604@qualcomm.com> <4DEEF3E3.3070003@stpeter.im>	<4DEF012B.40202@qualcomm.com> <2961.1307519909.283808@puncture>
In-Reply-To: <2961.1307519909.283808@puncture>
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, 11 Jun 2011 04:36:04 -0000

08.06.2011 10:58, Dave Cridland wrote:
> On Wed Jun  8 05:57:15 2011, Pete Resnick wrote:
>> On 6/7/11 11:00 PM, Peter Saint-Andre wrote:
>>> And, more to the point I think, to greatly decrease the quality of RFCs
>>> published. Perhaps that's OK, but we need pretty strong consensus that
>>> it's the right thing to do, and I haven't seen that consensus in the
>>> Last Call discussion.
>>
>> All of the above may be true. I personally think that the best thing 
>> that could happen in some sense is to "decrease the quality" of 
>> Proposed Standard RFCs, but that's certainly a controversial view. 
>> And I think it's worthy of an independent discussion. So, at the very 
>> least, we either need to agree on this as a topic for this document 
>> or remove it.
>
> [ . . . ]
>
> The best proposal I've seen - and I'd note that I can't recall now if 
> this is Keith Moore's or Scott Bradner's, to my shame - is that of 
> marking up specific I-D documents as being a "Stable Snapshot". 
To my mind, this will override the basic rule of RFC 2026:

>        ********************************************************
>        *                                                      *
>        *   Under no circumstances should an Internet-Draft    *
>        *   be referenced by any paper, report, or Request-    *
>        *   for-Proposal, nor should a vendor claim compliance *
>        *   with an Internet-Draft.                            *
>        *                                                      *
>        ********************************************************
whereas you propose making I-Ds almost Standards Track.  As it was 
discussed before, there is an evidence of leaving PSs without any 
action/progress; introducing "Stable Snapshots" there might occur 
"Stable Snapshots" left without any action, like PSs.  But PSs are RFCs 
at least and I-Ds are "nothing-as-per-2026".  Adopting this proposal 
might result in implementators claiming "we implement "Stable Snapshot" 
of the Internet-Draft", which is unacceptable, IMO.

Mykyta Yevstifeyev
> This proposal seems to have the following benefits:
>
> a) It satisfies the two paragraphs above in a non-conflicting manner. 
> That is, it provides everything that RFC 2026's PS was intended to 
> without being an RFC, with all that that moniker currently implies.
>
> b) It's fairly obvious, in my view, how to start to use the new grade, 
> and how we might adapt to it in a smooth manner. Working Groups, 
> authors, etc would be able to start to use it in a fairly ad-hoc 
> manner, without the kinds of flag day changes to process that 
> two-maturity-levels seems to imply.
>
> So if anyone has the patience for another I-D thrown into the soup, 
> I'm willing to [re]write this one up, assuming the original 
> instigator[s] of the proposal don't wish to.
>
> Dave.


From julian.reschke@gmx.de  Sat Jun 11 00:59:40 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D4D111E808A for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 00:59: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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w36JO1yvZ0wC for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 00:59:40 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id AEAAB11E8085 for <ietf@ietf.org>; Sat, 11 Jun 2011 00:59:39 -0700 (PDT)
Received: (qmail invoked by alias); 11 Jun 2011 07:59:31 -0000
Received: from p508FC0DE.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.192.222] by mail.gmx.net (mp006) with SMTP; 11 Jun 2011 09:59:31 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18J1Fo/3sEJoFRYkE3hs+x1yvnVumM5q/OxI9OVr1 AuLySRh/ur7nJu
Message-ID: <4DF32061.3050203@gmx.de>
Date: Sat, 11 Jun 2011 09:59:29 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-06.txt>	(Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110505161306.3291.13078.idtracker@ietfa.amsl.com>	<4DE42639.5060604@qualcomm.com>	<4DEEF3E3.3070003@stpeter.im>	<4DEF012B.40202@qualcomm.com>	<2961.1307519909.283808@puncture> <4DF2F0DE.2090704@gmail.com>
In-Reply-To: <4DF2F0DE.2090704@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Sat, 11 Jun 2011 07:59:40 -0000

On 2011-06-11 06:36, Mykyta Yevstifeyev wrote:
> ...
> whereas you propose making I-Ds almost Standards Track. As it was
> discussed before, there is an evidence of leaving PSs without any
> action/progress; introducing "Stable Snapshots" there might occur
> "Stable Snapshots" left without any action, like PSs. But PSs are RFCs
> at least and I-Ds are "nothing-as-per-2026". Adopting this proposal
> might result in implementators claiming "we implement "Stable Snapshot"
> of the Internet-Draft", which is unacceptable, IMO.
> ...

Out of curiosity: why do you find that "unacceptable"?

It's *good* when the stuff in IDs gets implemented, and it's also good 
if there's clear information *which* draft is implemented.

What can be problematic is when products are *released* with this kind 
of implementation.

Best regards, Julian

From mohta@necom830.hpcl.titech.ac.jp  Sat Jun 11 03:42:39 2011
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 0218211E809A for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 03:42:39 -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=[AWL=-0.000,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pum2O6sxGwck for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 03:42:38 -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 2CAC711E8093 for <ietf@ietf.org>; Sat, 11 Jun 2011 03:42:37 -0700 (PDT)
Received: (qmail 88820 invoked from network); 11 Jun 2011 10:49:18 -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; 11 Jun 2011 10:49:18 -0000
Message-ID: <4DF34663.5020205@necom830.hpcl.titech.ac.jp>
Date: Sat, 11 Jun 2011 19:41:39 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <20110610005758.BC2D110ABF81@drugs.dv.isc.org> <392CB277BC2EAE4FB83C1206954BA6CEF58C@newserver.arneill-py.local> <4DF1BA93.5070105@restena.lu> <BANLkTinJSLjbqxM-OzLN-JOK3==3rRgiOA@mail.gmail.com> <4DF1DF3B.2020408@restena.lu> <BANLkTim4arExNBHV5r=iZHdUHdxqvcuhpw@mail.gmail.com> <BANLkTi=WKMfvYQgkgQp4-sOJUbOdiKK8Uw@mail.gmail.com> <20110610234044.0E85B10B30A2@drugs.dv.isc.org> <4DF2BA67.9080400@necom830.hpcl.titech.ac.jp> <20110611010651.C2EF510B4484@drugs.dv.isc.org>
In-Reply-To: <20110611010651.C2EF510B4484@drugs.dv.isc.org>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: The 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, 11 Jun 2011 10:42:39 -0000

Mark Andrews wrote:

>> A major design flaw of IPv6 is half hearted support for multihoming
>> with multiple addresses by broken address selection architecture,
>> which causes a lot of operational problems, which is partly why
>> IPv6 is unusable.
>>
>> Disabling 6to4 and/or improving applications may work for some
>> faulty cases, but it's not enough at all.

> The next step is to make multi-homed clients also work well.

A problem is that RFC2374 was thrown away and the current address
assignment procedure is broken to promote multihoming with routing,
which means people won't use multihoming with multiple IPv6
addresses.

Thus, you can't expect proper support for hosts with two (IPv4 and
IPv6) addresses.

						Masataka Ohta

From evnikita2@gmail.com  Sat Jun 11 06:46:55 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3DFB11E80A5 for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 06:46:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.523
X-Spam-Level: 
X-Spam-Status: No, score=-3.523 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06F9MLth-xQ8 for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 06:46:55 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1C85411E8093 for <ietf@ietf.org>; Sat, 11 Jun 2011 06:46:54 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2352957fxm.31 for <ietf@ietf.org>; Sat, 11 Jun 2011 06:46:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=TO10Cqr++TI7cn13Q6h5mP2miT0yZaACShc9zdYsp9o=; b=O0L0+Rfi6KfiK/gpIUeuYRMyHLcSQDFpAakpXBO/o7XDm57eVP/eIBLhmK2MhhHv/F jn7se/sKrL84X4l66g5hHRmQ73MtmMxYXSWD1yeV5Zf7GsUiUslX6TGT6eDeZ1yMzF52 +mwlHZRO8L78CzXe/V6abbR3isXjuwymH8pm0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=ajMv38/MrdlwQ89uW2heQdSNoIhhmsFWs/rIrD6KqixvAiGEnQs1U+rM/smwbqKHl2 RfYI1R8l/vfC99s6B3TOIb8/qVBrsL5feKaHVDkI58MJAnlyjxIWsBfNrr5aR6sKNdl8 Yo/s8t3D2CvzLD7IkSeVaVlt+uoQcxGRWRMAA=
Received: by 10.223.145.78 with SMTP id c14mr3140448fav.75.1307800014318; Sat, 11 Jun 2011 06:46:54 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id e15sm1404412faa.47.2011.06.11.06.46.52 (version=SSLv3 cipher=OTHER); Sat, 11 Jun 2011 06:46:53 -0700 (PDT)
Message-ID: <4DF371FA.5060508@gmail.com>
Date: Sat, 11 Jun 2011 16:47:38 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Last Call: <draft-housley-two-maturity-levels-06.txt>	(Reducing the Standards Track to Two Maturity Levels) to BCP
References: <20110505161306.3291.13078.idtracker@ietfa.amsl.com>	<4DE42639.5060604@qualcomm.com>	<4DEEF3E3.3070003@stpeter.im>	<4DEF012B.40202@qualcomm.com>	<2961.1307519909.283808@puncture> <4DF2F0DE.2090704@gmail.com> <4DF32061.3050203@gmx.de>
In-Reply-To: <4DF32061.3050203@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Jun 2011 13:46:55 -0000

11.06.2011 10:59, Julian Reschke wrote:
> On 2011-06-11 06:36, Mykyta Yevstifeyev wrote:
>> ...
>> whereas you propose making I-Ds almost Standards Track. As it was
>> discussed before, there is an evidence of leaving PSs without any
>> action/progress; introducing "Stable Snapshots" there might occur
>> "Stable Snapshots" left without any action, like PSs. But PSs are RFCs
>> at least and I-Ds are "nothing-as-per-2026". Adopting this proposal
>> might result in implementators claiming "we implement "Stable Snapshot"
>> of the Internet-Draft", which is unacceptable, IMO.
>> ...
>
> Out of curiosity: why do you find that "unacceptable"?
>
> It's *good* when the stuff in IDs gets implemented, and it's also good 
> if there's clear information *which* draft is implemented.
>
> What can be problematic is when products are *released* with this kind 
> of implementation.
Under-development implementation is doubtlessly useful.  Above under 
"implementing" I meant final implementation, incorporating some 
technology in the final product.  Introducing "Stable Snaps" is very 
likely to make such cases more frequent, as they will be made almost 
equal to RFCs.

Mykyta Yevstifeyev
> Best regards, Julian
>


From ned+ietf@mauve.mrochek.com  Sat Jun 11 12:28:33 2011
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 735DA11E8210 for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 12:28: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eFYA5MGiVYvD for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 12:28:32 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 39AB111E81F7 for <ietf@ietf.org>; Sat, 11 Jun 2011 12:28:32 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O2CUUTK64G00BCMH@mauve.mrochek.com> for ietf@ietf.org; Sat, 11 Jun 2011 12:28:06 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01O28N39BBNK00VHKR@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 11 Jun 2011 12:27:58 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01O2CUUQ4V8K00VHKR@mauve.mrochek.com>
Date: Sat, 11 Jun 2011 12:26:40 -0700 (PDT)
Subject: Re: one data point regarding native IPv6 support
In-reply-to: "Your message dated Fri, 10 Jun 2011 22:11:22 +0100" <2961.1307740282.616986@puncture>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format=flowed; DelSp=yes
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <C1BE11D6-DDD3-4D23-BC28-9501E4AF1372@guppylake.com> <2961.1307740282.616986@puncture>
To: Dave Cridland <dave@cridland.net>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1307820182; i=@mrochek.com; bh=BIZ0AceI15uwwE/lg0xqqfxfV2uLLHHjlAony/LtdFw=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=mv9fwRZaV6dYtc7VKJrCCc+eDAxeOZDuLzNIxM46gxgYDZC4IM1NeCcTkwvt4CodQ aFe3/xFqp7e3Yg+IdHWL6Wb12Z6g6Di/lHTZLthW1TfjN8GnRRtu4aLuazs78FedeT NOhlAvSgTZO/tKUn4iMJtWmwsMZ+j3bxK+onZQOo=
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, Nathaniel Borenstein <nsb@guppylake.com>, IETF-Discussion <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Jun 2011 19:28:33 -0000

> On Fri Jun 10 17:15:55 2011, Nathaniel Borenstein wrote:
> > At the risk of piling on, I can't resist the opportunity to try to
> > one-up Ned's story.
> >
> > While in the UK this year, I had the misfortune to need to call BT
> > for support on my broken home Internet connection.  In the middle
> > of the usual mind-numbing "we will force you to walk through every
> > idiotic step that you already know is irrelevant after thirty years
> > in the business,"  the phone support guy told me to "Click on the
> > pulldown for 'Configure one-pee-vee-six' and set it to Off."  Not
> > only was this totally irrelevant, and not only did he routinely
> > make me turn off the very protocol we want to enable, but he called
> > that protocol "one pee v6" instead of "eye pee v6."   And when I
> > was stupid enough to correct him, he wouldn't go any further until
> > I admitted that he knew best, and that I should call it "one pee
> > v6" rather than "eye pee v6."    Needless to say, I didn't bother
> > asking about BT's plans to support IPv6 -- oops, I mean 1Pv6.
> >
> > No need to ask.  If BT can't even spell IP, we are a11 d00med.  --
> > Nathaniel
> >
> >
> Particularly poor as BT are actually quite clued up on IPv6:

> http://www.ipv6.bt.com/

> (And I don't work for BT, have never worked for BT, have been in
> competition with BT, and I don't use their service)

> I would *never* judge an ISP by the clueless nature of their scripted
> first-line suppor, at least not beyond their existence. (The ISP I
> use does not have clueless script monkeys, but smart and helpful
> people who craft their response to fit your ability, not theirs).

That rather depends on whether or not it's possible to get past the
cluelessness, doesn't it? If it isn't pssible it seems not only reasonable to
judge on this basis, but pretty silly not to.

				Ned

From moore@network-heretics.com  Sat Jun 11 12:36:54 2011
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 0EFB811E8241 for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 12:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.348
X-Spam-Level: 
X-Spam-Status: No, score=-3.348 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kq2zGyTqdKzI for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 12:36:53 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 39ED711E8201 for <ietf@ietf.org>; Sat, 11 Jun 2011 12:36:53 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 286A920A02; Sat, 11 Jun 2011 15:36:51 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute4.internal (MEProxy); Sat, 11 Jun 2011 15:36:51 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=4xqyg8R3CjSYeexHeailQd5awE4=; b=nbtE5kg6hCZr8ReS7l8pYpDrWua6O+xWGsJPoHLABI5RAl2dBJLQH/tNgCqIm0o40PO8a6M5PjcOHSu8WEBYXCOQJ2/phB0x4C7ZbMopTwKLXufzIfDlEP4uPxIhhwQxlHpg3v9QCTbKRt5kFbN/TtXa3nYhsbGJqeT18htSEuk=
X-Sasl-enc: kSFmjhmIR99yGvdQeAlwtL0YyIvbZiyd6RuYi63qvDyN 1307821010
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id B7849442ED8; Sat, 11 Jun 2011 15:36:49 -0400 (EDT)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-1-948810760
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <01O2CUUQ4V8K00VHKR@mauve.mrochek.com>
Date: Sat, 11 Jun 2011 15:36:48 -0400
Message-Id: <C9B0B75B-69E1-4D2F-8141-E618415AA6B2@network-heretics.com>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <BB993627-C05B-43AD-BCE2-0A642AC2D947@apple.com> <01O2A8KT5RZ600VHKR@mauve.mrochek.com> <C1BE11D6-DDD3-4D23-BC28-9501E4AF1372@guppylake.com> <2961.1307740282.616986@puncture> <01O2CUUQ4V8K00VHKR@mauve.mrochek.com>
To: Ned Freed <ned.freed@mrochek.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, Nathaniel Borenstein <nsb@guppylake.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: Sat, 11 Jun 2011 19:36:54 -0000

--Apple-Mail-1-948810760
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 11, 2011, at 3:26 PM, Ned Freed wrote:
>=20
>> I would *never* judge an ISP by the clueless nature of their scripted
>> first-line suppor, at least not beyond their existence. (The ISP I
>> use does not have clueless script monkeys, but smart and helpful
>> people who craft their response to fit your ability, not theirs).
>=20
> That rather depends on whether or not it's possible to get past the
> cluelessness, doesn't it? If it isn't pssible it seems not only =
reasonable to
> judge on this basis, but pretty silly not to.

If we want IPv6 to be available to the average user, I think it's fair =
to assume that the average user won't get past the cluelessness.

Then again, I fully suspect that the first line sales/support people =
will be the last to know when an ISP is ready to support IPv6.  They =
won't know until they're forced to watch a training video that says so.

Keith


--Apple-Mail-1-948810760
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 11, 2011, at 3:26 PM, Ned Freed =
wrote:</div><blockquote type=3D"cite"><div><font =
class=3D"Apple-style-span" color=3D"#000000"><br></font><blockquote =
type=3D"cite">I would *never* judge an ISP by the clueless nature of =
their scripted<br></blockquote><blockquote type=3D"cite">first-line =
suppor, at least not beyond their existence. (The ISP =
I<br></blockquote><blockquote type=3D"cite">use does not have clueless =
script monkeys, but smart and helpful<br></blockquote><blockquote =
type=3D"cite">people who craft their response to fit your ability, not =
theirs).<br></blockquote><br>That rather depends on whether or not it's =
possible to get past the<br>cluelessness, doesn't it? If it isn't =
pssible it seems not only reasonable to<br>judge on this basis, but =
pretty silly not to.<br></div></blockquote></div><br><div>If we want =
IPv6 to be available to the average user, I think it's fair to assume =
that the average user won't get past the =
cluelessness.</div><div><br></div><div>Then again, I fully suspect that =
the first line sales/support people will be the last to know when an ISP =
is ready to support IPv6. &nbsp;They won't know until they're forced to =
watch a training video that says =
so.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-1-948810760--

From johnl@iecc.com  Sat Jun 11 13:55:12 2011
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 11EB01F0C49 for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 13:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.766
X-Spam-Level: 
X-Spam-Status: No, score=-110.766 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ytDlaJ51JSx for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 13:55:11 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id 599281F0C43 for <ietf@ietf.org>; Sat, 11 Jun 2011 13:55:11 -0700 (PDT)
Received: (qmail 5372 invoked from network); 11 Jun 2011 20:55:09 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 11 Jun 2011 20:55:09 -0000
Date: 11 Jun 2011 20:54:47 -0000
Message-ID: <20110611205447.6579.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: one data point regarding native IPv6 support
In-Reply-To: <C9B0B75B-69E1-4D2F-8141-E618415AA6B2@network-heretics.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
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, 11 Jun 2011 20:55:12 -0000

>If we want IPv6 to be available to the average user, I think it's
>fair to assume that the average user won't get past the cluelessness.

The average user is never going to call up and ask "can I get IPv6 as
part of my bundle along with the Home Shopping Network" so the first
level cluelessness doesn't matter.

It's going to be available to the average user when the average cable
or DSL modem autoconfigures itself to offer IPv6, and SLAAC and DHCPv6
work well enough on average consumer PCs and other wifi devices that
they set themselves up without any manual intervention.  You know,
like they do with IPv4.

I realize all these pieces work in theory, and often in practice if
you know what button to tweak.  But Grandma is unlikely to tweak any
network buttons at all.

R's,
John

From hamza.gharsallah@gmail.com  Sat Jun 11 13:58:30 2011
Return-Path: <hamza.gharsallah@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BBC41F0C49 for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 13:58:30 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Hmq31VsXbxD for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 13:58:29 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 68C6E1F0C43 for <ietf@ietf.org>; Sat, 11 Jun 2011 13:58:29 -0700 (PDT)
Received: by iyn15 with SMTP id 15so4027167iyn.31 for <ietf@ietf.org>; Sat, 11 Jun 2011 13:58:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=6WNdJeEcyXTsQantzQzLKpga4bLjltkYzHgLGYHTMlc=; b=GUTa0V20rRSxufEOciFJc+9DgO5YIeC4eD2+9yHmNBRsTCS4uOqCah7OBOqV9Nyq4w 9Tno53/RYJQomCKgB4BxhLatZwgYuUnDAS9qYAzkCIlm1ZAtkdrpnZ0Du0+EpRIvpUzC e1jEVyaL7hY3Iy07I6UgmPZ5HQpw5hHASFcsc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=VC6EYhNpOX6vY19xC3LyZFGkHgz1hJ0lBpuHaIfugPhZ+prRuWuTpscCe9OkT+OOna xCxo/6jPFjDdPu72ZXZOxooCTpdVMp8Kdr8mrKLgQMKh0f2Kc9lvcXBJcZgjLOku4zbD c2RJFn7hezrP9yFHQoyJaWzAe2alWxNQ+gWBg=
MIME-Version: 1.0
Received: by 10.42.172.133 with SMTP id n5mr4624765icz.66.1307825907672; Sat, 11 Jun 2011 13:58:27 -0700 (PDT)
Received: by 10.231.13.204 with HTTP; Sat, 11 Jun 2011 13:58:27 -0700 (PDT)
In-Reply-To: <20110611205447.6579.qmail@joyce.lan>
References: <C9B0B75B-69E1-4D2F-8141-E618415AA6B2@network-heretics.com> <20110611205447.6579.qmail@joyce.lan>
Date: Sat, 11 Jun 2011 21:58:27 +0100
Message-ID: <BANLkTimsVmz_iucXtpZpiRo2q-VLaGuXWg@mail.gmail.com>
Subject: Re: one data point regarding native IPv6 support
From: Hamza GHARSALLAH <hamza.gharsallah@gmail.com>
To: John Levine <johnl@iecc.com>
Content-Type: multipart/alternative; boundary=90e6ba6e87faa7a85f04a575f252
Cc: ietf@ietf.org, 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, 11 Jun 2011 20:58:30 -0000

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

Hi! All!

Why don't we run it the opposite way:
-IPv6 by default, else:
-Legacy: just run IPv4 with some kind of NAT.



On Sat, Jun 11, 2011 at 9:54 PM, John Levine <johnl@iecc.com> wrote:

> >If we want IPv6 to be available to the average user, I think it's
> >fair to assume that the average user won't get past the cluelessness.
>
> The average user is never going to call up and ask "can I get IPv6 as
> part of my bundle along with the Home Shopping Network" so the first
> level cluelessness doesn't matter.
>
> It's going to be available to the average user when the average cable
> or DSL modem autoconfigures itself to offer IPv6, and SLAAC and DHCPv6
> work well enough on average consumer PCs and other wifi devices that
> they set themselves up without any manual intervention.  You know,
> like they do with IPv4.
>
> I realize all these pieces work in theory, and often in practice if
> you know what button to tweak.  But Grandma is unlikely to tweak any
> network buttons at all.
>
> R's,
> John
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

<div dir=3D"ltr">Hi! All!<br><br>Why don&#39;t we run it the opposite way:<=
br>-IPv6 by default, else:<br>-Legacy: just run IPv4 with some kind of NAT.=
<br><br><br><br><div class=3D"gmail_quote">On Sat, Jun 11, 2011 at 9:54 PM,=
 John Levine <span dir=3D"ltr">&lt;<a href=3D"mailto:johnl@iecc.com">johnl@=
iecc.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">&gt;If we want IPv6 to be=
 available to the average user, I think it&#39;s<br>
&gt;fair to assume that the average user won&#39;t get past the cluelessnes=
s.<br>
<br>
</div>The average user is never going to call up and ask &quot;can I get IP=
v6 as<br>
part of my bundle along with the Home Shopping Network&quot; so the first<b=
r>
level cluelessness doesn&#39;t matter.<br>
<br>
It&#39;s going to be available to the average user when the average cable<b=
r>
or DSL modem autoconfigures itself to offer IPv6, and SLAAC and DHCPv6<br>
work well enough on average consumer PCs and other wifi devices that<br>
they set themselves up without any manual intervention. =A0You know,<br>
like they do with IPv4.<br>
<br>
I realize all these pieces work in theory, and often in practice if<br>
you know what button to tweak. =A0But Grandma is unlikely to tweak any<br>
network buttons at all.<br>
<br>
R&#39;s,<br>
<font color=3D"#888888">John<br>
</font><div><div></div><div class=3D"h5">__________________________________=
_____________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
</div></div></blockquote></div><br></div>

--90e6ba6e87faa7a85f04a575f252--

From mcr@sandelman.ca  Sat Jun 11 16:31:43 2011
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 8F5BE11E809D for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 16:31:43 -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=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VqO60ye4TXXI for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 16:31:42 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id E114611E8097 for <ietf@ietf.org>; Sat, 11 Jun 2011 16:31:42 -0700 (PDT)
Received: from marajade.sandelman.ca (wlan204.sandelman.ca [209.87.252.204]) by relay.sandelman.ca (Postfix) with ESMTPS id B73EB3416C; Sat, 11 Jun 2011 19:31:41 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 87CE798ABD; Sat, 11 Jun 2011 19:33:24 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: ietf@ietf.org, moore@network-heretics.com
Subject: Re: one data point regarding native IPv6 support
In-Reply-To: <20110611205447.6579.qmail@joyce.lan>
References: <20110611205447.6579.qmail@joyce.lan>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Sat, 11 Jun 2011 19:33:24 -0400
Message-ID: <4532.1307835204@marajade.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: Sat, 11 Jun 2011 23:31:43 -0000

>>>>> "John" == John Levine <johnl@iecc.com> writes:
    >> If we want IPv6 to be available to the average user, I think it's
    >> fair to assume that the average user won't get past the cluelessness.

    John> The average user is never going to call up and ask "can I get IPv6 as
    John> part of my bundle along with the Home Shopping Network" so the first
    John> level cluelessness doesn't matter.

...

    John> you know what button to tweak.  But Grandma is unlikely to tweak any
    John> network buttons at all.

"I want that Internet that George down the street has, that let's his
daughter get the scoop on what groceries he needs"  

(by talking directly to his fridge)

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 




From johnl@iecc.com  Sat Jun 11 18:22:31 2011
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 71F9521F8535 for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 18:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.874
X-Spam-Level: 
X-Spam-Status: No, score=-110.874 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qcj9TrwtWu46 for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 18:22:30 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id DF5DD21F8534 for <ietf@ietf.org>; Sat, 11 Jun 2011 18:22:27 -0700 (PDT)
Received: (qmail 34082 invoked from network); 12 Jun 2011 01:22:26 -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:vbr-info:user-agent:cleverness; s=8521.4df414d2.k1106; i=johnl@submit.iecc.com; bh=ZPAxc1d+TXc2jYXd98daIE4Ux1qJiykctoy1RmYAsdQ=; b=uzvF5a8h3nI1ZTzUezX1kmcuFNVyxjYnsYq6H73sDsvL6O3Ct29XyAhT3089J+Fva9I6ydSRg3Ha926fE/nKeh5UQ3oa70+x3CAExjYdVMrWlvtwD6MfWfNatnTvRLEWr6FztCMe0SU7Fbq1SAoP8anmfH2+NtLZ9uAquKVK7mQ=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 12 Jun 2011 01:22:04 -0000
Date: 11 Jun 2011 21:22:26 -0400
Message-ID: <alpine.BSF.2.00.1106112122020.7048@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Hamza GHARSALLAH" <hamza.gharsallah@gmail.com>
Subject: Re: one data point regarding native IPv6 support
In-Reply-To: <BANLkTimsVmz_iucXtpZpiRo2q-VLaGuXWg@mail.gmail.com>
References: <C9B0B75B-69E1-4D2F-8141-E618415AA6B2@network-heretics.com> <20110611205447.6579.qmail@joyce.lan> <BANLkTimsVmz_iucXtpZpiRo2q-VLaGuXWg@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 01:22:31 -0000

> Why don't we run it the opposite way:
> -IPv6 by default, else:
> -Legacy: just run IPv4 with some kind of NAT.

If the answer to that question isn't obvious, I don't think I can help.

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 moore@network-heretics.com  Sat Jun 11 18:29:02 2011
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 341E121F8536 for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 18:29:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.358
X-Spam-Level: 
X-Spam-Status: No, score=-3.358 tagged_above=-999 required=5 tests=[AWL=0.241,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cRU+NomISpd9 for <ietf@ietfa.amsl.com>; Sat, 11 Jun 2011 18:29:01 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 790CE21F8535 for <ietf@ietf.org>; Sat, 11 Jun 2011 18:29:01 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 287E52126F; Sat, 11 Jun 2011 21:29:01 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Sat, 11 Jun 2011 21:29:01 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=q7TuI9vH7JcGX0zcD1mpudnva0o=; b=bIlrXQmx+2AL2sRpRPYxiohKl3Un94oNzX8DKObJvN5qO1RIFGA7GHA63jM5B3JTJ66goFKzysaJd3Ik4y8vnVKth4kPZPyLOZ6il28LfwvZ+4Dyj55w/PXRBuhJgSafEQUfRGigqd97Xh0ibGJUaVFdtf9ieDz6i7Cb+h3u29w=
X-Sasl-enc: 23w1sMRbVja9JdU3Lhy9D/6AHNs30DVUWQrX4EUdUznk 1307842140
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 504D8443D8A; Sat, 11 Jun 2011 21:29:00 -0400 (EDT)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110611205447.6579.qmail@joyce.lan>
Date: Sat, 11 Jun 2011 21:28:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA6710C1-A912-4328-99A0-4592EA59F72A@network-heretics.com>
References: <20110611205447.6579.qmail@joyce.lan>
To: John Levine <johnl@iecc.com>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 01:29:02 -0000

On Jun 11, 2011, at 4:54 PM, John Levine wrote:

>> If we want IPv6 to be available to the average user, I think it's
>> fair to assume that the average user won't get past the cluelessness.
>=20
> The average user is never going to call up and ask "can I get IPv6 as
> part of my bundle along with the Home Shopping Network" so the first
> level cluelessness doesn't matter.
>=20
> It's going to be available to the average user when the average cable
> or DSL modem autoconfigures itself to offer IPv6, and SLAAC and DHCPv6
> work well enough on average consumer PCs and other wifi devices that
> they set themselves up without any manual intervention.  You know,
> like they do with IPv4.
>=20
> I realize all these pieces work in theory, and often in practice if
> you know what button to tweak.  But Grandma is unlikely to tweak any
> network buttons at all.

agree.  So when we're trying to evaluate whether IPv6 is widely =
available, it's not sufficient for it to be widely available to clueful =
users who can badger their way past first tier support.  It has to be =
available to Grandma.

Keith
=20=

From krishnabirth@gmail.com  Sun Jun 12 03:41:57 2011
Return-Path: <krishnabirth@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CCF111E8081 for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 03:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.81
X-Spam-Level: 
X-Spam-Status: No, score=-2.81 tagged_above=-999 required=5 tests=[AWL=0.789,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ni9FJ3V-yYy3 for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 03:41:57 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1773411E8070 for <ietf@ietf.org>; Sun, 12 Jun 2011 03:41:56 -0700 (PDT)
Received: by ywp31 with SMTP id 31so2244542ywp.31 for <ietf@ietf.org>; Sun, 12 Jun 2011 03:41:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=ZoAd2S2oFUwm5kFZi9XRfBkjoL2LT9V5cfOH73edJ4w=; b=A1KKmXBGz7061mgKF1McmmLZPRiMq6aSwPnzZ5TOszJ6dJnF47T5W+lJ56c5voVcB5 WGJlULtJsfFwv1+GbbKqsd7jyRSTZzGTeK009OVgL6018zQi8xvkxboyqT9aMYdOqPQw ATQAONvrlFX4ZaGfKAVSMLWw9T46rJn+qQ+/k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=t4Xs+eQ3AYxkNW+978an2ghB6wWpri70GlF2mJ9CInueK6qg77Nzdiv7GGXSN6Xro3 II8eLxzBNP96vZSZ0Fs4TLT7ft4D04c7bn8z85yb2AcetqH/EsUdLltqo9YCXkw5u/H+ e/ndGwkqQpt3ZkJ8wdNW3rmIK0rBnfYDrnDWA=
MIME-Version: 1.0
Received: by 10.236.209.1 with SMTP id r1mr5471087yho.78.1307875316492; Sun, 12 Jun 2011 03:41:56 -0700 (PDT)
Received: by 10.236.179.9 with HTTP; Sun, 12 Jun 2011 03:41:56 -0700 (PDT)
Date: Sun, 12 Jun 2011 10:41:56 +0000
Message-ID: <BANLkTik7C-X6Eg+MnVF4BdM42Wp+Sc5zmg@mail.gmail.com>
Subject: Bring Your Own Server
From: Krishna Birth <krishnabirth@gmail.com>
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: Sun, 12 Jun 2011 10:41:57 -0000

I am not a techie and thus could any expert please say if there are
any data centres in GB offering inexpensive, 'Bring Your Own Server'
service with possibility to set up the India holy river water cooled
PC into a server for hosting websites?  Sorry if this mailing list
post is a bit different to the what you are used to.


Regards,


Meeku

From jari.arkko@piuha.net  Sun Jun 12 06:37:35 2011
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 B21FC11E80E1; Sun, 12 Jun 2011 06:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.467
X-Spam-Level: 
X-Spam-Status: No, score=-102.467 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ABroXdlNJ5KI; Sun, 12 Jun 2011 06:37:35 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 1C57B11E8072; Sun, 12 Jun 2011 06:37:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3CEDE2CC4D; Sun, 12 Jun 2011 16:37: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 b-+pE7a6o8H2; Sun, 12 Jun 2011 16:37:33 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 3B6682CC3B; Sun, 12 Jun 2011 16:37:33 +0300 (EEST)
Message-ID: <4DF4C11C.9020500@piuha.net>
Date: Sun, 12 Jun 2011 16:37:32 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-pppext-trill-protocol-06.txt> (PPP TRILL Protocol Control Protocol) to Proposed Standard
References: <20110525161357.5909.40860.idtracker@ietfa.amsl.com>
In-Reply-To: <20110525161357.5909.40860.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pppext@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 13:37:35 -0000

This document has been in IESG review last week. A number of technical 
issues were raised (thank you!) and we are almost done with addressing 
them. Still negotiating what change, if any, to be done based on the 
Security AD's Discuss.

However, the IESG has also asked me to treat this document as if it were 
an Individual Submission. This is not a negative assessment of the 
document content, the document was appreciated. But the IESG correctly 
noted that its not within the PPPEXT group's charter. It was my mistake 
to not catch this earlier. Sorry.

In any case, as a result, we will deal with this document as an 
Individual Submission. The main change is the last call period. The last 
call of this document will continue until it has been under review for 
four weeks, and will be re-evaluated in the IESG telechat on June 23rd. 
We'd be happy to receive additional reviews.

Jari


From touch@isi.edu  Sun Jun 12 06:51:40 2011
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 E126F11E8085; Sun, 12 Jun 2011 06:51: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KYUBljSuJ5KU; Sun, 12 Jun 2011 06:51:40 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 6044411E80F8; Sun, 12 Jun 2011 06:51:40 -0700 (PDT)
Received: from [128.9.176.27] (c1-vpn1.isi.edu [128.9.176.27]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id p5CDpGPF013880 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Sun, 12 Jun 2011 06:51:17 -0700 (PDT)
Message-ID: <4DF4C454.7070904@isi.edu>
Date: Sun, 12 Jun 2011 06:51:16 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, IETF discussion list <ietf@ietf.org>, draft-ietf-dnsext-rfc2672bis-dname@tools.ietf.org, dnsext@ietf.org
Subject: TSVDIR review of  draft-ietf-dnsext-rfc2672bis-dname
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: TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jun 2011 13:51:41 -0000

Hi, all,

I've reviewed this document as part of the transport area directorate's 
ongoing effort to review key IETF documents. These comments were written 
primarily for the transport area directors, but are copied to the 
document's authors for their information and to allow them to address 
any issues raised. The authors should consider this review together with 
any other last-call comments they receive. Please always CC 
tsv-dir@ietf.org if you reply to or forward this review.

The document discusses change to the DNAME DNS record. Such changes are 
discussed in their impact to both the DNS in general, and to SRV records 
in particular. These are the key ways in which this change affects 
transport protocols, and are sufficiently addressed; there do not appear 
to be any other transport issues.

I do have some other concerns which are noted below, and which are 
offered for consideration.

I hope this feedback will be useful to the authors, and will be glad to 
provide further assistance either on- or off-list as useful.

Joe

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

The document fails to explain exactly how it changes RFC 2672. At best 
this is noted obliquely in the end of section 2.5 (is this all?). These 
changes should be made clear in the abstract, the intro, and in a 
separate section summarizing the exact ways in which this document 
overrides RFC 2672. The same advice applies for other RFCs this document 
updates (though this does appear to occur in Sec 4).

Further, it is not clear whether this document changes only part of 
RFC2672. It includes some parts of that RFC unmodified (Sec 3.2). If 
this document *obsoletes* that RFC, is this document complete in the 
absence of that RFC? (this should be made clear in the document explicitly).

The abstract explains this is an update and which RFCs are affected, but 
should also briefly state how and why. I.e., the abstract should be 
self-contained.

"Punycode" should be described when introduced, with a reference.

Wherever this document includes advice from RFCs it does not update 
(e.g., Sec 3.3), it should explicitly indicate whether it is copying 
advice verbatim or clarifying it.

Sec 6 should be revised to clarify the relationship between IANA and the 
registries it operates. I.e.:

    The DNAME Resource Record type code 39 (decimal) originally has been
    registered by [RFC2672].  IANA should update the DNS resource record
    registry to point to this document for RR type 39.
should read:
    The DNAME Resource Record type code 39 (decimal) originally and
    currently refers to [RFC2672], the document that initiated its
    assignment. IANA should update the DNS resource record registry to
    refer to this document for RR type 39.

---








-----

From nsb@guppylake.com  Sun Jun 12 11:49:40 2011
Return-Path: <nsb@guppylake.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8390911E8117 for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 11:49:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EOv0I2+ZZ8pq for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 11:49:38 -0700 (PDT)
Received: from server1.netnutz.com (server1.netnutz.com [72.233.90.3]) by ietfa.amsl.com (Postfix) with ESMTP id 6A21E11E8115 for <ietf@ietf.org>; Sun, 12 Jun 2011 11:49:38 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=guppylake.com; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer; b=SvDCHff03QS4BIWO47YLkqjctujXEZkH0hW2EjB9Tvw8fE65hg21IhnUjkLk61h2EiFEBw9A0A2zndXw08CksRO/AE5wfIYlNHB4zIZ5jrOPkoeJwMh0DdJNqyIR2/WQ;
Received: from c-68-42-65-200.hsd1.mi.comcast.net ([68.42.65.200] helo=[192.168.2.3]) by server1.netnutz.com with esmtpa (Exim 4.69) (envelope-from <nsb@guppylake.com>) id 1QVpj4-0008Ud-2D; Sun, 12 Jun 2011 14:49:35 -0400
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <DA6710C1-A912-4328-99A0-4592EA59F72A@network-heretics.com>
Date: Sun, 12 Jun 2011 14:49:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <28D6E065-CB4D-48D7-B1C5-FC85C22BBF6F@guppylake.com>
References: <20110611205447.6579.qmail@joyce.lan> <DA6710C1-A912-4328-99A0-4592EA59F72A@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server1.netnutz.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - guppylake.com
Cc: John Levine <johnl@iecc.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jun 2011 18:49:40 -0000

Just for the record:

-- I don't believe that my single experience with first line tech =
support at BT says much about BT's broader role, or its relative =
sophistication and service quality as an ISP.  For all I know it's the =
best ISP in the world, and has a lone bozo at tech support to qualify =
for a "jobs for bozos" tax credit.  I was simply relating an experience =
that I found rather extreme.

-- I do believe that a world in which any tech support person at any =
major ISP doesn't know how to spell IP -- whether he's telling you to =
turn off IPv6 or not -- is a world in which it is very challenging to =
expect positive outcomes in the major technical transition we are trying =
to effect.

-- I don't believe that I know what to do about it.  I'm almost sorry I =
mentioned it -- we still have a long way to go before we need to start =
worrying about Grandma configuring IPv6 at home.  -- Nathaniel


On Jun 11, 2011, at 9:28 PM, Keith Moore wrote:

>=20
> On Jun 11, 2011, at 4:54 PM, John Levine wrote:
>=20
>>> If we want IPv6 to be available to the average user, I think it's
>>> fair to assume that the average user won't get past the =
cluelessness.
>>=20
>> The average user is never going to call up and ask "can I get IPv6 as
>> part of my bundle along with the Home Shopping Network" so the first
>> level cluelessness doesn't matter.
>>=20
>> It's going to be available to the average user when the average cable
>> or DSL modem autoconfigures itself to offer IPv6, and SLAAC and =
DHCPv6
>> work well enough on average consumer PCs and other wifi devices that
>> they set themselves up without any manual intervention.  You know,
>> like they do with IPv4.
>>=20
>> I realize all these pieces work in theory, and often in practice if
>> you know what button to tweak.  But Grandma is unlikely to tweak any
>> network buttons at all.
>=20
> agree.  So when we're trying to evaluate whether IPv6 is widely =
available, it's not sufficient for it to be widely available to clueful =
users who can badger their way past first tier support.  It has to be =
available to Grandma.
>=20
> Keith
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From michel@arneill-py.sacramento.ca.us  Sun Jun 12 12:24:05 2011
Return-Path: <michel@arneill-py.sacramento.ca.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 3953B11E811F for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 12:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AxD5JmaK79-l for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 12:24:04 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [69.12.226.219]) by ietfa.amsl.com (Postfix) with ESMTP id 8919B11E807D for <ietf@ietf.org>; Sun, 12 Jun 2011 12:24:04 -0700 (PDT)
Subject: RE: one data point regarding native IPv6 support
Date: Sun, 12 Jun 2011 12:24:03 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>
In-Reply-To: <C9B0B75B-69E1-4D2F-8141-E618415AA6B2@network-heretics.com>
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: one data point regarding native IPv6 support
Thread-Index: AcwobuyCRK34px0ARIW+rmHAWli3ewAvlaYg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@network-heretics.com>
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jun 2011 19:24:05 -0000

According to this:
http://blogs.cisco.com/sp/france-is-famous-for-fine-wine-cheese-and-now-
ipv6/
and some more recent direct talks in French, about half of worldwide
IPv6 traffic is French.

The bulk of it comes from a single ISP (Free, AS12322) and their IPv6 is
6RD (RFC5569, RFC5969), a variant of 6to4. Given the constant references
in 6RD to 6to4, I will point out that making 6to4 historic somehow
reduces the likeliness of another extremely successful ISP
implementation based on it.

Although Google (in
http://www.pam2010.ethz.ch/papers/full-length/15.pdf) and other
measurements classify AS12322's traffic as native, it is 6RD behind the
scenes.

If the argument is that IPv6 "native" should be the preferred solution
over "tunneled", it does not hold water. If you were to remove 6to4 and
6RD from the picture, that would set us back 10 years ago in terms of
IPv6 adoption.

Michel.


From michel@arneill-py.sacramento.ca.us  Sun Jun 12 12:33:33 2011
Return-Path: <michel@arneill-py.sacramento.ca.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 DA6CB21F8470 for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 12:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ybsv+5R+Lar for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 12:33:33 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [69.12.226.219]) by ietfa.amsl.com (Postfix) with ESMTP id 3596A21F846E for <ietf@ietf.org>; Sun, 12 Jun 2011 12:33:33 -0700 (PDT)
Subject: RE: one data point regarding native IPv6 support
Date: Sun, 12 Jun 2011 12:33:32 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF592@newserver.arneill-py.local>
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: one data point regarding native IPv6 support
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Index: AcwobuyCRK34px0ARIW+rmHAWli3ewAvlaYgAAJ6I+A=
References: <C9B0B75B-69E1-4D2F-8141-E618415AA6B2@network-heretics.com> <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@network-heretics.com>
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jun 2011 19:33:34 -0000

Oops, copy/paste casualty, sorry. Read below instead.

According to this: http://tinyurl.com/5u3eorn and some
more recent direct talks in French, about half of
worldwide IPv6 traffic is French.

The bulk of it comes from a single ISP (Free, AS12322) and
their IPv6 is 6RD (RFC5569, RFC5969), a variant of 6to4.
Given the constant references in 6RD to 6to4, I will point
out that making 6to4 historic somehow reduces the likeliness
of another extremely successful ISP implementation based on it.

Although Google (in
http://www.pam2010.ethz.ch/papers/full-length/15.pdf) and other
measurements classify AS12322's traffic as native, it is 6RD
behind the scenes.

If the argument is that IPv6 "native" should be the preferred
Solution over "tunneled", it does not hold water. If you were
to remove 6to4 and 6RD from the picture, that would set us back
10 years ago in terms of IPv6 adoption.

Michel.


From dougb@dougbarton.us  Sun Jun 12 12:45:18 2011
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 A040711E813E for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 12:45:18 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NfIg8J1FWqJc for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 12:45:17 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 9557F11E813F for <ietf@ietf.org>; Sun, 12 Jun 2011 12:45:17 -0700 (PDT)
Received: (qmail 4515 invoked by uid 399); 12 Jun 2011 19:45:15 -0000
Received: from unknown (HELO ?65.241.43.5?) (dougb@dougbarton.us@65.241.43.5) by mail2.fluidhosting.com with ESMTPAM; 12 Jun 2011 19:45:15 -0000
X-Originating-IP: 65.241.43.5
X-Sender: dougb@dougbarton.us
Message-ID: <4DF5174B.9060605@dougbarton.us>
Date: Sun, 12 Jun 2011 12:45:15 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Michel Py <michel@arneill-py.sacramento.ca.us>
Subject: Re: one data point regarding native IPv6 support
References: <C9B0B75B-69E1-4D2F-8141-E618415AA6B2@network-heretics.com>	<392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local> <392CB277BC2EAE4FB83C1206954BA6CEF592@newserver.arneill-py.local>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF592@newserver.arneill-py.local>
X-Enigmail-Version: 1.1.1
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: Sun, 12 Jun 2011 19:45:18 -0000

On 6/12/2011 12:33 PM, Michel Py wrote:
> If the argument is that IPv6 "native" should be the preferred
> Solution over "tunneled", it does not hold water. If you were
> to remove 6to4 and 6RD from the picture, that would set us back
> 10 years ago in terms of IPv6 adoption.

Can you explain the exact mechanism by which what you're concerned about 
will occur? I don't see anything in the draft which prevents an ISP from 
deploying 6rd.


Doug (but I might have missed something)

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From moore@network-heretics.com  Sun Jun 12 12:54:24 2011
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 1A79511E814B for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 12:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.366
X-Spam-Level: 
X-Spam-Status: No, score=-3.366 tagged_above=-999 required=5 tests=[AWL=0.233,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PUUUIx32TkHC for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 12:54:23 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 51C0D11E8147 for <ietf@ietf.org>; Sun, 12 Jun 2011 12:54:23 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 52BA82240D; Sun, 12 Jun 2011 15:54:21 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute6.internal (MEProxy); Sun, 12 Jun 2011 15:54:21 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=wW44TyyhpnjRSA516PcYsE4Txec=; b=uvLeIrAr0tjO5tcC77LtTcDSBNRp0KGlUzNBIuY/udpXHtREeoglUUJ0dBGou48pJG3yPtglF/sSmmG3P/qmlKQpyZoJB92xfVPxlFFbLUdmIdWXG68LhaGSdkWzip8i8+I3y/38rxy/XEOVbtW9FZhhLss8HV4+UbBwNNPevF4=
X-Sasl-enc: o2VltwWFLzySCX8pwQindb6Q8vCOCyWiZ0HUxaoG+mum 1307908460
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 7E3FD442A05; Sun, 12 Jun 2011 15:54:20 -0400 (EDT)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF592@newserver.arneill-py.local>
Date: Sun, 12 Jun 2011 15:54:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9862EBF2-A7E1-4169-AF12-B7676450BA1D@network-heretics.com>
References: <C9B0B75B-69E1-4D2F-8141-E618415AA6B2@network-heretics.com> <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local> <392CB277BC2EAE4FB83C1206954BA6CEF592@newserver.arneill-py.local>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jun 2011 19:54:24 -0000

On Jun 12, 2011, at 3:33 PM, Michel Py wrote:

> If the argument is that IPv6 "native" should be the preferred
> Solution over "tunneled", it does not hold water.

To be fair, I think the argument is more that "ISP managed" IPv6 is =
preferred over "IPv6 tunneled by end-users through relay routers set up =
on an ad hoc basis".  And I can't really disagree with that.

I don't think there's any doubt that native > 6rd > 6to4 (where ">" is =
"a better way to deploy IPv6").  But you have to use whatever you can =
get.

For ISPs that are still looking at native v6 as a target to be deployed =
to consumers in a few years or longer, I really wish they'd consider 6rd =
as an interim step.
And for those rolling out LSN, I really wish they'd at least roll out =
6rd along with it.  That way, application developers that currently use =
PnP or NAT-PMP to get through NATs would have the option of using IPv6, =
instead of having to support yet another NAT traversal hack in their =
code (and supporting different NAT hacks for different customers).

Keith


From michel@arneill-py.sacramento.ca.us  Sun Jun 12 18:18:23 2011
Return-Path: <michel@arneill-py.sacramento.ca.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 41AD721F8486 for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 18:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8FqMWcj6mG5K for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 18:18:22 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [69.12.226.219]) by ietfa.amsl.com (Postfix) with ESMTP id B62DC21F8484 for <ietf@ietf.org>; Sun, 12 Jun 2011 18:18:22 -0700 (PDT)
Subject: RE: one data point regarding native IPv6 support
Date: Sun, 12 Jun 2011 18:18:22 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF593@newserver.arneill-py.local>
In-Reply-To: <4DF5174B.9060605@dougbarton.us>
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: one data point regarding native IPv6 support
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Index: AcwpOUHtDIM9MKG6QaiV78F68p4Z9wALWCwg
References: <C9B0B75B-69E1-4D2F-8141-E618415AA6B2@network-heretics.com>	<392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local> <392CB277BC2EAE4FB83C1206954BA6CEF592@newserver.arneill-py.local> <4DF5174B.9060605@dougbarton.us>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Doug Barton" <dougb@dougbarton.us>
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2011 01:18:23 -0000

>> Michel Py wrote:
>> If you were to remove 6to4 and 6RD from the
>> picture, that would set us back 10 years
>> ago in terms of IPv6 adoption.

> Doug Barton wrote:
> Can you explain the exact mechanism by which what you're
> concerned about will occur? I don't see anything in the
> draft which prevents an ISP from deploying 6rd.

There is not. OTOH, I am not aware of any sizeable deployment of 6RD
outside of AS12322; 6RD may not be for everyone, and what making 6to4
historic may prevent is: someone else using 6to4, finding out that there
are some issues, and coining another highly successful 6to4 variant that
would fit their needs better.

Michel.


From cb.list6@gmail.com  Sun Jun 12 18:58:40 2011
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 3805C1F0C49 for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 18:58:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id evOMId9P-o0f for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 18:58:39 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 61B3F1F0C34 for <ietf@ietf.org>; Sun, 12 Jun 2011 18:58:39 -0700 (PDT)
Received: by wyb29 with SMTP id 29so3348417wyb.31 for <ietf@ietf.org>; Sun, 12 Jun 2011 18:58:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=6MvlHVYl7x50DMUINrAcp18sBIQZT6fXgE3m7dNYKcU=; b=X2cui+a0bqBt2FdIWIwOh7Gxzq0DYU2Q/3PZmU4oHwXrEyDvSLuQRZ5iLmCS3EZQxe kx2Ph02+aOZPy3JNLRvXBW5kMiFdbL6eR3AkEF8U2omdQnmLMB7tZN4oAgEivlYVxUbQ mDdFLA79S87cjon4giqXINiwKXEs4Mqe+BcBk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QgBhPIEw6/rpWglh3SoxQW2G1IUtqQSYQ1HJ8Fib+6hkKaKCYM4+VQHeeAMQ2FOmhg 37jJfv35Q9ok2M00zW/L6dm0KQ4iDSAVhAUlv/8nF+QD6ynPagrhXzQJnmIDSRHnlJKn FsibUiN7UMeyJHa01Q7pkxFvcbyWBOocSw9zg=
MIME-Version: 1.0
Received: by 10.217.1.212 with SMTP id n62mr2097182wes.25.1307930317616; Sun, 12 Jun 2011 18:58:37 -0700 (PDT)
Received: by 10.216.165.82 with HTTP; Sun, 12 Jun 2011 18:58:37 -0700 (PDT)
Received: by 10.216.165.82 with HTTP; Sun, 12 Jun 2011 18:58:37 -0700 (PDT)
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF593@newserver.arneill-py.local>
References: <C9B0B75B-69E1-4D2F-8141-E618415AA6B2@network-heretics.com> <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local> <392CB277BC2EAE4FB83C1206954BA6CEF592@newserver.arneill-py.local> <4DF5174B.9060605@dougbarton.us> <392CB277BC2EAE4FB83C1206954BA6CEF593@newserver.arneill-py.local>
Date: Sun, 12 Jun 2011 18:58:37 -0700
Message-ID: <BANLkTimQXT1AFdA05-BKHxLHLsP+OHgDAQ@mail.gmail.com>
Subject: Re: RE: one data point regarding native IPv6 support
From: Cameron Byrne <cb.list6@gmail.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
Content-Type: multipart/alternative; boundary=20cf301e2f5bf8f45604a58e41dd
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2011 01:58:40 -0000

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

On Jun 12, 2011 6:18 PM, "Michel Py" <michel@arneill-py.sacramento.ca.us>
wrote:
>
> >> Michel Py wrote:
> >> If you were to remove 6to4 and 6RD from the
> >> picture, that would set us back 10 years
> >> ago in terms of IPv6 adoption.
>
> > Doug Barton wrote:
> > Can you explain the exact mechanism by which what you're
> > concerned about will occur? I don't see anything in the
> > draft which prevents an ISP from deploying 6rd.
>
> There is not. OTOH, I am not aware of any sizeable deployment of 6RD
> outside of AS12322; 6RD may not be for everyone, and what making 6to4
> historic may prevent is: someone else using 6to4, finding out that there
> are some issues, and coining another highly successful 6to4 variant that
> would fit their needs better.
>

The faint promise of yet another transition mechanism is hardly a motivation
to keep 6to4 around.

The data (ripe ...) overwhelming proves default-on 6to4 clients + thinly
deployed relays = unreliable ipv6 and ipv6 deployment obstacle.
Cb

> Michel.
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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

<p><br>
On Jun 12, 2011 6:18 PM, &quot;Michel Py&quot; &lt;<a href=3D"mailto:michel=
@arneill-py.sacramento.ca.us">michel@arneill-py.sacramento.ca.us</a>&gt; wr=
ote:<br>
&gt;<br>
&gt; &gt;&gt; Michel Py wrote:<br>
&gt; &gt;&gt; If you were to remove 6to4 and 6RD from the<br>
&gt; &gt;&gt; picture, that would set us back 10 years<br>
&gt; &gt;&gt; ago in terms of IPv6 adoption.<br>
&gt;<br>
&gt; &gt; Doug Barton wrote:<br>
&gt; &gt; Can you explain the exact mechanism by which what you&#39;re<br>
&gt; &gt; concerned about will occur? I don&#39;t see anything in the<br>
&gt; &gt; draft which prevents an ISP from deploying 6rd.<br>
&gt;<br>
&gt; There is not. OTOH, I am not aware of any sizeable deployment of 6RD<b=
r>
&gt; outside of AS12322; 6RD may not be for everyone, and what making 6to4<=
br>
&gt; historic may prevent is: someone else using 6to4, finding out that the=
re<br>
&gt; are some issues, and coining another highly successful 6to4 variant th=
at<br>
&gt; would fit their needs better.<br>
&gt;</p>
<p>The faint promise of yet another transition mechanism is hardly a motiva=
tion to keep 6to4 around.=A0 </p>
<p>The data (ripe ...) overwhelming proves default-on 6to4 clients + thinly=
 deployed relays =3D unreliable ipv6 and ipv6 deployment obstacle.=A0 <br>
Cb</p>
<p>&gt; Michel.<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Ietf mailing list<br>
&gt; <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf">https://www.iet=
f.org/mailman/listinfo/ietf</a><br>
</p>

--20cf301e2f5bf8f45604a58e41dd--

From michel@arneill-py.sacramento.ca.us  Sun Jun 12 23:26:41 2011
Return-Path: <michel@arneill-py.sacramento.ca.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 D7BF4228015 for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 23:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NQHvgma4j0iZ for <ietf@ietfa.amsl.com>; Sun, 12 Jun 2011 23:26:41 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [69.12.226.219]) by ietfa.amsl.com (Postfix) with ESMTP id 5C61F228013 for <ietf@ietf.org>; Sun, 12 Jun 2011 23:26:41 -0700 (PDT)
Subject: RE: RE: one data point regarding native IPv6 support
Date: Sun, 12 Jun 2011 23:26:40 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF594@newserver.arneill-py.local>
In-Reply-To: <BANLkTimQXT1AFdA05-BKHxLHLsP+OHgDAQ@mail.gmail.com>
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: one data point regarding native IPv6 support
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Index: AcwpbWucYoKpDqAAT6WIxEbYUaqCWwAJKEQg
References: <392CB277BC2EAE4FB83C1206954BA6CEF593@newserver.arneill-py.local> <BANLkTimQXT1AFdA05-BKHxLHLsP+OHgDAQ@mail.gmail.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Cameron Byrne" <cb.list6@gmail.com>
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2011 06:26:42 -0000

> Cameron Byrne wrote:
> The faint promise of yet another transition mechanism is hardly
> a motivation to keep 6to4 around.=A0 The data (ripe ...)
> overwhelming proves default-on 6to4 clients + thinly deployed
> relays =3D unreliable ipv6 and ipv6 deployment obstacle.=A0=20

That's the difference between a fait promise and a proven failure. The =
promise of "IPv6 native IPv6 is going to be deployed next year" has =
failed for 10+ years in a row. Nobody believes in it anymore; your =
choices are to believe in yet another transition mechanism or switch to =
the post-mortem camp.

Get a life.

Michel.


From jari.arkko@piuha.net  Mon Jun 13 01:07:33 2011
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 58BBC11E8082 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 01:07:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.478
X-Spam-Level: 
X-Spam-Status: No, score=-102.478 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwLaOFsjcZrq for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 01:07:32 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 5DA2811E8071 for <ietf@ietf.org>; Mon, 13 Jun 2011 01:07:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id F07D32CC3C for <ietf@ietf.org>; Mon, 13 Jun 2011 11:07:29 +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 rH0liLfaXFZc for <ietf@ietf.org>; Mon, 13 Jun 2011 11:07:26 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 359702CC3B for <ietf@ietf.org>; Mon, 13 Jun 2011 11:07:26 +0300 (EEST)
Message-ID: <4DF5C53D.1070402@piuha.net>
Date: Mon, 13 Jun 2011 11:07:25 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: one data point regarding native IPv6 support
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <4DF1AD04.2090402@isdg.net>
In-Reply-To: <4DF1AD04.2090402@isdg.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, 13 Jun 2011 08:07:33 -0000

I have a general point and then a couple of my own stories to tell.

The general point is that you should NOT read too much into this. Tech 
support or sales on any consumer service is very dumb. Most often they 
do not even understand their own current business, let alone new 
features or trends. As an example, in cellular data networking the 
concept of an APN (Access Point Name) is crucial to the operation of the 
networks and the user configurations. A few years ago I had some 
connectivity trouble and called the operator's help desk to see if I had 
the right APN. I had to progress FOUR LEVELS through their technical 
support layers before I even got someone who understood the term APN. 
And this was for something about their current networks. Had I asked 
about rolling out (N+1)G I probably would have had to go through even 
more levels.

And then to my other story. Its a happy IPv6 story, I think. As a test 
case, I  called my ISP this morning. For background, my previous ISP 
merged with this ISP last week. I'm talking to their first level support 
guy.

Me: Can you enable IPv6 for my ADSL?
Agent: We do have that service. Can I get your address?
Me: <my address>
Agent: You are one of the customers moved from the other ISP last week
Me: Yes
Agent: I would normally just turn IPv6 for you here, but for these 
accounts its not possible yet.
Agent: You can get the IPv6 service but let us call you back after some 
investigation. You may need to change your account type.
Me: Ok

(The ISP is Nebula, by the way, http://www.nebula.fi. Other people have 
had good IPv6 experience with them.)

Jari


From daedulus@btconnect.com  Mon Jun 13 06:18:21 2011
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 5445621F8535 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 06:18:21 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzfQ22BVAdlE for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 06:18:19 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by ietfa.amsl.com (Postfix) with ESMTP id 7BCDB21F8533 for <ietf@ietf.org>; Mon, 13 Jun 2011 06:18:19 -0700 (PDT)
Received: from host81-156-207-154.range81-156.btcentralplus.com (HELO pc6) ([81.156.207.154]) by c2beaomr10.btconnect.com with SMTP id DDX05683; Mon, 13 Jun 2011 14:18:14 +0100 (BST)
Message-ID: <01f101cc29c3$ad48e960$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Keith Moore" <moore@network-heretics.com>, "IETF Discussion" <ietf@ietf.org>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com>
Subject: Re: one data point regarding native IPv6 support
Date: Mon, 13 Jun 2011 14:16:02 +0200
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-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0301.4DF60E16.0048, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.6.13.114822:17:7.586, ip=81.156.207.154, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_PATH, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0203.4DF60E18.001A,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: 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: Mon, 13 Jun 2011 13:18:21 -0000

Another data point from a different and large ISP (and mobile company).

Mobile supplier calls.  We have this great new broadband offer for you with all
these irresistible features.

Tom. Does it support IPv6, Internet Protocol version six?

Mobile supplier.  I will check with my supervisor.

.... {long pause}

Mobile supplier.  We support 95, 98, 2000, XP, Vista and 7.

Tom.  Thank you, but not today.

(This is one of four major suppliers in my country of whom zero have announced
IPv6 support or have any hits on their web sites last time I looked at them)

Tom Petch

----- Original Message -----
From: "Keith Moore" <moore@network-heretics.com>
To: "IETF Discussion" <ietf@ietf.org>
Sent: Thursday, June 09, 2011 8:24 PM
Subject: one data point regarding native IPv6 support


> I just called my ISP to ask about availability of IPv6 at my home.
>
> Me:  "I'm a current customer, and I'm just calling to ask if you support
Internet Protocol Version 6."
>
> First person: "Yes, we do support Internet.  We support DSL at 3 megabits and
6 megabits."
>
> Me: "I understand that, but I'm asking about Internet Protocol version 6,
IPv6.  The Internet has been using IP version 4 since the early 1980s, but
that's running out.  IPv6 is the new version."
>
> First person: "Let me transfer you to support."
>
> Second person: "Hi, this is support.  How may I help you?"
>
> Me: "I'm a current customer, and I'm just calling to ask if you support
Internet Protocol Version 6."
>
> Second person: "IP version what?"
>
> Me: "Internet protocol version 6".
>
> Second person: "I have no idea.  Let me transfer you to someone else."
>
> (places me on hold for 15 minutes)
>
> Second person: "I'm sorry for the wait time.  I've been trying to find the
answer to your question, but nobody here seems to know anything about it.  We're
trying to get in touch with people who run the network to ask them.   Can I get
your number and call you back?"
>
> Granted, this is just one ISP.  The other ISP that offers service in my area
put me on hold for an hour and a half *before anyone ever talked to me* when I
tried to get a quote from them, so I concluded that they wouldn't be a good
choice.  And these guys have been good about support in general.  They seem to
know their stuff, which is more than I can say for some ISPs I've dealt with in
the past.
>
> I live in a well-settled urban area, three miles from the center of the city
(and sadly, four miles from my CO, which means my DSL circuit gets around
380kbits/sec).  It's not a backwater, there's plenty of lit fiber running
through town.  But when the support people for a fairly well-established telco
haven't even heard of IPv6, it's hard to believe that it's going to be available
anytime soon.
>
> Meanwhile, 6to4 continues to work just fine for me.
>
> So please explain again why it isn't premature to discourage a valuable
transition mechanism?
>
> Keith
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From cb.list6@gmail.com  Mon Jun 13 06:35:26 2011
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 7CE6C9E8010 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 06:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E+2x6fGkmOWh for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 06:35:25 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6E4749E8007 for <ietf@ietf.org>; Mon, 13 Jun 2011 06:34:59 -0700 (PDT)
Received: by wyb29 with SMTP id 29so3698261wyb.31 for <ietf@ietf.org>; Mon, 13 Jun 2011 06:34:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=aKOdtLsrsxVR+XFrEFqxEjO9saX+UkW0YkFbbN7rCgI=; b=FgrLkAQIhxa4M5Z9l3qiRvb++e8cCW+0nD9C7GyWzjDNUgLKzUyOzaebpv1z2aLib2 3xsSSeUxglHqYfW9kx+3GT0qL+TR08tTqbLOxJ6h7UzERxM7yxE8CH1DeT5eGWIlDICQ r3PKELoLp4iV98hJLHjzkdEde83j+lUWY0GL0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ILRLMz4QQzkppd1kA/FJaxSMYaE4bijZAq1jBszHb8neH60VN4Uc9daAJwjCJVWLU7 TmVGFFWR+sI8Me4tcQl1CyTwo2ucxCIW14Ze9+PiFJrc5S5preUqOPbPSE2Ee4Ha7Zto yjn0z3kfAwTXIIsw22S9aOe1BmbnZubdkJT38=
MIME-Version: 1.0
Received: by 10.216.52.193 with SMTP id e43mr2668641wec.40.1307972098526; Mon, 13 Jun 2011 06:34:58 -0700 (PDT)
Received: by 10.216.165.82 with HTTP; Mon, 13 Jun 2011 06:34:58 -0700 (PDT)
Received: by 10.216.165.82 with HTTP; Mon, 13 Jun 2011 06:34:58 -0700 (PDT)
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF594@newserver.arneill-py.local>
References: <392CB277BC2EAE4FB83C1206954BA6CEF593@newserver.arneill-py.local> <BANLkTimQXT1AFdA05-BKHxLHLsP+OHgDAQ@mail.gmail.com> <392CB277BC2EAE4FB83C1206954BA6CEF594@newserver.arneill-py.local>
Date: Mon, 13 Jun 2011 06:34:58 -0700
Message-ID: <BANLkTima65057k+67ONyJs+DvhitfJhzfA@mail.gmail.com>
Subject: Re: RE: RE: one data point regarding native IPv6 support
From: Cameron Byrne <cb.list6@gmail.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
Content-Type: multipart/alternative; boundary=0016e6dee70f4f106504a597fc23
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2011 13:35:26 -0000

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

On Jun 12, 2011 11:26 PM, "Michel Py" <michel@arneill-py.sacramento.ca.us>
wrote:
>
> > Cameron Byrne wrote:
> > The faint promise of yet another transition mechanism is hardly
> > a motivation to keep 6to4 around.  The data (ripe ...)
> > overwhelming proves default-on 6to4 clients + thinly deployed
> > relays = unreliable ipv6 and ipv6 deployment obstacle.
>
> That's the difference between a fait promise and a proven failure. The
promise of "IPv6 native IPv6 is going to be deployed next year" has failed
for 10+ years in a row. Nobody believes in it anymore; your choices are to
believe in yet another transition mechanism or switch to the post-mortem
camp.
>

I believe there is data to show this time is different (iana and apnic are
exhausted, successful v6day, docsis 3.0 and LTE deployment ...)

> Get a life.
>

Thanks

Cb
> Michel.
>

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

<p><br>
On Jun 12, 2011 11:26 PM, &quot;Michel Py&quot; &lt;<a href=3D"mailto:miche=
l@arneill-py.sacramento.ca.us">michel@arneill-py.sacramento.ca.us</a>&gt; w=
rote:<br>
&gt;<br>
&gt; &gt; Cameron Byrne wrote:<br>
&gt; &gt; The faint promise of yet another transition mechanism is hardly<b=
r>
&gt; &gt; a motivation to keep 6to4 around.=A0 The data (ripe ...)<br>
&gt; &gt; overwhelming proves default-on 6to4 clients + thinly deployed<br>
&gt; &gt; relays =3D unreliable ipv6 and ipv6 deployment obstacle.=A0<br>
&gt;<br>
&gt; That&#39;s the difference between a fait promise and a proven failure.=
 The promise of &quot;IPv6 native IPv6 is going to be deployed next year&qu=
ot; has failed for 10+ years in a row. Nobody believes in it anymore; your =
choices are to believe in yet another transition mechanism or switch to the=
 post-mortem camp.<br>

&gt;</p>
<p>I believe there is data to show this time is different (iana and apnic a=
re exhausted, successful v6day, docsis 3.0 and LTE deployment ...)</p>
<p>&gt; Get a life.<br>
&gt;</p>
<p>Thanks</p>
<p>Cb<br>
&gt; Michel.<br>
&gt;<br>
</p>

--0016e6dee70f4f106504a597fc23--

From daedulus@btconnect.com  Mon Jun 13 06:54:51 2011
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 C328E21F8475 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 06:54:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmn59qy7HCVB for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 06:54:51 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by ietfa.amsl.com (Postfix) with ESMTP id CC2C521F846F for <ietf@ietf.org>; Mon, 13 Jun 2011 06:54:50 -0700 (PDT)
Received: from host81-156-207-154.range81-156.btcentralplus.com (HELO pc6) ([81.156.207.154]) by c2beaomr10.btconnect.com with SMTP id DDX47979; Mon, 13 Jun 2011 14:54:38 +0100 (BST)
Message-ID: <010001cc29c8$c24c9aa0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Nathaniel Borenstein" <nsb@guppylake.com>
References: <20110611205447.6579.qmail@joyce.lan><DA6710C1-A912-4328-99A0-4592EA59F72A@network-heretics.com> <28D6E065-CB4D-48D7-B1C5-FC85C22BBF6F@guppylake.com>
Subject: Re: one data point regarding native IPv6 support
Date: Mon, 13 Jun 2011 14:52:20 +0200
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-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0303.4DF61697.00EF, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.6.13.124817:17:7.586, ip=81.156.207.154, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_WWW, __URI_NO_PATH, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020D.4DF6169F.01D9,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: John Levine <johnl@iecc.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, 13 Jun 2011 13:54:51 -0000

----- Original Message -----
From: "Nathaniel Borenstein" <nsb@guppylake.com>
To: "Keith Moore" <moore@network-heretics.com>
Cc: "John Levine" <johnl@iecc.com>; <ietf@ietf.org>
Sent: Sunday, June 12, 2011 8:49 PM

> Just for the record:
>
> -- I don't believe that my single experience with first line tech support at
BT says much about BT's broader role, or its relative sophistication and service
quality as an ISP.  For all I know it's the best ISP in the world, and has a
lone bozo at tech support to qualify for a "jobs for bozos" tax credit.  I was
simply relating an experience that I found rather extreme.

In a similar but different vein, I asked BT marketing whether or not they
supported FTP (as in File Transfer Program).  I got escalated to Third line
support before I came across anyone who understood the question.

For me, the underlying point is that for the vast mass of Internet users and
Internet traffic, what we talk about in the IETF is mostly an irrelevance; the
ISPs (and content providers) are responding to the reality of the market.
Coming back to the original issue (should this I-D go forward?) I note that an
individual (and we are all of course participating as individuals), who
co-incidentally has google in his credentials, states that the failings of 6to4
are causing him big support problems.  For me, that is a powerful reason why
this I-D should advance, ideally before 8th June (sigh), regardless of whether
or not anyone can spell 1Pv6.

Tom Petch

>
> -- I do believe that a world in which any tech support person at any major ISP
doesn't know how to spell IP -- whether he's telling you to turn off IPv6 or
not -- is a world in which it is very challenging to expect positive outcomes in
the major technical transition we are trying to effect.
>
> -- I don't believe that I know what to do about it.  I'm almost sorry I
mentioned it -- we still have a long way to go before we need to start worrying
about Grandma configuring IPv6 at home.  -- Nathaniel
>
>
> On Jun 11, 2011, at 9:28 PM, Keith Moore wrote:
>
> >
> > On Jun 11, 2011, at 4:54 PM, John Levine wrote:
> >
> >>> If we want IPv6 to be available to the average user, I think it's
> >>> fair to assume that the average user won't get past the cluelessness.
> >>
> >> The average user is never going to call up and ask "can I get IPv6 as
> >> part of my bundle along with the Home Shopping Network" so the first
> >> level cluelessness doesn't matter.
> >>
> >> It's going to be available to the average user when the average cable
> >> or DSL modem autoconfigures itself to offer IPv6, and SLAAC and DHCPv6
> >> work well enough on average consumer PCs and other wifi devices that
> >> they set themselves up without any manual intervention.  You know,
> >> like they do with IPv4.
> >>
> >> I realize all these pieces work in theory, and often in practice if
> >> you know what button to tweak.  But Grandma is unlikely to tweak any
> >> network buttons at all.
> >
> > agree.  So when we're trying to evaluate whether IPv6 is widely available,
it's not sufficient for it to be widely available to clueful users who can
badger their way past first tier support.  It has to be available to Grandma.
> >
> > Keith
> >


From jnc@mercury.lcs.mit.edu  Mon Jun 13 08:28:28 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D60421F8497 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 08:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id omCzaxPK01Ym for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 08:28:27 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id C14AB21F8493 for <ietf@ietf.org>; Mon, 13 Jun 2011 08:28:27 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id C90D518C0EC; Mon, 13 Jun 2011 11:28:26 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: one data point regarding native IPv6 support
Message-Id: <20110613152826.C90D518C0EC@mercury.lcs.mit.edu>
Date: Mon, 13 Jun 2011 11:28:26 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2011 15:28:28 -0000

    > From: Keith Moore <moore@network-heretics.com>

    > To be fair, I think the argument is more that "ISP managed" IPv6 is
    > preferred over "IPv6 tunneled by end-users through relay routers ..."

It is exactly this sort of 'mandate it and they will come' thinking that IPv6
has relied on since it was rammed through in 1995, over _15 years_ ago - and
we can all see how well it has worked.

If _running out of IPv4 space_ isn't getting ISPs, etc, to deploy native
IPv6, what will? Making 6to4 historic sure isn't going to add much pressure.

If 6to4 has problems, fine, write a document that says something like '6to4
won't work for a host behind a NAT box because the host won't know it's true
IPv4 global-scope address - so you should also not turn 6to4 on by default'
and fix/publicize the issues.

But thinking that changing the standardization level is going to push ISPs
toward providing native IPv6 - give me a break.

	Noel

From jnc@mercury.lcs.mit.edu  Mon Jun 13 08:41:39 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08EC121F853E for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 08:41:39 -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_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2aE+A+9qIb0 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 08:41:38 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 6D99B21F853A for <ietf@ietf.org>; Mon, 13 Jun 2011 08:41:38 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id C05AA18C0F2; Mon, 13 Jun 2011 11:41:36 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: RE: RE: one data point regarding native IPv6 support
Message-Id: <20110613154136.C05AA18C0F2@mercury.lcs.mit.edu>
Date: Mon, 13 Jun 2011 11:41:36 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2011 15:41:39 -0000

    > From: Cameron Byrne <cb.list6@gmail.com>

    > The data (ripe ...) overwhelming proves default-on 6to4 clients +
    > thinly deployed relays = unreliable ipv6 and ipv6 deployment obstacle.

And how is making the protocol historic going to affect broken stuff that's
already been deployed (which is what is causing those observed problems) - or,
to put it more precisely, how is changing the protocol's label going to have
_more_ effect (i.e. above and beyond) than putting out a document which says
'here are some problems with using this, don't use this unless you know what
you're doing'?

    > I believe there is data to show this time is different (iana and apnic
    > are exhausted, successful v6day, docsis 3.0 and LTE deployment ...

I am personally dubious, since although technically we're now formally out of
space, I suspect we're just going to transition from a period in which it was
somewhat difficult to get IPv4 space [convincing an RIR you needed it] to
more difficult [acquiring space from a current holder] - that is, for those
organizations which don't already have space stockpiled. And that, along with
somewhat greater use of NAT - which has, of course, been keeping the Internet
functional for well over a decade) - will be the approach the market prefers.

We'll see, though, won't we?

	Noel

From joelja@bogus.com  Mon Jun 13 08:51:12 2011
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 0E25A11E80EC for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 08:51:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.419
X-Spam-Level: 
X-Spam-Status: No, score=-102.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QxlzZMMCikqb for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 08:51:11 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id EDD9211E80EB for <ietf@ietf.org>; Mon, 13 Jun 2011 08:51:03 -0700 (PDT)
Received: from 20317fgasperino.corp.zynga.com ([12.184.108.202]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5DFoxl2093154 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 13 Jun 2011 15:51:01 GMT (envelope-from joelja@bogus.com)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <20110613152826.C90D518C0EC@mercury.lcs.mit.edu>
Date: Mon, 13 Jun 2011 08:50:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <94B97987-3B62-4DB7-82D6-317743A4B826@bogus.com>
References: <20110613152826.C90D518C0EC@mercury.lcs.mit.edu>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 13 Jun 2011 15:51:02 +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, 13 Jun 2011 15:51:12 -0000

On Jun 13, 2011, at 8:28 AM, Noel Chiappa wrote:

>> From: Keith Moore <moore@network-heretics.com>
>=20
>> To be fair, I think the argument is more that "ISP managed" IPv6 is
>> preferred over "IPv6 tunneled by end-users through relay routers ..."
>=20
> It is exactly this sort of 'mandate it and they will come' thinking =
that IPv6
> has relied on since it was rammed through in 1995, over _15 years_ ago =
- and
> we can all see how well it has worked.
>=20
> If _running out of IPv4 space_ isn't getting ISPs, etc, to deploy =
native
> IPv6, what will? Making 6to4 historic sure isn't going to add much =
pressure.

I going to go out on a limb here and speculate that the reason we want =
to depreciate 6to4 because it causes damage to end users and the =
resources they want to connect to.

from my vantage point I have no problem serving ipv4 customers.

> If 6to4 has problems, fine, write a document that says something like =
'6to4
> won't work for a host behind a NAT box because the host won't know =
it's true
> IPv4 global-scope address - so you should also not turn 6to4 on by =
default'
> and fix/publicize the issues.
>=20
> But thinking that changing the standardization level is going to push =
ISPs
> toward providing native IPv6 - give me a break.
> 	Noel
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From joelja@bogus.com  Mon Jun 13 09:15:45 2011
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 1212511E8093 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 09:15:45 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mo+WbuchrRUl for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 09:15:44 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id E1A4A11E80A9 for <ietf@ietf.org>; Mon, 13 Jun 2011 09:15:43 -0700 (PDT)
Received: from 20317fgasperino.corp.zynga.com ([12.184.108.202]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5DGFWwb093678 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 13 Jun 2011 16:15:40 GMT (envelope-from joelja@bogus.com)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>
Date: Mon, 13 Jun 2011 09:15:27 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA20ACD0-DC55-45C6-895A-BB939ABAE856@bogus.com>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 13 Jun 2011 16:15:41 +0000 (UTC)
Cc: Keith Moore <moore@network-heretics.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, 13 Jun 2011 16:15:45 -0000

On Jun 12, 2011, at 12:24 PM, Michel Py wrote:

> According to this:
> =
http://blogs.cisco.com/sp/france-is-famous-for-fine-wine-cheese-and-now-
> ipv6/
> and some more recent direct talks in French, about half of worldwide
> IPv6 traffic is French.
>=20
> The bulk of it comes from a single ISP (Free, AS12322) and their IPv6 =
is
> 6RD (RFC5569, RFC5969), a variant of 6to4. Given the constant =
references
> in 6RD to 6to4, I will point out that making 6to4 historic somehow
> reduces the likeliness of another extremely successful ISP
> implementation based on it.

That's doesn't follow. 6rd borrows a mechanism used in 6to4, 6rd has no =
dependance on host 6to4 implementations or the 6to4 any-cast address.

> Although Google (in
> http://www.pam2010.ethz.ch/papers/full-length/15.pdf) and other
> measurements classify AS12322's traffic as native, it is 6RD behind =
the
> scenes.
>=20
> If the argument is that IPv6 "native" should be the preferred solution
> over "tunneled", it does not hold water. If you were to remove 6to4 =
and
> 6RD from the picture, that would set us back 10 years ago in terms of
> IPv6 adoption.
>=20
> Michel.
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From cos@mip.polyamory.org  Mon Jun 13 09:24:49 2011
Return-Path: <cos@mip.polyamory.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52F6421F84E0 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 09:24: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jiMsG8HptlZg for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 09:24:48 -0700 (PDT)
Received: from mip.polyamory.org (mip.polyamory.org [199.201.145.10]) by ietfa.amsl.com (Postfix) with ESMTP id 54B6421F84C7 for <ietf@ietf.org>; Mon, 13 Jun 2011 09:24:48 -0700 (PDT)
Received: by mip.polyamory.org (Postfix, from userid 1002) id D270A10760; Mon, 13 Jun 2011 12:24:40 -0400 (EDT)
Date: Mon, 13 Jun 2011 12:24:40 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: one data point regarding native IPv6 support
Message-ID: <20110613162440.GQ13584@mip.aaaaa.org>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <4DF1AD04.2090402@isdg.net> <4DF5C53D.1070402@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4DF5C53D.1070402@piuha.net>
User-Agent: Mutt/1.4.2.3i
X-URL: http://cos.polyamory.org/
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 16:24:49 -0000

I've never been able to get first level tech support at my ISP to
understand "latency" or "packet loss".  They only understand "can you
load a web page?"  This does not mean their ISP doesn't provide packet
loss and latency, standard with their service :)

More to the point, when I've been at hotels or conference centers or
similar places and found that I could connect to their wireless
network but not get an IP, it's been rare for their tech support to
recognize the term "DHCP", know what an auto-configured IP looks like,
or even understand the distinction between getting on the local
wireless and having routability to the Internet.  Yet their systems
clearly provide and depend on these things, and always have.  Their
lack of clue says nothing about the level of support for things like
basic IP routing, or DHCP, in hotel and conference center networks.

I wouldn't take what first level support has heard of to be a
systematic indication of anything other than that company's hiring
and training practices for first level support.
  -- Cos

From smb@cs.columbia.edu  Mon Jun 13 09:51:33 2011
Return-Path: <smb@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35D9311E8165 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 09:51: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t6TqEeyk93NA for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 09:51:32 -0700 (PDT)
Received: from paneer.cc.columbia.edu (paneer.cc.columbia.edu [128.59.29.4]) by ietfa.amsl.com (Postfix) with ESMTP id 4F9B011E8163 for <ietf@ietf.org>; Mon, 13 Jun 2011 09:51:32 -0700 (PDT)
Received: from v230.vpn.iad.rg.net (v230.vpn.iad.rg.net [198.180.150.230]) (user=smb2132 mech=PLAIN bits=0) by paneer.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id p5DGoSZL011572 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 13 Jun 2011 12:50:29 -0400 (EDT)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <20110613162440.GQ13584@mip.aaaaa.org>
Date: Mon, 13 Jun 2011 12:50:27 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <DEDDDBF9-1592-4940-97F0-FFB2D0569E3E@cs.columbia.edu>
References: <58682A33-6566-4758-8F61-F01A33050F30@network-heretics.com> <4DF1AD04.2090402@isdg.net> <4DF5C53D.1070402@piuha.net> <20110613162440.GQ13584@mip.aaaaa.org>
To: Ofer Inbar <cos@aaaaa.org>
X-Mailer: Apple Mail (2.1084)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.4
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2011 16:51:33 -0000

On Jun 13, 2011, at 12:24 40PM, Ofer Inbar wrote:

> I've never been able to get first level tech support at my ISP to
> understand "latency" or "packet loss".  They only understand "can you
> load a web page?"  This does not mean their ISP doesn't provide packet
> loss and latency, standard with their service :)

Oh yeah...  Many years ago, I was experiencing 5-15% packet loss and 5-90%
packet duplication.  Tier 1 told me to clear my browser cache, and besides
5% packet loss was normal.  I demurred; he told me he handled 20-25
performance calls/day and his advice fixed them.  I asked to speak to a
supervisor.  He and his supervisor apparently took offense; since my
connectivity was via a deal with my employer, they passed it up their
management chain to complain to my management that I didn't believe their
technicians.  Some VP on their side AltaVistaed me, though, at which
point my complaint got routed straight to engineering and the story got
passed on to my management...

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






From daedulus@btconnect.com  Mon Jun 13 10:09:03 2011
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 C93B711E8173 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 10:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TRjjHLVXVuFp for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 10:09:03 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by ietfa.amsl.com (Postfix) with ESMTP id AF4AB11E8162 for <ietf@ietf.org>; Mon, 13 Jun 2011 10:09:02 -0700 (PDT)
Received: from host81-156-207-154.range81-156.btcentralplus.com (HELO pc6) ([81.156.207.154]) by c2beaomr10.btconnect.com with SMTP id DDZ48901; Mon, 13 Jun 2011 18:08:53 +0100 (BST)
Message-ID: <042b01cc29e3$e50189a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Joel Jaeggli" <joelja@bogus.com>, "Michel Py" <michel@arneill-py.sacramento.ca.us>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local> <DA20ACD0-DC55-45C6-895A-BB939ABAE856@bogus.com>
Subject: Re: one data point regarding native IPv6 support
Date: Mon, 13 Jun 2011 18:06:35 +0200
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-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0302.4DF64424.009A, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.6.13.151218:17:7.586, ip=81.156.207.154, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __CP_URI_IN_BODY, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0206.4DF64426.0090,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jun 2011 17:09:03 -0000

----- Original Message -----
From: "Joel Jaeggli" <joelja@bogus.com>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
Cc: "Keith Moore" <moore@network-heretics.com>; "IETF-Discussion"
<ietf@ietf.org>
Sent: Monday, June 13, 2011 6:15 PM
>
> On Jun 12, 2011, at 12:24 PM, Michel Py wrote:
>
> > According to this:
> > http://blogs.cisco.com/sp/france-is-famous-for-fine-wine-cheese-and-now-
> > ipv6/
> > and some more recent direct talks in French, about half of worldwide
> > IPv6 traffic is French.
> >
> > The bulk of it comes from a single ISP (Free, AS12322) and their IPv6 is
> > 6RD (RFC5569, RFC5969), a variant of 6to4. Given the constant references
> > in 6RD to 6to4, I will point out that making 6to4 historic somehow
> > reduces the likeliness of another extremely successful ISP
> > implementation based on it.

To quote from the draft (anyone read it?:-)

"   6rd [RFC5969] utilizes the same encapsulation and base mechanism as
   6to4, and could be viewed as a superset of 6to4 (6to4 could be
   achieved by setting the 6rd prefix to 2002::/16).  However, the
   deployment model is such that 6rd can avoid the problems described
   here.  In this sense, 6rd can be viewed as superseding 6to4 as
   described in section 4.2.4 of [RFC2026]"

6rd good; 6to4 {as described in section 4.2.4 of [RFC2026]} bad.

Tom Petch

> That's doesn't follow. 6rd borrows a mechanism used in 6to4, 6rd has no
dependance on host 6to4 implementations or the 6to4 any-cast address.
>
> > Although Google (in
> > http://www.pam2010.ethz.ch/papers/full-length/15.pdf) and other
> > measurements classify AS12322's traffic as native, it is 6RD behind the
> > scenes.
> >
> > If the argument is that IPv6 "native" should be the preferred solution
> > over "tunneled", it does not hold water. If you were to remove 6to4 and
> > 6RD from the picture, that would set us back 10 years ago in terms of
> > IPv6 adoption.
> >
> > Michel.
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> >
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From suresh.krishnan@ericsson.com  Mon Jun 13 10:58:53 2011
Return-Path: <suresh.krishnan@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 EA424228004 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 10:58:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.485
X-Spam-Level: 
X-Spam-Status: No, score=-106.485 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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jxzaM-wCCTCk for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 10:58:53 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by ietfa.amsl.com (Postfix) with ESMTP id 3AA2E21F8581 for <ietf@ietf.org>; Mon, 13 Jun 2011 10:58:53 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p5DHwqiP021222 for <ietf@ietf.org>; Mon, 13 Jun 2011 12:58:53 -0500
Received: from [142.133.10.107] (147.117.20.214) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.3.137.0; Mon, 13 Jun 2011 13:58:45 -0400
Message-ID: <4DF64F07.60101@ericsson.com>
Date: Mon, 13 Jun 2011 13:55:19 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Nomcom 2011-12: Call for Volunteers
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 Jun 2011 17:58:54 -0000

Hi All,
   The Nomcom process for 2011-2012 has started. Please go through the 
message below and consider volunteering for the Nomcom.

Thanks
Suresh


-------- Original Message --------
Subject: Nomcom 2011-12: Call for Volunteers
Date: Fri, 10 Jun 2011 22:56:06 -0400
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>

The IETF nominating committee process for 2011-12 has begun. The IETF
nominating committee appoints folks to fill the open slots on the
IAOC, the IAB, and the IESG. The 10 nominating committee members are
selected randomly from a pool of volunteers. The more volunteers, the
better the chance we have of choosing a random yet representative
cross section of the IETF population.  The details of the nomcom
process can be found in RFC 3777.

To be eligible, volunteers for the nomcom need to have attended 3 of
the past 5 IETF meetings as of the time this announcement goes out
(i.e. IETF76-IETF80). If you qualify, and are not seeking appointment
to any of the open positions this nomcom will be filling, please
consider volunteering.

The list of people and posts whose terms end with the March 2012 IETF
meeting, and thus the positions for which the nominating committee is
responsible, are as follows:

IAB
===

Bernard Aboba
Hannes Tschofenig
Andrei Robachevsky
Olaf Kolkman
Spencer Dawkins
Ross Callon

IAOC
====

Marshall Eubanks

IESG
====

Peter Saint-Andre (Applications)
Jari Arkko (Internet)
Dan Romascanu (Operations & Management)
Gonzalo Camarillo (RAI)
Stewart Bryant (Routing)
Sean Turner (Security)
David Harrington (Transport)


The primary activity for this nomcom will begin during IETF-81 in
Quebec City and should be completed by January 2012. The nomcom will
be collecting requirements from the community, as well as talking to
candidates and to community members about candidates. There will be
regularly scheduled conference calls to ensure progress. Thus, being a
nomcom member does require some time commitment.

Please volunteer by sending an email to me before
11:59 pm EDT July 10, 2011 as follows:

To: suresh.krishnan@ericsson.com
Subject: Nomcom 2011-12 Volunteer

Please include the following information in the body of the mail:

Full Name:  // As you enter in the IETF Registration Form,
             // First/Given name followed by Last/Family Name

Current Primary Affiliation: // typically what goes in the Company
                              // field in the IETF Registration Form

Email Address(es): // all email addresses used to Register for the
                    // past 5 IETF meetings
		   // Please designate a Preferred email address for
                    // contact if there is more than one email address

Telephone number:  // With country code (for confirmation if selected)

Please expect an email response from me within 3 business days stating
whether or not you are qualified.  If you do not receive a response in
this timeframe, please re-send your email with the tag "RESEND:" added
to the subject line.

If you are not yet sure you would like to volunteer, please consider
that nomcom members play a very important role in shaping the
leadership of the IETF.  Ensuring the leadership of the IETF is fair
and balanced and comprised of those who can lead the IETF in the right
direction is an important responsibility that rests on the IETF
participants at large. Volunteering for the nomcom is a good way of
contributing in that direction.

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 few days.

Thank you in advance for your participation.

Suresh Krishnan
Nomcom Chair 2011-2012
Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From moore@network-heretics.com  Mon Jun 13 21:09:11 2011
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 96B4511E8131 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 21:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.074
X-Spam-Level: 
X-Spam-Status: No, score=-3.074 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hb1EEUbFGbFh for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 21:09:10 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id A01AD11E812F for <ietf@ietf.org>; Mon, 13 Jun 2011 21:09:10 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id D718620BED; Tue, 14 Jun 2011 00:09:09 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 14 Jun 2011 00:09:09 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=bH7hzQhgbiyKhgenVJwVD1cUnPI=; b=ij5FjE2erHW7rTU/7yfwtyyaIGeQWFIuRTshy74d/Frh0SfARHIKwQhQbAB/C/0BpewqXSap4nUzgGinieoQdpnIWL/fmnwnIF07wr5n71ktFBhNX7gQDG+OcR60YUO/wtR8j8rLcrD6HjYQrGyRbKL2uUpyzImhAi7RnH3EJbk=
X-Sasl-enc: 7bs2ZmTOSwPV6EmTUbmdhUR5eoqGHmgZFcrLzZJfq/VQ 1308024549
Received: from host65-16-145-177.birch.net (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id B6E39442DB8; Tue, 14 Jun 2011 00:09:08 -0400 (EDT)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-53--995168856
From: Keith Moore <moore@network-heretics.com>
X-Priority: 3
In-Reply-To: <042b01cc29e3$e50189a0$4001a8c0@gateway.2wire.net>
Date: Tue, 14 Jun 2011 00:08:32 -0400
Message-Id: <35C23E17-9FCF-44EA-9879-29E8E2B2486A@network-heretics.com>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local> <DA20ACD0-DC55-45C6-895A-BB939ABAE856@bogus.com> <042b01cc29e3$e50189a0$4001a8c0@gateway.2wire.net>
To: t.petch <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.1084)
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, 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, 14 Jun 2011 04:09:11 -0000

--Apple-Mail-53--995168856
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jun 13, 2011, at 12:06 PM, t.petch wrote:
>=20
> To quote from the draft (anyone read it?:-)
>=20
> "   6rd [RFC5969] utilizes the same encapsulation and base mechanism =
as
>   6to4, and could be viewed as a superset of 6to4 (6to4 could be
>   achieved by setting the 6rd prefix to 2002::/16).  However, the
>   deployment model is such that 6rd can avoid the problems described
>   here.  In this sense, 6rd can be viewed as superseding 6to4 as
>   described in section 4.2.4 of [RFC2026]"

yes, but that part of the draft is false.  6to4 and 6rd have different =
use cases.  It's not as if I can install 6rd on my laptop and be able to =
talk to IPv6 hosts.

> 6rd good; 6to4 {as described in section 4.2.4 of [RFC2026]} bad.

6to4 awesome.  it's those BGP advertisements for broken relay routers, =
and those ISPs that filter protocol 41 that are bad.

Keith


--Apple-Mail-53--995168856
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jun 13, 2011, at 12:06 PM, t.petch =
wrote:</div><blockquote type=3D"cite"><div><font =
class=3D"Apple-style-span" color=3D"#000000"><br></font>To quote from =
the draft (anyone read it?:-)<br><br>" &nbsp;&nbsp;6rd [RFC5969] =
utilizes the same encapsulation and base mechanism as<br> =
&nbsp;&nbsp;6to4, and could be viewed as a superset of 6to4 (6to4 could =
be<br> &nbsp;&nbsp;achieved by setting the 6rd prefix to 2002::/16). =
&nbsp;However, the<br> &nbsp;&nbsp;deployment model is such that 6rd can =
avoid the problems described<br> &nbsp;&nbsp;here. &nbsp;In this sense, =
6rd can be viewed as superseding 6to4 as<br> &nbsp;&nbsp;described in =
section 4.2.4 of [RFC2026]"<br></div></blockquote><br>yes, but that part =
of the draft is false. &nbsp;6to4 and 6rd have different use cases. =
&nbsp;It's not as if I can install 6rd on my laptop and be able to talk =
to IPv6 hosts.</div><div><br><blockquote type=3D"cite"><div>6rd good; =
6to4 {as described in section 4.2.4 of [RFC2026]} =
bad.<br></div></blockquote></div><br><div>6to4 awesome. &nbsp;it's those =
BGP advertisements for broken relay routers, and those ISPs that filter =
protocol 41 that are =
bad.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-53--995168856--

From michel@arneill-py.sacramento.ca.us  Mon Jun 13 21:57:42 2011
Return-Path: <michel@arneill-py.sacramento.ca.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 14CB61F0C87 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 21:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i0iM3pXEXBOG for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 21:57:41 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [69.12.226.219]) by ietfa.amsl.com (Postfix) with ESMTP id 198F61F0C82 for <ietf@ietf.org>; Mon, 13 Jun 2011 21:57:40 -0700 (PDT)
Subject: RE: one data point regarding native IPv6 support
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Mon, 13 Jun 2011 21:57:39 -0700
Content-Transfer-Encoding: quoted-printable
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF599@newserver.arneill-py.local>
Content-class: urn:content-classes:message
In-Reply-To: <35C23E17-9FCF-44EA-9879-29E8E2B2486A@network-heretics.com>
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: one data point regarding native IPv6 support
Thread-Index: AcwqSNEYK19Lj8EwQ7iY8kzGw6rlewABNhcg
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local> <DA20ACD0-DC55-45C6-895A-BB939ABAE856@bogus.com> <042b01cc29e3$e50189a0$4001a8c0@gateway.2wire.net> <35C23E17-9FCF-44EA-9879-29E8E2B2486A@network-heretics.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Keith Moore" <moore@network-heretics.com>, "t.petch" <daedulus@btconnect.com>
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, 14 Jun 2011 04:57:42 -0000

> Keith Moore wrote:
> 6to4 awesome. =A0it's those BGP advertisements for broken relay
> routers, and those ISPs that filter protocol 41 that are bad.

I won't go as far as supporting you on this one. Anything that makes the =
network work, good. Anything that breaks the network, bad.

<troll>
Please consider a new version of 6to4 over HTTPS, with a supplemental =
DPI layer to filter unwanted BGP announcements :P
</troll>

More seriously: if 6to4 is declared historic, someone will hire a =
brilliant attorney and file for 1Pv6 as a whole to go historic as well, =
on the same grounds: "disable 1Pv6" has become SOP for the script =
monkeys, and therefore 1Pv6 is detrimental for the Internet as a whole.

Everyone, careful what you are wishing for; the clock to IPv4 exhaustion =
as come and gone; it should be clear by now that if shortage of IPv4 was =
a valid concern, everyone would be scrambling to deploy 1Pv6 while the =
last crumbs of the last /8 given to the RIRs remains.

It is not the case. Warning: fecal matter impact on air turbine =
predicted.

Michel.


From moore@network-heretics.com  Mon Jun 13 22:37:04 2011
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 9127B11E82B9 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 22:37:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.372
X-Spam-Level: 
X-Spam-Status: No, score=-3.372 tagged_above=-999 required=5 tests=[AWL=0.227,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3okHSc-ae3Gk for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2011 22:37:04 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id E43F011E816E for <ietf@ietf.org>; Mon, 13 Jun 2011 22:37:03 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 7814920A4A; Tue, 14 Jun 2011 01:37:03 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 14 Jun 2011 01:37:03 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=Vd1JhUResLjpi4Jg9Z3Vez3Wv0Q=; b=lRJ95tPf0CbCxF1cvxKCmgOuUYwKv3Cuhb0Gowbe8NLDf2b9Ks759ox9Xjw5mRq+m9ISJYt21TTivBAISBqSiSUh1yCg38hushXtK7Lsj9JL1HeMuM8gYvglP6ypuhU+G6OpiS9Tw9YzHp/DEk14VXiF78HDJSifNS0VpU8G5Vo=
X-Sasl-enc: 8wCvTgb2V2cPt49wHhkKIaKfYhTyzh76gFFgmw4ZJ0A/ 1308029822
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 86A32445F83; Tue, 14 Jun 2011 01:37:02 -0400 (EDT)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF599@newserver.arneill-py.local>
Date: Tue, 14 Jun 2011 01:37:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E50ADE86-89A2-4E7C-81A1-4C8144669E96@network-heretics.com>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local> <DA20ACD0-DC55-45C6-895A-BB939ABAE856@bogus.com> <042b01cc29e3$e50189a0$4001a8c0@gateway.2wire.net> <35C23E17-9FCF-44EA-9879-29E8E2B2486A@network-heretics.com> <392CB277BC2EAE4FB83C1206954BA6CEF599@newserver.arneill-py.local>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.1084)
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, 14 Jun 2011 05:37:04 -0000

On Jun 14, 2011, at 12:57 AM, Michel Py wrote:

>> Keith Moore wrote:
>> 6to4 awesome.  it's those BGP advertisements for broken relay
>> routers, and those ISPs that filter protocol 41 that are bad.
>=20
> I won't go as far as supporting you on this one. Anything that makes =
the network work, good. Anything that breaks the network, bad.

There are several problems with that logic:

One problem is that the network doesn't entirely break or not break in =
the presence of feature X; it works for some people and breaks for some =
others.

Another is that it doesn't address tussles.  If feature X and feature Y =
are mutually incompatible, in that use of feature X breaks feature Y and =
vice versa, who is to say which feature is good and which is "breaking" =
the network?=20

Another is that when (some) network operators configure their network in =
such a way as to break feature X, others use that breakage as an excuse =
to justify breaking even more things.

Keith


From tjc@ecs.soton.ac.uk  Tue Jun 14 03:56:28 2011
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 6E91D21F848B for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 03:56:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.301,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fQZ7sxKuYKfB for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 03:56:27 -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 79EC021F848A for <ietf@ietf.org>; Tue, 14 Jun 2011 03:56:26 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p5EAuMpt015307 for <ietf@ietf.org>; Tue, 14 Jun 2011 11:56:22 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p5EAuMpt015307
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1308048982; bh=XApDwXx55O//p5vnuYSYN5GhLC0=; h=References:In-Reply-To:Mime-Version:From:Subject:Date:To; b=nLbPpuHqy0RQe/hK/7F6E6AJ0TrJdWpt1tI7qvkmReVJhQBbARTm4mmcbjniQoQRN NTJEr3O6rZXrYUPgIjDvvnLhgBjxIC7Pv9tPLHtlRvpU1Z7rM25BK4JHgDH7Wa6Ywz +7p/d/+El9BCLjVCBKxD/zpYKvVfatZQfEKEKrfU=
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 id n5DBuM0521303926Ln ret-id none; Tue, 14 Jun 2011 11:56:22 +0100
Received: from [IPv6:2001:630:d0:f103::c0:ffee] ([IPv6:2001:630:d0:f103::c0:ffee]) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p5EAuHmm011899 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 14 Jun 2011 11:56:17 +0100
References: <20110613152826.C90D518C0EC@mercury.lcs.mit.edu> <16C2AEA4-F6FA-45EC-9035-83194EF2FC27@ecs.soton.ac.uk>
In-Reply-To: <20110613152826.C90D518C0EC@mercury.lcs.mit.edu>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
Message-ID: <EMEW3|56930e8a7480561c9ce05daa70ba280fn5DBuM03tjc|ecs.soton.ac.uk|16C2AEA4-F6FA-45EC-9035-83194EF2FC27@ecs.soton.ac.uk>
Content-Transfer-Encoding: quoted-printable
From: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: one data point regarding native IPv6 support
Date: Tue, 14 Jun 2011 11:56:17 +0100
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n5DBuM052130392600; tid=n5DBuM0521303926Ln; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p5EAuMpt015307
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 10:56:28 -0000

On 13 Jun 2011, at 16:28, Noel Chiappa wrote:
>=20
> If 6to4 has problems, fine, write a document that says something like =
'6to4
> won't work for a host behind a NAT box because the host won't know =
it's true
> IPv4 global-scope address - so you should also not turn 6to4 on by =
default'
> and fix/publicize the issues.

There has been a good deal of work making tunnel brokers work through =
IPv4 NATs and with changing IPv4 endpoints.  Both SiXXS and HE brokers =
handle such issues, e.g. using a heartbeat method. So these ought to be =
(relatively) attractive to end users who want IPv6?

Presumably the prefixes used by such providers, and others like gogo6, =
are known so brokenness stats for such services could be deduced?

Tim=

From tom111.taylor@bell.net  Sun Jun 12 07:48:47 2011
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EF0111E80B2; Sun, 12 Jun 2011 07:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.579
X-Spam-Level: 
X-Spam-Status: No, score=-101.579 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dYPBxg2wgb3K; Sun, 12 Jun 2011 07:48:46 -0700 (PDT)
Received: from blu0-omc2-s1.blu0.hotmail.com (blu0-omc2-s1.blu0.hotmail.com [65.55.111.76]) by ietfa.amsl.com (Postfix) with ESMTP id A1C9C11E80AB; Sun, 12 Jun 2011 07:48:46 -0700 (PDT)
Received: from BLU0-SMTP80 ([65.55.111.72]) by blu0-omc2-s1.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 12 Jun 2011 07:48:46 -0700
X-Originating-IP: [76.70.76.63]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP801B5A24EB84B6151C06C2D8660@phx.gbl>
Received: from [192.168.2.17] ([76.70.76.63]) by BLU0-SMTP80.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 12 Jun 2011 07:48:46 -0700
Date: Sun, 12 Jun 2011 10:48:45 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [PCN] Last Call: <draft-ietf-pcn-cl-edge-behaviour-08.txt> (PCN Boundary	Node Behaviour for the Controlled Load (CL) Mode of	Operation)	to Informational RFC
References: <20110527203800.13071.15398.idtracker@ietfa.amsl.com>
In-Reply-To: <20110527203800.13071.15398.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Jun 2011 14:48:46.0141 (UTC) FILETIME=[D4FB9ED0:01CC290F]
X-Mailman-Approved-At: Tue, 14 Jun 2011 08:10:50 -0700
Cc: pcn@ietf.org, The IESG <iesg-secretary@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jun 2011 14:48:47 -0000

Through confusion, I have perpetrated a major screw-up regarding this 
document and its companion, draft-ietf-pcn-sm-edge-behaviour. Somewhere 
around Christmas I received a number of comments on the two documents. I 
have fixed all of them except the comment requesting sections on 
operations and management considerations sections. I am wishing now that 
I had submitted interim updates reflecting that work, pending completion 
of the new sections.

For various reasons I haven't had the time or energy to finish the job. 
When our AD came out with a revised set of comments I was confused and 
failed to respond. At first when Last Call was issued I thought this 
would do no real harm, since many of the fixes were really just 
editorial. Unfortunately, now that I look over some of the reviews, I 
realize that some substantive fixes were also included.

As a result, I have wasted the time of a lot of people. I apologize to 
the community for this. What I propose is that I submit the documents 
with the fixes that were carried out, and the IESG restart the Last Call 
process. Failing that, I will go through and identify the substantive 
issues that need correction in any event.

I note the discomfort with using the EXP code point. This is indirectly 
a matter of extensive debate in the PCN WG. My own view is that the 
solution is as suggested, make the CL-edge-behaviour draft Experimental 
rather than Informational.

Tom Taylor, Editor

On 27/05/2011 4:38 PM, The IESG wrote:
>
> The IESG has received a request from the Congestion and Pre-Congestion
> Notification WG (pcn) to consider the following document:
> - 'PCN Boundary Node Behaviour for the Controlled Load (CL) Mode of
>     Operation'
>    <draft-ietf-pcn-cl-edge-behaviour-08.txt>  as an 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 2011-06-10. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
> Pre-congestion notification (PCN) is a means for protecting the
> quality of service for inelastic traffic admitted to a Diffserv
> domain.  The overall PCN architecture is described in RFC 5559.  This
> memo is one of a series describing possible boundary node behaviours
> for a PCN-domain.  The behaviour described here is that for a form of
> measurement-based load control using three PCN marking states, not-
> marked, threshold-marked, and excess-traffic-marked.  This behaviour
> is known informally as the Controlled Load (CL) PCN-boundary-node
> behaviour.
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-pcn-cl-edge-behaviour/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-pcn-cl-edge-behaviour/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>
>

From lorenzo@google.com  Fri Jun 10 09:38:56 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E88221F0C8D for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 09:38:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80O-FFsoGqK3 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 09:38:56 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 306E61F0C43 for <ietf@ietf.org>; Fri, 10 Jun 2011 09:38:56 -0700 (PDT)
Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id p5AGct0W010746 for <ietf@ietf.org>; Fri, 10 Jun 2011 09:38:55 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1307723935; bh=9Ij3LdwmjeEYygvBJvV1IL1JGuY=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=oIVpZTJYAtG0lbOm1eR+6zjn7jU0wJ20u7GxPaC8JpT71+njn5mPHmjLAR6I8ACsr eV2TQdzyjCdtr9idj3hcg==
Received: from gxk23 (gxk23.prod.google.com [10.202.11.23]) by wpaz13.hot.corp.google.com with ESMTP id p5AGZTlw022068 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Fri, 10 Jun 2011 09:38:54 -0700
Received: by gxk23 with SMTP id 23so2076857gxk.28 for <ietf@ietf.org>; Fri, 10 Jun 2011 09:38:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=MgIqOIu5n2dTSwSoiBeN7HyhMQSU2VT9amCF9fDDQW4=; b=J6UaXE/esR4IKCDt0ZbLdELXqMjVv5Dx3IW4kHlN0X+XnvnW4Xotx3EJLgFT4pZVnd T36N6wFi5dotbi3jK3ig==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=YtzLWG5WpAjDl7Fih6lFmcoJoJLCzJcXA6H9tCzSRYIriOxxbso+xkopAEpEYn22Zg QE6104+RKyBFNtsMmfgA==
Received: by 10.150.116.1 with SMTP id o1mr3246545ybc.321.1307723934101; Fri, 10 Jun 2011 09:38:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.95.20 with HTTP; Fri, 10 Jun 2011 09:38:34 -0700 (PDT)
In-Reply-To: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 10 Jun 2011 09:38:34 -0700
Message-ID: <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: multipart/alternative; boundary=000e0cd3b0408e72ca04a55e342e
X-System-Of-Record: true
X-Mailman-Approved-At: Tue, 14 Jun 2011 08:10:51 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 16:38:57 -0000

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

On Fri, Jun 10, 2011 at 9:18 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu>wrote:

>    > Mac OS 10.6.4, which uses 6to4 by default, has a ~50x greater failure
>    > rate when connecting to dual-stack servers than Mac OS 10.6.5 - and
> the
>    > only change is to not use 6to4 by default.
>     > ...
>     > So the existence of 6to4 is in itself a significant barrier for IPv6
>    > deployment
>
> Surely you meant to say "the _incorrect configuration_ of 6to4 is in itself
> a
> significant barrier"?
>

You cannot expect something to be configured correctly if it is simply
turned on without a) being managed by someone or b) detection mechanisms to
see if it's working. Sadly, anycasted 6to4 meets neither of these
conditions.


> I get the impression that the problem comes in when 6to4 is configured on
> by default, and too high in the priority list (as opposed to native, other
> methods, etc). So fix the real issue, don't try and prematurely kill off
> something that's being used by lots of people.


I fundamentally disagree. I really don't think that 6to4 is used by "lots"
of people for applications that wouldn't just use (more reliable) IPv4 if
6to4 wasn't there.

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

<div class=3D"gmail_quote">On Fri, Jun 10, 2011 at 9:18 AM, Noel Chiappa <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:jnc@mercury.lcs.mit.edu">jnc@mercury.=
lcs.mit.edu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">=A0 =A0&gt; Mac OS 10.6.4, which uses 6to4 by default, ha=
s a ~50x greater failure<br>
 =A0 =A0&gt; rate when connecting to dual-stack servers than Mac OS 10.6.5 =
- and the<br>
 =A0 =A0&gt; only change is to not use 6to4 by default.<br>
</div> =A0 =A0&gt; ...<br>
<div class=3D"im"> =A0 =A0&gt; So the existence of 6to4 is in itself a sign=
ificant barrier for IPv6<br>
 =A0 =A0&gt; deployment<br>
<br>
</div>Surely you meant to say &quot;the _incorrect configuration_ of 6to4 i=
s in itself a<br>
significant barrier&quot;?<br></blockquote><div><br></div><div>You cannot e=
xpect something to be configured correctly if it is simply turned on withou=
t a) being managed by someone or b) detection mechanisms to see if it&#39;s=
 working. Sadly, anycasted 6to4 meets neither of these conditions.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;">I get the impression that the=
 problem comes in when 6to4 is configured on by=A0default, and too high in =
the priority list (as opposed to native, other<br>


methods, etc). So fix the real issue, don&#39;t try and prematurely kill of=
f<br>
something that&#39;s being used by lots of people.</blockquote><div><br></d=
iv><div>I fundamentally disagree. I really don&#39;t think that 6to4 is use=
d by &quot;lots&quot; of people for applications that wouldn&#39;t just use=
 (more reliable) IPv4 if 6to4 wasn&#39;t there.</div>

</div>

--000e0cd3b0408e72ca04a55e342e--

From lorenzo@google.com  Fri Jun 10 10:23:03 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3803121F84A2 for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 10:23:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTRXVu0SoeHz for <ietf@ietfa.amsl.com>; Fri, 10 Jun 2011 10:23:02 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 14A2B21F84A1 for <ietf@ietf.org>; Fri, 10 Jun 2011 10:23:01 -0700 (PDT)
Received: from hpaq6.eem.corp.google.com (hpaq6.eem.corp.google.com [172.25.149.6]) by smtp-out.google.com with ESMTP id p5AHN1N3017733 for <ietf@ietf.org>; Fri, 10 Jun 2011 10:23:01 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1307726581; bh=cvFg8G7R+wtyVWdM2wX1DNWh9Cw=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=lvWDos44GKNHxW7P2E2nBHjvKglmAUZzB+AgSXzwgLTPbTUVlGn8szG2mulHBKacP 68PcCJ4cf+MHdpTAXgZTw==
Received: from yxl31 (yxl31.prod.google.com [10.190.3.223]) by hpaq6.eem.corp.google.com with ESMTP id p5AHMBX7020272 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Fri, 10 Jun 2011 10:23:00 -0700
Received: by yxl31 with SMTP id 31so992110yxl.24 for <ietf@ietf.org>; Fri, 10 Jun 2011 10:22:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=qqZpfp0p8B8xGmC3V9pYh1GgjqUO2G8Fa9nnbXNlZzs=; b=UWSPVqSsnGpKho5VBEQf1aCIUj6hQ+anmcb6+XbcxrjBeouD4YWLQAQtYNm+r5AeLC GhWv2RygdLckZ95cHJ3Q==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=qjgGwGukGJPrMgKkpgoms+4NwDwb0fkke0Cd8WuHqwVtHNoDdv+NmS256HKx5Q2HBE tiK8Bk1xp3kZ4okYpuMA==
Received: by 10.150.183.3 with SMTP id g3mr3315912ybf.264.1307726579096; Fri, 10 Jun 2011 10:22:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.95.20 with HTTP; Fri, 10 Jun 2011 10:22:39 -0700 (PDT)
In-Reply-To: <3B25F81A-89D1-4272-942C-A699C8593099@apple.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <B7124EA0-B888-4240-9098-9D77F75B11A5@employees.org> <ADC44EF9-8472-477F-9AA1-2E81DDEE13FC@network-heretics.com> <BANLkTi=acGQnt_NrZV+LgoCbv=AxUoVo4C2TMnp=CgDbsN3v5Q@mail.gmail.com> <3B25F81A-89D1-4272-942C-A699C8593099@apple.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 10 Jun 2011 10:22:39 -0700
Message-ID: <BANLkTi=GaR7S=YTRi2fsYjVoLLLYd8BqzL1WsC=9jTP1PuVh-A@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: james woodyatt <jhw@apple.com>
Content-Type: multipart/alternative; boundary=000e0cd6ecd835de9404a55ed291
X-System-Of-Record: true
X-Mailman-Approved-At: Tue, 14 Jun 2011 08:10:51 -0700
Cc: IPv6 Operations Working Group <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 17:23:03 -0000

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

On Fri, Jun 10, 2011 at 10:15 AM, james woodyatt <jhw@apple.com> wrote:

> I don't want anybody to be misled by this statement.  I think what Lorenzo
> meant to say is that Mac OS X 10.6.4 and earlier doesn't implement the
> policy table in I-D.ietf-6man-rfc3484-revise, which prefers IPv4 source
> addresses over 2002::/16 IPv6 source addresses.
>

Yes, of course. I was trying to keep it short.

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

<div class=3D"gmail_quote">On Fri, Jun 10, 2011 at 10:15 AM, james woodyatt=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:jhw@apple.com">jhw@apple.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

I don&#39;t want anybody to be misled by this statement. =A0I think what Lo=
renzo meant to say is that Mac OS X 10.6.4 and earlier doesn&#39;t implemen=
t the policy table in I-D.ietf-6man-rfc3484-revise, which prefers IPv4 sour=
ce addresses over 2002::/16 IPv6 source addresses.<br>

</blockquote><div><br></div><div>Yes, of course. I was trying to keep it sh=
ort.=A0</div></div>

--000e0cd6ecd835de9404a55ed291--

From jhw@apple.com  Tue Jun 14 10:30:27 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 584AB11E817C; Tue, 14 Jun 2011 10:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9pa0TfJFFcrL; Tue, 14 Jun 2011 10:30:26 -0700 (PDT)
Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3C9DB11E817F; Tue, 14 Jun 2011 10:30:14 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LMS002W8J904T00@mail-out.apple.com>; Tue, 14 Jun 2011 10:30:13 -0700 (PDT)
X-AuditID: 11807134-b7c00ae0000074fb-3a-4df79aa5a032
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay14.apple.com (Apple SCV relay) with SMTP id 55.C1.29947.5AA97FD4; Tue, 14 Jun 2011 10:30:13 -0700 (PDT)
Received: from [17.193.13.64] (unknown [17.193.13.64]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LMS00EWKJADCJ30@cardamom.apple.com>; Tue, 14 Jun 2011 10:30:13 -0700 (PDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to	Historic status) to Informational RFC
From: james woodyatt <jhw@apple.com>
In-reply-to: <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com>
Date: Tue, 14 Jun 2011 10:30:12 -0700
Message-id: <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1237.1)
X-Brightmail-Tracker: AAAAAA==
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 17:30:27 -0000

On Jun 10, 2011, at 09:38 , Lorenzo Colitti wrote:
> 
> I fundamentally disagree. I really don't think that 6to4 is used by "lots" of people for applications that wouldn't just use (more reliable) IPv4 if 6to4 wasn't there.

The same is often said about IPv6 in general.

That's not meant to be snarky quip.  When you limit the population under observation to just current IPv6 users and leave out the vast teeming masses of people who are routed IPv4-only, I suspect the data will show that a significant fraction of people are still using 6to4 as a general network-layer NAT-avoidance mechanism because it continues to work for them, setting up a manual tunnel-broker account takes an order of magnitude more effort, and who has time?  Very few of the people using 6to4 in this way will show up in Google's user behavior analysis, of course, because Google doesn't run its own 6to4 return-path relay as I-D.ietf-v6ops-6to4-advisory recommends.

The way to find these people is to crawl the BitTorrent networks.  What's that old maxim?  "You can't test what you don't measure."  Do you measure the BitTorrent networks?


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From ichiroumakino@gmail.com  Tue Jun 14 10:43:19 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3871C11E8195 for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 10:43:19 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLKJTjyaC+Dd for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 10:43:18 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 23C4B11E8192 for <ietf@ietf.org>; Tue, 14 Jun 2011 10:43:17 -0700 (PDT)
Received: by wwa36 with SMTP id 36so4110269wwa.13 for <ietf@ietf.org>; Tue, 14 Jun 2011 10:43:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=/X/7HGj32BuvPQwkqt2JKk/vg4EZ8CUdeoP4Opv/Cj4=; b=RRcmwDPBgdIpRn24CO7v4vnMOdxaGztW0+IpgmSeXI33f1FSvabXvmuQscxvS7aqJ2 zOGWpSJcChMLz/wIZYuPH/xdkpormCVsKnPgPv4HDI/NJjFKIhDgV6xFDkmkPV9r8WeZ fr1gPI4rgjjXsAVrCuyx9mgf/Ui7IgdkSbOU8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=At3xcRAI4FteZ4RA/6SeIP/+GDfYZQDSYZO2096LBgk/YSa4hv9AP2cZtX6Q/jUtBz F0nYIy8+drI545eCqePfGtfNwDIfqI59qP9DC7ZGrH4K+BU14kXdXXzX1ZKyuulsi8PJ MZ/aREHaFmTNNVL3ZxsI2by/b9Z6Gh+Ut6HyQ=
Received: by 10.227.128.141 with SMTP id k13mr6843858wbs.81.1308073396929; Tue, 14 Jun 2011 10:43:16 -0700 (PDT)
Received: from ams3-vpn-dhcp7391.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id ex2sm5208352wbb.14.2011.06.14.10.43.13 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 14 Jun 2011 10:43:14 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>
Date: Tue, 14 Jun 2011 18:43:10 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4489CB40-0142-467A-9D27-33629F63DD3A@employees.org>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.1084)
Cc: Keith Moore <moore@network-heretics.com>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 17:43:19 -0000

Michel,

making 6to4 historic does not affect 6rd. I think the draft says that =
much too.
I don't think we are saying that native necessarily is better than =
tunnels.
we are saying unmanaged tunnels crossing the Internet is bad.
6rd is managed and contained within a single SP's network.

cheers,
Ole


> According to this:
> =
http://blogs.cisco.com/sp/france-is-famous-for-fine-wine-cheese-and-now-
> ipv6/
> and some more recent direct talks in French, about half of worldwide
> IPv6 traffic is French.
>=20
> The bulk of it comes from a single ISP (Free, AS12322) and their IPv6 =
is
> 6RD (RFC5569, RFC5969), a variant of 6to4. Given the constant =
references
> in 6RD to 6to4, I will point out that making 6to4 historic somehow
> reduces the likeliness of another extremely successful ISP
> implementation based on it.
>=20
> Although Google (in
> http://www.pam2010.ethz.ch/papers/full-length/15.pdf) and other
> measurements classify AS12322's traffic as native, it is 6RD behind =
the
> scenes.
>=20
> If the argument is that IPv6 "native" should be the preferred solution
> over "tunneled", it does not hold water. If you were to remove 6to4 =
and
> 6RD from the picture, that would set us back 10 years ago in terms of
> IPv6 adoption.
>=20
> Michel.
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From moore@network-heretics.com  Tue Jun 14 10:56:01 2011
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 0B5C011E8096 for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 10:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.379
X-Spam-Level: 
X-Spam-Status: No, score=-3.379 tagged_above=-999 required=5 tests=[AWL=0.220,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CNA0u6o-ZHY0 for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 10:56:00 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 563239E8026 for <ietf@ietf.org>; Tue, 14 Jun 2011 10:56:00 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id A106320FF6; Tue, 14 Jun 2011 13:55:59 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 14 Jun 2011 13:55:59 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=LfRVcRk34ukGLiVJr2p5i/V193Y=; b=rTNEtVYA4SsjHALXXCUGFkQZOl0Tg6rfOn/rUAGAGag/R/dWPcdcP72TSqvhNk7cNg8SYBtmqW3h5OyyK3AihWw53XTE0Gqa9mAaL+zgEqBgvWiS6PDcu/AS/eASIRDFK8QXv/kiNZzpZufuK8j3BEWD0Ehuar/3W0i0Goo5jXo=
X-Sasl-enc: 0gxMLfwvvXmI1ydeM4cLlakq5/AFHtrGg3SQSRytnd6b 1308074159
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id AA220401057; Tue, 14 Jun 2011 13:55:58 -0400 (EDT)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4489CB40-0142-467A-9D27-33629F63DD3A@employees.org>
Date: Tue, 14 Jun 2011 13:55:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9DC0A24-4624-431D-A5BC-8AA426DF089D@network-heretics.com>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local> <4489CB40-0142-467A-9D27-33629F63DD3A@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1084)
Cc: Michel Py <michel@arneill-py.sacramento.ca.us>, 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, 14 Jun 2011 17:56:01 -0000

On Jun 14, 2011, at 1:43 PM, Ole Troan wrote:

> making 6to4 historic does not affect 6rd. I think the draft says that =
much too.
> I don't think we are saying that native necessarily is better than =
tunnels.
> we are saying unmanaged tunnels crossing the Internet is bad.

I think this misses the point.  Most internet traffic is "unmanged".  =
The fact that in the case of 6to4 the traffic is protocol 41 doesn't =
affect this. =20

The real problem here is that there are relay routers that advertise =
connectivity to one or both anycast addresses via BGP, that aren't =
properly managed.

A related problem, I suppose, is that to a user, 6to4 looks like "the =
network".  And if there's a problem, the user will blame "the network" =
and ask "the network" support people to fix it.  And quite often the =
problem is not in the access network but in another network.  But (and =
please forgive my ignorance of operational issues) I don't see how =
that's inherently different from any case where there's a BGP =
advertisement to somewhere that blackholes traffic.  Except maybe that =
there are a growing number of 6to4 users who can complain, and that all =
6to4-related problems tend to get lumped together in the minds of =
support people even if they're caused by different networks and routers.

Keith


From alh-ietf@tndh.net  Tue Jun 14 11:16:46 2011
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 BCD639E800A for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.045
X-Spam-Level: *
X-Spam-Status: No, score=1.045 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LKEEpyDj5kPJ for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:16:45 -0700 (PDT)
Received: from tndh.net (unknown [50.46.43.186]) by ietfa.amsl.com (Postfix) with ESMTP id A2EB61F0C36 for <ietf@ietf.org>; Tue, 14 Jun 2011 11:16:45 -0700 (PDT)
X-AuthUser: alh-ietf@tndh.net
Received: from ahainW7 ([192.168.112.18]:23006) by tndh.net with [XMail 1.27 ESMTP Server] id <S18E62E7> for <ietf@ietf.org> from <alh-ietf@tndh.net>; Tue, 14 Jun 2011 11:16:42 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Keith Moore'" <moore@network-heretics.com>, "'Ole Troan'" <otroan@employees.org>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>	<4489CB40-0142-467A-9D27-33629F63DD3A@employees.org> <E9DC0A24-4624-431D-A5BC-8AA426DF089D@network-heretics.com>
In-Reply-To: <E9DC0A24-4624-431D-A5BC-8AA426DF089D@network-heretics.com>
Subject: RE: one data point regarding native IPv6 support
Date: Tue, 14 Jun 2011 11:16:40 -0700
Message-ID: <04d901cc2abf$369a3e20$a3ceba60$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Content-Language: en-us
Thread-Index: AcwqvGE1XqBCGEwNQIqOfJC0CFMxuAAAYWAw
Cc: 'Michel Py' <michel@arneill-py.sacramento.ca.us>, '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, 14 Jun 2011 18:16:46 -0000

Keith is correct, and the further issue is that the *-only-* reason the
'poorly managed' relays are in the path is that the content providers are
refusing to deploy the matching 6to4 router that would take a direct
connection from the customer. 

6to4 direct between the content and consumer is still an 'unmanaged' tunnel
which takes exactly the same path as IPv4 would, so the 'badness' is not due
to managed vs. not. In the grand scheme of things, the last thing the
content providers want is for the network to wrest control over streams into
a walled-garden model. Unfortunately they are not thinking this through,
they are just whining because the deployment of a second prefix on their
content servers does not conform to their IPv4-think dream world. 

Tony


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Keith Moore
> Sent: Tuesday, June 14, 2011 10:56 AM
> To: Ole Troan
> Cc: Michel Py; IETF-Discussion
> Subject: Re: one data point regarding native IPv6 support
> 
> On Jun 14, 2011, at 1:43 PM, Ole Troan wrote:
> 
> > making 6to4 historic does not affect 6rd. I think the draft says that
> much too.
> > I don't think we are saying that native necessarily is better than
> tunnels.
> > we are saying unmanaged tunnels crossing the Internet is bad.
> 
> I think this misses the point.  Most internet traffic is "unmanged".
> The fact that in the case of 6to4 the traffic is protocol 41 doesn't
> affect this.
> 
> The real problem here is that there are relay routers that advertise
> connectivity to one or both anycast addresses via BGP, that aren't
> properly managed.
> 
> A related problem, I suppose, is that to a user, 6to4 looks like "the
> network".  And if there's a problem, the user will blame "the network"
> and ask "the network" support people to fix it.  And quite often the
> problem is not in the access network but in another network.  But (and
> please forgive my ignorance of operational issues) I don't see how
> that's inherently different from any case where there's a BGP
> advertisement to somewhere that blackholes traffic.  Except maybe that
> there are a growing number of 6to4 users who can complain, and that all
> 6to4-related problems tend to get lumped together in the minds of
> support people even if they're caused by different networks and
> routers.
> 
> Keith
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From moore@network-heretics.com  Tue Jun 14 11:33:06 2011
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 7BA9611E8181 for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:33:06 -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.407, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MNzwtBhZawmV for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:33:04 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 3B62C11E810B for <ietf@ietf.org>; Tue, 14 Jun 2011 11:33:04 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 0BB5D212EB; Tue, 14 Jun 2011 14:33:03 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 14 Jun 2011 14:33:03 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=U5FN09Wq7sWmn1p2+6oi5FbZsZQ=; b=T9Bl/jfIInKnfcmUXSel6H3YZ5DHQB2bPvzseLcXg+e8uvGRAFyDvl+qR6hPL1GzXpVNAPFdF3q9Zo/4aZ0WiBYkgSkWTbmeK3mYOo2ofG4qx+nnPZB6l/lDmPMg6bSLrEVJNmmCot7NJb2xfxb9Z3uhAu3sUX655MfWGyDCyI4=
X-Sasl-enc: OgmKGzskSmWie2VVf2num0CflBDr6cv3CSrNMM5WGj5q 1308076382
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id E3951406840; Tue, 14 Jun 2011 14:33:01 -0400 (EDT)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <04d901cc2abf$369a3e20$a3ceba60$@net>
Date: Tue, 14 Jun 2011 14:33:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BED4CEBE-AAFC-45A6-9F08-C1ADCD48C550@network-heretics.com>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>	<4489CB40-0142-467A-9D27-33629F63DD3A@employees.org> <E9DC0A24-4624-431D-A5BC-8AA426DF089D@network-heretics.com> <04d901cc2abf$369a3e20$a3ceba60$@net>
To: "Tony Hain" <alh-ietf@tndh.net>
X-Mailer: Apple Mail (2.1084)
Cc: 'Michel Py' <michel@arneill-py.sacramento.ca.us>, '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, 14 Jun 2011 18:33:06 -0000

On Jun 14, 2011, at 2:16 PM, Tony Hain wrote:

> Keith is correct, and the further issue is that the *-only-* reason =
the
> 'poorly managed' relays are in the path is that the content providers =
are
> refusing to deploy the matching 6to4 router that would take a direct
> connection from the customer.=20

Well, to be fair, they weren't supposed to have to get involved with =
6to4 if they didn't want to.  To the extent that 6to4 causes pain for =
operators that don't provide relay routers, this is a =
mostly-unanticipated and unintended consequence.  (Operators weren't =
expected to *like* 6to4, because at the time 6to4 was written there was =
a general dislike for tunnels in general.  But neither was it expected =
to cause them as much pain as it apparently does.)

> 6to4 direct between the content and consumer is still an 'unmanaged' =
tunnel
> which takes exactly the same path as IPv4 would, so the 'badness' is =
not due
> to managed vs. not. In the grand scheme of things, the last thing the
> content providers want is for the network to wrest control over =
streams into
> a walled-garden model. Unfortunately they are not thinking this =
through,
> they are just whining because the deployment of a second prefix on =
their
> content servers does not conform to their IPv4-think dream world.=20

Though it's clear that some operators want to impose the walled garden, =
I think 6to4 can cause some pain even for those that don't.  I'm hopeful =
that this pain will be short-lived and will be remedied in the short =
term by (a) relay router operators acting more responsibly, (b) =
content-providers providing their own 6to4 addresses, their own 6to4 =
gateways for return traffic, and/or (c) (less ideally) DNS tricks to =
minimize IPv6 exposure to networks known to have trouble with 6to4.  In =
the not-so-much-longer term I hope the pain is relieved by widespread =
adoption of native IPv6 or at least "managed" transition schemes such as =
6rd.=20

But did we really expect there to not be growing pains associated with =
IPv6 transition and deployment?   We certainly had them with IPv4 =
transition and deployment.  After all, 6to4 is pretty much the =
ARPAnet/MILnet to Internet transition revisited; that's where I got the =
idea.

Keith


From joelja@bogus.com  Tue Jun 14 11:36:28 2011
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 027D311E8151 for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.47
X-Spam-Level: 
X-Spam-Status: No, score=-102.47 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UCNStj5+vxMK for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:36:27 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7988211E8102 for <ietf@ietf.org>; Tue, 14 Jun 2011 11:36:18 -0700 (PDT)
Received: from zorch.corp.zynga.com ([12.184.108.202]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5EIaBHN023429 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 14 Jun 2011 18:36:13 GMT (envelope-from joelja@bogus.com)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <04d901cc2abf$369a3e20$a3ceba60$@net>
Date: Tue, 14 Jun 2011 11:36:05 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A9F0A58-6311-4B5F-B642-D4E33A121380@bogus.com>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>	<4489CB40-0142-467A-9D27-33629F63DD3A@employees.org> <E9DC0A24-4624-431D-A5BC-8AA426DF089D@network-heretics.com> <04d901cc2abf$369a3e20$a3ceba60$@net>
To: "Tony Hain" <alh-ietf@tndh.net>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 14 Jun 2011 18:36:15 +0000 (UTC)
Cc: 'Michel Py' <michel@arneill-py.sacramento.ca.us>, 'Keith Moore' <moore@network-heretics.com>, 'IETF-Discussion' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 18:36:28 -0000

On Jun 14, 2011, at 11:16 AM, Tony Hain wrote:

> Keith is correct, and the further issue is that the *-only-* reason =
the
> 'poorly managed' relays are in the path is that the content providers =
are
> refusing to deploy the matching 6to4 router that would take a direct
> connection from the customer.=20
>=20
> 6to4 direct between the content and consumer is still an 'unmanaged' =
tunnel
> which takes exactly the same path as IPv4 would, so the 'badness' is =
not due
> to managed vs. not.

And the breakage still exists even if you do that.

> In the grand scheme of things, the last thing the
> content providers want is for the network to wrest control over =
streams into
> a walled-garden model. Unfortunately they are not thinking this =
through,
> they are just whining because the deployment of a second prefix on =
their
> content servers does not conform to their IPv4-think dream world.=20

Really? More ip addresses on load balancers has never been a problem.

> Tony
>=20
>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
>> Keith Moore
>> Sent: Tuesday, June 14, 2011 10:56 AM
>> To: Ole Troan
>> Cc: Michel Py; IETF-Discussion
>> Subject: Re: one data point regarding native IPv6 support
>>=20
>> On Jun 14, 2011, at 1:43 PM, Ole Troan wrote:
>>=20
>>> making 6to4 historic does not affect 6rd. I think the draft says =
that
>> much too.
>>> I don't think we are saying that native necessarily is better than
>> tunnels.
>>> we are saying unmanaged tunnels crossing the Internet is bad.
>>=20
>> I think this misses the point.  Most internet traffic is "unmanged".
>> The fact that in the case of 6to4 the traffic is protocol 41 doesn't
>> affect this.
>>=20
>> The real problem here is that there are relay routers that advertise
>> connectivity to one or both anycast addresses via BGP, that aren't
>> properly managed.
>>=20
>> A related problem, I suppose, is that to a user, 6to4 looks like "the
>> network".  And if there's a problem, the user will blame "the =
network"
>> and ask "the network" support people to fix it.  And quite often the
>> problem is not in the access network but in another network.  But =
(and
>> please forgive my ignorance of operational issues) I don't see how
>> that's inherently different from any case where there's a BGP
>> advertisement to somewhere that blackholes traffic.  Except maybe =
that
>> there are a growing number of 6to4 users who can complain, and that =
all
>> 6to4-related problems tend to get lumped together in the minds of
>> support people even if they're caused by different networks and
>> routers.
>>=20
>> Keith
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From moore@network-heretics.com  Tue Jun 14 11:46:58 2011
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 1AA4B11E80CE for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.373
X-Spam-Level: 
X-Spam-Status: No, score=-3.373 tagged_above=-999 required=5 tests=[AWL=0.225,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xsde50z8i1K2 for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:46:57 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2590D11E8072 for <ietf@ietf.org>; Tue, 14 Jun 2011 11:46:57 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 9A4C9213C3; Tue, 14 Jun 2011 14:46:56 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Tue, 14 Jun 2011 14:46:56 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=/DMvwxGAL1XQrVyMt3zNeACgWns=; b=o24MtyTc3qvX0yAxL9ujqnCsBEfmUQj2tyqmAteUTirLS2kHZQVd7eQzZ1wg+b1jmEb9/Tl34iyX6bNmeKpUnfo/4ywSeFf9zJWMuhB06PaFSZBfXmjQt/zbhgDth2ccgfRUDBVr00i8fjLt2s9LlkT72vi8WHPTa0nNu1OqfYo=
X-Sasl-enc: 77jQ8Bd8Iv1eslz5C1vQOpI84zgIEd02UZLLQsY4IUim 1308077215
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 34D22403FCE; Tue, 14 Jun 2011 14:46:55 -0400 (EDT)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-1--942467385
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <6A9F0A58-6311-4B5F-B642-D4E33A121380@bogus.com>
Date: Tue, 14 Jun 2011 14:46:54 -0400
Message-Id: <1428AFFC-AFE2-4895-B36B-1FB257B41BA2@network-heretics.com>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>	<4489CB40-0142-467A-9D27-33629F63DD3A@employees.org> <E9DC0A24-4624-431D-A5BC-8AA426DF089D@network-heretics.com> <04d901cc2abf$369a3e20$a3ceba60$@net> <6A9F0A58-6311-4B5F-B642-D4E33A121380@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1084)
Cc: 'Michel Py' <michel@arneill-py.sacramento.ca.us>, '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, 14 Jun 2011 18:46:58 -0000

--Apple-Mail-1--942467385
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 14, 2011, at 2:36 PM, Joel Jaeggli wrote:

> On Jun 14, 2011, at 11:16 AM, Tony Hain wrote:
>=20
>> Keith is correct, and the further issue is that the *-only-* reason =
the
>> 'poorly managed' relays are in the path is that the content providers =
are
>> refusing to deploy the matching 6to4 router that would take a direct
>> connection from the customer.=20
>>=20
>> 6to4 direct between the content and consumer is still an 'unmanaged' =
tunnel
>> which takes exactly the same path as IPv4 would, so the 'badness' is =
not due
>> to managed vs. not.
>=20
> And the breakage still exists even if you do that.

do "what"?

As I understand it, the breakage mostly happens when the traffic doesn't =
 take exactly the same path as IPv4 would, but rather when the traffic =
moves between the IPv4 world and the IPv6 world (or vice versa) via a =
relay router that's advertising a route to a network that it can't =
actually get traffic to.

Though of course there are other sources of breakage:  ISPs that filter =
protocol 41 (thus violating the "best effort" model); and NATs, =
including LSNs.  Neither of these is 6to4's fault.  The IPv4 network is =
supposed to make a best effort to convey traffic from source to =
destination, regardless of protocol type, without altering it other than =
the TTL field.   If ISPs break 6to4 traffic by filtering protocol 41, =
that's clearly their fault.  Likewise, if ISPs break 6to4 traffic by =
imposing NAT on their customers, that's also quite clearly their fault.  =
It's not like we haven't known FOR TWENTY YEARS NOW (remember Kobe?) =
that the Internet was running out of addresses and had a standardized =
replacement in place FOR OVER FIFTEEN YEARS.

If an ISP that has aggressively deployed IPv6 wants to whine about 6to4 =
support issues, I guess they have a legitimate gripe.

Keith


--Apple-Mail-1--942467385
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 14, 2011, at 2:36 PM, Joel Jaeggli =
wrote:</div><br><blockquote type=3D"cite"><div>On Jun 14, 2011, at 11:16 =
AM, Tony Hain wrote:<br><br><blockquote type=3D"cite">Keith is correct, =
and the further issue is that the *-only-* reason =
the<br></blockquote><blockquote type=3D"cite">'poorly managed' relays =
are in the path is that the content providers =
are<br></blockquote><blockquote type=3D"cite">refusing to deploy the =
matching 6to4 router that would take a =
direct<br></blockquote><blockquote type=3D"cite">connection from the =
customer. <br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">6to4 direct =
between the content and consumer is still an 'unmanaged' =
tunnel<br></blockquote><blockquote type=3D"cite">which takes exactly the =
same path as IPv4 would, so the 'badness' is not =
due<br></blockquote><blockquote type=3D"cite">to managed vs. =
not.<br></blockquote><br>And the breakage still exists even if you do =
that.<br></div></blockquote><div><br></div>do =
"what"?</div><div><br></div><div>As I understand it, the breakage mostly =
happens when the traffic <i>doesn't &nbsp;</i>take exactly the same path =
as IPv4 would, but rather when the traffic moves between the IPv4 world =
and the IPv6 world (or vice versa) via a relay router that's advertising =
a route to a network that it can't actually get traffic =
to.</div><div><br></div><div>Though of course there are other sources of =
breakage: &nbsp;ISPs that filter protocol 41 (thus violating the "best =
effort" model); and NATs, including LSNs. &nbsp;Neither of these is =
6to4's fault. &nbsp;The IPv4 network is <i>supposed</i> to make a best =
effort to convey traffic from source to destination, regardless of =
protocol type, without altering it other than the TTL field. &nbsp; If =
ISPs break 6to4 traffic by filtering protocol 41, that's clearly their =
fault. &nbsp;Likewise, if ISPs break 6to4 traffic by imposing NAT on =
their customers, that's also quite clearly their fault. &nbsp;It's not =
like we haven't known FOR TWENTY YEARS NOW (remember Kobe?) that the =
Internet was running out of addresses and had a standardized replacement =
in place FOR OVER FIFTEEN YEARS.</div><div><br></div><div>If an ISP that =
has aggressively deployed IPv6 wants to whine about 6to4 support issues, =
I guess they have a legitimate =
gripe.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-1--942467385--

From joelja@bogus.com  Tue Jun 14 11:52:59 2011
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 E154411E8072 for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dZk8H3Z3qe36 for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:52:59 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id C3A84228014 for <ietf@ietf.org>; Tue, 14 Jun 2011 11:52:58 -0700 (PDT)
Received: from zorch.corp.zynga.com ([12.184.108.202]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5EIqpPG023808 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 14 Jun 2011 18:52:55 GMT (envelope-from joelja@bogus.com)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-5--942117997
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <1428AFFC-AFE2-4895-B36B-1FB257B41BA2@network-heretics.com>
Date: Tue, 14 Jun 2011 11:52:43 -0700
Message-Id: <23D0C699-58F5-410E-94A0-AB834FA564F2@bogus.com>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>	<4489CB40-0142-467A-9D27-33629F63DD3A@employees.org> <E9DC0A24-4624-431D-A5BC-8AA426DF089D@network-heretics.com> <04d901cc2abf$369a3e20$a3ceba60$@net> <6A9F0A58-6311-4B5F-B642-D4E33A121380@bogus.com> <1428AFFC-AFE2-4895-B36B-1FB257B41BA2@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 14 Jun 2011 18:52:55 +0000 (UTC)
Cc: 'Michel Py' <michel@arneill-py.sacramento.ca.us>, '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, 14 Jun 2011 18:53:00 -0000

--Apple-Mail-5--942117997
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jun 14, 2011, at 11:46 AM, Keith Moore wrote:

> On Jun 14, 2011, at 2:36 PM, Joel Jaeggli wrote:
>=20
>> On Jun 14, 2011, at 11:16 AM, Tony Hain wrote:
>>=20
>>> Keith is correct, and the further issue is that the *-only-* reason =
the
>>> 'poorly managed' relays are in the path is that the content =
providers are
>>> refusing to deploy the matching 6to4 router that would take a direct
>>> connection from the customer.=20
>>>=20
>>> 6to4 direct between the content and consumer is still an 'unmanaged' =
tunnel
>>> which takes exactly the same path as IPv4 would, so the 'badness' is =
not due
>>> to managed vs. not.
>>=20
>> And the breakage still exists even if you do that.
>=20
> do "what"?

deploy your own relay, as observed by geoff and others that does not =
rehabilitate (by which I mean make it usable for those customers) 6to4.

> As I understand it, the breakage mostly happens when the traffic =
doesn't  take exactly the same path as IPv4 would, but rather when the =
traffic moves between the IPv4 world and the IPv6 world (or vice versa) =
via a relay router that's advertising a route to a network that it can't =
actually get traffic to.
>=20
> Though of course there are other sources of breakage:  ISPs that =
filter protocol 41 (thus violating the "best effort" model); and NATs, =
including LSNs.  Neither of these is 6to4's fault.

it results in a failure from the vantage point of the customer. you're =
splitting hairs pretty fine if you not willing to ascribe that to 6to4.

>  The IPv4 network is supposed to make a best effort to convey traffic =
from source to destination, regardless of protocol type, without =
altering it other than the TTL field.   If ISPs break 6to4 traffic by =
filtering protocol 41, that's clearly their fault.  Likewise, if ISPs =
break 6to4 traffic by imposing NAT on their customers, that's also quite =
clearly their fault.  It's not like we haven't known FOR TWENTY YEARS =
NOW (remember Kobe?) that the Internet was running out of addresses and =
had a standardized replacement in place FOR OVER FIFTEEN YEARS.
>=20
> If an ISP that has aggressively deployed IPv6 wants to whine about =
6to4 support issues, I guess they have a legitimate gripe.
>=20
> Keith
>=20


--Apple-Mail-5--942117997
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jun 14, 2011, at 11:46 AM, Keith Moore =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><div>On Jun 14, =
2011, at 2:36 PM, Joel Jaeggli wrote:</div><br><blockquote =
type=3D"cite"><div>On Jun 14, 2011, at 11:16 AM, Tony Hain =
wrote:<br><br><blockquote type=3D"cite">Keith is correct, and the =
further issue is that the *-only-* reason =
the<br></blockquote><blockquote type=3D"cite">'poorly managed' relays =
are in the path is that the content providers =
are<br></blockquote><blockquote type=3D"cite">refusing to deploy the =
matching 6to4 router that would take a =
direct<br></blockquote><blockquote type=3D"cite">connection from the =
customer. <br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">6to4 direct =
between the content and consumer is still an 'unmanaged' =
tunnel<br></blockquote><blockquote type=3D"cite">which takes exactly the =
same path as IPv4 would, so the 'badness' is not =
due<br></blockquote><blockquote type=3D"cite">to managed vs. =
not.<br></blockquote><br>And the breakage still exists even if you do =
that.<br></div></blockquote><div><br></div>do =
"what"?</div></div></blockquote><div><br></div><div>deploy your own =
relay, as observed by geoff and others that does not rehabilitate (by =
which I mean make it usable for those customers) =
6to4.</div><br><blockquote type=3D"cite"><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div>As I understand it, the breakage mostly =
happens when the traffic <i>doesn't &nbsp;</i>take exactly the same path =
as IPv4 would, but rather when the traffic moves between the IPv4 world =
and the IPv6 world (or vice versa) via a relay router that's advertising =
a route to a network that it can't actually get traffic =
to.</div><div><br></div><div>Though of course there are other sources of =
breakage: &nbsp;ISPs that filter protocol 41 (thus violating the "best =
effort" model); and NATs, including LSNs. &nbsp;Neither of these is =
6to4's fault. </div></div></blockquote><div><br></div><div>it results in =
a failure from the vantage point of the customer. you're splitting hairs =
pretty fine if you not willing to ascribe that to =
6to4.</div><br><blockquote type=3D"cite"><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div>&nbsp;The IPv4 network is <i>supposed</i> to =
make a best effort to convey traffic from source to destination, =
regardless of protocol type, without altering it other than the TTL =
field. &nbsp; If ISPs break 6to4 traffic by filtering protocol 41, =
that's clearly their fault. &nbsp;Likewise, if ISPs break 6to4 traffic =
by imposing NAT on their customers, that's also quite clearly their =
fault. &nbsp;It's not like we haven't known FOR TWENTY YEARS NOW =
(remember Kobe?) that the Internet was running out of addresses and had =
a standardized replacement in place FOR OVER FIFTEEN =
YEARS.</div><div><br></div><div>If an ISP that has aggressively deployed =
IPv6 wants to whine about 6to4 support issues, I guess they have a =
legitimate =
gripe.</div><div><br></div><div>Keith</div><div><br></div></div></blockquo=
te></div><br></body></html>=

--Apple-Mail-5--942117997--

From moore@network-heretics.com  Tue Jun 14 11:59:46 2011
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 2F0D511E80EA for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.38
X-Spam-Level: 
X-Spam-Status: No, score=-3.38 tagged_above=-999 required=5 tests=[AWL=0.218,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bcEi-h9wHEK7 for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:59:45 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2D43011E81AE for <ietf@ietf.org>; Tue, 14 Jun 2011 11:59:45 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id D24C9213D8; Tue, 14 Jun 2011 14:59:44 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 14 Jun 2011 14:59:44 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=mxY54AdcPBsztHj2G0snHcSiZeE=; b=pi4aYkvRK0OPrPVzX4dH4OG3E8GoQ9z0Byw6WerORA48zw1HQjCocPDVuzZRzm5PAFKdXtMcCpvWBmixPv8X4l8xTeDxp3dZXAx/rw7fjaneY2GZmmmU9sPf1ll3tBFxjGqummFlVhhTdq3/JUu3NPXdXiy1F1/a8a4XlQjGIak=
X-Sasl-enc: cqTkQMhAbRfdor6pNKmOhBFrycU8LnU2+1pPkDN5SJgW 1308077983
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 2A8FE402EDF; Tue, 14 Jun 2011 14:59:42 -0400 (EDT)
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-2--941700188
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <23D0C699-58F5-410E-94A0-AB834FA564F2@bogus.com>
Date: Tue, 14 Jun 2011 14:59:41 -0400
Message-Id: <B4538688-EF69-4A83-AE3B-7E9ABC794CF3@network-heretics.com>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>	<4489CB40-0142-467A-9D27-33629F63DD3A@employees.org> <E9DC0A24-4624-431D-A5BC-8AA426DF089D@network-heretics.com> <04d901cc2abf$369a3e20$a3ceba60$@net> <6A9F0A58-6311-4B5F-B642-D4E33A121380@bogus.com> <1428AFFC-AFE2-4895-B36B-1FB257B41BA2@network-heretics.com> <23D0C699-58F5-410E-94A0-AB834FA564F2@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1084)
Cc: 'Michel Py' <michel@arneill-py.sacramento.ca.us>, '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, 14 Jun 2011 18:59:46 -0000

--Apple-Mail-2--941700188
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 14, 2011, at 2:52 PM, Joel Jaeggli wrote:

>>>> Keith is correct, and the further issue is that the *-only-* reason =
the
>>>> 'poorly managed' relays are in the path is that the content =
providers are
>>>> refusing to deploy the matching 6to4 router that would take a =
direct
>>>> connection from the customer.=20
>>>>=20
>>>> 6to4 direct between the content and consumer is still an =
'unmanaged' tunnel
>>>> which takes exactly the same path as IPv4 would, so the 'badness' =
is not due
>>>> to managed vs. not.
>>>=20
>>> And the breakage still exists even if you do that.
>>=20
>> do "what"?
>=20
> deploy your own relay, as observed by geoff and others that does not =
rehabilitate (by which I mean make it usable for those customers) 6to4.

Ah yes.  This reduces but does not eliminate the potential for breakage. =
 Native IPv4 will still work better, and should generally be preferred =
over 6to4, for the cases where both endpoints have v4 addresses and the =
application can tolerate any NATs in the signal path.

>> As I understand it, the breakage mostly happens when the traffic =
doesn't  take exactly the same path as IPv4 would, but rather when the =
traffic moves between the IPv4 world and the IPv6 world (or vice versa) =
via a relay router that's advertising a route to a network that it can't =
actually get traffic to.
>>=20
>> Though of course there are other sources of breakage:  ISPs that =
filter protocol 41 (thus violating the "best effort" model); and NATs, =
including LSNs.  Neither of these is 6to4's fault.
>=20
> it results in a failure from the vantage point of the customer. you're =
splitting hairs pretty fine if you not willing to ascribe that to 6to4.

Admittedly, to the customer's point-of-view the problems are associated =
with 6to4, or (more likely) IPv6 in general.  But the problems can't be =
fixed by looking only at the vantage point of the customer. =20

When network operators are the major cause of the problems, and they =
want to blame 6to4 for it... well, there's a word for that.  Bottom =
line, that kind of attitude is not going to get the problem fixed either =
for 6to4 specifically or IPv6 in general.

Keith


--Apple-Mail-2--941700188
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 14, 2011, at 2:52 PM, Joel Jaeggli =
wrote:</div><br><blockquote type=3D"cite"><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><blockquote =
type=3D"cite"><div><blockquote type=3D"cite">Keith is correct, and the =
further issue is that the *-only-* reason =
the<br></blockquote><blockquote type=3D"cite">'poorly managed' relays =
are in the path is that the content providers =
are<br></blockquote><blockquote type=3D"cite">refusing to deploy the =
matching 6to4 router that would take a =
direct<br></blockquote><blockquote type=3D"cite">connection from the =
customer. <br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">6to4 direct =
between the content and consumer is still an 'unmanaged' =
tunnel<br></blockquote><blockquote type=3D"cite">which takes exactly the =
same path as IPv4 would, so the 'badness' is not =
due<br></blockquote><blockquote type=3D"cite">to managed vs. =
not.<br></blockquote><br>And the breakage still exists even if you do =
that.<br></div></blockquote><div><br></div>do =
"what"?</div></div></blockquote><div><br></div><div>deploy your own =
relay, as observed by geoff and others that does not rehabilitate (by =
which I mean make it usable for those customers) =
6to4.</div></div></div></blockquote><div><br></div>Ah yes. &nbsp;This =
reduces but does not eliminate the potential for breakage. &nbsp;Native =
IPv4 will still work better, and should generally be preferred over =
6to4, for the cases where both endpoints have v4 addresses and the =
application can tolerate any NATs in the signal =
path.</div><div><br><blockquote type=3D"cite"><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>As I understand it, the =
breakage mostly happens when the traffic <i>doesn't &nbsp;</i>take =
exactly the same path as IPv4 would, but rather when the traffic moves =
between the IPv4 world and the IPv6 world (or vice versa) via a relay =
router that's advertising a route to a network that it can't actually =
get traffic to.</div><div><br></div><div>Though of course there are =
other sources of breakage: &nbsp;ISPs that filter protocol 41 (thus =
violating the "best effort" model); and NATs, including LSNs. =
&nbsp;Neither of these is 6to4's fault. =
</div></div></blockquote><div><br></div><div>it results in a failure =
from the vantage point of the customer. you're splitting hairs pretty =
fine if you not willing to ascribe that to =
6to4.</div></div></div></blockquote><div><br></div><div>Admittedly, to =
the customer's point-of-view the problems are associated with 6to4, or =
(more likely) IPv6 in general. &nbsp;But the problems can't be fixed by =
looking only at the vantage point of the customer. =
&nbsp;</div><div><br></div><div>When network operators are the major =
cause of the problems, and they want to blame 6to4 for it... well, =
there's a word for that. &nbsp;Bottom line, that kind of attitude is not =
going to get the problem fixed either for 6to4 specifically or IPv6 in =
general.</div><div><br></div><div>Keith</div><div><br></div></div></body><=
/html>=

--Apple-Mail-2--941700188--

From yaronf.ietf@gmail.com  Tue Jun 14 13:18:50 2011
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 98F751F0C3D; Tue, 14 Jun 2011 13:18:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.141
X-Spam-Level: 
X-Spam-Status: No, score=-102.141 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K3ndS0ORcAYx; Tue, 14 Jun 2011 13:18:49 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id B5C441F0C3C; Tue, 14 Jun 2011 13:18:48 -0700 (PDT)
Received: by wyb29 with SMTP id 29so4805610wyb.31 for <multiple recipients>; Tue, 14 Jun 2011 13:18:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=jpL3B0w/WgZrufXFcv9pxf5HJ/32ZhGoIMIe/CCOrbQ=; b=gG93W42Ap92IWp1wI69RAn9otmQkuOWkXP5urfIfmcoOuLnSq6PbPnU6rLQE/0nQvn tlV3ywszIosHVfaU9B/EJLfSHgAmgwOSOzcc67DwicSl9qs0OwnhXOHsY66SQScWHlOm mHsc8PzKzDHlqK/qrB10jPkEcVHBUHkyp401k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=erH1i6xaww9DtEm/OMtWaHHxO5FuNAK+vX15X/vpaUFrvKfP8I0pkMk1KS5Ga5GhNS 3Lr28VZ9YZGtZc/L7Blch+Gou/Ndu1+ScqNm7I59V1wIfjgj1PMvB+2iQjBF9Uf3etOv T6k32fRppULVzDNZSUoYyElBtKVEtbWL3ZVFs=
Received: by 10.227.166.129 with SMTP id m1mr6821922wby.65.1308082726759; Tue, 14 Jun 2011 13:18:46 -0700 (PDT)
Received: from [10.0.0.2] (bzq-79-183-225-187.red.bezeqint.net [79.183.225.187]) by mx.google.com with ESMTPS id fm14sm5305523wbb.41.2011.06.14.13.18.43 (version=SSLv3 cipher=OTHER); Tue, 14 Jun 2011 13:18:44 -0700 (PDT)
Message-ID: <4DF7C222.5030808@gmail.com>
Date: Tue, 14 Jun 2011 23:18:42 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: "Cakulev, Violeta (Violeta)" <violeta.cakulev@alcatel-lucent.com>
Subject: Re: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
References: <20110520135022.1622.22713.idtracker@ietfa.amsl.com> <4DD9581C.3070900@gmail.com> <AAE76B481E7A0E4C96610790A852B9A625099F98E2@USNAVSXCHMBSA3.ndc.alcatel-lucent.com> <4DE944C1.5020608@gmail.com> <AAE76B481E7A0E4C96610790A852B9A6250A4F815C@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
In-Reply-To: <AAE76B481E7A0E4C96610790A852B9A6250A4F815C@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: IPsecme WG <ipsec@ietf.org>, "draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org>, "dime@ietf.org" <dime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 20:18:50 -0000

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=us-ascii"
      http-equiv="Content-Type">
    <title></title>
  </head>
  <body text="#000000" bgcolor="#ffffff">
    Hi Violeta,<br>
    <br>
    I am fine with the latest version of the document.<br>
    <br>
    Thank you,<br>
    <br>
    &nbsp;&nbsp;&nbsp; Yaron<br>
    <br>
    On 06/14/2011 09:41 PM, Cakulev, Violeta (Violeta) wrote:
    <blockquote
cite="mid:AAE76B481E7A0E4C96610790A852B9A6250A4F815C@USNAVSXCHMBSA3.ndc.alcatel-lucent.com"
      type="cite">
      <pre wrap="">
Hi Yaron,
Thanks for the suggestions.
Please see inline.

-Violeta

-----Original Message-----
From: Yaron Sheffer [<a class="moz-txt-link-freetext" href="mailto:yaronf.ietf@gmail.com">mailto:yaronf.ietf@gmail.com</a>]
Sent: Friday, June 03, 2011 4:32 PM
To: Cakulev, Violeta (Violeta)
Cc: <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>; IPsecme WG; <a class="moz-txt-link-abbreviated" href="mailto:dime@ietf.org">dime@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org">draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org</a>
Subject: Re: [IPsec] Last Call: &lt;draft-ietf-dime-ikev2-psk-diameter-06.txt&gt; (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard

Hi Violeta,

thanks for your response.

I understand now where you're coming from. But the next person to read the document might not have the authors so readily available :-) Implementors need to understand the motivation for this solution as well as the missing pieces.
[VC] And the next person indeed had the same concern. Therefore, in v8 we made the changes as proposed below.


So I would suggest that you add:
- A short paragraph in the Introduction putting this document in perspective and referencing (non-normative references of course) the
3GGP2 documents.
- Another paragraph in the Security Considerations that says that generation/derivation of the PSK is security-critical, and provides the
3GPP2 docs again as an example of a solution to this problem.
[VC] Please see v8. We added statements both in Introduction and Security Considerations as proposed above.

Regarding usage of the SPI, the document says: "Upon receiving the IKE_AUTH message from the IKEv2 Peer, the IKEv2 Server uses the information received in IDi *and the SPI* if available, to determine if it has the PSK for this IKEv2 Peer."This sounds to me as if the SPI is used as part of the PSK lookup operation. Maybe the SPI should not be mentioned in the above text.
[VC] We modified this paragraph in v8. Please see v8.

Best regards,

     Yaron

On 06/01/2011 11:04 PM, Cakulev, Violeta (Violeta) wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Hi Yaron,
Thanks for the comments.
Please see inline [VC].

-Violeta

-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:ipsec-bounces@ietf.org">ipsec-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:ipsec-bounces@ietf.org">mailto:ipsec-bounces@ietf.org</a>] On Behalf
Of Yaron Sheffer
Sent: Sunday, May 22, 2011 2:38 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>
Cc: IPsecme WG; <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-dime-ikev2-psk-diameter@tools.ietf.og">draft-ietf-dime-ikev2-psk-diameter@tools.ietf.og</a>;
<a class="moz-txt-link-abbreviated" href="mailto:dime@ietf.org">dime@ietf.org</a>
Subject: Re: [IPsec] Last
Call:&lt;draft-ietf-dime-ikev2-psk-diameter-06.txt&gt;  (Diameter IKEv2 PSK:
Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server
Interaction) to Proposed Standard

Hi,

Having read this document only now, I think there's a number of serious issues with it. This document was sent to the ipsec mailing list a while ago but unfortunately got no review.

Summary:
1. I think the wrong architectural choice was made, in preferring PSK over EAP authentication.
2. There is not enough detail in the document to result in interoperable implementations.
[VC] Please see responses to detailed comments.

Detailed comments:
* The appropriate ref for IKEv2 is RFC 5996. This was actually noted in the shepherd review back in March.
[VC] This is fixed in v7.


* The document notes that EAP is one of the authentication modes supported by IKEv2. EAP is designed for interaction with backend AAA servers, and is quite capable of performing shared-secret authentication, using a variety of EAP methods (and see also RFC 5998, on IKEv2 mutual auth with EAP). Yet the document does not explain why EAP is not used, instead preferring the IKE PSK authentication method.
[VC] Diameter application for Diameter client to server communication for IKEv2 with EAP has been specified in RFC 5778. However, there is no Diameter application specified for IKE PSK authentication method. This is stated in the draft both in Abstract and Introduction. The draft does not recommend one or the other, it is simply specifying what is not specified. It is up to a specific use case to decide what to use. For example 3GPP2 decided to use IKEv2 PSK (in 2 of its specifications), and that is what triggered this effort in IETF.


* 4.1: how can the incoming SPI be used to identify the peer?
[VC] As stated in Section 4.1 IDi payload is extracted from the IKE_AUTH message and this payload 'MUST contain an identity that is meaningful
    for the Diameter infrastructure, such as a Network Access Identifier (NAI), since it is used by the IKEv2 Server to populate the User-Name
    AVP in the Diameter message'. SPI is not used to identify the peer.


* Packing additional semantics into SPI may conflict with elements of the IPsec architecture (see for example Sec. 9.3 of draft-ietf-ipsecme-failure-detection-08).
[VC] Agreed.


* 4.1, 2nd paragraph: generation of the PSK is central to this solution, so it cannot be "outside the scope" of the document. There is no way to interoperate otherwise.
[VC] This draft focuses on IKEv2 server, as a Diameter client, to the Diameter server communication for IKEv2 with pre-
    shared secret based authentication, and specifies Diameter application for this communication. It is left to specifications that make use of this Diameter application to specify where the PSK comes from and how it is generated. As mentioned above, there are two 3GPP2 specs that make use of this Diameter application and both of those specs specify generation of the PSK.


* Moreover, if a single client is expected to sometimes use EAP and sometimes PSK, there must be a way to notify it which one to use.
[VC] This is not the assumption. Again this draft specifies Diameter application for Diameter client to the Diameter server communication for IKEv2 with PSK. IKEv2 server knows whether EAP or PSK is used.


* How does key-lifetime relate to the lifetime of the IKE SA?
[VC] This should be the same as in RFC 5996, how pre-shared secret lifetime relates to the lifetime of the IKE SA. This draft should not make any changes.


* Sec. 10 refers to the PSK as a "session key" which is incorrect, as PSK is only used for authentication and does not encrypt anything.
[VC] Good point. It is changed to PSK in v7.


* The same paragraph is very vague about the security properties of PSK.
RFC 5996 takes PSK much more seriously, e.g. "When using pre-shared keys, a critical consideration is how to assure the randomness of these secrets." Again, I believe the document should specify how the PSK is derived.
[VC] I absolutely agree that derivation of PSK is critical. However, as stated above, this draft specifies Diameter application only. Therefore, security consideration section cannot include much more details on derivation of PSK as it is specified elsewhere.


* Why "if nonces are included" where the document says that they *must* be included (in the AVP occurrence table).
[VC] Good point. This is removed in v7.


Thanks,
Yaron

On 05/20/2011 04:50 PM, The IESG wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">The IESG has received a request from the Diameter Maintenance and
Extensions WG (dime) to consider the following document:
- 'Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server
     to Diameter Server Interaction'
    &lt;draft-ietf-dime-ikev2-psk-diameter-06.txt&gt;   as a 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 <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2011-06-03. Exceptionally,
comments may be sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please
retain the beginning of the Subject line to allow automated sorting.

Abstract


     The Internet Key Exchange protocol version 2 (IKEv2) is a component
     of the IPsec architecture and is used to perform mutual
     authentication as well as to establish and to maintain IPsec security
     associations (SAs) between the respective parties.  IKEv2 supports
     several different authentication mechanisms, such as the Extensible
     Authentication Protocol (EAP), certificates, and pre-shared secrets.

     With [RFC5778] the Diameter interworking for Mobile IPv6 between the
     Home Agent, as a Diameter client, and the Diameter server has been
     specified.  However, that specification focused on the usage of EAP
     and did not include support for pre-shared secret based
     authentication available with IKEv2.  This document specifies IKEv2
     server, as a Diameter client, to the Diameter server communication
     for IKEv2 with pre-shared secret based authentication.




The file can be obtained via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/">http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/</a>

IESG discussion can be tracked via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/">http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/</a>


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
IETF-Announce mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IETF-Announce@ietf.org">IETF-Announce@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf-announce">https://www.ietf.org/mailman/listinfo/ietf-announce</a>
</pre>
        </blockquote>
        <pre wrap="">_______________________________________________
IPsec mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IPsec@ietf.org">IPsec@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ipsec">https://www.ietf.org/mailman/listinfo/ipsec</a>
</pre>
      </blockquote>
    </blockquote>
  </body>
</html>

From alh-ietf@tndh.net  Tue Jun 14 13:38:02 2011
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 00A8611E80F4 for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 13:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.045
X-Spam-Level: *
X-Spam-Status: No, score=1.045 tagged_above=-999 required=5 tests=[AWL=-0.001,  BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FH_RELAY_NODNS=1.451,  HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q+6vYXiisGyp for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 13:38:00 -0700 (PDT)
Received: from tndh.net (unknown [50.46.43.186]) by ietfa.amsl.com (Postfix) with ESMTP id 1B22811E80E8 for <ietf@ietf.org>; Tue, 14 Jun 2011 13:37:58 -0700 (PDT)
X-AuthUser: alh-ietf@tndh.net
Received: from ahainW7 ([192.168.112.18]:35137) by tndh.net with [XMail 1.27 ESMTP Server] id <S18E6307> for <ietf@ietf.org> from <alh-ietf@tndh.net>; Tue, 14 Jun 2011 13:37:56 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Joel Jaeggli'" <joelja@bogus.com>, "'Keith Moore'" <moore@network-heretics.com>
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local>	<4489CB40-0142-467A-9D27-33629F63DD3A@employees.org> <E9DC0A24-4624-431D-A5BC-8AA426DF089D@network-heretics.com> <04d901cc2abf$369a3e20$a3ceba60$@net> <6A9F0A58-6311-4B5F-B642-D4E33A121380@bogus.com> <1428AFFC-AFE2-4895-B36B-1FB257B41BA2@network-heretics.com> <23D0C699-58F5-410E-94A0-AB834FA564F2@bogus.com>
In-Reply-To: <23D0C699-58F5-410E-94A0-AB834FA564F2@bogus.com>
Subject: RE: one data point regarding native IPv6 support
Date: Tue, 14 Jun 2011 13:37:54 -0700
Message-ID: <054201cc2ad2$f16a3530$d43e9f90$@net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0543_01CC2A98.450B5D30"
X-Mailer: Microsoft Office Outlook 12.0
Content-Language: en-us
Thread-Index: AcwqxE2NFhkDjgpJSrauvcxK7kiuAAADfm0Q
Cc: 'Michel Py' <michel@arneill-py.sacramento.ca.us>, '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, 14 Jun 2011 20:38:02 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0543_01CC2A98.450B5D30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I did not say deploy you own relay ... that is braindead and doesn't even
come close to understanding how the technology works. A 6to4 router at the
content end is not a relay because it is strictly dealing with 2002:: on
both sides. The only time a relay is required is to transit between the
2002:: prefix and the RIR prefixes. There is no reason to go there, but
people insist because their IPv4-think myopia refuses to allow them to
realize that their content server can simultaneously have an RIR prefix and
a 2002:: prefix.

 

Tony

 

 

From: Joel Jaeggli [mailto:joelja@bogus.com] 
Sent: Tuesday, June 14, 2011 11:53 AM
To: Keith Moore
Cc: Tony Hain; 'Ole Troan'; 'Michel Py'; 'IETF-Discussion'
Subject: Re: one data point regarding native IPv6 support

 

 

On Jun 14, 2011, at 11:46 AM, Keith Moore wrote:





On Jun 14, 2011, at 2:36 PM, Joel Jaeggli wrote:





On Jun 14, 2011, at 11:16 AM, Tony Hain wrote:




Keith is correct, and the further issue is that the *-only-* reason the

'poorly managed' relays are in the path is that the content providers are

refusing to deploy the matching 6to4 router that would take a direct

connection from the customer. 

 

6to4 direct between the content and consumer is still an 'unmanaged' tunnel

which takes exactly the same path as IPv4 would, so the 'badness' is not due

to managed vs. not.


And the breakage still exists even if you do that.

 

do "what"?

 

deploy your own relay, as observed by geoff and others that does not
rehabilitate (by which I mean make it usable for those customers) 6to4.





As I understand it, the breakage mostly happens when the traffic doesn't
take exactly the same path as IPv4 would, but rather when the traffic moves
between the IPv4 world and the IPv6 world (or vice versa) via a relay router
that's advertising a route to a network that it can't actually get traffic
to.

 

Though of course there are other sources of breakage:  ISPs that filter
protocol 41 (thus violating the "best effort" model); and NATs, including
LSNs.  Neither of these is 6to4's fault. 

 

it results in a failure from the vantage point of the customer. you're
splitting hairs pretty fine if you not willing to ascribe that to 6to4.





 The IPv4 network is supposed to make a best effort to convey traffic from
source to destination, regardless of protocol type, without altering it
other than the TTL field.   If ISPs break 6to4 traffic by filtering protocol
41, that's clearly their fault.  Likewise, if ISPs break 6to4 traffic by
imposing NAT on their customers, that's also quite clearly their fault.
It's not like we haven't known FOR TWENTY YEARS NOW (remember Kobe?) that
the Internet was running out of addresses and had a standardized replacement
in place FOR OVER FIFTEEN YEARS.

 

If an ISP that has aggressively deployed IPv6 wants to whine about 6to4
support issues, I guess they have a legitimate gripe.

 

Keith

 

 


------=_NextPart_000_0543_01CC2A98.450B5D30
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:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* 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-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple style=3D'word-wrap: break-word;-webkit-nbsp-mode: =
space;-webkit-line-break: after-white-space'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I did not say deploy you own relay ... that is braindead and =
doesn&#8217;t even come close to understanding how the technology works. =
A 6to4 router at the content end is not a relay because it is strictly =
dealing with 2002:: on both sides. The only time a relay is required is =
to transit between the 2002:: prefix and the RIR prefixes. There is no =
reason to go there, but people insist because their IPv4-think myopia =
refuses to allow them to realize that their content server can =
simultaneously have an RIR prefix and a 2002:: =
prefix.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Tony<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Joel Jaeggli [mailto:joelja@bogus.com] <br><b>Sent:</b> Tuesday, June =
14, 2011 11:53 AM<br><b>To:</b> Keith Moore<br><b>Cc:</b> Tony Hain; =
'Ole Troan'; 'Michel Py'; 'IETF-Discussion'<br><b>Subject:</b> Re: one =
data point regarding native IPv6 =
support<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Jun 14, 2011, at 11:46 AM, Keith Moore wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><div><p =
class=3DMsoNormal>On Jun 14, 2011, at 2:36 PM, Joel Jaeggli =
wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><p class=3DMsoNormal>On =
Jun 14, 2011, at 11:16 AM, Tony Hain wrote:<br><br><br><o:p></o:p></p><p =
class=3DMsoNormal>Keith is correct, and the further issue is that the =
*-only-* reason the<o:p></o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal>'poorly managed' relays are in the path is that the =
content providers are<o:p></o:p></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal>refusing to deploy the matching 6to4 router that would =
take a direct<o:p></o:p></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal>connection from the customer. =
<o:p></o:p></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p class=3DMsoNormal>6to4 =
direct between the content and consumer is still an 'unmanaged' =
tunnel<o:p></o:p></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal>which takes exactly the same path as IPv4 would, so =
the 'badness' is not due<o:p></o:p></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p class=3DMsoNormal>to =
managed vs. not.<o:p></o:p></p></blockquote><p class=3DMsoNormal><br>And =
the breakage still exists even if you do =
that.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal>do =
&quot;what&quot;?<o:p></o:p></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>deploy your own relay, as observed by geoff and others =
that does not rehabilitate (by which I mean make it usable for those =
customers) 6to4.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal>As I understand it, the breakage mostly happens when =
the traffic <i>doesn't &nbsp;</i>take exactly the same path as IPv4 =
would, but rather when the traffic moves between the IPv4 world and the =
IPv6 world (or vice versa) via a relay router that's advertising a route =
to a network that it can't actually get traffic =
to.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Though of course there are other sources of breakage: =
&nbsp;ISPs that filter protocol 41 (thus violating the &quot;best =
effort&quot; model); and NATs, including LSNs. &nbsp;Neither of these is =
6to4's fault. <o:p></o:p></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>it results in a failure from the vantage point of the =
customer. you're splitting hairs pretty fine if you not willing to =
ascribe that to 6to4.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal>&nbsp;The IPv4 network is <i>supposed</i> to make a =
best effort to convey traffic from source to destination, regardless of =
protocol type, without altering it other than the TTL field. &nbsp; If =
ISPs break 6to4 traffic by filtering protocol 41, that's clearly their =
fault. &nbsp;Likewise, if ISPs break 6to4 traffic by imposing NAT on =
their customers, that's also quite clearly their fault. &nbsp;It's not =
like we haven't known FOR TWENTY YEARS NOW (remember Kobe?) that the =
Internet was running out of addresses and had a standardized replacement =
in place FOR OVER FIFTEEN YEARS.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>If an ISP that has aggressively deployed IPv6 wants to =
whine about 6to4 support issues, I guess they have a legitimate =
gripe.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Keith<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_0543_01CC2A98.450B5D30--


From yaronf.ietf@gmail.com  Tue Jun 14 13:47:09 2011
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 25C9021F84C4; Tue, 14 Jun 2011 13:47:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.87
X-Spam-Level: 
X-Spam-Status: No, score=-102.87 tagged_above=-999 required=5 tests=[AWL=0.729, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0VVan5xvlTGW; Tue, 14 Jun 2011 13:47:08 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBF021F84C1; Tue, 14 Jun 2011 13:47:07 -0700 (PDT)
Received: by wwa36 with SMTP id 36so4223736wwa.13 for <multiple recipients>; Tue, 14 Jun 2011 13:47:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5cCkchvKjej11qUKUxC7mqTDWCUb31Nlh2JM0SAgGRA=; b=rT41ILV9lnTjsNzfN2ha9VehVkmFUnlU22unhLLBO0VMRLSFmS4qOOBaQmdb8p1mR6 GRGqGWAQaFSJNBkAfLqXN2YMVau3jZIZxpaB5Z1OpFpx82g/ZkgFgvPI+sIk5UxZpyl6 WVPkHVh6NFIAolwZl7Vbr1dq92Q9VMzKQhLSQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=XKu+nU68viLYozunUPQ99dGp4xXpQZUMPNg6uQQJYuj0jH04va9UPfUPGZa7mSm5EB EuaW6UowGQqW7bA7HRvBu5q5uRNVDseqv/xZEh37iOu4DSnBterqbZBEOPWom0CzqloW 2X9Vby00qUumx2JfstwIHSFfSFZrkZtqcjW/0=
Received: by 10.227.12.18 with SMTP id v18mr189682wbv.89.1308084424449; Tue, 14 Jun 2011 13:47:04 -0700 (PDT)
Received: from [10.0.0.2] (bzq-79-183-225-187.red.bezeqint.net [79.183.225.187]) by mx.google.com with ESMTPS id fm14sm5322493wbb.41.2011.06.14.13.47.01 (version=SSLv3 cipher=OTHER); Tue, 14 Jun 2011 13:47:03 -0700 (PDT)
Message-ID: <4DF7C8C3.7020303@gmail.com>
Date: Tue, 14 Jun 2011 23:46:59 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: "Cakulev, Violeta (Violeta)" <violeta.cakulev@alcatel-lucent.com>
Subject: Re: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
References: <20110520135022.1622.22713.idtracker@ietfa.amsl.com> <4DD9581C.3070900@gmail.com> <AAE76B481E7A0E4C96610790A852B9A625099F98E2@USNAVSXCHMBSA3.ndc.alcatel-lucent.com> <4DE944C1.5020608@gmail.com> <AAE76B481E7A0E4C96610790A852B9A6250A4F815C@USNAVSXCHMBSA3.ndc.alcatel-lucent.com> <4DF7C222.5030808@gmail.com>
In-Reply-To: <4DF7C222.5030808@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IPsecme WG <ipsec@ietf.org>, "draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org>, "dime@ietf.org" <dime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 20:47:09 -0000

Resending, apologies if you see it twice.

On 06/14/2011 11:18 PM, Yaron Sheffer wrote:
> Hi Violeta,
>
> I am fine with the latest version of the document.
>
> Thank you,
>
>     Yaron
>
> On 06/14/2011 09:41 PM, Cakulev, Violeta (Violeta) wrote:
>> Hi Yaron,
>> Thanks for the suggestions.
>> Please see inline.
>>
>> -Violeta
>>
>> -----Original Message-----
>> From: Yaron Sheffer [mailto:yaronf.ietf@gmail.com]
>> Sent: Friday, June 03, 2011 4:32 PM
>> To: Cakulev, Violeta (Violeta)
>> Cc:ietf@ietf.org; IPsecme WG;dime@ietf.org;draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org
>> Subject: Re: [IPsec] Last Call:<draft-ietf-dime-ikev2-psk-diameter-06.txt>  (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
>>
>> Hi Violeta,
>>
>> thanks for your response.
>>
>> I understand now where you're coming from. But the next person to read the document might not have the authors so readily available :-) Implementors need to understand the motivation for this solution as well as the missing pieces.
>> [VC] And the next person indeed had the same concern. Therefore, in v8 we made the changes as proposed below.
>>
>>
>> So I would suggest that you add:
>> - A short paragraph in the Introduction putting this document in perspective and referencing (non-normative references of course) the
>> 3GGP2 documents.
>> - Another paragraph in the Security Considerations that says that generation/derivation of the PSK is security-critical, and provides the
>> 3GPP2 docs again as an example of a solution to this problem.
>> [VC] Please see v8. We added statements both in Introduction and Security Considerations as proposed above.
>>
>> Regarding usage of the SPI, the document says: "Upon receiving the IKE_AUTH message from the IKEv2 Peer, the IKEv2 Server uses the information received in IDi *and the SPI* if available, to determine if it has the PSK for this IKEv2 Peer."This sounds to me as if the SPI is used as part of the PSK lookup operation. Maybe the SPI should not be mentioned in the above text.
>> [VC] We modified this paragraph in v8. Please see v8.
>>
>> Best regards,
>>
>>       Yaron
>>
>> On 06/01/2011 11:04 PM, Cakulev, Violeta (Violeta) wrote:
>>> Hi Yaron,
>>> Thanks for the comments.
>>> Please see inline [VC].
>>>
>>> -Violeta
>>>
>>> -----Original Message-----
>>> From:ipsec-bounces@ietf.org  [mailto:ipsec-bounces@ietf.org] On Behalf
>>> Of Yaron Sheffer
>>> Sent: Sunday, May 22, 2011 2:38 PM
>>> To:ietf@ietf.org
>>> Cc: IPsecme WG;draft-ietf-dime-ikev2-psk-diameter@tools.ietf.og;
>>> dime@ietf.org
>>> Subject: Re: [IPsec] Last
>>> Call:<draft-ietf-dime-ikev2-psk-diameter-06.txt>   (Diameter IKEv2 PSK:
>>> Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server
>>> Interaction) to Proposed Standard
>>>
>>> Hi,
>>>
>>> Having read this document only now, I think there's a number of serious issues with it. This document was sent to the ipsec mailing list a while ago but unfortunately got no review.
>>>
>>> Summary:
>>> 1. I think the wrong architectural choice was made, in preferring PSK over EAP authentication.
>>> 2. There is not enough detail in the document to result in interoperable implementations.
>>> [VC] Please see responses to detailed comments.
>>>
>>> Detailed comments:
>>> * The appropriate ref for IKEv2 is RFC 5996. This was actually noted in the shepherd review back in March.
>>> [VC] This is fixed in v7.
>>>
>>>
>>> * The document notes that EAP is one of the authentication modes supported by IKEv2. EAP is designed for interaction with backend AAA servers, and is quite capable of performing shared-secret authentication, using a variety of EAP methods (and see also RFC 5998, on IKEv2 mutual auth with EAP). Yet the document does not explain why EAP is not used, instead preferring the IKE PSK authentication method.
>>> [VC] Diameter application for Diameter client to server communication for IKEv2 with EAP has been specified in RFC 5778. However, there is no Diameter application specified for IKE PSK authentication method. This is stated in the draft both in Abstract and Introduction. The draft does not recommend one or the other, it is simply specifying what is not specified. It is up to a specific use case to decide what to use. For example 3GPP2 decided to use IKEv2 PSK (in 2 of its specifications), and that is what triggered this effort in IETF.
>>>
>>>
>>> * 4.1: how can the incoming SPI be used to identify the peer?
>>> [VC] As stated in Section 4.1 IDi payload is extracted from the IKE_AUTH message and this payload 'MUST contain an identity that is meaningful
>>>      for the Diameter infrastructure, such as a Network Access Identifier (NAI), since it is used by the IKEv2 Server to populate the User-Name
>>>      AVP in the Diameter message'. SPI is not used to identify the peer.
>>>
>>>
>>> * Packing additional semantics into SPI may conflict with elements of the IPsec architecture (see for example Sec. 9.3 of draft-ietf-ipsecme-failure-detection-08).
>>> [VC] Agreed.
>>>
>>>
>>> * 4.1, 2nd paragraph: generation of the PSK is central to this solution, so it cannot be "outside the scope" of the document. There is no way to interoperate otherwise.
>>> [VC] This draft focuses on IKEv2 server, as a Diameter client, to the Diameter server communication for IKEv2 with pre-
>>>      shared secret based authentication, and specifies Diameter application for this communication. It is left to specifications that make use of this Diameter application to specify where the PSK comes from and how it is generated. As mentioned above, there are two 3GPP2 specs that make use of this Diameter application and both of those specs specify generation of the PSK.
>>>
>>>
>>> * Moreover, if a single client is expected to sometimes use EAP and sometimes PSK, there must be a way to notify it which one to use.
>>> [VC] This is not the assumption. Again this draft specifies Diameter application for Diameter client to the Diameter server communication for IKEv2 with PSK. IKEv2 server knows whether EAP or PSK is used.
>>>
>>>
>>> * How does key-lifetime relate to the lifetime of the IKE SA?
>>> [VC] This should be the same as in RFC 5996, how pre-shared secret lifetime relates to the lifetime of the IKE SA. This draft should not make any changes.
>>>
>>>
>>> * Sec. 10 refers to the PSK as a "session key" which is incorrect, as PSK is only used for authentication and does not encrypt anything.
>>> [VC] Good point. It is changed to PSK in v7.
>>>
>>>
>>> * The same paragraph is very vague about the security properties of PSK.
>>> RFC 5996 takes PSK much more seriously, e.g. "When using pre-shared keys, a critical consideration is how to assure the randomness of these secrets." Again, I believe the document should specify how the PSK is derived.
>>> [VC] I absolutely agree that derivation of PSK is critical. However, as stated above, this draft specifies Diameter application only. Therefore, security consideration section cannot include much more details on derivation of PSK as it is specified elsewhere.
>>>
>>>
>>> * Why "if nonces are included" where the document says that they *must* be included (in the AVP occurrence table).
>>> [VC] Good point. This is removed in v7.
>>>
>>>
>>> Thanks,
>>> Yaron
>>>
>>> On 05/20/2011 04:50 PM, The IESG wrote:
>>>> The IESG has received a request from the Diameter Maintenance and
>>>> Extensions WG (dime) to consider the following document:
>>>> - 'Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server
>>>>       to Diameter Server Interaction'
>>>>      <draft-ietf-dime-ikev2-psk-diameter-06.txt>    as a 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
>>>> theietf@ietf.org  mailing lists by 2011-06-03. Exceptionally,
>>>> comments may be sent toiesg@ietf.org  instead. In either case, please
>>>> retain the beginning of the Subject line to allow automated sorting.
>>>>
>>>> Abstract
>>>>
>>>>
>>>>       The Internet Key Exchange protocol version 2 (IKEv2) is a component
>>>>       of the IPsec architecture and is used to perform mutual
>>>>       authentication as well as to establish and to maintain IPsec security
>>>>       associations (SAs) between the respective parties.  IKEv2 supports
>>>>       several different authentication mechanisms, such as the Extensible
>>>>       Authentication Protocol (EAP), certificates, and pre-shared secrets.
>>>>
>>>>       With [RFC5778] the Diameter interworking for Mobile IPv6 between the
>>>>       Home Agent, as a Diameter client, and the Diameter server has been
>>>>       specified.  However, that specification focused on the usage of EAP
>>>>       and did not include support for pre-shared secret based
>>>>       authentication available with IKEv2.  This document specifies IKEv2
>>>>       server, as a Diameter client, to the Diameter server communication
>>>>       for IKEv2 with pre-shared secret based authentication.
>>>>
>>>>
>>>>
>>>>
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/
>>>>
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/
>>>>
>>>>
>>>> No IPR declarations have been submitted directly on this I-D.
>>>>
>>>>
>>>> _______________________________________________
>>>> IETF-Announce mailing list
>>>> IETF-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>> _______________________________________________
>>> IPsec mailing list
>>> IPsec@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ipsec

From jnc@mercury.lcs.mit.edu  Tue Jun 14 19:20:10 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35D041F0C5B for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 19:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exJFQJ+KnThF for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 19:20:09 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 214B21F0C4F for <ietf@ietf.org>; Tue, 14 Jun 2011 19:20:08 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 0816818C172; Tue, 14 Jun 2011 22:20:08 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: one data point regarding native IPv6 support
Message-Id: <20110615022008.0816818C172@mercury.lcs.mit.edu>
Date: Tue, 14 Jun 2011 22:20:08 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 02:20:10 -0000

    > From: Keith Moore <moore@network-heretics.com>

    > As I understand it, the breakage mostly happens when the traffic
    > doesn't take exactly the same path as IPv4 would, but rather when the
    > traffic moves between the IPv4 world and the IPv6 world (or vice versa)
    > via a relay router that's advertising a route to a network that it
    > can't actually get traffic to.
    > Though of course there are other sources of breakage: ISPs that filter
    > protocol 41 ... and NATs, 

Keith, I'm not sure that relay routers advertising incorrectly are the main
problem (although none of the studies I've looked at are really comprehensive
in terms of data on _all_ causes of 6to4 failure, especially on failures on
the path _from_ the 6to4 host, which are obviously sort of impossible to
detect at servers).

First, RFC-3068 does say:

  "Any 6to4 relay router corresponding to this specification must
   include a monitoring function, to check that the 6to4 relay function
   is operational.  The router must stop injecting the route leading to
   the 6to4 anycast prefix immediately if it detects that the relay
   function is not operational."

So if the 6to4 relay is operating properly, it shouldn't be advertising into
the IPv4 world (i.e. using the anycast address) unless it has 'good' IPv6
connectivity, or into the IPv6 world (i.e. advertising the 6to4 block) unless
it has 'good' IPv4 connectivity. (Advertising only the 6to4 variants of those
pieces of the IPv4 space which it definitely has routes to is not allowed by
the spec; reasonably, as it would add the size of the IPv4 routing table to
the IPv6 routing table.)

I'm not sure how exactly various boxes measure 'good' connectivity (and of
course a poor implementation might not do a good job of this), but in
_theory_ it shouldn't be the worst part of the problem.


Second, while I don't know about failures on the '4to6_host->relay_router'
(i.e. outbound) part of the path, when I read:

  http://www.potaroo.net/ispcol/2010-12/6to4fail.html

it looked into failures on the 'relay_router->4to6_host' (i.e. inbound) path,
and there, of the failures which were not due to a problem in the relay
router itself, many were caused by failures on the inbound path between the
relay router and the 4to6_host, failures which may well be not the fault of
the ISP:

- roughly 25% because of the presence of a NAT between the relay router and
the 4to6 host (so that the host did not know its public IPv4 address, and
probably didn't have a way to get packets to itself even if it did)

- roughly 75% because of the presence of some device between the relay router
and the 4to6 host that filtered _inbound_ protocol 41 (so that the host cannot
get any return 6to4 traffic)

While we don't know exactly what share of the overall 6to4 'problem' these two
cause, we can guess that it's likely quite substantial: 'paranoid' firewalls
are common, and NAT boxes are basically ubiquitous (anyone with IP service at
home, and a wireless laptop - which is a lot of people - will have one).

	Noel

From marka@isc.org  Tue Jun 14 20:03:29 2011
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 F3BCE11E8099 for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 20:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kMBRYGbACIBz for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 20:03:28 -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 7157511E808C for <ietf@ietf.org>; Tue, 14 Jun 2011 20:03:27 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 32D95C9516; Wed, 15 Jun 2011 03:01:43 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 263BE216C7B; Wed, 15 Jun 2011 03:01:35 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 3E2A810C7E48; Wed, 15 Jun 2011 13:01:30 +1000 (EST)
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
From: Mark Andrews <marka@isc.org>
References: <20110615022008.0816818C172@mercury.lcs.mit.edu>
Subject: Re: one data point regarding native IPv6 support
In-reply-to: Your message of "Tue, 14 Jun 2011 22:20:08 -0400." <20110615022008.0816818C172@mercury.lcs.mit.edu>
Date: Wed, 15 Jun 2011 13:01:29 +1000
Message-Id: <20110615030130.3E2A810C7E48@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, 15 Jun 2011 03:03:29 -0000

In message <20110615022008.0816818C172@mercury.lcs.mit.edu>, Noel Chiappa write
s:
>     > From: Keith Moore <moore@network-heretics.com>
> 
>     > As I understand it, the breakage mostly happens when the traffic
>     > doesn't take exactly the same path as IPv4 would, but rather when the
>     > traffic moves between the IPv4 world and the IPv6 world (or vice versa)
>     > via a relay router that's advertising a route to a network that it
>     > can't actually get traffic to.
>     > Though of course there are other sources of breakage: ISPs that filter
>     > protocol 41 ... and NATs, 
> 
> Keith, I'm not sure that relay routers advertising incorrectly are the main
> problem (although none of the studies I've looked at are really comprehensive
> in terms of data on _all_ causes of 6to4 failure, especially on failures on
> the path _from_ the 6to4 host, which are obviously sort of impossible to
> detect at servers).
> 
> First, RFC-3068 does say:
> 
>   "Any 6to4 relay router corresponding to this specification must
>    include a monitoring function, to check that the 6to4 relay function
>    is operational.  The router must stop injecting the route leading to
>    the 6to4 anycast prefix immediately if it detects that the relay
>    function is not operational."
> 
> So if the 6to4 relay is operating properly, it shouldn't be advertising into
> the IPv4 world (i.e. using the anycast address) unless it has 'good' IPv6
> connectivity, or into the IPv6 world (i.e. advertising the 6to4 block) unless
> it has 'good' IPv4 connectivity. (Advertising only the 6to4 variants of those
> pieces of the IPv4 space which it definitely has routes to is not allowed by
> the spec; reasonably, as it would add the size of the IPv4 routing table to
> the IPv6 routing table.)
> 
> I'm not sure how exactly various boxes measure 'good' connectivity (and of
> course a poor implementation might not do a good job of this), but in
> _theory_ it shouldn't be the worst part of the problem.
> 
> 
> Second, while I don't know about failures on the '4to6_host->relay_router'
> (i.e. outbound) part of the path, when I read:
> 
>   http://www.potaroo.net/ispcol/2010-12/6to4fail.html
> 
> it looked into failures on the 'relay_router->4to6_host' (i.e. inbound) path,
> and there, of the failures which were not due to a problem in the relay
> router itself, many were caused by failures on the inbound path between the
> relay router and the 4to6_host, failures which may well be not the fault of
> the ISP:
> 
> - roughly 25% because of the presence of a NAT between the relay router and
> the 4to6 host (so that the host did not know its public IPv4 address, and
> probably didn't have a way to get packets to itself even if it did)

Presumable non-RFC 1918 internal addresses being NAT'd as RFC 1918 address
are already verboten.
 
> - roughly 75% because of the presence of some device between the relay router
> and the 4to6 host that filtered _inbound_ protocol 41 (so that the host canno
> t
> get any return 6to4 traffic)
> 
> While we don't know exactly what share of the overall 6to4 'problem' these tw
> o
> cause, we can guess that it's likely quite substantial: 'paranoid' firewalls
> are common, and NAT boxes are basically ubiquitous (anyone with IP service at
> home, and a wireless laptop - which is a lot of people - will have one).

And making 6to4 historic fixes these without breaking 6to4 for those
that it works for how?

draft-andrews-v6ops-6to4-router-option-02.txt provides a mechanism
which allows network operators for signal that 6to4 should not be
used in both of the above cases.

Similarly testing that you can reach the 6to4 relay router before
adding a route pointing to it or advertising a 6to4 prefix is a
good backup without the option however no all 6to4 relays have
machine listening on the all zeros address.  HE for example listens
on 2002:c058:6301::1 so you can't just ping it.

A I-D saying how to test if a 6to4 relay is up may be needed.

Mark
 
> 	Noel
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From evnikita2@gmail.com  Wed Jun 15 02:06:20 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 731AB11E80AA for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 02:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.23
X-Spam-Level: 
X-Spam-Status: No, score=-3.23 tagged_above=-999 required=5 tests=[AWL=-0.231,  BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-hD7el3GAWT for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 02:06:19 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB8211E8094 for <ietf@ietf.org>; Wed, 15 Jun 2011 02:06:19 -0700 (PDT)
Received: by fxm15 with SMTP id 15so280906fxm.31 for <ietf@ietf.org>; Wed, 15 Jun 2011 02:06:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+dhZgrPn7BhdOEJoF9OMn5CbhbZCucKvdkJuZgsdEAc=; b=hHn+F0ZAaQKnlIy2RA8N6dWPZXG+g7YKgs6yThauJKbyhKzuajzTyFX+FhPiA6rfs0 hDHJs5bQZYQ8v6/8NFj3oJEJffuedacJpX7QBoBL3nQaFxvsCRRwjO2+ivMb0RVdmMZv te6Tztd5YtlMe/NbG9qqTPexiU4eZIdSf0HMU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=DHAd3mH8EAb4At3JxxW/rGBy+bOydijrBHZhrpWNJwmSIxf/vIPA4YOacTp/XtHqer cS8zFUwrzu9+VLquN1Qh4F9eI8iB0l5VENvEpTJovjip9d5Jv14qlz/VHRSiRwynVP4l 6++cokrek/I3c1QG0gshp0rPWftTbTDoZgWOM=
Received: by 10.223.67.210 with SMTP id s18mr305879fai.41.1308128778463; Wed, 15 Jun 2011 02:06:18 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id g8sm99676fai.20.2011.06.15.02.06.16 (version=SSLv3 cipher=OTHER); Wed, 15 Jun 2011 02:06:17 -0700 (PDT)
Message-ID: <4DF87637.2000301@gmail.com>
Date: Wed, 15 Jun 2011 12:07:03 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Boris Zbarsky <bzbarsky@MIT.EDU>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu>
In-Reply-To: <4D3A64FF.1020000@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 09:06:20 -0000

Hello Boris, all,

FYI, authors of draft-holsten-about-uri-scheme allowed me to become the 
co-author of this draft.  We got to your message.  The -07 is almost 
prepared for publication, but Lachlan pointed these comments were not 
addressed.  Let me express my opinion regarding them.

22.01.2011 7:02, Boris Zbarsky wrote:
> There seem to be two differences between what the draft specifies 
> right now and what Gecko, at least, does:
>
> 1) Section 5.3 says:
>
>    Applications SHOULD resolve unrecognized "about" URIs in the
>    same way as "about:blank".
>
> Gecko treats unknown about:* as unparseable URIs, and is not likely to 
> change that behavior.  While that's allowed by the SHOULD, it's not 
> clear to me why this is a SHOULD as opposed to a MAY, nor is it clear 
> why this is present at all.  In particular, as specified this will 
> cause situations where an empty resource is silently returned instead 
> of a failure that the consumer can notice (e.g. in the DOM case via 
> error event handlers and the like).
I don't think MAY is fine here, as this is a recommendation.  Moreover, 
as Gecko seems to be an only browser with such behavior, I don't think 
changing the Standards Track specification should mention/change this; 
as you noted, SHOULD is not a restriction.
>
> 2)  Section 6 says:
>
>   For example, "about:blank", "about:blan%6B" and "about:blan%6b"
>   are equivalent
>
> In Gecko they are not.  The string after ':' is treated as a literal 
> string; when looking up a way to handle the URI the second and third 
> URIs above are treated as unparseable by Gecko in its default 
> configuration.  Changing this has some security implications that 
> would require careful auditing of not only Gecko code but some 
> specifications (e.g. HTML5 defines certain special-case security 
> behavior for about:blank that's not obviously safe to apply to the 
> other strings above).
>
> The same section says:
>
>   Similarly, "about:blank%3F" is not equivalent to "about:blank?".
>
> which I think is trying to explain by example that only unreserved 
> characters need to be unescaped.  But that assumes an implementation 
> of RFC 3986 which may or may not be the case in web browsers (and is 
> NOT the case in Gecko, for example, for various web-compatibility 
> reasons).  Unless there are very strong reasons for it, I would 
> recommend that no normalization is performed on about: URIs, period.
The point of this comment is to propose abandoning normalization of 
'about' URIs because of some ad hoc behavior of an only application - 
Gecko.  The purpose of our draft is to give a stable specification of 
the scheme and normalize all existing types of behavior with regard to 
handling 'about' URIs.  It will be easier for Gecko to change its 
behavior rather than for other apps to do this.

Boris, could you please let me know whether you have some strong opinion 
regarding your January comments/insist on incorporating them in the draft.

Thanks,
Mykyta Yevstifeyev
>
> -Boris
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From julian.reschke@gmx.de  Wed Jun 15 03:13:15 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1D1C11E8074 for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 03:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.262
X-Spam-Level: 
X-Spam-Status: No, score=-103.262 tagged_above=-999 required=5 tests=[AWL=-1.262, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bLwLaHLIfKun for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 03:13:14 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 0942111E8070 for <ietf@ietf.org>; Wed, 15 Jun 2011 03:13:13 -0700 (PDT)
Received: (qmail invoked by alias); 15 Jun 2011 10:13:12 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp069) with SMTP; 15 Jun 2011 12:13:12 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/FrPZ999LFlE1gYsZCaWGGBO5XQay2+JgsN3e1zt Vl4VX14nZM71jZ
Message-ID: <4DF885B5.4020202@gmx.de>
Date: Wed, 15 Jun 2011 12:13:09 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com>
In-Reply-To: <4DF87637.2000301@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Boris Zbarsky <bzbarsky@MIT.EDU>, draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 10:13:15 -0000

On 2011-06-15 11:07, Mykyta Yevstifeyev wrote:
> ...
>> 2) Section 6 says:
>>
>> For example, "about:blank", "about:blan%6B" and "about:blan%6b"
>> are equivalent
>>
>> In Gecko they are not. The string after ':' is treated as a literal
>> string; when looking up a way to handle the URI the second and third
>> URIs above are treated as unparseable by Gecko in its default
>> configuration. Changing this has some security implications that would
>> require careful auditing of not only Gecko code but some
>> specifications (e.g. HTML5 defines certain special-case security
>> behavior for about:blank that's not obviously safe to apply to the
>> other strings above).
>>
>> The same section says:
>>
>> Similarly, "about:blank%3F" is not equivalent to "about:blank?".
>>
>> which I think is trying to explain by example that only unreserved
>> characters need to be unescaped. But that assumes an implementation of
>> RFC 3986 which may or may not be the case in web browsers (and is NOT
>> the case in Gecko, for example, for various web-compatibility
>> reasons). Unless there are very strong reasons for it, I would
>> recommend that no normalization is performed on about: URIs, period.
> The point of this comment is to propose abandoning normalization of
> 'about' URIs because of some ad hoc behavior of an only application -
> Gecko. The purpose of our draft is to give a stable specification of the
> scheme and normalize all existing types of behavior with regard to
> handling 'about' URIs. It will be easier for Gecko to change its
> behavior rather than for other apps to do this.
> ...

I agree that not treating them as equivalent is a bug.

That being said, if our Mozilla friends do not want to fix this it might 
be a good idea to warn readers that certain implementations fail to 
properly unescape, thus it's unwise to rely on that behavior (why would 
you anyway?).

Best regards, Julian

From huitema@microsoft.com  Wed Jun 15 07:12:49 2011
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A21D69E8016 for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 07:12:49 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XBgIuk7Ym5Xx for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 07:12:49 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by ietfa.amsl.com (Postfix) with ESMTP id 09E0C9E8014 for <ietf@ietf.org>; Wed, 15 Jun 2011 07:12:49 -0700 (PDT)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 15 Jun 2011 07:12:48 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) with Microsoft SMTP Server (TLS) id 14.1.289.8; Wed, 15 Jun 2011 07:12:47 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.58]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi id 14.01.0289.008; Wed, 15 Jun 2011 07:12:47 -0700
From: Christian Huitema <huitema@microsoft.com>
To: Mark Andrews <marka@isc.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: RE: one data point regarding native IPv6 support
Thread-Topic: one data point regarding native IPv6 support
Thread-Index: AQHMKwK+4YfSG670iUCP1VAO4WifGZS9vDcDgAC3S9A=
Date: Wed, 15 Jun 2011 14:12:47 +0000
Message-ID: <22F6318E46E26B498ABC828879B08D4F16FF26@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <20110615022008.0816818C172@mercury.lcs.mit.edu> <20110615030130.3E2A810C7E48@drugs.dv.isc.org>
In-Reply-To: <20110615030130.3E2A810C7E48@drugs.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.43]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 14:12:49 -0000

>From Noel analysis, it seems that a lot of the issues could be mitigated by=
 a simple connectivity test. Have the 6to4 router perform a simple ping tes=
t through the tentative 6to4 relay, towards some well-known IPv6 host. Or a=
n HTTP test, if we fear that ICMPv6 might be somehow tampered with.  If the=
 test succeed, then it shows that the path to that 6to4 relay is clear of f=
irewalls and other obstructions. If the path is not clear, pick another 6to=
4 relay, or do not enable 6to4.

Of course, this does not solve the problem of intermittent failures on the =
IPv4 path to the relay, e.g. due to congestion.=20

It also does not solve the problem of routers advertising an IPv6 route to =
2002::/16 and then failing to deliver the IPv4 packets. But this "return" p=
roblem is easily solved by IPv6 ISP deploying their own 6to4 routers, and t=
hus avoiding dependencies on a "generic" path to 2002::/16.

-- Christian Huitema




From evnikita2@gmail.com  Wed Jun 15 08:05:06 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71A9311E814E for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 08:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.219
X-Spam-Level: 
X-Spam-Status: No, score=-3.219 tagged_above=-999 required=5 tests=[AWL=-0.220, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y+1adt1Q-MP2 for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 08:05:05 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5C36411E8119 for <ietf@ietf.org>; Wed, 15 Jun 2011 08:04:50 -0700 (PDT)
Received: by fxm15 with SMTP id 15so548315fxm.31 for <ietf@ietf.org>; Wed, 15 Jun 2011 08:04:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=cANRJD1i4BeSsERdS0QAYdzcjqldWgbUXCpx1ij4fFw=; b=vAIC44XPpaQg5HaBkCoXfEexfRrtNqbLKaDojTIjq90CVtJjSereLjb0IOf5Tlhxfx kUSuif5lXO3v6nQfK/UJrjN5BunkrhcFWY5c1BuA4sG4wXY/Kg2a1re/OPzifrYwRHES Cac0L6Arf6KNJYOsQ1hIMSAhg6TpGSmKR01Bw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Rh3DuEiBa5qyU3w/CwdTdTedRYni17Iip1L8eJ07mRfLV32OIdAJvbsZaZvjptQBtH cA/ykMNyCwSewq5c9dnap7ROXFxHuBvsXvS/wDEtN+zlVJ8g24VPZQ48q9dpYtZSUWw9 fAZA/43bK+dBtOKSa6Z1DwnAcsKV3dfBgVA3w=
Received: by 10.223.6.201 with SMTP id a9mr714539faa.110.1308150289439; Wed, 15 Jun 2011 08:04:49 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id o23sm271076faa.9.2011.06.15.08.04.47 (version=SSLv3 cipher=OTHER); Wed, 15 Jun 2011 08:04:48 -0700 (PDT)
Message-ID: <4DF8CA3D.7020904@gmail.com>
Date: Wed, 15 Jun 2011 18:05:33 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF885B5.4020202@gmx.de>
In-Reply-To: <4DF885B5.4020202@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Boris Zbarsky <bzbarsky@MIT.EDU>, draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 15:05:06 -0000

15.06.2011 13:13, Julian Reschke wrote:
> On 2011-06-15 11:07, Mykyta Yevstifeyev wrote:
>> ...
>>> 2) Section 6 says:
>>>
>>> For example, "about:blank", "about:blan%6B" and "about:blan%6b"
>>> are equivalent
>>>
>>> In Gecko they are not. The string after ':' is treated as a literal
>>> string; when looking up a way to handle the URI the second and third
>>> URIs above are treated as unparseable by Gecko in its default
>>> configuration. Changing this has some security implications that would
>>> require careful auditing of not only Gecko code but some
>>> specifications (e.g. HTML5 defines certain special-case security
>>> behavior for about:blank that's not obviously safe to apply to the
>>> other strings above).
>>>
>>> The same section says:
>>>
>>> Similarly, "about:blank%3F" is not equivalent to "about:blank?".
>>>
>>> which I think is trying to explain by example that only unreserved
>>> characters need to be unescaped. But that assumes an implementation of
>>> RFC 3986 which may or may not be the case in web browsers (and is NOT
>>> the case in Gecko, for example, for various web-compatibility
>>> reasons). Unless there are very strong reasons for it, I would
>>> recommend that no normalization is performed on about: URIs, period.
>> The point of this comment is to propose abandoning normalization of
>> 'about' URIs because of some ad hoc behavior of an only application -
>> Gecko. The purpose of our draft is to give a stable specification of the
>> scheme and normalize all existing types of behavior with regard to
>> handling 'about' URIs. It will be easier for Gecko to change its
>> behavior rather than for other apps to do this.
>> ...
>
> I agree that not treating them as equivalent is a bug.
>
> That being said, if our Mozilla friends do not want to fix this it 
> might be a good idea to warn readers that certain implementations fail 
> to properly unescape, thus it's unwise to rely on that behavior (why 
> would you anyway?).
I fully agree with you, Julian.  I think we'll do certainly as you 
propose, unless Boris will provide some strong reasons to do in other way.

Mykyta
>
> Best regards, Julian
>


From lorenzo@google.com  Tue Jun 14 11:00:24 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8703511E8135 for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JNWZMGTpLdJV for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 11:00:24 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id E945111E8123 for <ietf@ietf.org>; Tue, 14 Jun 2011 11:00:18 -0700 (PDT)
Received: from wpaz24.hot.corp.google.com (wpaz24.hot.corp.google.com [172.24.198.88]) by smtp-out.google.com with ESMTP id p5EI0ITx020208 for <ietf@ietf.org>; Tue, 14 Jun 2011 11:00:18 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1308074418; bh=624XQbmp+rGZhC7kAJ3OYO0Rhsg=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=O/td9IHNAwg12BIEBwgAiKpn966BLfS2T7rUmrsObbophHGkLhlCBs/mMKzYcI7lT 9WSFsSH4f1D+vz24asp6g==
Received: from ywe9 (ywe9.prod.google.com [10.192.5.9]) by wpaz24.hot.corp.google.com with ESMTP id p5EHsaDu009160 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Tue, 14 Jun 2011 11:00:07 -0700
Received: by ywe9 with SMTP id 9so2724130ywe.19 for <ietf@ietf.org>; Tue, 14 Jun 2011 11:00:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Oy88dhrYWuKFP8esGkFa0M0fc5jvOAhql2POw8H44D4=; b=bF5UvpIDgKzeHNjItkfzNvZJtkOCtBR6yObmUrnXivhJOqXszhEDUz/C0kJkji4b1w 0gF/2pdQI0LAYD8fvaxg==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=to4D+gc0TIhXxi3alDIWwuTy1dY4F4O7w/EHt1rxWMNXgzT6Fc+qYD7dAQBbHzxyT2 rM8cGI+D6AK3AW9iqBxw==
Received: by 10.150.195.18 with SMTP id s18mr7944004ybf.207.1308074407090; Tue, 14 Jun 2011 11:00:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.147.16 with HTTP; Tue, 14 Jun 2011 10:59:47 -0700 (PDT)
In-Reply-To: <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 14 Jun 2011 10:59:47 -0700
Message-ID: <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: james woodyatt <jhw@apple.com>
Content-Type: multipart/alternative; boundary=000e0cd4d83c5fda2704a5afce0e
X-System-Of-Record: true
X-Mailman-Approved-At: Wed, 15 Jun 2011 08:23:23 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 18:00:24 -0000

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

On Tue, Jun 14, 2011 at 10:30 AM, james woodyatt <jhw@apple.com> wrote:
>
> Very few of the people using 6to4 in this way will show up in Google's user
> behavior analysis, of course, because Google doesn't run its own 6to4
> return-path relay as I-D.ietf-v6ops-6to4-advisory recommends.
>

We would not see these users even if we operated reverse path relays as
recommended in the draft - from the point of view of the server, in both
cases it's just a TCP connection to a 2002::/16 address, regardless of
whether the relay is inside the Google network or outside it.

Those users would become visible if we added AAAA records with 6to4
addresses, but that's a bad plan because it would likely lead to the
double-digit connection failure rates that Geoff observes. It would also
become visible if Google operated an open anycast relay, which we do not
plan to do.


> The way to find these people is to crawl the BitTorrent networks.  What's
> that old maxim?  "You can't test what you don't measure."  Do you measure
> the BitTorrent networks?


No, we don't. The measurements we conduct have the purpose of determining
the impact of adding AAAA records to web sites, so we don't measure the
population of users that has 6to4 but does not use it to make HTTP
connections to dual-stack websites. We do measure the impact of 6to4 on the
reliability of websites indirectly, e.g., by observing the difference
between OSes that prefer IPv4 over 6to4 and OSes that don't.

Also, is there a way we can put this debate to rest using real data? What if
we asked someone like Hurricane Electric how much traffic on their network
is native IPv6 vs. 6to4?

That said, I would argue that most or all 6to4 traffic could just as well
use IPv4, since both parties to the communication obviously have access to a
public IPv4 address. What is the advantage of using 6to4 over IPv4 that
makes it worth suffering an 80% failure rate?

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

<div class=3D"gmail_quote">On Tue, Jun 14, 2011 at 10:30 AM, james woodyatt=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:jhw@apple.com">jhw@apple.com</a>&g=
t;</span> wrote:=A0<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">Very few of the people using 6to4 in this way will show u=
p in Google&#39;s user behavior analysis, of course, because Google doesn&#=
39;t run its own 6to4 return-path relay as I-D.ietf-v6ops-6to4-advisory rec=
ommends.</div>

</blockquote><div><br></div><div>We would not see these users even if we op=
erated reverse path relays as recommended in the draft - from the point of =
view of the server, in both cases it&#39;s just a TCP connection to a 2002:=
:/16 address, regardless of whether the relay is inside the Google network =
or outside it.</div>

<div><br></div><div><div>Those users would become visible if we added AAAA =
records with 6to4 addresses, but that&#39;s a bad plan because it would lik=
ely lead to the double-digit connection failure rates that Geoff observes. =
It would also become visible if Google operated=A0an open anycast relay, wh=
ich we do not plan to do.</div>

</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex;">The way to find these p=
eople is to crawl the BitTorrent networks. =A0What&#39;s that old maxim? =
=A0&quot;You can&#39;t test what you don&#39;t measure.&quot; =A0Do you mea=
sure the BitTorrent networks?</blockquote>

<div><br></div><div>No, we don&#39;t. The measurements we conduct have the =
purpose of determining the impact of adding AAAA records to web sites, so w=
e don&#39;t measure the population of users that has 6to4 but does not use =
it to make HTTP connections to dual-stack websites.=A0We do measure the imp=
act of 6to4 on the reliability of websites indirectly, e.g., by observing t=
he difference between OSes that prefer IPv4 over 6to4 and OSes that don&#39=
;t.</div>

<div><br></div><div><meta http-equiv=3D"content-type" content=3D"text/html;=
 charset=3Dutf-8">Also, is there a way we can put this debate to rest using=
 real data? What if we asked someone like Hurricane Electric how much traff=
ic on their network is native IPv6 vs. 6to4?</div>

<div><br></div><div>That said, I would argue that most or all 6to4 traffic =
could just as well use IPv4, since both parties to the communication obviou=
sly have access to a public IPv4 address. What is the advantage of using 6t=
o4 over IPv4 that makes it worth suffering an 80% failure rate?</div>

</div>

--000e0cd4d83c5fda2704a5afce0e--

From violeta.cakulev@alcatel-lucent.com  Tue Jun 14 11:41:51 2011
Return-Path: <violeta.cakulev@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE1F811E80CE; Tue, 14 Jun 2011 11:41:51 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NMNf8+JOuY3d; Tue, 14 Jun 2011 11:41:50 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 9F49D11E8072; Tue, 14 Jun 2011 11:41:50 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p5EIfn6n018254 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 14 Jun 2011 13:41:49 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p5EIfmV5019498 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 14 Jun 2011 13:41:48 -0500
Received: from USNAVSXCHMBSA3.ndc.alcatel-lucent.com ([135.3.39.126]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Tue, 14 Jun 2011 13:41:48 -0500
From: "Cakulev, Violeta (Violeta)" <violeta.cakulev@alcatel-lucent.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Date: Tue, 14 Jun 2011 13:41:35 -0500
Subject: RE: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
Thread-Topic: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt> (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server Interaction) to Proposed Standard
Thread-Index: AcwiLU6FhyJ9Tdc6S5CFRmbevpIxTwIlHqyQ
Message-ID: <AAE76B481E7A0E4C96610790A852B9A6250A4F815C@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
References: <20110520135022.1622.22713.idtracker@ietfa.amsl.com> <4DD9581C.3070900@gmail.com> <AAE76B481E7A0E4C96610790A852B9A625099F98E2@USNAVSXCHMBSA3.ndc.alcatel-lucent.com> <4DE944C1.5020608@gmail.com>
In-Reply-To: <4DE944C1.5020608@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
X-Mailman-Approved-At: Wed, 15 Jun 2011 08:23:23 -0700
Cc: IPsecme WG <ipsec@ietf.org>, "draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter@tools.ietf.org>, "dime@ietf.org" <dime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 18:41:52 -0000

Hi Yaron,
Thanks for the suggestions.
Please see inline.

-Violeta

-----Original Message-----
From: Yaron Sheffer [mailto:yaronf.ietf@gmail.com]
Sent: Friday, June 03, 2011 4:32 PM
To: Cakulev, Violeta (Violeta)
Cc: ietf@ietf.org; IPsecme WG; dime@ietf.org; draft-ietf-dime-ikev2-psk-dia=
meter@tools.ietf.org
Subject: Re: [IPsec] Last Call: <draft-ietf-dime-ikev2-psk-diameter-06.txt>=
 (Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server to D=
iameter Server Interaction) to Proposed Standard

Hi Violeta,

thanks for your response.

I understand now where you're coming from. But the next person to read the =
document might not have the authors so readily available :-) Implementors n=
eed to understand the motivation for this solution as well as the missing p=
ieces.
[VC] And the next person indeed had the same concern. Therefore, in v8 we m=
ade the changes as proposed below.


So I would suggest that you add:
- A short paragraph in the Introduction putting this document in perspectiv=
e and referencing (non-normative references of course) the
3GGP2 documents.
- Another paragraph in the Security Considerations that says that generatio=
n/derivation of the PSK is security-critical, and provides the
3GPP2 docs again as an example of a solution to this problem.
[VC] Please see v8. We added statements both in Introduction and Security C=
onsiderations as proposed above.

Regarding usage of the SPI, the document says: "Upon receiving the IKE_AUTH=
 message from the IKEv2 Peer, the IKEv2 Server uses the information receive=
d in IDi *and the SPI* if available, to determine if it has the PSK for thi=
s IKEv2 Peer."This sounds to me as if the SPI is used as part of the PSK lo=
okup operation. Maybe the SPI should not be mentioned in the above text.
[VC] We modified this paragraph in v8. Please see v8.

Best regards,

     Yaron

On 06/01/2011 11:04 PM, Cakulev, Violeta (Violeta) wrote:
> Hi Yaron,
> Thanks for the comments.
> Please see inline [VC].
>
> -Violeta
>
> -----Original Message-----
> From: ipsec-bounces@ietf.org [mailto:ipsec-bounces@ietf.org] On Behalf
> Of Yaron Sheffer
> Sent: Sunday, May 22, 2011 2:38 PM
> To: ietf@ietf.org
> Cc: IPsecme WG; draft-ietf-dime-ikev2-psk-diameter@tools.ietf.og;
> dime@ietf.org
> Subject: Re: [IPsec] Last
> Call:<draft-ietf-dime-ikev2-psk-diameter-06.txt>  (Diameter IKEv2 PSK:
> Pre-Shared Secret-based Support for IKEv2 Server to Diameter Server
> Interaction) to Proposed Standard
>
> Hi,
>
> Having read this document only now, I think there's a number of serious i=
ssues with it. This document was sent to the ipsec mailing list a while ago=
 but unfortunately got no review.
>
> Summary:
> 1. I think the wrong architectural choice was made, in preferring PSK ove=
r EAP authentication.
> 2. There is not enough detail in the document to result in interoperable =
implementations.
> [VC] Please see responses to detailed comments.
>
> Detailed comments:
> * The appropriate ref for IKEv2 is RFC 5996. This was actually noted in t=
he shepherd review back in March.
> [VC] This is fixed in v7.
>
>
> * The document notes that EAP is one of the authentication modes supporte=
d by IKEv2. EAP is designed for interaction with backend AAA servers, and i=
s quite capable of performing shared-secret authentication, using a variety=
 of EAP methods (and see also RFC 5998, on IKEv2 mutual auth with EAP). Yet=
 the document does not explain why EAP is not used, instead preferring the =
IKE PSK authentication method.
> [VC] Diameter application for Diameter client to server communication for=
 IKEv2 with EAP has been specified in RFC 5778. However, there is no Diamet=
er application specified for IKE PSK authentication method. This is stated =
in the draft both in Abstract and Introduction. The draft does not recommen=
d one or the other, it is simply specifying what is not specified. It is up=
 to a specific use case to decide what to use. For example 3GPP2 decided to=
 use IKEv2 PSK (in 2 of its specifications), and that is what triggered thi=
s effort in IETF.
>
>
> * 4.1: how can the incoming SPI be used to identify the peer?
> [VC] As stated in Section 4.1 IDi payload is extracted from the IKE_AUTH =
message and this payload 'MUST contain an identity that is meaningful
>     for the Diameter infrastructure, such as a Network Access Identifier =
(NAI), since it is used by the IKEv2 Server to populate the User-Name
>     AVP in the Diameter message'. SPI is not used to identify the peer.
>
>
> * Packing additional semantics into SPI may conflict with elements of the=
 IPsec architecture (see for example Sec. 9.3 of draft-ietf-ipsecme-failure=
-detection-08).
> [VC] Agreed.
>
>
> * 4.1, 2nd paragraph: generation of the PSK is central to this solution, =
so it cannot be "outside the scope" of the document. There is no way to int=
eroperate otherwise.
> [VC] This draft focuses on IKEv2 server, as a Diameter client, to the Dia=
meter server communication for IKEv2 with pre-
>     shared secret based authentication, and specifies Diameter applicatio=
n for this communication. It is left to specifications that make use of thi=
s Diameter application to specify where the PSK comes from and how it is ge=
nerated. As mentioned above, there are two 3GPP2 specs that make use of thi=
s Diameter application and both of those specs specify generation of the PS=
K.
>
>
> * Moreover, if a single client is expected to sometimes use EAP and somet=
imes PSK, there must be a way to notify it which one to use.
> [VC] This is not the assumption. Again this draft specifies Diameter appl=
ication for Diameter client to the Diameter server communication for IKEv2 =
with PSK. IKEv2 server knows whether EAP or PSK is used.
>
>
> * How does key-lifetime relate to the lifetime of the IKE SA?
> [VC] This should be the same as in RFC 5996, how pre-shared secret lifeti=
me relates to the lifetime of the IKE SA. This draft should not make any ch=
anges.
>
>
> * Sec. 10 refers to the PSK as a "session key" which is incorrect, as PSK=
 is only used for authentication and does not encrypt anything.
> [VC] Good point. It is changed to PSK in v7.
>
>
> * The same paragraph is very vague about the security properties of PSK.
> RFC 5996 takes PSK much more seriously, e.g. "When using pre-shared keys,=
 a critical consideration is how to assure the randomness of these secrets.=
" Again, I believe the document should specify how the PSK is derived.
> [VC] I absolutely agree that derivation of PSK is critical. However, as s=
tated above, this draft specifies Diameter application only. Therefore, sec=
urity consideration section cannot include much more details on derivation =
of PSK as it is specified elsewhere.
>
>
> * Why "if nonces are included" where the document says that they *must* b=
e included (in the AVP occurrence table).
> [VC] Good point. This is removed in v7.
>
>
> Thanks,
> Yaron
>
> On 05/20/2011 04:50 PM, The IESG wrote:
>> The IESG has received a request from the Diameter Maintenance and
>> Extensions WG (dime) to consider the following document:
>> - 'Diameter IKEv2 PSK: Pre-Shared Secret-based Support for IKEv2 Server
>>      to Diameter Server Interaction'
>>     <draft-ietf-dime-ikev2-psk-diameter-06.txt>   as a 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 2011-06-03. 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 Internet Key Exchange protocol version 2 (IKEv2) is a component
>>      of the IPsec architecture and is used to perform mutual
>>      authentication as well as to establish and to maintain IPsec securi=
ty
>>      associations (SAs) between the respective parties.  IKEv2 supports
>>      several different authentication mechanisms, such as the Extensible
>>      Authentication Protocol (EAP), certificates, and pre-shared secrets=
.
>>
>>      With [RFC5778] the Diameter interworking for Mobile IPv6 between th=
e
>>      Home Agent, as a Diameter client, and the Diameter server has been
>>      specified.  However, that specification focused on the usage of EAP
>>      and did not include support for pre-shared secret based
>>      authentication available with IKEv2.  This document specifies IKEv2
>>      server, as a Diameter client, to the Diameter server communication
>>      for IKEv2 with pre-shared secret based authentication.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-dime-ikev2-psk-diameter/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec

From violeta.cakulev@alcatel-lucent.com  Tue Jun 14 12:11:20 2011
Return-Path: <violeta.cakulev@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BED811E80D3; Tue, 14 Jun 2011 12:11:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.449
X-Spam-Level: 
X-Spam-Status: No, score=-5.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tGs9JUJYGz+j; Tue, 14 Jun 2011 12:11:19 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id E97C61F0C38; Tue, 14 Jun 2011 12:11:18 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p5EJBG9S008898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 14 Jun 2011 14:11:16 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p5EJB98T014009 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 14 Jun 2011 14:11:16 -0500
Received: from USNAVSXCHMBSA3.ndc.alcatel-lucent.com ([135.3.39.126]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Tue, 14 Jun 2011 14:11:09 -0500
From: "Cakulev, Violeta (Violeta)" <violeta.cakulev@alcatel-lucent.com>
To: Ben Campbell <ben@nostrum.com>, "draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Date: Tue, 14 Jun 2011 14:11:08 -0500
Subject: RE: Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
Thread-Topic: Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
Thread-Index: AcwiKj7iku9VGVqtSm+aoaC5QK0s2QImgLkw
Message-ID: <AAE76B481E7A0E4C96610790A852B9A6250A4F81A5@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
References: <5E434E92-2EB7-43B3-A29F-8410B1AC23AE@nostrum.com>
In-Reply-To: <5E434E92-2EB7-43B3-A29F-8410B1AC23AE@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
X-Mailman-Approved-At: Wed, 15 Jun 2011 08:23:23 -0700
Cc: The 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, 14 Jun 2011 19:11:20 -0000

Ben,
Thanks for the comments.
Please see inline [VC].

-Violeta

-----Original Message-----
From: Ben Campbell [mailto:ben@nostrum.com]
Sent: Friday, June 03, 2011 4:10 PM
To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org; gen-art@ietf.org=
 Review Team
Cc: The IETF
Subject: Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07

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-dime-ikev2-psk-diameter-07
Reviewer: Ben Campbell
Review Date: 2011-06-03
IETF LC End Date: 2011-06-03


Summary:

This draft is almost ready for publication as a proposed standard. I have a=
 question concerning the procedure for generating PSKs, and a number of min=
or and editorial comments.


Major issues:

The draft says that the procedure that the HAAA follows to generate the PSK=
 is out of scope. But doesn't the IKE2 initiator need to understand the pro=
cedure? If the procedure is not defined somewhere, how you achieve any degr=
ee of interoperability?
[VC] Indeed the IKEv2 initiator needs to understand the procedure. However,=
 this draft focuses on IKEv2 server, as a Diameter client, to the Diameter =
server communication for IKEv2 with pre-shared key based authentication, an=
d specifies Diameter application for this communication. It is left to spec=
ifications that make use of this Diameter application to specify where the =
PSK comes from and how it is generated. There are two 3GPP2 specs that make=
 use of this Diameter application and both of those specs specify generatio=
n of the PSK. Statements to clarify this are added in v8.


Minor issues:

-- section 4.1, 1st paragraph:"The IDi payload extracted from the IKE_AUTH =
message MUST contain an identity that is meaningful for the Diameter infras=
tructure, such as a Network Access Identifier (NAI), since it is used by th=
e IKEv2 Server to populate the User-Name AVP in the Diameter message. "

Do you mean that as a normative MUST, or a statement of fact? If normative,=
 isn't that a requirement on the initiator?
[VC] Good point. It is changed to statement of fact in v8.

-- section 10:

The security considerations should describe the threat models. We're talkin=
g about requesting an authentication key from a third party, which is trick=
y from a security perspective. Does the PSK have greater security concerns =
than for Diameter AVPs in general? In particular, what are the consequences=
 if the PSK is disclosed or tampered with?
[VC] If the PSK is disclosed to an adversary then it would present a securi=
ty breach.  Hence we recommend that the PSK be short-lived.  As well,
the assumption is that the IKEv2 Server and the Diameter Server where the P=
SK is generated are in a trusted relationship. They may be in the same Admi=
nistrative domain (typical case) or third party but nevertheless there is a=
 trust relationship between them.  As such we assume that there is an appro=
priate security mechanism to protect the communication between these server=
s.  For example the IKEV2 Server and the Diameter server would be deployed =
in the same secure network or would utilize transport layer security as spe=
cified by Diameter 3588 specification. We added statements in v8 to reflect=
 this.

-- section 10, 1st paragraph: "Furthermore, any agents that process IKEv2-P=
SK-Answer messages can see the contents of the Key AVP. For this reason, th=
is specification strongly recommends avoiding Diameter agents when they can=
not be trusted to keep the keys secret."

Should that be normative? Is there no way to protect the PSK AVP from diame=
ter agents? E.g. can it be encrypted?
[VC] It is hard to use normative text here as this application can be used =
for many uses cases. Depending on the use case it may be possible to encryp=
t the PSK, however it is not possible to make it a requirement.

-- section 10, 2nd paragraph: "this specification also recommends the use o=
f nonces included in IKEv2-PSK-Request."

Actually, the spec requires it using a normative SHALL.
[VC] In v8 it is aligned as 'recommended' throughout the document.


Nits/editorial comments:

-- IDNits reports an out-of-date reference
[VC] I missed this one in v8. This will be fixed in v9.

-- Section 1, general:

It's probably worth elaborating that we are talking about a PSK used during=
 the IKEv2 authentication process, which is distinct from any shared secret=
s negotiated by IKE for use in the resulting SA.
[VC] In v8 there are statements clarifying that it is a PSK used for IKEv2 =
authentication.


-- Section 1, paragraph 1, 1st sentence:

The use, and lack of, commas in this sentence is confusing. It's easy to pa=
rse as saying IKE2 is a protocol and a set of algorithms, when I think you =
meant to say that the resulting SA has a set of algorithms along with the s=
hared secret.
[VC] Changed in v8 to 'The Internet Key Exchange version 2 (IKEv2) protocol=
 [RFC5996] is
   used to mutually authenticate two parities and to establish a
   security association (SA) that can be used to efficiently secure the
   communication between the IKEv2 Peer and Server, for example, using
   Encapsulating Security Payload (ESP) [RFC4303] and/or Authentication
   Header (AH) [RFC4302].'

-- section 4.1, 2nd paragraph: "message is routed to the IKEv2 Peer's HAAA.=
"

What routes it? ( be careful not to let passive voice obscure responsibilit=
ies)
[VC] Changed in v8 to 'The IKEv2 Server sends the IKEv2-PSK-Request message=
 to the IKEv2
   Peer's HAAA.'

-- section 4.2, paragraph 1: "The HAAA may maintain state or may be statele=
ss"

What kind of state? I assume from the following sentences you mean Diameter=
 session state, but it should be explicit.
[VC] Changed in v8 to 'The HAAA may maintain Diameter session state or may =
be stateless.'

-- "indicated by presence or absence of the Auth-Session-State AVP."

In what message(s)?
[VC] This is clarified by adding that it is the Answer message.

-- section 4.2, paragraph 2:

This sentence is long and hard to parse. Can it be broken up?
[VC] Based on some other comments this sentence is removed.

-- section 5.1, last paragraph: "SHALL be used to identify the appropriate =
PSK."

Shall be used by what? (passive voice obscures responsibility)
[VC] Changed in v8 to 'If
   included, it contains the Security Parameter Index (SPI) that HAAA
   SHALL use to identify the appropriate PSK.'

-- 5.2, last paragraph: "associated key SHALL NOT be used if the lifetime h=
as expired."

SHALL NOT be used by what?
[VC] In v8 changed to: 'The Key-Lifetime AVP may be
   included and if it is included then the associated key SHALL NOT be
   used by the receiver of the answer if the lifetime has expired.'

-- section 8, first paragraph: "whether the AVP MAY be encrypted."

I don't see anything about encryption in the table.
[VC] The text referring to encryption is deleted.

-- section 8, AVP table:

Are all the Key* AVPs intended to have the same code? I assume not, but mix=
ing in TBD with the various TBD* placeholders is confusing.
[VC] These AVPs are being defined in another ietf draft that has not been p=
ublished yet. There is Note 1 clarifying it.


-- section 9:

Consider a note to the RFC editor to change all occurances of TBD(x) with t=
he IANA assignment throughout the entire document. Since these are scattere=
d throughout the doc, the intent may not be obvious to them.
[VC] We will do that.


From ek@google.com  Tue Jun 14 16:05:38 2011
Return-Path: <ek@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F305411E807D for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 16:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.977
X-Spam-Level: 
X-Spam-Status: No, score=-105.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0E24Eh8DfWnM for <ietf@ietfa.amsl.com>; Tue, 14 Jun 2011 16:05:38 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 36C2A11E8078 for <ietf@ietf.org>; Tue, 14 Jun 2011 16:05:37 -0700 (PDT)
Received: from hpaq3.eem.corp.google.com (hpaq3.eem.corp.google.com [172.25.149.3]) by smtp-out.google.com with ESMTP id p5EN5aAK004711 for <ietf@ietf.org>; Tue, 14 Jun 2011 16:05:36 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1308092737; bh=Zci261TLzJzDk7BA7J2e0ff/xlw=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=CfH9quxiiKmYi8IhW1EX9hekgXxfIwOy9S5OnRabTJ1Wm0jYBEBuex1xkrErb8B9B Q2cdUakZRuvMg/rbB0ydQ==
Received: from pzk36 (pzk36.prod.google.com [10.243.19.164]) by hpaq3.eem.corp.google.com with ESMTP id p5EN5YHY006311 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Tue, 14 Jun 2011 16:05:35 -0700
Received: by pzk36 with SMTP id 36so3056256pzk.20 for <ietf@ietf.org>; Tue, 14 Jun 2011 16:05:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=P95cOrBJVFmX46mwyEqA8GSsbZDKIKVjch5mFVeRpuI=; b=wJlFiq3UUndKi/5TqgBKDouXr2YIg9WjN/kQVFEaiHCpQ2vtx9tHFpENFg1E2ctGDQ 3zqaoGiUCIvYrJuPv4gA==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=arPlbChVFYAAUNfWW/qNk1Sysci4MfVMc07aQJROycSZVDPbna2ZTNKKGLxzxCfHXR 0gc19eDg1vcze6oztIWA==
MIME-Version: 1.0
Received: by 10.142.142.13 with SMTP id p13mr1324744wfd.324.1308092733863; Tue, 14 Jun 2011 16:05:33 -0700 (PDT)
Received: by 10.143.37.8 with HTTP; Tue, 14 Jun 2011 16:05:33 -0700 (PDT)
In-Reply-To: <20110615081050.70c9112a@opy.nosense.org>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com> <20110615081050.70c9112a@opy.nosense.org>
Date: Tue, 14 Jun 2011 16:05:33 -0700
Message-ID: <BANLkTikXmQRqK1NzeXg2B7-S2sShQH5DWjpXcwBas8VE+idXKA@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
From: Erik Kline <ek@google.com>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Content-Type: text/plain; charset=UTF-8
X-System-Of-Record: true
X-Mailman-Approved-At: Wed, 15 Jun 2011 08:23:23 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>, Lorenzo Colitti <lorenzo@google.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 Jun 2011 23:05:39 -0000

The youtube folks made the decision to leave the video-serving
hostnames available in blacklist-mode, meaning only very broken
networks won't get AAAAs.

This is being watched, and could easily change back.  The exact policy
for blacklisting has yet to be fully formalized.

But re: 6to4 in this case, it still gains you nothing you didn't
already have while risking randomly crappy performance.

From ipng@69706e6720323030352d30312d31340a.nosense.org  Tue Jun 14 15:41:00 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.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 6F5B91F0C8A; Tue, 14 Jun 2011 15:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.745
X-Spam-Level: 
X-Spam-Status: No, score=-1.745 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vwEIL-MldIna; Tue, 14 Jun 2011 15:40:59 -0700 (PDT)
Received: from smtp4.adam.net.au (smtp4.adam.net.au [202.136.110.247]) by ietfa.amsl.com (Postfix) with ESMTP id 8D2281F0C88; Tue, 14 Jun 2011 15:40:59 -0700 (PDT)
Received: from 219-90-147-167.ip.adam.com.au ([219.90.147.167] helo=opy.nosense.org) by smtp4.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1QWcI1-0005wD-7u; Wed, 15 Jun 2011 08:10:53 +0930
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 63D963B33E; Wed, 15 Jun 2011 08:10:51 +0930 (CST)
Date: Wed, 15 Jun 2011 08:10:50 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Message-ID: <20110615081050.70c9112a@opy.nosense.org>
In-Reply-To: <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.4; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 15 Jun 2011 08:24:04 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2011 22:41:00 -0000

On Tue, 14 Jun 2011 10:59:47 -0700
Lorenzo Colitti <lorenzo@google.com> wrote:

> On Tue, Jun 14, 2011 at 10:30 AM, james woodyatt <jhw@apple.com> wrote:
> >
> > Very few of the people using 6to4 in this way will show up in Google's user
> > behavior analysis, of course, because Google doesn't run its own 6to4
> > return-path relay as I-D.ietf-v6ops-6to4-advisory recommends.
> >
> 
> We would not see these users even if we operated reverse path relays as
> recommended in the draft - from the point of view of the server, in both
> cases it's just a TCP connection to a 2002::/16 address, regardless of
> whether the relay is inside the Google network or outside it.
> 
> Those users would become visible if we added AAAA records with 6to4
> addresses, but that's a bad plan because it would likely lead to the
> double-digit connection failure rates that Geoff observes. It would also
> become visible if Google operated an open anycast relay, which we do not
> plan to do.
> 

I don't know if it is intentional, however if I use Google's public
8.8.8.8 and 8.8.4.4 resolvers, and prefer 6to4 over native IPv4
(via /etc/gai.conf under Linux/glibc), it seems that the video content
of all youtube videos is now being delivered over IPv6. The same thing
happens if I use my ISP's resolvers - I know they're doing IPv6 work
behind the scenes, however I don't know but dont think their
resolvers are Google whitelisted. That suggests that if there are hosts
out there that blindly prefer tunnelled IPv6 over native IPv4, and
have 6to4 available, there is a likelyhood that more people are using
6to4 now than there was before World IPv6 day.

I'm having no performance problems at all with any videos I
select, including 1080P ones.


> 
> > The way to find these people is to crawl the BitTorrent networks.  What's
> > that old maxim?  "You can't test what you don't measure."  Do you measure
> > the BitTorrent networks?
> 
> 
> No, we don't. The measurements we conduct have the purpose of determining
> the impact of adding AAAA records to web sites, so we don't measure the
> population of users that has 6to4 but does not use it to make HTTP
> connections to dual-stack websites. We do measure the impact of 6to4 on the
> reliability of websites indirectly, e.g., by observing the difference
> between OSes that prefer IPv4 over 6to4 and OSes that don't.
> 
> Also, is there a way we can put this debate to rest using real data? What if
> we asked someone like Hurricane Electric how much traffic on their network
> is native IPv6 vs. 6to4?
> 
> That said, I would argue that most or all 6to4 traffic could just as well
> use IPv4, since both parties to the communication obviously have access to a
> public IPv4 address. What is the advantage of using 6to4 over IPv4 that
> makes it worth suffering an 80% failure rate?

I'm having and have been having 100% success rate (or near enough to it
that I can remember) using 6to4 for a number of years, including with
an IPv6 MTU of as large as my PPPoE connection will support i.e. my
6to4 tunnel has an IPv6 MTU of 1472. Since noticing that youtube videos
are coming over IPv6, I've paid a bit more attention to the "quality of
experience" I've had, and have not found any reasons to change my
preference back to native IPv4 instead of 6to4.

From ipng@69706e6720323030352d30312d31340a.nosense.org  Tue Jun 14 16:30:08 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.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 A558311E80DF; Tue, 14 Jun 2011 16:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.795
X-Spam-Level: 
X-Spam-Status: No, score=-1.795 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rGdjY5zez5wf; Tue, 14 Jun 2011 16:30:05 -0700 (PDT)
Received: from smtp4.adam.net.au (smtp4.adam.net.au [202.136.110.247]) by ietfa.amsl.com (Postfix) with ESMTP id B015111E80A8; Tue, 14 Jun 2011 16:30:05 -0700 (PDT)
Received: from 219-90-147-167.ip.adam.com.au ([219.90.147.167] helo=opy.nosense.org) by smtp4.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1QWd3b-0008Ju-QV; Wed, 15 Jun 2011 09:00:03 +0930
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 9DE343B33E; Wed, 15 Jun 2011 09:00:02 +0930 (CST)
Date: Wed, 15 Jun 2011 09:00:02 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Erik Kline <ek@google.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Message-ID: <20110615090002.066f3219@opy.nosense.org>
In-Reply-To: <BANLkTikXmQRqK1NzeXg2B7-S2sShQH5DWjpXcwBas8VE+idXKA@mail.gmail.com>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com> <20110615081050.70c9112a@opy.nosense.org> <BANLkTikXmQRqK1NzeXg2B7-S2sShQH5DWjpXcwBas8VE+idXKA@mail.gmail.com>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.4; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 15 Jun 2011 08:24:53 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>, Lorenzo Colitti <lorenzo@google.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 Jun 2011 23:30:08 -0000

On Tue, 14 Jun 2011 16:05:33 -0700
Erik Kline <ek@google.com> wrote:

> The youtube folks made the decision to leave the video-serving
> hostnames available in blacklist-mode, meaning only very broken
> networks won't get AAAAs.
> 
> This is being watched, and could easily change back.  The exact policy
> for blacklisting has yet to be fully formalized.
> 
> But re: 6to4 in this case, it still gains you nothing you didn't
> already have while risking randomly crappy performance.

A less used content cache could give me better performance. Not that it
has happened recently, however in the past there have been IPv4
delivered performance issues with youtube here in .au. That's the
reason I've paid a bit more attention to the quality of IPv6 delivery
and tried 1080P videos when they've been available.

Regards,
Mark.

From rdroms.ietf@gmail.com  Wed Jun 15 09:03:33 2011
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 1EF9E11E811F for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 09:03:33 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G5T6TQYFD67N for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 09:03:32 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id BE8FC11E8081 for <ietf@ietf.org>; Wed, 15 Jun 2011 09:03:28 -0700 (PDT)
Received: by iyn15 with SMTP id 15so552771iyn.31 for <ietf@ietf.org>; Wed, 15 Jun 2011 09:03:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=EhOuay5Ra1HcmXZ3JBdDkCPygGcAELvp2nwqcj3XLt8=; b=AJU4pKA4wsAEufapB0EgSZDZf9KT8ukbZDNpXovh7eCT1d84kz+euAVfiV38Qg6+vg Zp8Er3DOGexlts4DEmStG+IBOUEo5Z29fucQ6GaK53NhfzVDdxkRbcjnzvlL8g3IZ2cd 7igaMh0gJ4N38yVwFaTxaSG1DjRJ8P6DOBwuU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=vl6tQspHeGTAvrcEBZjESN+dp1ITECr4vhFpWcRhuv71NdjBkJNtUNt9PhroDZ/qve xp+hau4VJTAAaYOOHIJkQ2ozlmTM4dnDPe6xEJDvJDi6bDwNQh9/0J0pW9oTzD8Ub2dU NtmTFr5lzQfRi60pry1byfrmbJ3WzjSuF3S4c=
Received: by 10.231.31.129 with SMTP id y1mr545515ibc.138.1308153808003; Wed, 15 Jun 2011 09:03:28 -0700 (PDT)
Received: from [10.21.108.1] (128-107-239-233.cisco.com [128.107.239.233]) by mx.google.com with ESMTPS id v15sm290628ibh.62.2011.06.15.09.02.59 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 15 Jun 2011 09:03:26 -0700 (PDT)
Subject: Re: Liaison and request for review of ITU-T document
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <4DF2906F.9000607@gmail.com>
Date: Wed, 15 Jun 2011 17:02:15 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7DA8CDDE-F5BE-45D5-BEDC-56003429EE09@gmail.com>
References: <666AC2E8-ECF9-4C64-98B3-839315ED56C3@gmail.com> <4DF2906F.9000607@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
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 Jun 2011 16:03:33 -0000

Brian - thanks for your review and comments.

- Ralph

On Jun 10, 2011, at 10:45 PM 6/10/11, Brian E Carpenter wrote:

> Ralph,
>=20
> As far as I can tell this seems to describe some sort of a Layer 2 =
stateful
> per-flow QoS mechanism using new Ethertype headers. As such I don't =
see why
> the IETF would care. The point of it escapes me, since we have plenty =
of reason
> to believe that such solutions are impractical and do not scale, but =
that doesn't
> seem like our problem.
>=20
> I only looked at this to check if it impacted current work in 6MAN on
> the IPv6 Flow Label, and there doesn't appear to be any impact or =
relevance.
>=20
> Regards
>   Brian Carpenter
>=20
> On 2011-06-08 08:27, Ralph Droms wrote:
>> The IETF has recently received a liaison from ITU-T Q5/SG-11 =
regarding a Draft Recommendation.  That liaison is available as =
https://datatracker.ietf.org/liaison/1054/.  The official liaison is =
available at =
https://datatracker.ietf.org/documents/LIAISON/file1232.pdf.
>>=20
>> The liaison asks for IETF review of Draft Recommendation "Signalling =
protocols and procedures relating to Flow State Aware QoS control in a =
bounded sub-network of a NGN", which is available at =
https://datatracker.ietf.org/documents/LIAISON/file1231.pdf.  This note =
opens an IETF comment period on the document, ending midnight, anywhere =
on earth, 2011/7/5.  After the comment period, a summary will be =
prepared and returned in a liaison to ITU-T Q5/SG-11.
>>=20
>> Of specific interest to the IETF are any ways in which the =
"signalling protocols and procedures" defined in the Draft =
Recommendation might interact with existing IETF Internet protocols.  We =
are especially interested in potential adverse interactions or =
interference with IETF Internet protocols.  The technical merits of the =
"signalling protocols and procedures" defined in the Draft =
Recommendation are of interest inasmuch as the IETF community might =
provide technical advice and recommendations to improve the Draft =
Recommendation itself.
>>=20
>> Please respond with any comments on the Draft Recommendation to =
ietf@ietf.org.  Thanks in advance for your review of the Draft =
Recommendation.
>>=20
>> - Ralph Droms, Internet Area Director
>>  for the IESG
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>=20


From avi@bridgewatersystems.com  Wed Jun 15 11:00:06 2011
Return-Path: <avi@bridgewatersystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63F6911E8089; Wed, 15 Jun 2011 11:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level: 
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sf6+x4fysW7G; Wed, 15 Jun 2011 11:00:05 -0700 (PDT)
Received: from mail51.messagelabs.com (mail51.messagelabs.com [216.82.241.99]) by ietfa.amsl.com (Postfix) with ESMTP id BC33B11E8081; Wed, 15 Jun 2011 11:00:04 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: avi@bridgewatersystems.com
X-Msg-Ref: server-4.tower-51.messagelabs.com!1308160803!54325837!1
X-StarScan-Version: 6.2.17; banners=-,-,-
X-Originating-IP: [72.35.6.119]
Received: (qmail 32580 invoked from network); 15 Jun 2011 18:00:03 -0000
Received: from mail.bridgewatersystems.com (HELO webmail.bridgewatersystems.com) (72.35.6.119) by server-4.tower-51.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jun 2011 18:00:03 -0000
Received: from m679t05.fpmis.bridgewatersys.com ([10.52.81.148]) by m679t01.fpmis.bridgewatersys.com ([10.52.81.144]) with mapi; Wed, 15 Jun 2011 14:00:01 -0400
From: Avi Lior <avi@bridgewatersystems.com>
To: Ben Campbell <ben@nostrum.com>, "Cakulev, Violeta (Violeta)" <violeta.cakulev@alcatel-lucent.com>
Date: Wed, 15 Jun 2011 14:00:00 -0400
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
Thread-Topic: [Gen-art] Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
Thread-Index: AcwrhgvFOik9rUJmTxibBzvGi52JYQ==
Message-ID: <CA1E6771.1A314%avi@bridgewatersystems.com>
In-Reply-To: <4A6A10F5-5C34-494A-B922-EAB9DDE73551@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.12.0.110505
acceptlanguage: en-US
x-exclaimer-md-config: f069778a-5a3c-4a57-aa01-0f5f3f2623e3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The 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 Jun 2011 18:00:06 -0000

Hi Ben,

Please see inline...

-- Avi Lior
--Bridgewater Systems



>>eview Date: 2011-06-03
>> IETF LC End Date: 2011-06-03
>>=20
>>=20
>> Summary:
>>=20
>> This draft is almost ready for publication as a proposed standard. I
>>have a question concerning the procedure for generating PSKs, and a
>>number of minor and editorial comments.
>>=20
>>=20
>> Major issues:
>>=20
>> The draft says that the procedure that the HAAA follows to generate the
>>PSK is out of scope. But doesn't the IKE2 initiator need to understand
>>the procedure? If the procedure is not defined somewhere, how you
>>achieve any degree of interoperability?
>> [VC] Indeed the IKEv2 initiator needs to understand the procedure.
>>However, this draft focuses on IKEv2 server, as a Diameter client, to
>>the Diameter server communication for IKEv2 with pre-shared key based
>>authentication, and specifies Diameter application for this
>>communication. It is left to specifications that make use of this
>>Diameter application to specify where the PSK comes from and how it is
>>generated. There are two 3GPP2 specs that make use of this Diameter
>>application and both of those specs specify generation of the PSK.
>>Statements to clarify this are added in v8.
>
>The effect of this is that this spec, as written, cannot be implemented
>in an interoperable way. I don't think that meets the usual expectations
>for a proposed standard. Now, I realize there are some situations where
>the IETF has chosen this approach, and deliberately created a standards
>track RFC that must be profiled for actual use--but hopefully that's the
>exception rather than the rule.  I guess it's up to the IESG to decide if
>that is reasonable in this instance. (I'm explicitly not counting
>situations where the IETF puts out a standard as a series of modular
>RFCs, since I gather there's no immediate intent to publish PSK
>generation RFCs.)
>
>Additionally, whether or not PSK generation mechanisms are specified in
>the IETF vs somewhere else, how does an implementation (that might
>support more than one such mechanism) know which to use for any given SA?
>Is there a negotiation mechanism?

I agree with your comments in general. What we need to keep in mind though
is the intent of this draft, which is to deliver the PSK key to the IKEv2
server.  The issues you discuss relating to PSK are issues that are there
with or without this document.  The document uses all the information that
is available in IKEv2 to fetch that PSK and to allow a PSK to be derived
(via the nonces). =20


>
>>=20
>>=20
>> Minor issues:
>>=20
>
>[...]

>[...]
>
>>=20
>> -- section 10, 1st paragraph: "Furthermore, any agents that process
>>IKEv2-PSK-Answer messages can see the contents of the Key AVP. For this
>>reason, this specification strongly recommends avoiding Diameter agents
>>when they cannot be trusted to keep the keys secret."
>>=20
>> Should that be normative? Is there no way to protect the PSK AVP from
>>diameter agents? E.g. can it be encrypted?
>> [VC] It is hard to use normative text here as this application can be
>>used for many uses cases. Depending on the use case it may be possible
>>to encrypt the PSK, however it is not possible to make it a requirement.
>
>I don't see why a "SHOULD" or "RECOMMENDED" would cause problems here,
>along with some short explanation of why it might not always be possible.
>Otherwise, the text says "strongly recommends", when, without normative
>text, such recommendation is really pretty weak.

I may be okay with using stronger terms (SHOULD or RECOMMEND).  I actually
wish now that this entire paragraph be deleted. The reason being is that
the security issues relating to multi-hop Diameter communication is well
understood and documented in 3588 (and we already make a reference to that
document).  I don't see a need for recommendation.

[...]

>> Nits/editorial comments:
>>=20
>
>[...]
>
>> -- section 8, first paragraph: "whether the AVP MAY be encrypted."
>>=20
>> I don't see anything about encryption in the table.
>> [VC] The text referring to encryption is deleted.
>>=20
>
>So how does an implementor know if it can be encrypted?

We used an old style of table which is not really used.  There is no end
to end encryption mechanisms in Diameter.  And Diameter provides transport
level security (integrity and privacy protection).  If the end to end
encryption that is between the Diameter Client (IKEv2 Server) and the
Diameter Server (where the PSK is stored/generated) is needed it would
have to be built on-top of this document - so the implementor will know.

>
>[...]


From ajs@anvilwalrusden.com  Wed Jun 15 13:16:47 2011
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 D7EF49E8026 for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 13:16: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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FZ4RZ3K0BL61 for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 13:16:47 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 1A5BB9E800F for <ietf@ietf.org>; Wed, 15 Jun 2011 13:16:47 -0700 (PDT)
Received: from shinkuro.com (68-248-62-130.ded.ameritech.net [68.248.62.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id E80911ECB41C; Wed, 15 Jun 2011 20:16:44 +0000 (UTC)
Date: Wed, 15 Jun 2011 16:16:44 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
Message-ID: <20110615201644.GB69872@shinkuro.com>
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF885B5.4020202@gmx.de> <4DF8CA3D.7020904@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4DF8CA3D.7020904@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Julian Reschke <julian.reschke@gmx.de>, Alexey Melnikov <alexey.melnikov@isode.com>, Boris Zbarsky <bzbarsky@MIT.EDU>, draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 20:16:48 -0000

On Wed, Jun 15, 2011 at 06:05:33PM +0300, Mykyta Yevstifeyev wrote:
> 15.06.2011 13:13, Julian Reschke wrote:

> >That being said, if our Mozilla friends do not want to fix this it
> >might be a good idea to warn readers that certain implementations
> >fail to properly unescape, thus it's unwise to rely on that
> >behavior (why would you anyway?).
> I fully agree with you, Julian.  I think we'll do certainly as you
> propose, unless Boris will provide some strong reasons to do in
> other way.

If I am reading the document and the above correctly, then you are
proposing the following:

    1.  The document proposes to make standard rules about what
    applications do with input that is, by definition, completely
    internal to that application; and,

    2.  You propose in addition to state what is the standard, but
    note that nobody should rely on it because one of the largest
    implementers of the scheme doesn't follow the supposed standard.

Do I have this correct?  If so, I would like to request that the
WINDMILL or perhaps TILT WG be chartered to deal with this manner of
work.

More substantively, I fail to understand how this specification
proposes to create a class of "reserved" about: URIs when the about:
scheme seems to be internal information to an application.  I think
the Security Considerations section doesn't address any of that, and
probably ought to, particularly in light of the proposal to add text
that users ought not to depend on "standard" behaviour.  

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From moore@network-heretics.com  Wed Jun 15 15:58:45 2011
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 9BAED11E80C7; Wed, 15 Jun 2011 15:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.387
X-Spam-Level: 
X-Spam-Status: No, score=-3.387 tagged_above=-999 required=5 tests=[AWL=0.212,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i9p6kXiYulKg; Wed, 15 Jun 2011 15:58:45 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id E18EA11E80A0; Wed, 15 Jun 2011 15:58:44 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id BA06220E43; Wed, 15 Jun 2011 18:58:43 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 15 Jun 2011 18:58:43 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=o9snRecj8YwuD488YJkkVMGcVEk=; b=cPw+eTuGU5/5oVSfudKPFkg4leVBYz1vd7PXKpDwlHMQ3fWI/3buiB/YjHEJpPsh3jyWkjhjfjbUcqpVU12e6g8gYLlGSPSAbyHhx6Ia7CrGmY6TJ+VJqNaPJXrjP50CQqss5yCW2sM+karwj3ymrW497ar9DNrl2d22M6iyUM8=
X-Sasl-enc: y+AH5u7sLlqsqTewhgvm6vOzXMmFsqZbJJLE46/q1uUG 1308178723
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id A055F440D1D; Wed, 15 Jun 2011 18:58:42 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com>
Date: Wed, 15 Jun 2011 18:58:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5A79D68-C636-4C07-9C86-F394EF3ECFA3@network-heretics.com>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 22:58:45 -0000

On Jun 14, 2011, at 1:59 PM, Lorenzo Colitti wrote:

> That said, I would argue that most or all 6to4 traffic could just as =
well use IPv4, since both parties to the communication obviously have =
access to a public IPv4 address. What is the advantage of using 6to4 =
over IPv4 that makes it worth suffering an 80% failure rate?


it can communicate with hosts that have only IPv6,
it can communicate with hosts that are stuck behind a single IPv4 =
address (if the router acts as a 6to4 gateway) without a NAT being in =
the way,
it can be used to develop and test IPv6 applications without having to =
build a special-purpose network,
it can be used to deploy applications now that already support IPv6 and =
so are in some sense future-proofed,
it can be deployed on either a single host or a network

again, trying to judge how well 6to4 works by how well it works with web =
sites that also support IPv4 is entirely missing the point.

Keith



From moore@network-heretics.com  Wed Jun 15 16:38:49 2011
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 9412F11E81E4; Wed, 15 Jun 2011 16:38:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.392
X-Spam-Level: 
X-Spam-Status: No, score=-3.392 tagged_above=-999 required=5 tests=[AWL=0.206,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dTZ5-HuAyHmo; Wed, 15 Jun 2011 16:38:48 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 767AB11E81DE; Wed, 15 Jun 2011 16:38:48 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 185F120DD0; Wed, 15 Jun 2011 19:38:47 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Wed, 15 Jun 2011 19:38:48 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=23s1RC2Qa0oRgmgeHyE2HsAfiuo=; b=ot2u8rswrHj+0wtG1UZNRatImEtFTceeHYKuOUxv7/3dORCpv9DvgDQx52HKbrP1dK6I3tNL/zMXfaQagrPAHDmRdzRyC2xJQGii3Ry3bkk03DcPK/SyOSyk11ObBS+BemioTuEFdTioHEKiGkBW+f3Cw0e2aWiUbbSWP2KS1F8=
X-Sasl-enc: QL9uBjIAB1xShj4IOG00pcdk+k6Im86mbwVdyBPIoQ/f 1308181126
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 637AB4425A2; Wed, 15 Jun 2011 19:38:46 -0400 (EDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-9--838556222
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <BANLkTi=GGAY2U0sX54hnv7Bz7QDgrAjZ9H+8rwhmwkjK+9ssig@mail.gmail.com>
Date: Wed, 15 Jun 2011 19:38:45 -0400
Message-Id: <11B87B4E-6F6F-4ABF-B5B9-BDA177E2FD7E@network-heretics.com>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com> <F5A79D68-C636-4C07-9C86-F394EF3ECFA3@network-heretics.com> <BANLkTi=GGAY2U0sX54hnv7Bz7QDgrAjZ9H+8rwhmwkjK+9ssig@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 23:38:49 -0000

--Apple-Mail-9--838556222
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jun 15, 2011, at 7:10 PM, Lorenzo Colitti wrote:

> On Wed, Jun 15, 2011 at 3:58 PM, Keith Moore =
<moore@network-heretics.com> wrote:
> > That said, I would argue that most or all 6to4 traffic could just as =
well use IPv4, since both parties to the communication obviously have =
access to a public IPv4 address. What is the advantage of using 6to4 =
over IPv4 that makes it worth suffering an 80% failure rate?
>=20
>=20
> it can communicate with hosts that have only IPv6,
> it can communicate with hosts that are stuck behind a single IPv4 =
address (if the router acts as a 6to4 gateway) without a NAT being in =
the way,
> it can be used to develop and test IPv6 applications without having to =
build a special-purpose network,
> it can be used to deploy applications now that already support IPv6 =
and so are in some sense future-proofed,
> it can be deployed on either a single host or a network
>=20
> ... about 80% of the time.

A single figure doesn't really describe the situation.   The =
successes/failures aren't independent of one another.  It's not that you =
get only an 80% probability of things working on every connection.  It's =
more like, it either works fairly well for what you need it to do, or it =
doesn't.

Again, don't assume that this is like the web and the connections are =
mostly client-to-server, or one source to large numbers of different =
destinations.

> I would argue that cases 1, 3, 4, 5, and 6 can be solved more reliably =
using configured tunnels,

There are lots of different tunneling methods each with strengths and =
weaknesses.   What you probably do in practice is try one, and if that =
doesn't work for your purposes, try another.  6to4 is very easy to try, =
and it often works.=20

Keith


--Apple-Mail-9--838556222
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jun 15, 2011, at 7:10 PM, Lorenzo Colitti =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div class=3D"gmail_quote">On Wed, Jun 15, 2011 at 3:58 =
PM, Keith Moore <span dir=3D"ltr">&lt;<a =
href=3D"mailto:moore@network-heretics.com">moore@network-heretics.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">&gt; That said, I would argue that most or all 6to4 =
traffic could just as well use IPv4, since both parties to the =
communication obviously have access to a public IPv4 address. What is =
the advantage of using 6to4 over IPv4 that makes it worth suffering an =
80% failure rate?<br>


<br>
<br>
</div>it can communicate with hosts that have only IPv6,<br>
it can communicate with hosts that are stuck behind a single IPv4 =
address (if the router acts as a 6to4 gateway) without a NAT being in =
the way,<br>
it can be used to develop and test IPv6 applications without having to =
build a special-purpose network,<br>
it can be used to deploy applications now that already support IPv6 and =
so are in some sense future-proofed,<br>
it can be deployed on either a single host or a =
network<br></blockquote><div><br></div><div>... about 80% of the =
time.</div></div></blockquote><div><br></div>A single figure doesn't =
really describe the situation. &nbsp; The successes/failures aren't =
independent of one another. &nbsp;It's not that you get only an 80% =
probability of things working on every connection. &nbsp;It's more like, =
it either works fairly well for what you need it to do, or it =
doesn't.</div><div><br></div><div>Again, don't assume that this is like =
the web and the connections are mostly client-to-server, or one source =
to large numbers of different destinations.</div><div><br><blockquote =
type=3D"cite"><div class=3D"gmail_quote"><div>I would argue that cases =
1, 3, 4, 5, and 6 can be solved more reliably using configured tunnels, =
</div></div></blockquote><div><br></div><div>There are lots of different =
tunneling methods each with strengths and weaknesses. &nbsp; What you =
probably do in practice is try one, and if that doesn't work for your =
purposes, try another. &nbsp;6to4 is very easy to try, and it often =
works.&nbsp;</div></div><div><br></div><div>Keith</div><div><br></div></bo=
dy></html>=

--Apple-Mail-9--838556222--

From conte@isoc.org  Wed Jun 15 16:54:14 2011
Return-Path: <conte@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74EB511E81DB for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 16:54:14 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L-GeU23raPur for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 16:54:13 -0700 (PDT)
Received: from smtp177.iad.emailsrvr.com (smtp177.iad.emailsrvr.com [207.97.245.177]) by ietfa.amsl.com (Postfix) with ESMTP id 574F511E80DF for <ietf@ietf.org>; Wed, 15 Jun 2011 16:54:13 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp27.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id B4D5A1184A1 for <ietf@ietf.org>; Wed, 15 Jun 2011 19:54:12 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp27.relay.iad1a.emailsrvr.com (Authenticated sender: conte-AT-isoc.org) with ESMTPSA id 4E3EA1182C2 for <ietf@ietf.org>; Wed, 15 Jun 2011 19:54:12 -0400 (EDT)
From: Steve Conte <conte@isoc.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: IETF Fellowship Announcement (IETF 82 and 83)
Date: Wed, 15 Jun 2011 16:54:11 -0700
Message-Id: <343E8492-2A56-4D9C-AB13-4917C35BBEDA@isoc.org>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 23:54:14 -0000

Dear Colleagues,

The Internet Society has announced that it is inviting applications for =
its latest Internet Society Fellowships to the IETF, part of its Next =
Generation Leaders (NGL) programme (www.InternetSociety.org/Leaders). =
The Fellowship programme allows engineers from developing countries to =
attend an Internet Engineering Task Force (IETF) meeting.

As you know, the IETF is the Internet's premier standards-making body, =
responsible for the development of protocols used in IP-based networks. =
IETF participants represent an international community of network =
designers, operators, vendors, and researchers involved in the technical =
operation of the Internet and the continuing evolution of Internet =
architecture.

Fellowships will be awarded through a competitive application process. =
The Internet Society is currently accepting fellowship applications for =
the next two IETF meetings:

* IETF 82, 13 - 18 Nov 2011, Taipei, TW   =20
* IETF 83, 25 - 30 March, Paris, FR

http://www.isoc.org/educpillar/fellowship/index.php

Fellowship applications for both IETF meetings are due by 15 July 2011.

Please note that this fellowship is aimed at individuals from developing =
regions that possess a solid level of technical education and enough =
knowledge about concrete areas of IETF work to follow and benefit from =
the meeting=92s technical discussions.=20

I encourage you to pass on information about this program to individuals =
involved in your network that have a keen interest in the Internet =
standardisation activities of the IETF.

The Internet Society Fellowships to the IETF are sponsored by Afilias, =
Google, Microsoft, and Intel.

The Internet Society=92s Next Generation Leaders programme is sponsored =
by Nominet Trust, the Association Fran=E7aise pour le Nommage Internet =
en Coop=E9ration (AFNIC), SIDN, and the European Commission.

If you have questions, please do not hesitate to contact Steve Conte =
<conte[at]isoc[dot]org>.

Kind Regards,
Steve Conte
Internet Society
-----
Steve Conte
conte@isoc.org




From marka@isc.org  Wed Jun 15 17:00:55 2011
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 CFB8021F84FB for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 17:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.269
X-Spam-Level: 
X-Spam-Status: No, score=-0.269 tagged_above=-999 required=5 tests=[AWL=-2.270, BAYES_00=-2.599, MANGLED_OFF=2.3, MANGLED_PRBLMS=2.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SZV4iMiOnr0W for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 17:00: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 0F76221F84F8 for <ietf@ietf.org>; Wed, 15 Jun 2011 17:00:54 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 639585F9982; Thu, 16 Jun 2011 00:00:33 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 81BA7216C80; Thu, 16 Jun 2011 00:00:31 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id C123410CD566; Thu, 16 Jun 2011 10:00:24 +1000 (EST)
To: Christian Huitema <huitema@microsoft.com>
From: Mark Andrews <marka@isc.org>
References: <20110615022008.0816818C172@mercury.lcs.mit.edu> <20110615030130.3E2A810C7E48@drugs.dv.isc.org> <22F6318E46E26B498ABC828879B08D4F16FF26@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Subject: Re: one data point regarding native IPv6 support
In-reply-to: Your message of "Wed, 15 Jun 2011 14:12:47 GMT." <22F6318E46E26B498ABC828879B08D4F16FF26@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Date: Thu, 16 Jun 2011 10:00:24 +1000
Message-Id: <20110616000024.C123410CD566@drugs.dv.isc.org>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2011 00:00:55 -0000

In message <22F6318E46E26B498ABC828879B08D4F16FF26@TK5EX14MBXW653.wingroup.wind
eploy.ntdev.microsoft.com>, Christian Huitema writes:
> >From Noel analysis, it seems that a lot of the issues could be mitigated by=
>  a simple connectivity test. Have the 6to4 router perform a simple ping tes=
> t through the tentative 6to4 relay, towards some well-known IPv6 host. Or a=
> n HTTP test, if we fear that ICMPv6 might be somehow tampered with.  If the=
>  test succeed, then it shows that the path to that 6to4 relay is clear of f=
> irewalls and other obstructions. If the path is not clear, pick another 6to=
> 4 relay, or do not enable 6to4.
> 
> Of course, this does not solve the problem of intermittent failures on the =
> IPv4 path to the relay, e.g. due to congestion.

But happy-eyeballs does mostly solve that problem.  If the path is
congested and dropping packets then the IPv6 connect will likely
not succeed before the IPv4 connect succeeds.  happy-eyeballs also
deals with relay routers that are topologically bad for the destination
machines which are dual stack.

> It also does not solve the problem of routers advertising an IPv6 route to =
> 2002::/16 and then failing to deliver the IPv4 packets. But this "return" p=
> roblem is easily solved by IPv6 ISP deploying their own 6to4 routers, and t=
> hus avoiding dependencies on a "generic" path to 2002::/16.
> 
> -- Christian Huitema
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From marka@isc.org  Wed Jun 15 18:22:06 2011
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 6D55711E80C7; Wed, 15 Jun 2011 18:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.363
X-Spam-Level: 
X-Spam-Status: No, score=-2.363 tagged_above=-999 required=5 tests=[AWL=0.236,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id coumNOmqaTWv; Wed, 15 Jun 2011 18:22:05 -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 7953C11E8080; Wed, 15 Jun 2011 18:22:05 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id A48C45F9861; Thu, 16 Jun 2011 01:21:44 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 7D383216C7B; Thu, 16 Jun 2011 01:21:42 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 63F3510CDCB3; Thu, 16 Jun 2011 11:21:40 +1000 (EST)
To: Lorenzo Colitti <lorenzo@google.com>
From: Mark Andrews <marka@isc.org>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com> <F5A79D68-C636-4C07-9C86-F394EF3ECFA3@network-heretics.com> <BANLkTi=GGAY2U0sX54hnv7Bz7QDgrAjZ9H+8rwhmwkjK+9ssig@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
In-reply-to: Your message of "Wed, 15 Jun 2011 16:10:12 MST." <BANLkTi=GGAY2U0sX54hnv7Bz7QDgrAjZ9H+8rwhmwkjK+9ssig@mail.gmail.com>
Date: Thu, 16 Jun 2011 11:21:40 +1000
Message-Id: <20110616012140.63F3510CDCB3@drugs.dv.isc.org>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Keith Moore <moore@network-heretics.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2011 01:22:06 -0000

In message <BANLkTi=GGAY2U0sX54hnv7Bz7QDgrAjZ9H+8rwhmwkjK+9ssig@mail.gmail.com>
, Lorenzo Colitti writes:
> On Wed, Jun 15, 2011 at 3:58 PM, Keith Moore <moore@network-heretics.com>wrot
> e:
> 
> > > That said, I would argue that most or all 6to4 traffic could just as well
> > use IPv4, since both parties to the communication obviously have access to 
> a
> > public IPv4 address. What is the advantage of using 6to4 over IPv4 that
> > makes it worth suffering an 80% failure rate?
> >
> >
> > it can communicate with hosts that have only IPv6,
> > it can communicate with hosts that are stuck behind a single IPv4 address
> > (if the router acts as a 6to4 gateway) without a NAT being in the way,
> > it can be used to develop and test IPv6 applications without having to
> > build a special-purpose network,
> > it can be used to deploy applications now that already support IPv6 and so
> > are in some sense future-proofed,
> > it can be deployed on either a single host or a network
> 
> ... about 80% of the time.

Or 99.999% of the time once you get it setup.  The problem isn't 6to4, it's
*automatic* 6to4.
 
> I would argue that cases 1, 3, 4, 5, and 6 can be solved more reliably using
> configured tunnels, and that case 2 is today solved more reliably, and in
> more cases (e.g., when no public IPv4 address is available at the border) by
> the various NAT traversal mechanisms that are implemented in applications.
> But I think we're just going around in circles here.
 
Which often times requires special software to be installed.  Tunnels
are a lot more hassle to setup and yes I've used both so I know.

6to4 historic is throwing the baby out with the bath water.

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

From mail@sabahattin-gucukoglu.com  Wed Jun 15 19:25:26 2011
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DF0111E80EA for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 19:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.962
X-Spam-Level: 
X-Spam-Status: No, score=0.962 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HOST_MISMATCH_COM=0.311,  RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E8o1cNHMSimi for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 19:25:25 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com (sgucukoglu-2-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:7ef::2]) by ietfa.amsl.com (Postfix) with ESMTP id D6D8B11E80DC for <ietf@ietf.org>; Wed, 15 Jun 2011 19:25:23 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:43671) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S36373> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Thu, 16 Jun 2011 03:25:22 +0100
Received: from [192.168.1.20] (cpc2-dals7-0-0-cust570.hari.cable.virginmedia.com [82.35.114.59]) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Thu, 16 Jun 2011 03:25:20 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
In-Reply-To: <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com>
Date: Thu, 16 Jun 2011 03:25:18 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DEAF8A56-E1B6-450B-9082-FD04DF3119D2@sabahattin-gucukoglu.com>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-Delivery-Agent: TMDA/1.1.12-kg3 (Haumea)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1310783122.fe9949@sabahattin-gucukoglu.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 Jun 2011 02:25:27 -0000

On 14 Jun 2011, at 18:59, Lorenzo Colitti wrote:
> On Tue, Jun 14, 2011 at 10:30 AM, james woodyatt <jhw@apple.com> =
wrote:
>> Very few of the people using 6to4 in this way will show up in =
Google's user
>> behavior analysis, of course, because Google doesn't run its own 6to4
>> return-path relay as I-D.ietf-v6ops-6to4-advisory recommends.
>=20
> We would not see these users even if we operated reverse path relays =
as
> recommended in the draft - from the point of view of the server, in =
both
> cases it's just a TCP connection to a 2002::/16 address, regardless of
> whether the relay is inside the Google network or outside it.

Running the relay inside your network lets you correlate the failure =
rate you observe to the direction of the path the failures occur in, =
though.  That data may be valuable to you.  And since it's HTTP we're =
talking about, it might be a consolation to know that it's your side of =
the network generating the most traffic.

> Those users would become visible if we added AAAA records with 6to4
> addresses, but that's a bad plan because it would likely lead to the
> double-digit connection failure rates that Geoff observes. It would =
also
> become visible if Google operated an open anycast relay, which we do =
not
> plan to do.

Your (Google's) problem is the relays.  So, if we take this thought a =
step further, by deploying (no, I'm not suggesting you do this, =
obviously) a 6to4-reachable presence you may actually reduce the total =
traffic by volume reaching you over native IPv6, if it transpires that =
6to4 is a good portion of the majority of tunnel traffic, the vast =
majority of IPv6 traffic reaching you.  That's not to speak of address =
selection algorithms which would do the right thing (in theory) given =
the choice of native or 6to4, of course.

> The way to find these people is to crawl the BitTorrent networks.  =
What's
>> that old maxim?  "You can't test what you don't measure."  Do you =
measure
>> the BitTorrent networks?
>=20
> No, we don't. The measurements we conduct have the purpose of =
determining
> the impact of adding AAAA records to web sites, so we don't measure =
the
> population of users that has 6to4 but does not use it to make HTTP
> connections to dual-stack websites. We do measure the impact of 6to4 =
on the
> reliability of websites indirectly, e.g., by observing the difference
> between OSes that prefer IPv4 over 6to4 and OSes that don't.

That's a real shame, because the use of peer-to-peer applications is a =
solid reason to turn various tunnel techniques on.  One popular Windows =
BitTorrent client makes it a single-button operation; others simply take =
the IPv6 connectivity for granted, when available.  See:
http://thepiratebay.org/blog/146

> Also, is there a way we can put this debate to rest using real data? =
What if
> we asked someone like Hurricane Electric how much traffic on their =
network
> is native IPv6 vs. 6to4?

I agree, this would be a good thing.

> That said, I would argue that most or all 6to4 traffic could just as =
well
> use IPv4, since both parties to the communication obviously have =
access to a
> public IPv4 address. What is the advantage of using 6to4 over IPv4 =
that
> makes it worth suffering an 80% failure rate?

Others have beaten me to this one but I will say one thing in your =
favour: NAT traversal techniques are ubiquitous and, curse them, =
actually fairly transparent.  This is probably a good thing and it does =
support your view that at least in the case of BitTorrent or other =
vanilla address-neutral protocols the end-user transparency really =
doesn't usually justify the added tunnels for v4-to-v4 communication, =
regardless of technical impropriety.  However this does nothing to =
address other real concerns, most of them brought up by Keith already.  =
Most importantly, new protocols or uses of the Internet shouldn't be =
sabotaged by the need for some sort of imaginary all-or-nothing =
transition to IPv6.

One final thought: assuming we ever get to the stage of minority native =
IPv6 worth service providers' time to set up IPv6 reachability for, and =
not just the big ones either, what exactly do all the tunnel brokers of =
the world do about the sudden demand for their services?

Cheers,
Sabahattin

From johnl@iecc.com  Wed Jun 15 21:47:44 2011
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 C26C011E812B for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 21:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.982
X-Spam-Level: 
X-Spam-Status: No, score=-110.982 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SGp2ONdqfXdj for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 21:47:44 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id F400E11E8116 for <ietf@ietf.org>; Wed, 15 Jun 2011 21:47:43 -0700 (PDT)
Received: (qmail 50659 invoked from network); 16 Jun 2011 04:47:42 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 16 Jun 2011 04:47:42 -0000
Date: 16 Jun 2011 04:47:20 -0000
Message-ID: <20110616044720.11371.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified Mail (DKIM) Signatures) to Draft Standard
In-Reply-To: <20110615213858.9853.22165.idtracker@ietfa.amsl.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2011 04:47:44 -0000

In article <20110615213858.9853.22165.idtracker@ietfa.amsl.com> you write:
>
>The IESG has received a request from the Domain Keys Identified Mail WG
>(dkim) to consider the following document:
>- 'DomainKeys Identified Mail (DKIM) Signatures'
>  <draft-ietf-dkim-rfc4871bis-12.txt> as a Draft Standard

I've reviewed this document, indeed my fingerprints are all over it.

It's definitely an improvement to 4871: folds in the errata, takes out
a lot of gratuitous and often wrong non-normative advice, cleans up
the 2119 MUSTage, and otherwise improves the text.  Except for the one
obscure feature that is deprecated due to lack of use, I think that
any implementation that is compliant with 4871+errata should still be
compliant with this draft.

R's,
John

From lachlan.hunt@lachy.id.au  Thu Jun 16 01:59:35 2011
Return-Path: <lachlan.hunt@lachy.id.au>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9743B11E819D for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 01:59:35 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XaEv6UZCewHN for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 01:59:30 -0700 (PDT)
Received: from homiemail-a59.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id EB73C11E8193 for <ietf@ietf.org>; Thu, 16 Jun 2011 01:59:30 -0700 (PDT)
Received: from homiemail-a59.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a59.g.dreamhost.com (Postfix) with ESMTP id 6A4A1564061; Thu, 16 Jun 2011 01:59:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=lachy.id.au; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=lachy.id.au; b=GYuUAzAK2Nm57L2LUSNPPC/9/GuPfhSLh2r0c64b+HekUre2xMa8/d1mtMxCy IoI4pz8YXaU3LxCpFZE8oUqCm2jbqzbk5Jsrc3Smz8LE5HxBbrhLlP3vOe7MqF5g tVpq6XyBS65O6JGY/cozVCEwTPL0PNigZNWIUlvlafo7RQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=lachy.id.au; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=lachy.id.au; bh=aFmUk q+uviL5Iz0wam2WWRQ/NJE=; b=leDeaQYDbOF5HvtKbHHZ6NGqIxmxpI76ddhvl Ei1NE6HTrqS4XXE9EuiniWh/OirFoFvS2aEvS+NoZbiKJjA7aXNSVZuP0eIGzY9F UHxg/9UFpGZk6nagphS+ul+yXe58pIYmRHY90/TSOWMysWGMTha1uO82ahmKJhUn oPqmMY=
Received: from jonas.eng.oslo.osa (pat-tdc.opera.com [213.236.208.22]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lachlan.hunt@lachy.id.au) by homiemail-a59.g.dreamhost.com (Postfix) with ESMTPSA id 5802A564059;  Thu, 16 Jun 2011 01:59:29 -0700 (PDT)
Message-ID: <4DF9C5EE.9010703@lachy.id.au>
Date: Thu, 16 Jun 2011 10:59:26 +0200
From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Boris Zbarsky <bzbarsky@MIT.EDU>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF8D6C6.5080005@mit.edu>
In-Reply-To: <4DF8D6C6.5080005@mit.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2011 08:59:35 -0000

On 2011-06-15 17:59, Boris Zbarsky wrote:
> On 6/15/11 5:07 AM, Mykyta Yevstifeyev wrote:
>> The point of this comment is to propose abandoning normalization of
>> 'about' URIs because of some ad hoc behavior of an only application -
>> Gecko.
>
> No, it's to propose abandoning normalization because it's not
> necessarily compatible with existing deployed uses of about:, not
> clearly compatible with the web security model, and because the
> normalization is not defined in the spec. The Gecko behavior is just an
> illustration of the first point.
>
>> The purpose of our draft is to give a stable specification of the
>> scheme
>
> Yes, this is fine.
>
>> and normalize all existing types of behavior with regard to
>> handling 'about' URIs. It will be easier for Gecko to change its
>> behavior rather than for other apps to do this.

Mykyta, we do need to make this spec document reality, particularly 
where implementations are unwilling to make changes.  If it doesn't do 
that, then the spec is useless.  I will be reviewing the options and 
look into exactly how other browsers handle these cases, and make 
appropriate changes to the spec.

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/

From julian.reschke@gmx.de  Thu Jun 16 02:14:24 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C94CB11E81E7 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 02:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YO0z-1YOVro9 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 02:14:24 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id CDC7311E81DF for <ietf@ietf.org>; Thu, 16 Jun 2011 02:14:23 -0700 (PDT)
Received: (qmail invoked by alias); 16 Jun 2011 09:14:22 -0000
Received: from p508FAA9D.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.170.157] by mail.gmx.net (mp013) with SMTP; 16 Jun 2011 11:14:22 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19CX+h8pVpCk2XCzCFLni+Q6yUp3LAg7vpTfXnPVs q/eL1DkZ+ZyeZB
Message-ID: <4DF9C96C.9090607@gmx.de>
Date: Thu, 16 Jun 2011 11:14:20 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com>	<4DF8D6C6.5080005@mit.edu> <4DF9C5EE.9010703@lachy.id.au>
In-Reply-To: <4DF9C5EE.9010703@lachy.id.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, 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, 16 Jun 2011 09:14:25 -0000

On 2011-06-16 10:59, Lachlan Hunt wrote:
> On 2011-06-15 17:59, Boris Zbarsky wrote:
>> On 6/15/11 5:07 AM, Mykyta Yevstifeyev wrote:
>>> The point of this comment is to propose abandoning normalization of
>>> 'about' URIs because of some ad hoc behavior of an only application -
>>> Gecko.
>>
>> No, it's to propose abandoning normalization because it's not
>> necessarily compatible with existing deployed uses of about:, not
>> clearly compatible with the web security model, and because the
>> normalization is not defined in the spec. The Gecko behavior is just an
>> illustration of the first point.
>>
>>> The purpose of our draft is to give a stable specification of the
>>> scheme
>>
>> Yes, this is fine.
>>
>>> and normalize all existing types of behavior with regard to
>>> handling 'about' URIs. It will be easier for Gecko to change its
>>> behavior rather than for other apps to do this.
>
> Mykyta, we do need to make this spec document reality, particularly
> where implementations are unwilling to make changes. If it doesn't do
> that, then the spec is useless. I will be reviewing the options and look
> into exactly how other browsers handle these cases, and make appropriate
> changes to the spec.

On the other hand, you're trying to define a URI scheme. If it's 
handling conflicts with the base URI spec, that's a bug. Period. You may 
*document* that some UAs have this bug, but you can't change it to be 
not a bug.

Best regards, Julian

From lachlan.hunt@lachy.id.au  Thu Jun 16 02:20:19 2011
Return-Path: <lachlan.hunt@lachy.id.au>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFBD011E81F6 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 02:20:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u57Wpxq0PoiS for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 02:20:18 -0700 (PDT)
Received: from homiemail-a79.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 6D5FF11E81F5 for <ietf@ietf.org>; Thu, 16 Jun 2011 02:20:18 -0700 (PDT)
Received: from homiemail-a79.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a79.g.dreamhost.com (Postfix) with ESMTP id 019B37D406C; Thu, 16 Jun 2011 02:20:18 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=lachy.id.au; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=lachy.id.au; b=lPs1Dg51XYhO65j6oY6MbAqgLnnHpulpLoX4lOVK42ZbTPhOmDAH3giSHd+/m wLE+o/Zhn80SDLZCCbMOOSP/yOm53+0dk0HnuynK58GhgVHl2TZPBdindG1u4aaZ 3Z4XkD9RGLq0jNdwch/K+0AJFFMqpuUjABhyW2Jyjvm/+4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=lachy.id.au; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=lachy.id.au; bh=OrruO zT3+quQ7kPg5uZLgJJSblk=; b=ncPJv6YeCjBDt868dzztt4U9kCRmclr0a2Em3 +5hO5KQEZPdFNco1Yi9taDo/ULjgRTDTDbSyd/UVtjX9hZqDrj3N+0khh8dGYO1z rZTVAMPZ832e5EdstaHz1Q2Ve2qtO+JmVItikp30IvFgqtUU2JyxO7fURdrXJ93k qdxf3k=
Received: from jonas.eng.oslo.osa (pat-tdc.opera.com [213.236.208.22]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lachlan.hunt@lachy.id.au) by homiemail-a79.g.dreamhost.com (Postfix) with ESMTPSA id F16767D4057;  Thu, 16 Jun 2011 02:20:16 -0700 (PDT)
Message-ID: <4DF9CACE.2000004@lachy.id.au>
Date: Thu, 16 Jun 2011 11:20:14 +0200
From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com>	<4DF8D6C6.5080005@mit.edu> <4DF9C5EE.9010703@lachy.id.au> <4DF9C96C.9090607@gmx.de>
In-Reply-To: <4DF9C96C.9090607@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, 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, 16 Jun 2011 09:20:20 -0000

On 2011-06-16 11:14, Julian Reschke wrote:
> On the other hand, you're trying to define a URI scheme. If it's
> handling conflicts with the base URI spec, that's a bug. Period. You may
> *document* that some UAs have this bug, but you can't change it to be
> not a bug.

Theoretical purity is not a priority for the specs I edit.  Wilful 
violations of other specs where necessary are acceptable.

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/

From julian.reschke@gmx.de  Thu Jun 16 02:36:03 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0561F0C37 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 02:36:03 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YG2xUMmdlvQf for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 02:36:03 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 7A75F1F0C35 for <ietf@ietf.org>; Thu, 16 Jun 2011 02:36:02 -0700 (PDT)
Received: (qmail invoked by alias); 16 Jun 2011 09:36:01 -0000
Received: from p508FAA9D.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.170.157] by mail.gmx.net (mp025) with SMTP; 16 Jun 2011 11:36:01 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19GteQQFOVGkYAAMkb9qhD1E1ulPt64Q9wTOjpkKV g0xvdzmgJKiSUe
Message-ID: <4DF9CE7F.6080704@gmx.de>
Date: Thu, 16 Jun 2011 11:35:59 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com>	<4DF8D6C6.5080005@mit.edu> <4DF9C5EE.9010703@lachy.id.au> <4DF9C96C.9090607@gmx.de> <4DF9CACE.2000004@lachy.id.au>
In-Reply-To: <4DF9CACE.2000004@lachy.id.au>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, 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, 16 Jun 2011 09:36:03 -0000

On 2011-06-16 11:20, Lachlan Hunt wrote:
> On 2011-06-16 11:14, Julian Reschke wrote:
>> On the other hand, you're trying to define a URI scheme. If it's
>> handling conflicts with the base URI spec, that's a bug. Period. You may
>> *document* that some UAs have this bug, but you can't change it to be
>> not a bug.
>
> Theoretical purity is not a priority for the specs I edit. Wilful
> violations of other specs where necessary are acceptable.

Lachlan, with all due respect, I really do not care what *your* 
priorities here are.

If you define a URI scheme, you'll have to be consistent with URI 
syntax. There's really no wiggle room except for warning about 
implementations that may not do it right.

Best regards, Julian

From jmh@joelhalpern.com  Thu Jun 16 07:15:13 2011
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 C9AA611E81FA for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 07:15:12 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XpwkyWKcDtIP for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 07:15:12 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob-ipv6.tigertech.net [IPv6:2604:4f00::1:0:0:22]) by ietfa.amsl.com (Postfix) with ESMTP id BAE8C11E81EA for <ietf@ietf.org>; Thu, 16 Jun 2011 07:15:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 13C3E3228BF3; Thu, 16 Jun 2011 07:15:10 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-50-44.clppva.btas.verizon.net [71.161.50.44]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 812E63246556; Thu, 16 Jun 2011 07:15:09 -0700 (PDT)
Message-ID: <4DFA0FEB.4060006@joelhalpern.com>
Date: Thu, 16 Jun 2011 10:15:07 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu>	<4DF87637.2000301@gmail.com>	<4DF8D6C6.5080005@mit.edu>	<4DF9C5EE.9010703@lachy.id.au> <4DF9C96C.9090607@gmx.de> <4DF9CACE.2000004@lachy.id.au>
In-Reply-To: <4DF9CACE.2000004@lachy.id.au>
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: Thu, 16 Jun 2011 14:15:13 -0000

The question is what "necessary" means in terms of willful violations of 
specs.  There are at least three cases I can understand, with different 
implications:

There are cases where the existing spec, while it claims to apply, 
actually is a bad idea.  Then we need to document the problem and the 
solution, and make sure the community agrees to the change.  This 
happens.  It usually results in an "updates" indication in the new spec, 
so folks know that the old one is not complete.

There are cases where a spec is documenting existing practice.  IIt can 
document that practice is different from the spec.  It has to do so 
while carefully being clear that the standards should apply, and that 
the practice does not match.  It is often useful to discuss the reasons 
for the mismatch.

Then there are cases where folks are attempting to standardizea space 
that has been unclear, under-specified, or a mess, and much of the space 
does not comply with the specs.  That is NOT a good reason to 
standardize non-compliant behavior.

I can not tell which of those you mean when you say that "Willful 
violations of other specs where necessary are acceptable."

Yours,
Joel


On 6/16/2011 5:20 AM, Lachlan Hunt wrote:
> On 2011-06-16 11:14, Julian Reschke wrote:
>> On the other hand, you're trying to define a URI scheme. If it's
>> handling conflicts with the base URI spec, that's a bug. Period. You may
>> *document* that some UAs have this bug, but you can't change it to be
>> not a bug.
>
> Theoretical purity is not a priority for the specs I edit. Wilful
> violations of other specs where necessary are acceptable.
>

From bzbarsky@mit.edu  Wed Jun 15 08:59:12 2011
Return-Path: <bzbarsky@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 3CEAB11E8132 for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 08:59: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E7Lun-Afdctm for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 08:59:11 -0700 (PDT)
Received: from dmz-mailsec-scanner-7.mit.edu (DMZ-MAILSEC-SCANNER-7.MIT.EDU [18.7.68.36]) by ietfa.amsl.com (Postfix) with ESMTP id 8AA1511E811F for <ietf@ietf.org>; Wed, 15 Jun 2011 08:59:11 -0700 (PDT)
X-AuditID: 12074424-b7bc6ae000005a77-67-4df8d6cec5d4
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id 7F.32.23159.EC6D8FD4; Wed, 15 Jun 2011 11:59:10 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id p5FFx84E002639;  Wed, 15 Jun 2011 11:59:08 -0400
Received: from Boris-Zbarskys-MacBook-Pro-2.local (pool-71-184-125-56.bstnma.fios.verizon.net [71.184.125.56]) (authenticated bits=0) (User authenticated as bzbarsky@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p5FFx2Zb027717 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 15 Jun 2011 11:59:03 -0400 (EDT)
Message-ID: <4DF8D6C6.5080005@mit.edu>
Date: Wed, 15 Jun 2011 11:59:02 -0400
From: Boris Zbarsky <bzbarsky@MIT.EDU>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com>
In-Reply-To: <4DF87637.2000301@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuphleLIzCtJLcpLzFFi42IRYrdT1z137YevwYEl2hYzVhdZXNjzj8Xi /YV2JotnG+ezWBzb08/swOqxc9Zddo8lS34yeZxqNvSYu+cFs8eXy5/ZAlijuGxSUnMyy1KL 9O0SuDLaz+xiK5jPU9G47glzA+M1zi5GTg4JAROJma++M0HYYhIX7q1n62Lk4hAS2McoMWH2 HChnA6PEmYc/mSCcV0wS/44dZeli5ODgFVCTWDTDHqSbRUBVonnCbxYQmw0ofP90I9hUUYFC iRnfZzKC2LwCghInZz4BqxER0JH40H6TEWQms8AhRoljj1+BNQgL5Eu0rAc5gxNombPEqnmX wZo5BTQlzv9tANvLLGAt8W13EUiYWUBeYvvbOcwTGAVnIVkxC6FqFpKqBYzMqxhlU3KrdHMT M3OKU5N1i5MT8/JSi3TN9XIzS/RSU0o3MYLD3kVlB2PzIaVDjJIcTEqivKeu/vAV4kvKT6nM SCzOiC8qzUktBjqag1lJhHd2KFCONyWxsiq1KB8mJc3BoiTOO09S3VdIID2xJDU7NbUgtQgm K8PBoSTBywmMXCHBotT01Iq0zJwShDQTByfIcB6g4Z9AFvMWFyTmFmemQ+RPMepyLFy3/hCj EEtefl6qlDjvB5AiAZCijNI8uDmwRPSKUZyDUUkYYhQPMInBTXoFtIQJaMmtl99AlpQkIqSk Ghh3NL7oNItWOnZRI3fZ/66tosFSIVM2vr/GuTjGydFEuF7hmq93vath3dPZ7/wvtrbf/Nty b7dL1Csv1kzW+5afU7iP/9m3IjWhzVqB60abbdbjrVvZ1zeXeDQI23uwPf1qELp7/eFYsy3B EdETeByKPHUny0lr/z/6vnnTi/0rlQt0/j429FdiKc5INNRiLipOBAAkb7FtHwMAAA==
X-Mailman-Approved-At: Thu, 16 Jun 2011 08:10:30 -0700
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 15:59:12 -0000

On 6/15/11 5:07 AM, Mykyta Yevstifeyev wrote:
>> Applications SHOULD resolve unrecognized "about" URIs in the
>> same way as "about:blank".
...

> I don't think MAY is fine here, as this is a recommendation.

I'm questioning it being a recommendation, is the point.  Why is this 
behavior recommended, exactly?  Given lack of existing interop and lack 
of a MUST-level requirement here, the only reason for a SHOULD would be 
if the behavior is believed to be better than other alternatives, right? 
  Is it?  I don't see why.

> The point of this comment is to propose abandoning normalization of
> 'about' URIs because of some ad hoc behavior of an only application -
> Gecko.

No, it's to propose abandoning normalization because it's not 
necessarily compatible with existing deployed uses of about:, not 
clearly compatible with the web security model, and because the 
normalization is not defined in the spec.  The Gecko behavior is just an 
illustration of the first point.

> The purpose of our draft is to give a stable specification of the
> scheme

Yes, this is fine.

> and normalize all existing types of behavior with regard to
> handling 'about' URIs. It will be easier for Gecko to change its
> behavior rather than for other apps to do this.

That's not clear to me given the security implications.  Do you have 
data to back this up?

> Boris, could you please let me know whether you have some strong opinion
> regarding your January comments/insist on incorporating them in the draft.

See above.

-Boris

From ben@nostrum.com  Wed Jun 15 09:02:07 2011
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 084F411E811F; Wed, 15 Jun 2011 09:02:07 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KI5KxCeqSMNJ; Wed, 15 Jun 2011 09:02:06 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8854311E8081; Wed, 15 Jun 2011 09:02:04 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5FG1tDE090642 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 15 Jun 2011 11:01:56 -0500 (CDT) (envelope-from ben@nostrum.com)
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <AAE76B481E7A0E4C96610790A852B9A6250A4F81A5@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
Date: Wed, 15 Jun 2011 11:01:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A6A10F5-5C34-494A-B922-EAB9DDE73551@nostrum.com>
References: <5E434E92-2EB7-43B3-A29F-8410B1AC23AE@nostrum.com> <AAE76B481E7A0E4C96610790A852B9A6250A4F81A5@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
To: "Cakulev, Violeta (Violeta)" <violeta.cakulev@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Thu, 16 Jun 2011 08:10:26 -0700
Cc: "draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org" <draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The 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 Jun 2011 16:02:07 -0000

Thanks for the response. Comments inline. I deleted sections that appear =
not to need further discussion.

Thanks!

Ben.

On Jun 14, 2011, at 2:11 PM, Cakulev, Violeta (Violeta) wrote:

>=20
> Ben,
> Thanks for the comments.
> Please see inline [VC].
>=20
> -Violeta
>=20
> -----Original Message-----
> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Friday, June 03, 2011 4:10 PM
> To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org; =
gen-art@ietf.org Review Team
> Cc: The IETF
> Subject: Gen-ART LC review of draft-ietf-dime-ikev2-psk-diameter-07
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document: draft-ietf-dime-ikev2-psk-diameter-07
> Reviewer: Ben Campbell
> Review Date: 2011-06-03
> IETF LC End Date: 2011-06-03
>=20
>=20
> Summary:
>=20
> This draft is almost ready for publication as a proposed standard. I =
have a question concerning the procedure for generating PSKs, and a =
number of minor and editorial comments.
>=20
>=20
> Major issues:
>=20
> The draft says that the procedure that the HAAA follows to generate =
the PSK is out of scope. But doesn't the IKE2 initiator need to =
understand the procedure? If the procedure is not defined somewhere, how =
you achieve any degree of interoperability?
> [VC] Indeed the IKEv2 initiator needs to understand the procedure. =
However, this draft focuses on IKEv2 server, as a Diameter client, to =
the Diameter server communication for IKEv2 with pre-shared key based =
authentication, and specifies Diameter application for this =
communication. It is left to specifications that make use of this =
Diameter application to specify where the PSK comes from and how it is =
generated. There are two 3GPP2 specs that make use of this Diameter =
application and both of those specs specify generation of the PSK. =
Statements to clarify this are added in v8.

The effect of this is that this spec, as written, cannot be implemented =
in an interoperable way. I don't think that meets the usual expectations =
for a proposed standard. Now, I realize there are some situations where =
the IETF has chosen this approach, and deliberately created a standards =
track RFC that must be profiled for actual use--but hopefully that's the =
exception rather than the rule.  I guess it's up to the IESG to decide =
if that is reasonable in this instance. (I'm explicitly not counting =
situations where the IETF puts out a standard as a series of modular =
RFCs, since I gather there's no immediate intent to publish PSK =
generation RFCs.)

Additionally, whether or not PSK generation mechanisms are specified in =
the IETF vs somewhere else, how does an implementation (that might =
support more than one such mechanism) know which to use for any given =
SA? Is there a negotiation mechanism?

>=20
>=20
> Minor issues:
>=20

[...]

> -- section 10:
>=20
> The security considerations should describe the threat models. We're =
talking about requesting an authentication key from a third party, which =
is tricky from a security perspective. Does the PSK have greater =
security concerns than for Diameter AVPs in general? In particular, what =
are the consequences if the PSK is disclosed or tampered with?
> [VC] If the PSK is disclosed to an adversary then it would present a =
security breach.  Hence we recommend that the PSK be short-lived.  As =
well,
> the assumption is that the IKEv2 Server and the Diameter Server where =
the PSK is generated are in a trusted relationship. They may be in the =
same Administrative domain (typical case) or third party but =
nevertheless there is a trust relationship between them.  As such we =
assume that there is an appropriate security mechanism to protect the =
communication between these servers.  For example the IKEV2 Server and =
the Diameter server would be deployed in the same secure network or =
would utilize transport layer security as specified by Diameter 3588 =
specification. We added statements in v8 to reflect this.

Thanks, that probably helps (pending seeing the actual text).

>=20
> -- section 10, 1st paragraph: "Furthermore, any agents that process =
IKEv2-PSK-Answer messages can see the contents of the Key AVP. For this =
reason, this specification strongly recommends avoiding Diameter agents =
when they cannot be trusted to keep the keys secret."
>=20
> Should that be normative? Is there no way to protect the PSK AVP from =
diameter agents? E.g. can it be encrypted?
> [VC] It is hard to use normative text here as this application can be =
used for many uses cases. Depending on the use case it may be possible =
to encrypt the PSK, however it is not possible to make it a requirement.

I don't see why a "SHOULD" or "RECOMMENDED" would cause problems here, =
along with some short explanation of why it might not always be =
possible. Otherwise, the text says "strongly recommends", when, without =
normative text, such recommendation is really pretty weak.

>=20
> -- section 10, 2nd paragraph: "this specification also recommends the =
use of nonces included in IKEv2-PSK-Request."
>=20
> Actually, the spec requires it using a normative SHALL.
> [VC] In v8 it is aligned as 'recommended' throughout the document.
>=20

I'm curious why you chose to weaken the rest of the text, vs =
strengthening the comment in the security considerations? (Also, is that =
"recommended" or "RECOMMENDED"?)

> Nits/editorial comments:
>=20

[...]

> -- section 8, first paragraph: "whether the AVP MAY be encrypted."
>=20
> I don't see anything about encryption in the table.
> [VC] The text referring to encryption is deleted.
>=20

So how does an implementor know if it can be encrypted?

[...]=

From lorenzo@google.com  Wed Jun 15 15:04:49 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12D7E11E81D0 for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 15:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G0ReUz7cySq3 for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 15:04:48 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 2052511E81BE for <ietf@ietf.org>; Wed, 15 Jun 2011 15:04:47 -0700 (PDT)
Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id p5FM4k2D011594 for <ietf@ietf.org>; Wed, 15 Jun 2011 15:04:46 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1308175487; bh=C3B7r9ABLXkwhnTq8z1eVeYqc+g=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=IGi36rN1KaU/g+H4JDSDLF/+UGGn75HKrLlEhX3FF4ZEQtThC/1FKPuwxVT0o4Rdj qd6uaGapT8Lb/87IzVNsg==
Received: from yxe1 (yxe1.prod.google.com [10.190.2.1]) by wpaz13.hot.corp.google.com with ESMTP id p5FM3avu017797 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Wed, 15 Jun 2011 15:04:45 -0700
Received: by yxe1 with SMTP id 1so682378yxe.34 for <ietf@ietf.org>; Wed, 15 Jun 2011 15:04:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Sx0AtDS4qQBeHV1Cz0eety0njh5zV69vQPBqTmabYXM=; b=coUb3J6dhr83bMkU7/fjeuqzKROPAUkEOvJNT2ymYKLRlDuxVdeVuiclCcE0Aa4Ejb t8RVft8814EL/oJhqqOw==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=yUBBSylSAAcKCHUwG+mejez8USZi0Y1jZaZCCd1YYxAy5QbvsrKnYJ6VbWabpe3ZfP 3Xh0MSGtHOgfuteb2TCA==
Received: by 10.151.24.10 with SMTP id b10mr182240ybj.93.1308175485107; Wed, 15 Jun 2011 15:04:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.147.16 with HTTP; Wed, 15 Jun 2011 15:04:24 -0700 (PDT)
In-Reply-To: <20110615081050.70c9112a@opy.nosense.org>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com> <20110615081050.70c9112a@opy.nosense.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Jun 2011 15:04:24 -0700
Message-ID: <BANLkTikePKFTjVvf326Wm7Mt0hP_5OdGxKyjuDfNmBUaYi6z9A@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Content-Type: multipart/alternative; boundary=000e0cd23ef617fcdd04a5c75705
X-System-Of-Record: true
X-Mailman-Approved-At: Thu, 16 Jun 2011 08:10:31 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 22:04:49 -0000

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

On Tue, Jun 14, 2011 at 3:40 PM, Mark Smith <
ipng@69706e6720323030352d30312d31340a.nosense.org> wrote:

> I don't know if it is intentional, however if I use Google's public
> 8.8.8.8 and 8.8.4.4 resolvers, and prefer 6to4 over native IPv4
> (via /etc/gai.conf under Linux/glibc), it seems that the video content
> of all youtube videos is now being delivered over IPv6.
>

Yes, YouTube videos are currently being served on dual-stack hostnames. The
percentage of YouTube users that uses 6to4 is less than 0.02%. The
percentage of YouTube users that uses native IPv6 is approximately 0.2% -
over 10x more.

> That said, I would argue that most or all 6to4 traffic could just as well
> > use IPv4, since both parties to the communication obviously have access
> to a
> > public IPv4 address. What is the advantage of using 6to4 over IPv4 that
> > makes it worth suffering an 80% failure rate?
>
> I'm having and have been having 100% success rate (or near enough to it
> that I can remember) using 6to4 for a number of years, including with
> an IPv6 MTU of as large as my PPPoE connection will support i.e. my
> 6to4 tunnel has an IPv6 MTU of 1472. Since noticing that youtube videos
> are coming over IPv6, I've paid a bit more attention to the "quality of
> experience" I've had, and have not found any reasons to change my
> preference back to native IPv4 instead of 6to4.
>

Sure - you're one of the 80% for whom it works. But that wasn't my question
- my question was "what is the advantage?" You said that you have near
enough 100% success rate, but I bet that your IPv4 success rate is near
enough 100% as well. So what are you gaining by using 6to4 to talk to
YouTube?

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

<div class=3D"gmail_quote">On Tue, Jun 14, 2011 at 3:40 PM, Mark Smith <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:ipng@69706e6720323030352d30312d31340a.n=
osense.org" target=3D"_blank">ipng@69706e6720323030352d30312d31340a.nosense=
.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>I don&#39;t know if it is intentional, =
however if I use Google&#39;s public</div>
8.8.8.8 and 8.8.4.4 resolvers, and prefer 6to4 over native IPv4<br>
(via /etc/gai.conf under Linux/glibc), it seems that the video content<br>
of all youtube videos is now being delivered over IPv6.<br></blockquote><di=
v><br></div><div>Yes, YouTube videos are currently being served on dual-sta=
ck hostnames.=A0The percentage of YouTube users that uses 6to4 is less than=
 0.02%. The percentage of YouTube users that uses native IPv6 is approximat=
ely 0.2% - over 10x more.</div>

<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<div>&gt; That said, I would argue that most or all 6to4 traffic could just=
 as well<br>
&gt; use IPv4, since both parties to the communication obviously have acces=
s to a<br>
&gt; public IPv4 address. What is the advantage of using 6to4 over IPv4 tha=
t<br>
&gt; makes it worth suffering an 80% failure rate?<br>
<br>
</div>I&#39;m having and have been having 100% success rate (or near enough=
 to it<br>
that I can remember) using 6to4 for a number of years, including with<br>
an IPv6 MTU of as large as my PPPoE connection will support i.e. my<br>
6to4 tunnel has an IPv6 MTU of 1472. Since noticing that youtube videos<br>
are coming over IPv6, I&#39;ve paid a bit more attention to the &quot;quali=
ty of<br>
experience&quot; I&#39;ve had, and have not found any reasons to change my<=
br>
preference back to native IPv4 instead of 6to4.<br>
</blockquote></div><br><div>Sure - you&#39;re one of the 80% for whom it wo=
rks. But that wasn&#39;t my question - my question was &quot;what is the ad=
vantage?&quot; You said that you have near enough 100% success rate, but I =
bet that your IPv4 success rate is near enough 100% as well. So what are yo=
u gaining by using 6to4 to talk to YouTube?</div>



--000e0cd23ef617fcdd04a5c75705--

From lorenzo@google.com  Wed Jun 15 16:10:53 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 817FD11E8183 for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 16:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EIr0ZbRwz3Hp for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 16:10:52 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF1011E812A for <ietf@ietf.org>; Wed, 15 Jun 2011 16:10:51 -0700 (PDT)
Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id p5FNAXB0003415 for <ietf@ietf.org>; Wed, 15 Jun 2011 16:10:33 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1308179434; bh=NlNp/hwNjfNH2eCut373Ij+OFBw=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=qe6kgTDQ4dTvP+KrBqW01S2tivmbHCVs8aYuwVlb2pSx8/NOG+VnWBNw0LJZUtzd8 LmDhFz+FN/Ol00hD0XcUw==
Received: from ywa12 (ywa12.prod.google.com [10.192.1.12]) by wpaz13.hot.corp.google.com with ESMTP id p5FNA1ue028616 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Wed, 15 Jun 2011 16:10:32 -0700
Received: by ywa12 with SMTP id 12so11405ywa.20 for <ietf@ietf.org>; Wed, 15 Jun 2011 16:10:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=W/jKYruZj85BFAEECs41mPi8QVatHKPJu6upyg8Iyo8=; b=aE5ZPAkd9Qz/Qtg5ve53huYgovo1TcZnEpB2Lpg7US2BEiYbT3JguZwA44Jt3cW5g6 tpRsTCFMJY7DycAbx+3g==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=W7kLAXBnZnWUnmg39QiYA/DK1pJi4Gdio2LOlt3TvGSQJMcej/DGOKsqCXiOpPAFDs oLP4RPYncEWasFg4tktg==
Received: by 10.150.7.15 with SMTP id 15mr211196ybg.378.1308179432104; Wed, 15 Jun 2011 16:10:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.147.16 with HTTP; Wed, 15 Jun 2011 16:10:12 -0700 (PDT)
In-Reply-To: <F5A79D68-C636-4C07-9C86-F394EF3ECFA3@network-heretics.com>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com> <F5A79D68-C636-4C07-9C86-F394EF3ECFA3@network-heretics.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Jun 2011 16:10:12 -0700
Message-ID: <BANLkTi=GGAY2U0sX54hnv7Bz7QDgrAjZ9H+8rwhmwkjK+9ssig@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=000e0cd287885a63de04a5c842ef
X-System-Of-Record: true
X-Mailman-Approved-At: Thu, 16 Jun 2011 08:10:32 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2011 23:10:53 -0000

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

On Wed, Jun 15, 2011 at 3:58 PM, Keith Moore <moore@network-heretics.com>wrote:

> > That said, I would argue that most or all 6to4 traffic could just as well
> use IPv4, since both parties to the communication obviously have access to a
> public IPv4 address. What is the advantage of using 6to4 over IPv4 that
> makes it worth suffering an 80% failure rate?
>
>
> it can communicate with hosts that have only IPv6,
> it can communicate with hosts that are stuck behind a single IPv4 address
> (if the router acts as a 6to4 gateway) without a NAT being in the way,
> it can be used to develop and test IPv6 applications without having to
> build a special-purpose network,
> it can be used to deploy applications now that already support IPv6 and so
> are in some sense future-proofed,
> it can be deployed on either a single host or a network
>

... about 80% of the time.

I would argue that cases 1, 3, 4, 5, and 6 can be solved more reliably using
configured tunnels, and that case 2 is today solved more reliably, and in
more cases (e.g., when no public IPv4 address is available at the border) by
the various NAT traversal mechanisms that are implemented in applications.
But I think we're just going around in circles here.

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

<div class=3D"gmail_quote">On Wed, Jun 15, 2011 at 3:58 PM, Keith Moore <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com">moore@netw=
ork-heretics.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">&gt; That said, I would argue that most or all 6to4 traff=
ic could just as well use IPv4, since both parties to the communication obv=
iously have access to a public IPv4 address. What is the advantage of using=
 6to4 over IPv4 that makes it worth suffering an 80% failure rate?<br>


<br>
<br>
</div>it can communicate with hosts that have only IPv6,<br>
it can communicate with hosts that are stuck behind a single IPv4 address (=
if the router acts as a 6to4 gateway) without a NAT being in the way,<br>
it can be used to develop and test IPv6 applications without having to buil=
d a special-purpose network,<br>
it can be used to deploy applications now that already support IPv6 and so =
are in some sense future-proofed,<br>
it can be deployed on either a single host or a network<br></blockquote><di=
v><br></div><div>... about 80% of the time.</div><div><br></div><div>I woul=
d argue that cases 1, 3, 4, 5, and 6 can be solved more reliably using conf=
igured tunnels, and that case 2 is today solved more reliably, and in more =
cases (e.g., when no public IPv4 address is available at the border) by the=
 various NAT traversal mechanisms that are implemented in applications. But=
 I think we&#39;re just going around in circles here.</div>

</div>

--000e0cd287885a63de04a5c842ef--

From lorenzo@google.com  Wed Jun 15 18:43:47 2011
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DABBF11E8181 for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 18:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dC3VN0jKrkwr for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 18:43:47 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 2982E11E817D for <ietf@ietf.org>; Wed, 15 Jun 2011 18:43:47 -0700 (PDT)
Received: from kpbe16.cbf.corp.google.com (kpbe16.cbf.corp.google.com [172.25.105.80]) by smtp-out.google.com with ESMTP id p5G1hjE8013797 for <ietf@ietf.org>; Wed, 15 Jun 2011 18:43:46 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1308188626; bh=Z2zFNLo3NCiexyG3IwpGEjjL5fE=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=eYPjhA9UVZBaq7e2achA1mI2LmU1SZiU9MQMvM3lsJGmwhYvqPn/z7rsPue78jN/x VnVlL4YeKGPUhsOR0BANA==
Received: from pwj5 (pwj5.prod.google.com [10.241.219.69]) by kpbe16.cbf.corp.google.com with ESMTP id p5G1hhYQ004191 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Wed, 15 Jun 2011 18:43:44 -0700
Received: by pwj5 with SMTP id 5so378635pwj.26 for <ietf@ietf.org>; Wed, 15 Jun 2011 18:43:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=btjCGuUpmdoLv4umMV9KJWuAtCOM0tJFqMU7RTtHyao=; b=gMFiq8MDfW3s9bv4cyAl1u1KThHMG9PIf38pZu7T6jhisa79TDn0Gkj3lpaEW7Ig/j 8Ug2CblOkGV+i1wnvECw==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=SMGNdyRYFWCOL6AT1PE0EOP+se+Ov9NSJ+GwUQiijGICWssEEzXpxEgFuVzGRvlspl gABYGrwEAWN89cKH1SPQ==
Received: by 10.142.231.2 with SMTP id d2mr60230wfh.262.1308188623524; Wed, 15 Jun 2011 18:43:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.216.13 with HTTP; Wed, 15 Jun 2011 18:43:23 -0700 (PDT)
In-Reply-To: <20110616012140.63F3510CDCB3@drugs.dv.isc.org>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com> <F5A79D68-C636-4C07-9C86-F394EF3ECFA3@network-heretics.com> <BANLkTi=GGAY2U0sX54hnv7Bz7QDgrAjZ9H+8rwhmwkjK+9ssig@mail.gmail.com> <20110616012140.63F3510CDCB3@drugs.dv.isc.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Jun 2011 18:43:23 -0700
Message-ID: <BANLkTin6wOCPifSd0odrTZzUS_02vXh7j_Qg5_f_gRBOUkq2ag@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
To: Mark Andrews <marka@isc.org>
Content-Type: multipart/alternative; boundary=000e0cd17f2034553404a5ca66f2
X-System-Of-Record: true
X-Mailman-Approved-At: Thu, 16 Jun 2011 08:10:33 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Keith Moore <moore@network-heretics.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2011 01:43:48 -0000

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

On Wed, Jun 15, 2011 at 6:21 PM, Mark Andrews <marka@isc.org> wrote:

> > ... about 80% of the time.
>
> Or 99.999% of the time once you get it setup.  The problem isn't 6to4, it's
> *automatic* 6to4.
>

No, because you often end up being dependent on the whims of BGP and
third-party relays for your return path. Sure, if you have enough control
over routing in a closed network, you can make sure the right relays are
used. But in that case, why not use configured tunnels?


> 6to4 historic is throwing the baby out with the bath water.
>

On this we know we disagree.

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

<div class=3D"gmail_quote">On Wed, Jun 15, 2011 at 6:21 PM, Mark Andrews <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:marka@isc.org">marka@isc.org</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">&gt; ... about 80% of the time.<br>
<br>
</div>Or 99.999% of the time once you get it setup. =A0The problem isn&#39;=
t 6to4, it&#39;s<br>
*automatic* 6to4.<br></blockquote><div><br></div><div>No, because you often=
 end up being dependent on the whims of BGP and third-party relays for your=
 return path. Sure, if you have enough control over routing in a closed net=
work, you can make sure the right relays are used. But in that case, why no=
t use configured tunnels?</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">6to4 historic is throwing the baby out with the bath wate=
r.</div></blockquote><div><br></div><div>On this we know we disagree.</div>=
</div>

--000e0cd17f2034553404a5ca66f2--

From ipng@69706e6720323030352d30312d31340a.nosense.org  Wed Jun 15 19:45:22 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.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 87D1211E8136; Wed, 15 Jun 2011 19:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8pxEo2HRLcHH; Wed, 15 Jun 2011 19:45:22 -0700 (PDT)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by ietfa.amsl.com (Postfix) with ESMTP id A2CD311E811E; Wed, 15 Jun 2011 19:45:21 -0700 (PDT)
Received: from 114-30-99-224.ip.adam.com.au ([114.30.99.224] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1QX2a6-0005ce-BO; Thu, 16 Jun 2011 12:15:18 +0930
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id C07013B33E; Thu, 16 Jun 2011 12:15:17 +0930 (CST)
Date: Thu, 16 Jun 2011 12:15:17 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Message-ID: <20110616121517.079ba496@opy.nosense.org>
In-Reply-To: <BANLkTin6wOCPifSd0odrTZzUS_02vXh7j_Qg5_f_gRBOUkq2ag@mail.gmail.com>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com> <F5A79D68-C636-4C07-9C86-F394EF3ECFA3@network-heretics.com> <BANLkTi=GGAY2U0sX54hnv7Bz7QDgrAjZ9H+8rwhmwkjK+9ssig@mail.gmail.com> <20110616012140.63F3510CDCB3@drugs.dv.isc.org> <BANLkTin6wOCPifSd0odrTZzUS_02vXh7j_Qg5_f_gRBOUkq2ag@mail.gmail.com>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.4; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 16 Jun 2011 08:10:28 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, Keith Moore <moore@network-heretics.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2011 02:45:22 -0000

On Wed, 15 Jun 2011 18:43:23 -0700
Lorenzo Colitti <lorenzo@google.com> wrote:

> On Wed, Jun 15, 2011 at 6:21 PM, Mark Andrews <marka@isc.org> wrote:
> 
> > > ... about 80% of the time.
> >
> > Or 99.999% of the time once you get it setup.  The problem isn't 6to4, it's
> > *automatic* 6to4.
> >
> 
> No, because you often end up being dependent on the whims of BGP and
> third-party relays for your return path.

If you generalise that statement a bit,

"No, because you often end up being dependent on the whims of BGP and
third-party routers for your return path."

you're describing the trust inherent in the operation of the Internet,
both for IPv4 and IPv6.

Yes there are some incompetent operators out there, but most of them
aren't - they wouldn't keep their jobs otherwise, and the Internet
would break more often than it does. I can only remember one instance
of 6to4 relay breakage in the last 5 years, and IIRC that was fixed
within 24 hours.

People seem to be using a very coarse "less than absolute 100% success
means total technology failure" to state that 6to4 as a whole is
unreliable. Where is the data to back this up? Did Geoff Huston do any
more detailed analysis of the 6to4 data, other than measuring success
verses failure rates for 6to4 connections? Could I, for example, have
warped his 6to4 failure rates during the test if I used all my 2^16 x
2^64 IPv6 6to4 addresses to purposely create excessive failed 6to4
connections apparently from many different hosts? I'm certainly not
saying that exists in Geoff's data, rather asking how do we know that
it doesn't?

I have a vested interest in anycast 6to4 continuing to exist, because it
has been as reliable as any other Internet technology I use. I also
think it has some latency advantages over configured tunnels because my
IPv6 traffic enters the IPv6 Internet where ever the closest 6to4 relay
reachable via IPv4 is. That used to be in Europe (around 14000 Km from
me) when I first started using 6to4, now it is only around 3000 Km,
and as my ISP is going to deploy a 6to4 relay in the near future,
will be around 8Km away. These changes have and will continue to be
transparent on my end. I'd also get these latency benefits if I was
changing my IPv4 Internet points of attachment, such as if I were
travelling internationally.

Anycast 6to4 also tends to distribute the IPv6 traffic load better
across all the 6to4 globally gateways, instead of concentrating it at
likely lower number of configured tunnel entry/exit points. Over time,
increased IPv6 traffic will become a disincentive to running a
configured tunnel entry/exit point because people will continue to use
it even if there is a more local configured tunnel or 6to4 relay they
could be using. If people use anycast 6to4, then they inherently get
lower latency as a closer one becomes available, and 6to4 relay
operators will see lower traffic load without intervention as more 6to4
relays are deployed.


> Sure, if you have enough control
> over routing in a closed network, you can make sure the right relays are
> used. But in that case, why not use configured tunnels?
> 
> 
> > 6to4 historic is throwing the baby out with the bath water.
> >
> 
> On this we know we disagree.

From gert@space.net  Wed Jun 15 23:51:36 2011
Return-Path: <gert@space.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0F7B11E807E for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 23:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level: 
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kHJ2MUdsjYja for <ietf@ietfa.amsl.com>; Wed, 15 Jun 2011 23:51:33 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by ietfa.amsl.com (Postfix) with ESMTP id 816C511E807B for <ietf@ietf.org>; Wed, 15 Jun 2011 23:51:31 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id BFB69F8179 for <ietf@ietf.org>; Thu, 16 Jun 2011 08:51:26 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id A5E5CF81D8 for <ietf@ietf.org>; Thu, 16 Jun 2011 08:51:26 +0200 (CEST)
Received: (qmail 78884 invoked by uid 1007); 16 Jun 2011 08:51:26 +0200
Date: Thu, 16 Jun 2011 08:51:26 +0200
From: Gert Doering <gert@space.net>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Message-ID: <20110616065126.GB45955@Space.Net>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com> <F5A79D68-C636-4C07-9C86-F394EF3ECFA3@network-heretics.com> <BANLkTi=GGAY2U0sX54hnv7Bz7QDgrAjZ9H+8rwhmwkjK+9ssig@mail.gmail.com> <20110616012140.63F3510CDCB3@drugs.dv.isc.org> <BANLkTin6wOCPifSd0odrTZzUS_02vXh7j_Qg5_f_gRBOUkq2ag@mail.gmail.com> <20110616121517.079ba496@opy.nosense.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110616121517.079ba496@opy.nosense.org>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Thu, 16 Jun 2011 08:10:30 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>, Lorenzo Colitti <lorenzo@google.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 Jun 2011 06:51:37 -0000

Hi,

On Thu, Jun 16, 2011 at 12:15:17PM +0930, Mark Smith wrote:
> I have a vested interest in anycast 6to4 continuing to exist, 

This actually brings up a good argument:

  are you going to pay for us to run our 6to4 relay?


not that the cost of it is high, but there is cost to it - to make sure
it keeps working, to monitor the system for overload, etc.

Our customers don't really need it (because we have native IPv6), we're
offering this for free to benefit users on the other side that do not
have native IPv6, but insist on not using IPv4.


And this also points out why anycasted 6to4 is necessarily(!) less 
reliable than those other Internet technologies that you have mentioned -
because those that run the relays usually have no financial interest in
doing so.  So if it breaks, it will take longer to notice and even longer
to fix than for something that directly affects paying customers.

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279

From ipng@69706e6720323030352d30312d31340a.nosense.org  Thu Jun 16 00:35:56 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.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 A1EEE11E808C; Thu, 16 Jun 2011 00:35:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HPDoCEvHMn6k; Thu, 16 Jun 2011 00:35:55 -0700 (PDT)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by ietfa.amsl.com (Postfix) with ESMTP id 56BC211E807E; Thu, 16 Jun 2011 00:35:55 -0700 (PDT)
Received: from 114-30-99-224.ip.adam.com.au ([114.30.99.224] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1QX77C-0005Jj-Ne; Thu, 16 Jun 2011 17:05:46 +0930
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 463303B33E; Thu, 16 Jun 2011 17:05:46 +0930 (CST)
Date: Thu, 16 Jun 2011 17:05:45 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Gert Doering <gert@space.net>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-6to4-to-historic-04.txt> (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Message-ID: <20110616170545.6f926f2a@opy.nosense.org>
In-Reply-To: <20110616065126.GB45955@Space.Net>
References: <20110610161806.99D1618C0F6@mercury.lcs.mit.edu> <BANLkTi=PAKcKV7XkLEyJY36qdmfNXfh27yLTAdc69Pa2-DxQsA@mail.gmail.com> <F83AD350-7378-4B4C-8D09-DB56FCECFE9E@apple.com> <BANLkTimCo0wht5uXT=twZr-96LUNt0QzdZFa=FpXXXVFaQVv_A@mail.gmail.com> <F5A79D68-C636-4C07-9C86-F394EF3ECFA3@network-heretics.com> <BANLkTi=GGAY2U0sX54hnv7Bz7QDgrAjZ9H+8rwhmwkjK+9ssig@mail.gmail.com> <20110616012140.63F3510CDCB3@drugs.dv.isc.org> <BANLkTin6wOCPifSd0odrTZzUS_02vXh7j_Qg5_f_gRBOUkq2ag@mail.gmail.com> <20110616121517.079ba496@opy.nosense.org> <20110616065126.GB45955@Space.Net>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.4; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 16 Jun 2011 08:10:29 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>, Lorenzo Colitti <lorenzo@google.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 Jun 2011 07:35:56 -0000

Hi Gert,

On Thu, 16 Jun 2011 08:51:26 +0200
Gert Doering <gert@space.net> wrote:

> Hi,
> 
> On Thu, Jun 16, 2011 at 12:15:17PM +0930, Mark Smith wrote:
> > I have a vested interest in anycast 6to4 continuing to exist, 
> 
> This actually brings up a good argument:
> 
>   are you going to pay for us to run our 6to4 relay?
> 
> 
> not that the cost of it is high, but there is cost to it - to make sure
> it keeps working, to monitor the system for overload, etc.
>

It was a conscious decision of yours to announce it globally, so you've
made a conscious decision to provide it to people for free and to take
on the operational responsibilities of doing so. If you become unhappy
with accepting those costs without corresponding compensation, withdraw
the 6to4 anycast IPv4 address from the global route table, and people
like me would move onto another 6to4 relay automatically.

I certainly don't take for granted people's generosity in providing them
to global users, however I think that if you choose to do something
charitable, you have then created an obligation on yourself to do it
well and reliably. Most people both understand and deliver on that
obligation.

I've actually become more conscious of this lack of financial incentive
since I've noticed that youtube videos are coming to me over IPv6.
That's what prompted me to ask if my ISP was planning to deploy a 6to4
relay soon as an interim step towards their native service.

> Our customers don't really need it (because we have native IPv6), we're
> offering this for free to benefit users on the other side that do not
> have native IPv6, but insist on not using IPv4.
> 
> 
> And this also points out why anycasted 6to4 is necessarily(!) less 
> reliable than those other Internet technologies that you have mentioned -
> because those that run the relays usually have no financial interest in
> doing so. So if it breaks, it will take longer to notice and even longer
> to fix than for something that directly affects paying customers.
> 

Actually, a broken local 6to4 relay is likely to be impacting your
paying customers too as it is their local 6to4 relay.

Your arguments are not specific to 6to4 though - I think they apply to
anybody providing a free configured tunnel service too. In some cases
they apply more so - the administrative effort to support automated
provisioning of configured tunnels is greater than that involved in
setting up an anycast 6to4 relay.

Regards,
Mark.

From evnikita2@gmail.com  Thu Jun 16 20:20:48 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA54011E807D; Thu, 16 Jun 2011 20:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.489
X-Spam-Level: 
X-Spam-Status: No, score=-3.489 tagged_above=-999 required=5 tests=[AWL=0.110,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VEe+PjKO3FO2; Thu, 16 Jun 2011 20:20:47 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6ABDA11E8079; Thu, 16 Jun 2011 20:20:46 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1697426fxm.31 for <multiple recipients>; Thu, 16 Jun 2011 20:20:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=WdV6NsnjeBCPj6HnqIZIrKgZb44FJN13AQkKC5ssCpE=; b=NRiwqGnqLDDT2E1c1Ir2UaY7hr7PN3zUJsjCzcawZ1vqCw/uzhgQ6wV77v96ENXHgI MWLIizMdrSqs6N+9WSFuzTy7VWPFuGWOU4gYlZaoVEtoPevLjQ+1dY7pYC8ZB45dHPNV wK7czNCp8rO9TKn77esUF1Kgqkz7rQJ1hZcgc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=cY3U5Miiuh3GLUdC3QtoBNVocEXi6Tbn+vL1hTpKx+gXD7Fq2KBDJc088TQwzcnukt DCeR7hMR7QvtBp52bmTRE12nF69uvg2y6Yc03UiQsixiOiioAJP+2QQ4RYovhw1SUh2P GH5oDa7ZDr2YvF1qUGIQxjSCbtU9lBbvVP4rw=
Received: by 10.223.33.80 with SMTP id g16mr1894230fad.125.1308280845518; Thu, 16 Jun 2011 20:20:45 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id o23sm1105859faa.33.2011.06.16.20.20.43 (version=SSLv3 cipher=OTHER); Thu, 16 Jun 2011 20:20:44 -0700 (PDT)
Message-ID: <4DFAC83A.6010208@gmail.com>
Date: Fri, 17 Jun 2011 06:21:30 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-rfc3536bis-02.txt> (Terminology Used	in Internationalization in the IETF) to BCP
References: <20110616130400.4851.68985.idtracker@ietfa.amsl.com>
In-Reply-To: <20110616130400.4851.68985.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: iesg <iesg@ietf.org>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 03:20:48 -0000

Hello all,

I have an only concern with regard to this document which I expressed 
before, during WG discussions, and which I'd like to bring to IESG's 
attention now.

For a number of times I proposed improving the "control character" 
definition in Section 4.1:

>     control character
>
>        The 65 characters in the ranges U+0000..U+001F and U+007F..U+009F.
>        The basic space character, U+0020, is often considered as a
>        control character as well, making the total number 66.  They are
>        also known as control codes.  In terminology adopted by Unicode
>        from ASCII and the ISO 8859 standards, these codes are treated as
>        belonging to three ranges: "C0" (for U+0000..U+001F), "C1" (for
>        U+0080...U+009F), and the single control character "DEL" (U+007F).
>        <UNICODE>
My proposals included 
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg02558.html 
and 
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg02589.html.  The 
main justification I provided is that, in accordance with Abstract: 
"This document provides a glossary of terms [...]" so we need to specify 
"what does the control character mean" but not "what Unicode codepoints 
are assigned for control characters".  Yet, on the apps-discuss mailing 
list there were some concerns regarding the fact that control characters 
are unfamiliar to internalization so my proposed definition is not an 
option (one of the authors shares this opinion).  Thus, why does it 
occur in its current form?  So, there are two possible variants, I 
think: (1) remove the "control character" definition from the document 
as irrelevant to internalization or (2) produce a really good definition 
of this term (consider we're trying to give the terms normative meaning 
within IETF, since the intended status is BCP).  I didn't manage to 
persuade the authors or WG to undertake any of the aforementioned 
options and I hope IESG should decide on this.

Also, as a minor remark on references.  The document makes normative 
reference to an obsolete document - ISO/IEC 10646:2003 whereas ISO/IEC 
10646:2011 is published.  The reference should be corrected.

Thanks,
Mykyta Yevstifeyev

16.06.2011 16:04, The IESG wrote:
> The IESG has received a request from the Applications Area Working Group
> WG (appsawg) to consider the following document:
> - 'Terminology Used in Internationalization in the IETF'
>    <draft-ietf-appsawg-rfc3536bis-02.txt>  as a BCP
>
> 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 2011-06-30. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document provides a glossary of terms used in the IETF when
>     discussing internationalization.  The purpose is to help frame
>     discussions of internationalization in the various areas of the IETF
>     and to help introduce the main concepts to IETF participants.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-rfc3536bis/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-rfc3536bis/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>


From evnikita2@gmail.com  Thu Jun 16 20:30:09 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C68A411E8080 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 20:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.474
X-Spam-Level: 
X-Spam-Status: No, score=-3.474 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3jHDoAz8Nel for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 20:30:04 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5232E11E807D for <ietf@ietf.org>; Thu, 16 Jun 2011 20:30:04 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1700281fxm.31 for <ietf@ietf.org>; Thu, 16 Jun 2011 20:30:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=0SPc8u7RpMLZT+jy5HjClnCq5cvQgmVOsKnbfi2Htkg=; b=DXlq+S/wERW9DInVn+mjgMtzxkLvJtjMbGJ1SQoseAdC5mkrRKREsJG45IyK9H8b+E XXNPqW0Je7plGSg5sPmX4D7n0Srnzsh37KUBV0wCiy/Y5gFKSXBCRJdOuZULiO4ftig2 g/m7AxaUCvPNONpwTAZS3bEm11xNsgM3aOi84=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=JfIvgN0nFU8B/0JLb9+kba1hyU6Cy4W+dFa69a5fZS30sRgRU9bldiT4RQhd42VaWD y7laxDRu0Z11dqDCgcnELhmduYbowOEL/ATw4AFZnAz+SwUE/3WM9xpz4cPnANhaMb3t V6rJcXDm70PfBVyr20BK7z5/KfO2jTVK8Nvmk=
Received: by 10.223.64.66 with SMTP id d2mr770804fai.116.1308281403391; Thu, 16 Jun 2011 20:30:03 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id g8sm1108488fai.44.2011.06.16.20.30.01 (version=SSLv3 cipher=OTHER); Thu, 16 Jun 2011 20:30:02 -0700 (PDT)
Message-ID: <4DFACA68.3040206@gmail.com>
Date: Fri, 17 Jun 2011 06:30:48 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu>	<4DF87637.2000301@gmail.com>	<4DF8D6C6.5080005@mit.edu>	<4DF9C5EE.9010703@lachy.id.au> <4DF9C96C.9090607@gmx.de>	<4DF9CACE.2000004@lachy.id.au> <4DF9CE7F.6080704@gmx.de>
In-Reply-To: <4DF9CE7F.6080704@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, 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, 17 Jun 2011 03:30:11 -0000

16.06.2011 12:35, Julian Reschke wrote:
> On 2011-06-16 11:20, Lachlan Hunt wrote:
>> On 2011-06-16 11:14, Julian Reschke wrote:
>>> On the other hand, you're trying to define a URI scheme. If it's
>>> handling conflicts with the base URI spec, that's a bug. Period. You 
>>> may
>>> *document* that some UAs have this bug, but you can't change it to be
>>> not a bug.
>>
>> Theoretical purity is not a priority for the specs I edit. Wilful
>> violations of other specs where necessary are acceptable.
>
> Lachlan, with all due respect, I really do not care what *your* 
> priorities here are.
>
> If you define a URI scheme, you'll have to be consistent with URI 
> syntax. There's really no wiggle room except for warning about 
> implementations that may not do it right.
Please note that we're trying to produce the specification of the scheme 
which is used internally by the browsers.  Thus, it is almost impossible 
to consider all existing behavior of all existing browsers.  In order to 
avoid such situation as we currently have with Gecko, when an 
application is known to fail to satisfy one of the regulations of the 
Standards Track document, I think we could make the document 
Informational, which will specify "the most common" practice while 
mentioning some other "non-common" behavior.  In this way we will fail 
to "standardize" the scheme, but at least won't create a lot of 
conflicts, which, IMO, is more important.

As for the normalization of the about URIs.  They are a subject to RFC 
3986, being URIs, and are a subject to its normalization rules.  Making 
an exception for them isn't an option, I think.

Mykyta Yevstifeyev
>
> Best regards, Julian
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From barryleiba.mailing.lists@gmail.com  Thu Jun 16 20:41:15 2011
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 3AA0011E80E8; Thu, 16 Jun 2011 20:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.904
X-Spam-Level: 
X-Spam-Status: No, score=-102.904 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rFAS4XTtRsqj; Thu, 16 Jun 2011 20:41:14 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 845FA11E80DC; Thu, 16 Jun 2011 20:41:14 -0700 (PDT)
Received: by gyf3 with SMTP id 3so952985gyf.31 for <multiple recipients>; Thu, 16 Jun 2011 20:41:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=wgn7wIVBXv2GXZRO0FfrE3tDAWoFf0DBJ7p91VqO/1E=; b=iWy1GtfTTSXH5iLAzZif7VHXnb1hgRWVt5Pgust1QUrqbTMIoI9BCJ7bj2VMcl/uIv 4a3rUx63dNphHXz0LbpGHjjkRMWWPRjVqzNcdywjPYb95EZ/3Je0zFzB7dx5ZlnurVUH EA39FsYcO8Y1zcbdPgabPA89u7aGdci2KPYp4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=bsL9hLrH+iwbo1OLs7fYdlSkXQxqoLwWBP5EDUsqz0V3llgZjSD14UWoit44iD181M WzEar0mcc9TqDpINTJ5cRRFvFwlSuHSXHRzVXzKjaGLm/Xfm6SF1NzSc+2F2BFFLys9w JN1n7mJS42Na9KXl7zH9LDPNPzhN0DxgtK7QA=
MIME-Version: 1.0
Received: by 10.236.80.69 with SMTP id j45mr2767196yhe.50.1308282073930; Thu, 16 Jun 2011 20:41:13 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.99.3 with HTTP; Thu, 16 Jun 2011 20:41:13 -0700 (PDT)
In-Reply-To: <4DFAC83A.6010208@gmail.com>
References: <20110616130400.4851.68985.idtracker@ietfa.amsl.com> <4DFAC83A.6010208@gmail.com>
Date: Thu, 16 Jun 2011 23:41:13 -0400
X-Google-Sender-Auth: ytg7NALuHkKPawrQ5lZGcFHkqVQ
Message-ID: <BANLkTimQfTfnc4U7UDGBXvgEP-b-v7DdCw@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-rfc3536bis-02.txt> (Terminology Used in Internationalization in the IETF) to BCP
From: Barry Leiba <barryleiba@computer.org>
To: apps-discuss@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, 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: Fri, 17 Jun 2011 03:41:15 -0000

On Thu, Jun 16, 2011 at 11:21 PM, Mykyta Yevstifeyev
<evnikita2@gmail.com> wrote:
> I have an only concern with regard to this document which I expressed
> before, during WG discussions, and which I'd like to bring to IESG's
> attention now.
>
> For a number of times I proposed improving the "control character"
> definition in Section 4.1:

And in the WG discussions, Mykyta was in the rough when it came to a
consensus judgment.  I, as chair and doc shepherd, actually supported
some change initially, but was convinced that the final text that's in
the document is best.  The document isn't meant to be a history
lesson, but to make it clear what certain terms refer to.  The current
"control character" text accomplishes that, and there's been no
support for Mykyta's suggested change.

Barry, appsawg chair

From evnikita2@gmail.com  Thu Jun 16 20:47:43 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C2F411E8158 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 20:47:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.179
X-Spam-Level: 
X-Spam-Status: No, score=-3.179 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0YQCaUjOOxo3 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 20:47:42 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id DEAAF11E80DC for <ietf@ietf.org>; Thu, 16 Jun 2011 20:47:41 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1705300fxm.31 for <ietf@ietf.org>; Thu, 16 Jun 2011 20:47:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4J1g+ayRMO52mCMzvfwxhIakoU75YcICIuumLb/oRos=; b=TRcBjgJWV90nAtHpwbAlLJNvBDX9jb4gzm141QwmCS3VPmpWkXTVopDfl6bjpkyNCT 8tFOTyhvvY/7mDbSOMDMV2zWQoBF82molS0P10EtQF0rGU2PHQsFYu7gQr65lM4Kr8Kq lhpwStWCnAJWt/HTNAPj9FYiIl0Bu0ysWo520=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=PUh/c1xkm3Ahns+s6S5MGd8w5p8wEiWe9SupYb1TvtNVIAq56oo7hnLXquOg/LKSrc F4gcNNSLzhOU/ThyAZtXR2D1+dGvcrazxK4FqHgVz7n1N5vAROB/uhlpUlnqsBTj3q0K o6o7NoX9aduzfbsm1pLMjUHaGcN7K4FEy+Ww4=
Received: by 10.223.54.148 with SMTP id q20mr1918174fag.84.1308282460907; Thu, 16 Jun 2011 20:47:40 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id f7sm612158fai.0.2011.06.16.20.47.38 (version=SSLv3 cipher=OTHER); Thu, 16 Jun 2011 20:47:39 -0700 (PDT)
Message-ID: <4DFACE89.4070908@gmail.com>
Date: Fri, 17 Jun 2011 06:48:25 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF885B5.4020202@gmx.de> <4DF8CA3D.7020904@gmail.com> <20110615201644.GB69872@shinkuro.com>
In-Reply-To: <20110615201644.GB69872@shinkuro.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Julian Reschke <julian.reschke@gmx.de>, Alexey Melnikov <alexey.melnikov@isode.com>, Boris Zbarsky <bzbarsky@MIT.EDU>, draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 03:47:43 -0000

15.06.2011 23:16, Andrew Sullivan wrote:
> On Wed, Jun 15, 2011 at 06:05:33PM +0300, Mykyta Yevstifeyev wrote:
>> 15.06.2011 13:13, Julian Reschke wrote:
>>> That being said, if our Mozilla friends do not want to fix this it
>>> might be a good idea to warn readers that certain implementations
>>> fail to properly unescape, thus it's unwise to rely on that
>>> behavior (why would you anyway?).
>> I fully agree with you, Julian.  I think we'll do certainly as you
>> propose, unless Boris will provide some strong reasons to do in
>> other way.
> If I am reading the document and the above correctly, then you are
> proposing the following:
>
>      1.  The document proposes to make standard rules about what
>      applications do with input that is, by definition, completely
>      internal to that application; and,
>
>      2.  You propose in addition to state what is the standard, but
>      note that nobody should rely on it because one of the largest
>      implementers of the scheme doesn't follow the supposed standard.
Currently and actually I have nearly the same concern.  The -02 version 
still had Informational intended status, I don't know what was a reason 
for switching to Standards Track.  I have a feeling that producing the 
Informational RFC describing "the most common behavior" is an option, 
but we'll fail to "standardize" the scheme.  I personally think 
standardizing the internal-usage scheme is a bit irrelevant, so here i 
agree with you.
> Do I have this correct?  If so, I would like to request that the
> WINDMILL or perhaps TILT WG be chartered to deal with this manner of
> work.
>
> More substantively, I fail to understand how this specification
> proposes to create a class of "reserved" about: URIs when the about:
> scheme seems to be internal information to an application.  I think
> the Security Considerations section doesn't address any of that, and
> probably ought to, particularly in light of the proposal to add text
> that users ought not to depend on "standard" behaviour.
That's an interesting point as well.  Trying to standardize the abut URI 
scheme, we're trying to state that URI about:nnnn is used only and only 
fir the purpose xxxx whereas about:mmmm is used only for purpose yyyy.  
I understand your concern regarding different purposes of one about URI 
in different apps.  I can share it with you as well.  As a result, 
abandoning the intends to give the scheme a Standards Track 
specification and complete revision of regulations with regard to 
resolving about URIs may be an option.

Mykyta Yevstifeyev
> Best,
>
> A
>


From barryleiba.mailing.lists@gmail.com  Thu Jun 16 21:01:09 2011
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 D32AB11E8168 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 21:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.611
X-Spam-Level: 
X-Spam-Status: No, score=-102.611 tagged_above=-999 required=5 tests=[AWL=-0.234, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ey+gyDMFE5uU for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 21:01:06 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2948711E8085 for <ietf@ietf.org>; Thu, 16 Jun 2011 21:01:06 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1548025gxk.31 for <ietf@ietf.org>; Thu, 16 Jun 2011 21:01:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xT6918Ue6ckNyIzu9zkBJfmnSd69E0pxIvFn5CwRBKw=; b=KcggqcDzzuCFAIO1x2Qe9o0GlvqBrrYSgbZUVVzPoLaPQwK4O8WkI8O67wjaQH+PV2 yT05DrkNpdlLtOypMi9O3NwAI/DPzvOoO/IJuQtmI6Sqh2e5rRTsRu057+12oTfu+aCc If37idEYTxP0R0BeQKUF/DKa3i/DM1oXQ1FTU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Nezk/Atzafnhua6qFE04dvzd/umOFIULDNC+u9mca7XmOFgLnj3okhoUYNOwSvjYJT USJD47blYAyNiumcsTPe5KvoQRz7XjBU4EKSwCCVY5VUfxsDiIxsb4L5T4xKbiynMmsn onSIE6aj0tWY+PFBVNnf3ikjE1PbQNHbc/FJ0=
MIME-Version: 1.0
Received: by 10.236.80.69 with SMTP id j45mr2790250yhe.50.1308283265609; Thu, 16 Jun 2011 21:01:05 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.99.3 with HTTP; Thu, 16 Jun 2011 21:01:05 -0700 (PDT)
In-Reply-To: <20110615201644.GB69872@shinkuro.com>
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF885B5.4020202@gmx.de> <4DF8CA3D.7020904@gmail.com> <20110615201644.GB69872@shinkuro.com>
Date: Fri, 17 Jun 2011 00:01:05 -0400
X-Google-Sender-Auth: lGi2qBdEkXbwuGcJx-c92WG-o2o
Message-ID: <BANLkTineJQ0BGSrO_V4h1LnjCnnZmm-GGQ@mail.gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, Boris Zbarsky <bzbarsky@mit.edu>, Alexey Melnikov <alexey.melnikov@isode.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 Jun 2011 04:01:10 -0000

> More substantively, I fail to understand how this specification
> proposes to create a class of "reserved" about: URIs when the about:
> scheme seems to be internal information to an application. =A0I think
> the Security Considerations section doesn't address any of that, and
> probably ought to, particularly in light of the proposal to add text
> that users ought not to depend on "standard" behaviour.

Yes... I'm actually very confused about the point of this document.
It's documenting a URI scheme that's used ONLY internally, and,
therefore, has no interoperability requirements.  As best I can tell,
the issue here is to let browser makers know what other browsers do,
so that maybe new browsers will decide to do the same things.  That's
fine, and that helps users have a consistent experience across
browsers.  But it strikes me as Informational, not Standards Track.
MUSTs and MUST NOTs seem completely out of place here, to me.

If different browsers exhibit different behaviour with the same
about:xxxx URI, that's as it is, and the variations should be
documented.  Developers of new browsers will have to decide which
older browsers to emulate.

But none of this actually speaks to interoperability among browsers or
web servers or applications or....

Barry

From evnikita2@gmail.com  Thu Jun 16 21:02:18 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7624611E80F2 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 21:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.472
X-Spam-Level: 
X-Spam-Status: No, score=-3.472 tagged_above=-999 required=5 tests=[AWL=0.127,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1b+iRCzBUeDB for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 21:02:18 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id A81A211E816C for <ietf@ietf.org>; Thu, 16 Jun 2011 21:02:17 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1709765fxm.31 for <ietf@ietf.org>; Thu, 16 Jun 2011 21:02:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=SE1Zefuz1NjU1652496sEv/3MnFuqlkdlUyWDFOSlb0=; b=Y9Sd5/EGtllQx6wgJifjhgL/cxweSC316Zc/Mc8GrS/PAdFL/rKXZFy0kuDU5QJrep Bf06q6U8KJjrVw61D7nM8WYZVqgAfgcpF102IOOrbwCIEHkflc7xCMA7mVYrHCr2Vi3Y vf/L4gPrmFj+ffe/xsU3D9bG86LxuCK+g2KrI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=GWwg/0k9j+MGy7thOVymVL68ryQJV/HsMTJjn/2j65sp4MqnA3CQYb49lHt/z9EKs1 h+pRWK+RMQrHZdZ6xpmDLhe7zFSfgr7uoyL5/KW93a2QAuyQhjNAFbC3WMv5twdJ3vZI mGQyIBaHdovZjvapsooogL1VSrvntQDeHaR+w=
Received: by 10.223.102.131 with SMTP id g3mr1926715fao.68.1308283336820; Thu, 16 Jun 2011 21:02:16 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id h1sm1115949fag.11.2011.06.16.21.02.15 (version=SSLv3 cipher=OTHER); Thu, 16 Jun 2011 21:02:16 -0700 (PDT)
Message-ID: <4DFAD1F6.70203@gmail.com>
Date: Fri, 17 Jun 2011 07:03:02 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF8D6C6.5080005@mit.edu> <4DF9C5EE.9010703@lachy.id.au>
In-Reply-To: <4DF9C5EE.9010703@lachy.id.au>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, 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, 17 Jun 2011 04:02:18 -0000

16.06.2011 11:59, Lachlan Hunt wrote:
> On 2011-06-15 17:59, Boris Zbarsky wrote:
>> On 6/15/11 5:07 AM, Mykyta Yevstifeyev wrote:
>>> The point of this comment is to propose abandoning normalization of
>>> 'about' URIs because of some ad hoc behavior of an only application -
>>> Gecko.
>>
>> No, it's to propose abandoning normalization because it's not
>> necessarily compatible with existing deployed uses of about:,
Probably.  Because of this in my previous messages I proposed abandoning 
making the spec. Standards Track.
>> not
>> clearly compatible with the web security model,
How?
>> and because the
>> normalization is not defined in the spec. 
Normalization is defined in RFC 3986.
>> The Gecko behavior is just an
>> illustration of the first point.
>>
>>> The purpose of our draft is to give a stable specification of the
>>> scheme
>>
>> Yes, this is fine.
But see above.
>>
>>> and normalize all existing types of behavior with regard to
>>> handling 'about' URIs. It will be easier for Gecko to change its
>>> behavior rather than for other apps to do this.
>
> Mykyta, we do need to make this spec document reality, particularly 
> where implementations are unwilling to make changes.
I agree; but different existing behavior makes this impossible.  We 
can't list everything which is currently supported by all 
implementations in the Standards Track document, but we can do this in 
the Informational.

Mykyta
> If it doesn't do that, then the spec is useless.  I will be reviewing 
> the options and look into exactly how other browsers handle these 
> cases, and make appropriate changes to the spec.
>


From msk@cloudmark.com  Thu Jun 16 21:37:57 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ABE211E8085 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 21:37:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.684
X-Spam-Level: 
X-Spam-Status: No, score=-102.684 tagged_above=-999 required=5 tests=[AWL=-0.685, BAYES_00=-2.599, J_CHICKENPOX_54=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3fglVQ9e0DBm for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 21:37:56 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id D663711E812C for <ietf@ietf.org>; Thu, 16 Jun 2011 21:37:56 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Thu, 16 Jun 2011 21:37:56 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Barry Leiba <barryleiba@computer.org>, Andrew Sullivan <ajs@anvilwalrusden.com>
Date: Thu, 16 Jun 2011 21:37:54 -0700
Subject: RE: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
Thread-Topic: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about'	URI scheme) to Proposed Standard
Thread-Index: Acwso0nBXdVstSrtTLW0MLCzuJoZcgABLxkQ
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC4874@EXCH-C2.corp.cloudmark.com>
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF885B5.4020202@gmx.de> <4DF8CA3D.7020904@gmail.com> <20110615201644.GB69872@shinkuro.com> <BANLkTineJQ0BGSrO_V4h1LnjCnnZmm-GGQ@mail.gmail.com>
In-Reply-To: <BANLkTineJQ0BGSrO_V4h1LnjCnnZmm-GGQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Julian Reschke <julian.reschke@gmx.de>, Alexey Melnikov <alexey.melnikov@isode.com>, "draft-holsten-about-uri-scheme@tools.ietf.org" <draft-holsten-about-uri-scheme@tools.ietf.org>, IETF Discussion <ietf@ietf.org>, Boris Zbarsky <bzbarsky@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 04:37:57 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of B=
arry Leiba
> Sent: Thursday, June 16, 2011 9:01 PM
> To: Andrew Sullivan
> Cc: draft-holsten-about-uri-scheme@tools.ietf.org; IETF Discussion;
> Julian Reschke; Boris Zbarsky; Alexey Melnikov
> Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The
> 'about' URI scheme) to Proposed Standard
>=20
> Yes... I'm actually very confused about the point of this document.
> It's documenting a URI scheme that's used ONLY internally, and,
> therefore, has no interoperability requirements.  As best I can tell,
> the issue here is to let browser makers know what other browsers do,
> so that maybe new browsers will decide to do the same things.  That's
> fine, and that helps users have a consistent experience across
> browsers.  But it strikes me as Informational, not Standards Track.
> MUSTs and MUST NOTs seem completely out of place here, to me.
>=20
> If different browsers exhibit different behaviour with the same
> about:xxxx URI, that's as it is, and the variations should be
> documented.  Developers of new browsers will have to decide which
> older browsers to emulate.
>=20
> But none of this actually speaks to interoperability among browsers or
> web servers or applications or....

I suppose adding it as an IANA-registered scheme, referencing something tha=
t's Informational, is a reasonable way for a new browser implementer to be =
reminded that support for such a scheme is common and probably expected.

But if we feel that's either not useful or not the IETF's place (or not a v=
alid use of the IANA scheme registry), then I'm left to +1 Barry's comments=
 above.

-MSK

From narten@us.ibm.com  Thu Jun 16 21:53:22 2011
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 319BC21F859F for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 21:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.299
X-Spam-Level: 
X-Spam-Status: No, score=-105.299 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 88rICeu6+XgZ for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 21:53:21 -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 0407921F8598 for <ietf@ietf.org>; Thu, 16 Jun 2011 21:53:20 -0700 (PDT)
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by e39.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p5H4cmAH011805 for <ietf@ietf.org>; Thu, 16 Jun 2011 22:38:48 -0600
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p5H4r4rx360858 for <ietf@ietf.org>; Thu, 16 Jun 2011 22:53:04 -0600
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 p5GMr3KZ013929 for <ietf@ietf.org>; Thu, 16 Jun 2011 16:53:03 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.176.22]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p5GMr2OK013533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 16 Jun 2011 16:53:03 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p5H4r2AD031778 for <ietf@ietf.org>; Fri, 17 Jun 2011 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p5H4r2D3031741 for ietf@ietf.org; Fri, 17 Jun 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201106170453.p5H4r2D3031741@rotala.raleigh.ibm.com>
Date: Fri, 17 Jun 2011 00:53:01 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 04:53:22 -0000

Total of 146 messages in the last 7 days.
 
script run at: Fri Jun 17 00:53:01 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  9.59% |   14 |  9.56% |   100323 | moore@network-heretics.com
  8.22% |   12 | 10.90% |   114417 | lorenzo@google.com
  5.48% |    8 |  5.39% |    56570 | evnikita2@gmail.com
  4.11% |    6 |  3.85% |    40372 | marka@isc.org
  4.11% |    6 |  3.84% |    40273 | joelja@bogus.com
  3.42% |    5 |  3.62% |    38023 | brian.e.carpenter@gmail.com
  4.11% |    6 |  2.73% |    28627 | michel@arneill-py.sacramento.ca.us
  3.42% |    5 |  2.64% |    27665 | jhw@apple.com
  2.74% |    4 |  2.87% |    30154 | john-ietf@jck.com
  2.74% |    4 |  2.63% |    27580 | ipng@69706e6720323030352d30312d31340a.nosense.org
  2.05% |    3 |  3.18% |    33360 | alh-ietf@tndh.net
  1.37% |    2 |  3.61% |    37906 | otuenehoj@gmail.com
  2.74% |    4 |  1.98% |    20799 | julian.reschke@gmx.de
  2.74% |    4 |  1.84% |    19305 | jnc@mercury.lcs.mit.edu
  1.37% |    2 |  3.07% |    32216 | yaronf.ietf@gmail.com
  2.74% |    4 |  1.63% |    17101 | johnl@iecc.com
  2.05% |    3 |  2.13% |    22347 | daedulus@btconnect.com
  1.37% |    2 |  2.50% |    26237 | violeta.cakulev@alcatel-lucent.com
  2.05% |    3 |  1.57% |    16517 | mcr@sandelman.ca
  2.05% |    3 |  1.32% |    13905 | mohta@necom830.hpcl.titech.ac.jp
  1.37% |    2 |  1.96% |    20577 | stefan.winter@restena.lu
  1.37% |    2 |  1.45% |    15222 | cb.list6@gmail.com
  1.37% |    2 |  1.34% |    14050 | nsb@guppylake.com
  1.37% |    2 |  1.29% |    13553 | mail@sabahattin-gucukoglu.com
  1.37% |    2 |  1.08% |    11307 | lachlan.hunt@lachy.id.au
  1.37% |    2 |  0.98% |    10291 | jari.arkko@piuha.net
  0.68% |    1 |  0.94% |     9838 | ben@nostrum.com
  0.68% |    1 |  0.86% |     9011 | avi@bridgewatersystems.com
  0.68% |    1 |  0.83% |     8666 | elwynd@dial.pipex.com
  0.68% |    1 |  0.78% |     8181 | hsantos@isdg.net
  0.68% |    1 |  0.77% |     8029 | narten@us.ibm.com
  0.68% |    1 |  0.75% |     7880 | hamza.gharsallah@gmail.com
  0.68% |    1 |  0.74% |     7766 | fred.l.templin@boeing.com
  0.68% |    1 |  0.74% |     7745 | tom111.taylor@bell.net
  0.68% |    1 |  0.72% |     7539 | bertietf@bwijnen.net
  0.68% |    1 |  0.72% |     7525 | suresh.krishnan@ericsson.com
  0.68% |    1 |  0.71% |     7503 | jun@wide.ad.jp
  0.68% |    1 |  0.70% |     7360 | trejrco@gmail.com
  0.68% |    1 |  0.67% |     7062 | rdroms.ietf@gmail.com
  0.68% |    1 |  0.66% |     6906 | bzbarsky@mit.edu
  0.68% |    1 |  0.62% |     6476 | touch@isi.edu
  0.68% |    1 |  0.61% |     6366 | ned+ietf@mauve.mrochek.com
  0.68% |    1 |  0.60% |     6249 | tnadeau@lucidvision.com
  0.68% |    1 |  0.58% |     6129 | dave@cridland.net
  0.68% |    1 |  0.58% |     6119 | otroan@employees.org
  0.68% |    1 |  0.56% |     5906 | ek@google.com
  0.68% |    1 |  0.56% |     5879 | gert@space.net
  0.68% |    1 |  0.55% |     5766 | jmh@joelhalpern.com
  0.68% |    1 |  0.55% |     5728 | conte@isoc.org
  0.68% |    1 |  0.54% |     5700 | tjc@ecs.soton.ac.uk
  0.68% |    1 |  0.52% |     5451 | ajs@anvilwalrusden.com
  0.68% |    1 |  0.51% |     5395 | rogerj@gmail.com
  0.68% |    1 |  0.51% |     5372 | barryleiba@computer.org
  0.68% |    1 |  0.50% |     5252 | huitema@microsoft.com
  0.68% |    1 |  0.47% |     4918 | dworley@avaya.com
  0.68% |    1 |  0.46% |     4840 | smb@cs.columbia.edu
  0.68% |    1 |  0.44% |     4604 | dougb@dougbarton.us
  0.68% |    1 |  0.44% |     4603 | iad@ietf.org
  0.68% |    1 |  0.43% |     4528 | cos@aaaaa.org
  0.68% |    1 |  0.42% |     4447 | krishnabirth@gmail.com
--------+------+--------+----------+------------------------
100.00% |  146 |100.00% |  1049436 | Total

From julian.reschke@gmx.de  Thu Jun 16 23:51:54 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C42F121F84AE for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 23:51:54 -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_54=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24s3lGrGNnLA for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 23:51:53 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 0EC1521F84AD for <ietf@ietf.org>; Thu, 16 Jun 2011 23:51:52 -0700 (PDT)
Received: (qmail invoked by alias); 17 Jun 2011 06:51:51 -0000
Received: from p508FD183.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.209.131] by mail.gmx.net (mp051) with SMTP; 17 Jun 2011 08:51:51 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+gV90UUrigb9SAFYgH7Js+zpLyWC9DMkGsWC3Gfz 07cBdSYbGA4mlA
Message-ID: <4DFAF985.9070802@gmx.de>
Date: Fri, 17 Jun 2011 08:51:49 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu>	<4DF87637.2000301@gmail.com>	<4DF885B5.4020202@gmx.de>	<4DF8CA3D.7020904@gmail.com>	<20110615201644.GB69872@shinkuro.com> <BANLkTineJQ0BGSrO_V4h1LnjCnnZmm-GGQ@mail.gmail.com>
In-Reply-To: <BANLkTineJQ0BGSrO_V4h1LnjCnnZmm-GGQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>, Boris Zbarsky <bzbarsky@mit.edu>, Alexey Melnikov <alexey.melnikov@isode.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 Jun 2011 06:51:54 -0000

On 2011-06-17 06:01, Barry Leiba wrote:
>> More substantively, I fail to understand how this specification
>> proposes to create a class of "reserved" about: URIs when the about:
>> scheme seems to be internal information to an application.  I think
>> the Security Considerations section doesn't address any of that, and
>> probably ought to, particularly in light of the proposal to add text
>> that users ought not to depend on "standard" behaviour.
>
> Yes... I'm actually very confused about the point of this document.
> It's documenting a URI scheme that's used ONLY internally, and,
> therefore, has no interoperability requirements.  As best I can tell,
> the issue here is to let browser makers know what other browsers do,
> so that maybe new browsers will decide to do the same things.  That's
> fine, and that helps users have a consistent experience across
> browsers.  But it strikes me as Informational, not Standards Track.
> MUSTs and MUST NOTs seem completely out of place here, to me.
>
> If different browsers exhibit different behaviour with the same
> about:xxxx URI, that's as it is, and the variations should be
> documented.  Developers of new browsers will have to decide which
> older browsers to emulate.
>
> But none of this actually speaks to interoperability among browsers or
> web servers or applications or....
> ...

The reason this whole activity is started is...

   <http://www.w3.org/TR/2011/WD-html5-20110525/syntax.html#the-doctype>

which "defines"

   about:legacy-compat

for which interoperable behavior is required from browsers.

Best regards, Julian

From julian.reschke@gmx.de  Thu Jun 16 23:53:54 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B20321F84BA for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 23:53:54 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PBS2sAtoR2Ss for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 23:53:54 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id A82BF21F84B1 for <ietf@ietf.org>; Thu, 16 Jun 2011 23:53:53 -0700 (PDT)
Received: (qmail invoked by alias); 17 Jun 2011 06:53:51 -0000
Received: from p508FD183.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.209.131] by mail.gmx.net (mp064) with SMTP; 17 Jun 2011 08:53:51 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+ROi5kKi2RqhUMDOYbhEZfxGPbdowuUHyW0KTCt0 dcxOwU/kBtBXze
Message-ID: <4DFAF9FE.7060709@gmx.de>
Date: Fri, 17 Jun 2011 08:53:50 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com>	<4DF885B5.4020202@gmx.de> <4DF8CA3D.7020904@gmail.com>	<20110615201644.GB69872@shinkuro.com> <BANLkTineJQ0BGSrO_V4h1LnjCnnZmm-GGQ@mail.gmail.com> <F5833273385BB34F99288B3648C4F06F134EBC4874@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134EBC4874@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "draft-holsten-about-uri-scheme@tools.ietf.org" <draft-holsten-about-uri-scheme@tools.ietf.org>, IETF Discussion <ietf@ietf.org>, Boris Zbarsky <bzbarsky@mit.edu>, Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba <barryleiba@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 06:53:54 -0000

On 2011-06-17 06:37, Murray S. Kucherawy wrote:
> ...
> I suppose adding it as an IANA-registered scheme, referencing something that's Informational, is a reasonable way for a new browser implementer to be reminded that support for such a scheme is common and probably expected.
> ...

Optimally, we had a strategy by which we can reserve certain scheme 
names (*), although they aren't really interoperable nor have a proper spec.

Best regards, Julian

(*) about, chrome, itms, ical, and probably many more...

From lear@cisco.com  Thu Jun 16 23:57:35 2011
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 28F1711E8086 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 23:57:35 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Z5sG-EyxSZr for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 23:57:34 -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 3D3F511E8076 for <ietf@ietf.org>; Thu, 16 Jun 2011 23:57:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=903; q=dns/txt; s=iport; t=1308293854; x=1309503454; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=V1gI6unQkYxArYXnZBWp7ohYxLM0A2By6RBlwKzTt9A=; b=BW4p44F2sE3hk/gyYhQqRNfR27khKpLJ5lrk/oSPDT21CEpSltfNbzZh +yFJPENfbo5Q3CKHdy7XUwYppXf81hzk3WKlhi8JrR6o1NByeujCMXoqh pxD3lPYcckqWwjtyIJaqyPVF+qJsPNEY8s6928ujocV3AJ1+YRf/UJzfc s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EABj6+k2Q/khL/2dsb2JhbABShEmiI3eIc6IOjSuQaYErg3KBCgSRXo9/
X-IronPort-AV: E=Sophos;i="4.65,380,1304294400"; d="scan'208";a="94451911"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 17 Jun 2011 06:57:31 +0000
Received: from dhcp-10-55-83-58.cisco.com (dhcp-10-55-83-58.cisco.com [10.55.83.58]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5H6vUv1028344; Fri, 17 Jun 2011 06:57:31 GMT
Message-ID: <4DFAFADA.8030907@cisco.com>
Date: Fri, 17 Jun 2011 08:57:30 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com>	<4DF885B5.4020202@gmx.de> <4DF8CA3D.7020904@gmail.com>	<20110615201644.GB69872@shinkuro.com> <BANLkTineJQ0BGSrO_V4h1LnjCnnZmm-GGQ@mail.gmail.com>
In-Reply-To: <BANLkTineJQ0BGSrO_V4h1LnjCnnZmm-GGQ@mail.gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, Boris Zbarsky <bzbarsky@mit.edu>, Alexey Melnikov <alexey.melnikov@isode.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 Jun 2011 06:57:35 -0000

Hi Barry,

On 6/17/11 6:01 AM, Barry Leiba wrote:
> Yes... I'm actually very confused about the point of this document.
> It's documenting a URI scheme that's used ONLY internally, and,
> therefore, has no interoperability requirements.

Indeed.  That's a good argument to stop right there.

>   As best I can tell,
> the issue here is to let browser makers know what other browsers do,
> so that maybe new browsers will decide to do the same things.  That's
> fine, and that helps users have a consistent experience across
> browsers.  But it strikes me as Informational, not Standards Track.
> MUSTs and MUST NOTs seem completely out of place here, to me.
It seems to me we could simply inform IANA that about: is reserved for
internal use by a browser, and not to be assigned for other purposes,
and not to be exchanged between hosts.  Do we really need an RFC to do that?

Eliot


From lachlan.hunt@lachy.id.au  Fri Jun 17 04:25:31 2011
Return-Path: <lachlan.hunt@lachy.id.au>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF20411E80C7 for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 04:25:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_55=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YyPtO8pXx9nJ for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 04:25:31 -0700 (PDT)
Received: from homiemail-a83.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id EEC9611E808B for <ietf@ietf.org>; Fri, 17 Jun 2011 04:25:30 -0700 (PDT)
Received: from homiemail-a83.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a83.g.dreamhost.com (Postfix) with ESMTP id D6A045E06A; Fri, 17 Jun 2011 04:25:29 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=lachy.id.au; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=lachy.id.au; b=A5Vgwu3HZuHSr28v35BGASuo8TI+QxyA332uuzRmjmQtL2gItnB7PEio8BoET FXXNIEBbkpoAYf8iHwK4hso1CN760Q2Wh6HMVX9Op2h/XoVy1XDEIld+X8KlfYnP JBxL6wMH35JQfGmsEHRW5dOouYiT3uOskW8c78iouwkXcM=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=lachy.id.au; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=lachy.id.au; bh=UadYe Pe1wDv0yUJWjF855Ta8mSY=; b=faedOM1WgUxEwmy9qd5V7VTflusigl7S+MeVJ w7Z0hK/29OFY0a3Zh3w3MeGBni4aQrVWz8m8ODYWZ+9XoTMVILCkipkeonj1oBwN Q/eZyHm1WHgxB1CfbrjBREigp5Ch6aj/lq/3dXVwLAbOUUs94x/q3z81ajowmiNp LpBQdc=
Received: from jonas.eng.oslo.osa (pat-tdc.opera.com [213.236.208.22]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lachlan.hunt@lachy.id.au) by homiemail-a83.g.dreamhost.com (Postfix) with ESMTPSA id 002785E056;  Fri, 17 Jun 2011 04:25:28 -0700 (PDT)
Message-ID: <4DFB39A6.5050105@lachy.id.au>
Date: Fri, 17 Jun 2011 13:25:26 +0200
From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Boris Zbarsky <bzbarsky@MIT.EDU>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF8D6C6.5080005@mit.edu> <4DF9C5EE.9010703@lachy.id.au> <4DFAD1F6.70203@gmail.com> <4DFAD8CD.2030402@mit.edu>
In-Reply-To: <4DFAD8CD.2030402@mit.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 11:25:31 -0000

On 2011-06-17 06:32, Boris Zbarsky wrote:
> On 6/17/11 12:03 AM, Mykyta Yevstifeyev wrote:
>>>> not
>>>> clearly compatible with the web security model,
>> How?
>
> "about:blank" in particular is magic with respect to security on the web
> in various ways (e.g. it can end up same-origin with http:// pages). So
> I think we do need to specify exactly when this magic security behavior
> takes place.

The spec is not meant to imply that the special same-origin behaviour 
for about:blank is to be inherited by any other about URI, even if other 
URIs also return a blank document.  Perhaps, I need to make that clearer 
in the spec.

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/

From mcr@sandelman.ca  Fri Jun 17 06:31:01 2011
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 9E04F11E80E2 for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 06:31:01 -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=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wEJfacjRJ8V0 for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 06:31:00 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id CE20311E8070 for <ietf@ietf.org>; Fri, 17 Jun 2011 06:31:00 -0700 (PDT)
Received: from marajade.sandelman.ca (wlan204.sandelman.ca [209.87.252.204]) by relay.sandelman.ca (Postfix) with ESMTPS id D9A31341E0; Fri, 17 Jun 2011 09:30:58 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id D562498122; Fri, 17 Jun 2011 09:32:44 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
In-Reply-To: <BANLkTineJQ0BGSrO_V4h1LnjCnnZmm-GGQ@mail.gmail.com>
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF885B5.4020202@gmx.de> <4DF8CA3D.7020904@gmail.com> <20110615201644.GB69872@shinkuro.com> <BANLkTineJQ0BGSrO_V4h1LnjCnnZmm-GGQ@mail.gmail.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Jun 2011 09:32:44 -0400
Message-ID: <29624.1308317564@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, Boris Zbarsky <bzbarsky@mit.edu>, Alexey Melnikov <alexey.melnikov@isode.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 Jun 2011 13:31:01 -0000

>>>>> "Barry" =3D=3D Barry Leiba <barryleiba@computer.org> writes:
    >> More substantively, I fail to understand how this specification
    >> proposes to create a class of "reserved" about: URIs when the
    >> about: scheme seems to be internal information to an
    >> application. =A0I think the Security Considerations section doesn't
    >> address any of that, and probably ought to, particularly in light
    >> of the proposal to add text that users ought not to depend on
    >> "standard" behaviour.

    Barry> Yes... I'm actually very confused about the point of this
    Barry> document.  It's documenting a URI scheme that's used ONLY
    Barry> internally, and, therefore, has no interoperability
    Barry> requirements.  As best I can tell, the issue here is to let

It does.  It's an RFC1918-type use, and for the same reason we had to
document those networks, we have to document this URI.
This document prevents someone else from creating "about:" scheme which
is NOT internal.

--=20
]       He who is tired of Weird Al is tired of life!           |  firewall=
s  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net archit=
ect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device dri=
ver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=3Dkzx1ycLXQS=
E>
	               then sign the petition.=20

From barryleiba@gmail.com  Fri Jun 17 06:44:13 2011
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E10C11E814B for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 06:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.891
X-Spam-Level: 
X-Spam-Status: No, score=-102.891 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8V3jaywz-mkF for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 06:44:13 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 003DF11E8148 for <ietf@ietf.org>; Fri, 17 Jun 2011 06:44:12 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1805602gxk.31 for <ietf@ietf.org>; Fri, 17 Jun 2011 06:44:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=E/wv4cRcSlU03Wf7ejPpkLUogE16x9474rQSaotC28A=; b=Xjg15vxdOo0ELL8P83lk9r/DLVMOlDWL+reHQDClltuZ7MgCcusTbrVudj40Lt7BXq bxwLhd/uTHzvmv9l8oGvfm/a9m+U+5rtm0rEf2AEORV9Sc97yD2JxKxppiuELUYFnHb/ VDpwHyozVi2lZUSL3aziXzXksW637L3p23cJ4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=kXuC2Kg4H4aF3XtocEMZed12QqBT6whYzukETDvWWR14r2OJNlqC6Uk0XiC92DumOI K/to0Tw1KdkURPQP81MbdVbrTF/wyhXbQOq/xM0i6QLFceLq9Qmf9mugn2ysdyyEWRLB /RR5nAucieuaX5nKL3zDQXYDGykOCP5WVr+YE=
MIME-Version: 1.0
Received: by 10.236.192.201 with SMTP id i49mr3344103yhn.525.1308318252444; Fri, 17 Jun 2011 06:44:12 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.236.42.200 with HTTP; Fri, 17 Jun 2011 06:44:12 -0700 (PDT)
In-Reply-To: <29624.1308317564@marajade.sandelman.ca>
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF885B5.4020202@gmx.de> <4DF8CA3D.7020904@gmail.com> <20110615201644.GB69872@shinkuro.com> <BANLkTineJQ0BGSrO_V4h1LnjCnnZmm-GGQ@mail.gmail.com> <29624.1308317564@marajade.sandelman.ca>
Date: Fri, 17 Jun 2011 09:44:12 -0400
X-Google-Sender-Auth: Myey97WtcssSHNqgR7leBtXZxsw
Message-ID: <BANLkTinzzcaGZYW-DO2n9mrgV8SdWaHQQw@mail.gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Michael Richardson <mcr@sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, Boris Zbarsky <bzbarsky@mit.edu>, Alexey Melnikov <alexey.melnikov@isode.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 Jun 2011 13:44:13 -0000

> =A0 =A0Barry> internally, and, therefore, has no interoperability
> =A0 =A0Barry> requirements. =A0As best I can tell, the issue here is to l=
et
>
> It does. =A0It's an RFC1918-type use, and for the same reason we had to
> document those networks, we have to document this URI.
> This document prevents someone else from creating "about:" scheme which
> is NOT internal.

Oh, yes: to be clear here... I am NOT suggesting that we shouldn't
register the URI scheme.  I'm only saying that the registration
doesn't require a great deal of standards-track documentation.  A
short Informational doc should do.

Barry

From bzbarsky@mit.edu  Thu Jun 16 09:08:48 2011
Return-Path: <bzbarsky@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 2B7DC9E8033 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 09:08:48 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ImaXsirf-sW for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 09:08:47 -0700 (PDT)
Received: from dmz-mailsec-scanner-2.mit.edu (DMZ-MAILSEC-SCANNER-2.MIT.EDU [18.9.25.13]) by ietfa.amsl.com (Postfix) with ESMTP id 92CAE9E8040 for <ietf@ietf.org>; Thu, 16 Jun 2011 09:08:47 -0700 (PDT)
X-AuditID: 1209190d-b7bdeae0000004f8-e8-4dfa2a45adf3
Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id F8.67.01272.54A2AFD4; Thu, 16 Jun 2011 12:07:33 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id p5GG8jCm003475;  Thu, 16 Jun 2011 12:08:45 -0400
Received: from Boris-Zbarskys-MacBook-Pro-2.local (pool-71-184-125-56.bstnma.fios.verizon.net [71.184.125.56]) (authenticated bits=0) (User authenticated as bzbarsky@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p5GG8gj7002318 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 16 Jun 2011 12:08:43 -0400 (EDT)
Message-ID: <4DFA2A8A.7020701@mit.edu>
Date: Thu, 16 Jun 2011 12:08:42 -0400
From: Boris Zbarsky <bzbarsky@MIT.EDU>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF8D6C6.5080005@mit.edu> <4DF9C5EE.9010703@lachy.id.au>
In-Reply-To: <4DF9C5EE.9010703@lachy.id.au>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpileLIzCtJLcpLzFFi42IR4hTV1nXV+uVrMGGDgsX7C+1MFs82zmex WDfzG7MDs8fOWXfZPZYs+cnkMe9QJ3MAcxSXTUpqTmZZapG+XQJXxszNH5kKdjBXLDqwlLGB 8RFTFyMnh4SAiUTnou1sELaYxIV764FsLg4hgX2MEh1nPzFBOBsYJdacWcAMUiUk8IpJYlVn PojNK6Am8fTBIrA4i4CqxOU/88EmsQHF759uBNsgKlAoMeP7TEaIekGJkzOfsIDYIgLaEo/e doHVMAv4SpyY1sEKYgsL5Eu0rF/PBrGrVmLzrHPsIDYnUH3Pg02sEPVmEl1buxghbHmJ7W/n ME9gFJyFZMUsJGWzkJQtYGRexSibklulm5uYmVOcmqxbnJyYl5dapGukl5tZopeaUrqJERzU krw7GN8dVDrEKMDBqMTDe+zsD18h1sSy4srcQ4ySHExKorwMKr98hfiS8lMqMxKLM+KLSnNS iw8xSnAwK4nwnvr901eINyWxsiq1KB8mJc3BoiTOO1NS3VdIID2xJDU7NbUgtQgmK8PBoSTB e1kTaKhgUWp6akVaZk4JQpqJgxNkOA/Q8HMgNbzFBYm5xZnpEPlTjIpS4rwdIAkBkERGaR5c LyzpvGIUB3pFmHclSBUPMGHBdb8CGswENPjWy28gg0sSEVJSDYwTJ34SPlXT/EGNdXe3xNZ1 ewx7durMT5GPN57J2PBmQvuypc93OJt+z/vFvmZ5tMT39fueW0+3SztzbOUlqZ1LlhycK7h3 /RP1FxldLx245bfor+bOvHa9621B+rYb2hOOlBv9r1wat+l4ANc7GbuWpgKuEvfiTxvMHfqX VnROX7Uw+bWLwuQoJZbijERDLeai4kQAJbA9CxUDAAA=
X-Mailman-Approved-At: Fri, 17 Jun 2011 08:48:30 -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: Thu, 16 Jun 2011 16:08:48 -0000

On 6/16/11 4:59 AM, Lachlan Hunt wrote:
> Mykyta, we do need to make this spec document reality, particularly
> where implementations are unwilling to make changes

To be clear, in the normalization case we (Gecko) may be willing to make 
changes, but not if it causes conflicts with existing security 
assumptions on the web.  And that's something that needs to be 
investigated _before_ this spec if finalized, clearly.

-Boris

From hoene@uni-tuebingen.de  Thu Jun 16 14:12:51 2011
Return-Path: <hoene@uni-tuebingen.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 96E8211E8234; Thu, 16 Jun 2011 14:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K4S89hgPsmcz; Thu, 16 Jun 2011 14:12:51 -0700 (PDT)
Received: from mx06.uni-tuebingen.de (mx06.uni-tuebingen.de [134.2.3.3]) by ietfa.amsl.com (Postfix) with ESMTP id D295911E8138; Thu, 16 Jun 2011 14:12:49 -0700 (PDT)
Received: from hoeneT60 ([109.52.109.175]) (authenticated bits=0) by mx06.uni-tuebingen.de (8.13.6/8.13.6) with ESMTP id p5GKgJWB023981 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 16 Jun 2011 22:42:27 +0200
From: "Christian Hoene" <hoene@uni-tuebingen.de>
To: <ietf@ietf.org>
Subject: RE: [codec] Last Call: <draft-ietf-codec-requirements-04.txt>	(Codec	Requirements) to Informational RFC
Date: Thu, 16 Jun 2011 22:42:23 +0200
Organization: =?us-ascii?Q?Universitat_Tubingen?=
Message-ID: <003e01cc2c65$ea831540$bf893fc0$@uni-tuebingen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AcwsZds3pfKRAGu9R3uSaH1Z3il1hA==
Content-Language: de
X-AntiVirus: NOT checked by Avira MailGate (version: 3.1.2; host: mx06)
X-Mailman-Approved-At: Fri, 17 Jun 2011 08:48:30 -0700
Cc: codec@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 21:12:51 -0000

Hello,

In this draft, the editors of draft are not named as editors but as authors.
Thus, I would suggest to follow the example given in
http://www.rfc-editor.org/rfc/rfc5620.txt and add an ", Ed." behind the
names. A list of authors is given in the acknowledgement section of the
draft.

With best regards,

 Christian Hoene


> -----Original Message-----
> From: codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] On Behalf
> Of The IESG
> Sent: Thursday, June 16, 2011 9:24 PM
> To: IETF-Announce
> Cc: codec@ietf.org
> Subject: [codec] Last Call: <draft-ietf-codec-requirements-04.txt> (Codec
> Requirements) to Informational RFC
> 
> 
> The IESG has received a request from the Internet Wideband Audio Codec
> WG
> (codec) to consider the following document:
> - 'Codec Requirements'
>   <draft-ietf-codec-requirements-04.txt> as an 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 2011-06-30. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document provides specific requirements for an Internet audio
>    codec.  These requirements address quality, sampling rate, bit-rate,
>    and packet loss robustness, as well as other desirable properties.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-codec-requirements/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-codec-requirements/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec


From bzbarsky@mit.edu  Thu Jun 16 21:32:18 2011
Return-Path: <bzbarsky@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 9342911E8161 for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 21:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2sCNT0PqpyMM for <ietf@ietfa.amsl.com>; Thu, 16 Jun 2011 21:32:17 -0700 (PDT)
Received: from dmz-mailsec-scanner-8.mit.edu (DMZ-MAILSEC-SCANNER-8.MIT.EDU [18.7.68.37]) by ietfa.amsl.com (Postfix) with ESMTP id 5B65111E8153 for <ietf@ietf.org>; Thu, 16 Jun 2011 21:32:17 -0700 (PDT)
X-AuditID: 12074425-b7b82ae000000a2a-f7-4dfad8b0180a
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 99.7C.02602.0B8DAFD4; Fri, 17 Jun 2011 00:31:44 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id p5H4WGva008229;  Fri, 17 Jun 2011 00:32:16 -0400
Received: from Boris-Zbarskys-MacBook-Pro-2.local (pool-71-184-125-56.bstnma.fios.verizon.net [71.184.125.56]) (authenticated bits=0) (User authenticated as bzbarsky@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p5H4WEwK014787 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 17 Jun 2011 00:32:15 -0400 (EDT)
Message-ID: <4DFAD8CD.2030402@mit.edu>
Date: Fri, 17 Jun 2011 00:32:13 -0400
From: Boris Zbarsky <bzbarsky@MIT.EDU>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF8D6C6.5080005@mit.edu> <4DF9C5EE.9010703@lachy.id.au> <4DFAD1F6.70203@gmail.com>
In-Reply-To: <4DFAD1F6.70203@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpkleLIzCtJLcpLzFFi42IRYrdT191w45evwaQnKhbvL7QzWTzbOJ/F Yt3Mb8wOzB47Z91l91iy5CeTx7xDncwBzFFcNimpOZllqUX6dglcGT9W72AtOMRT0X+av4Hx C2cXIyeHhICJxMzHnxkhbDGJC/fWs3UxcnEICexjlDg04ScLhLOBUWLd0W5GCOcVk8T6q2eY QVp4BdQkJrw9D1TFwcEioCrxc6s7SJgNKHz/dCMTiC0qUCgx4/tMRohyQYmTM5+wgNgiAjoS H9pvMoK0Mgv4SOxstQEJCwvkS7SshzliBqPE9+X/WEESnALqEksXzGADsZkFzCS6tnYxQtjy EtvfzmGewCg4C8mKWUjKZiEpW8DIvIpRNiW3Sjc3MTOnODVZtzg5MS8vtUjXQi83s0QvNaV0 EyM4pF1UdzBOOKR0iFGAg1GJh/elxS9fIdbEsuLK3EOMkhxMSqK8C84DhfiS8lMqMxKLM+KL SnNSiw8xSnAwK4nwnvr901eINyWxsiq1KB8mJc3BoiTOO19S3VdIID2xJDU7NbUgtQgmK8PB oSTBmwGMXSHBotT01Iq0zJwShDQTByfIcB6g4WkgNbzFBYm5xZnpEPlTjIpS4rx6IAkBkERG aR5cLyzlvGIUB3pFmDcEpIoHmK7gul8BDWYCGnzr5TeQwSWJCCmpBsa2ZbMVAwKUDB4UXva0 z7z1u/un1t6dZz9PmfRWd4Xr8yWrhLLs1V4/3qrUXrJDPHT52gV7zm9WX3pPMfRY/zJXlX+J Eo9sbuQevsx4LCr89dXgUxmcuZ8/LnbpmNQkmvTHKC+v5snENwtj6zZOtHTP/1fnLHjgc8QW 3smO1SJCodMSb/MGe8cqsRRnJBpqMRcVJwIA7D9OaBQDAAA=
X-Mailman-Approved-At: Fri, 17 Jun 2011 08:48:30 -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: Fri, 17 Jun 2011 04:32:18 -0000

On 6/17/11 12:03 AM, Mykyta Yevstifeyev wrote:
>>> not
>>> clearly compatible with the web security model,
> How?

"about:blank" in particular is magic with respect to security on the web 
in various ways (e.g. it can end up same-origin with http:// pages).  So 
I think we do need to specify exactly when this magic security behavior 
takes place.

The question is what existing UAs do and what assumptions web authors 
make, as well as what assumptions should be safe for them to make.

Note that "not clearly compatible" doesn't mean "not compatible"; it 
just means it needs sorting out.

Note that this is also an exception to the general claim that about: is 
only used internally.   That's not the case for about:blank.

So I think we do need a Standards Track document that pins down how 
about:blank works; I will be happy to make whatever changes are needed 
to Gecko here to achieve interop assuming that the result has been 
vetted in terms of the security implications.

For other about: URIs, I don't know whether Standards Track necessarily 
make sense.

>>> and because the
>>> normalization is not defined in the spec.
> Normalization is defined in RFC 3986.

Browsers don't actually implement RFC 3986 in practice because it's not 
compatible with web content, last I checked....  Pretending like they do 
doesn't seem to be productive.

Or is the point that the algorithms to be used are just the ones defined 
in 3986 and those are sufficiently ok that browsers do actually use 
them?  That wasn't clear to me from the current draft.

-Boris

From julian.reschke@gmx.de  Fri Jun 17 09:14:30 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 865FC11E81F2 for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 09:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.394
X-Spam-Level: 
X-Spam-Status: No, score=-103.394 tagged_above=-999 required=5 tests=[AWL=-0.795, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9EkbPAWyHFWd for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 09:14:30 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 8B4A311E81F0 for <ietf@ietf.org>; Fri, 17 Jun 2011 09:14:29 -0700 (PDT)
Received: (qmail invoked by alias); 17 Jun 2011 16:14:28 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp026) with SMTP; 17 Jun 2011 18:14:28 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+94xo6kz+9s1fIr6FkyZ/IN10mmrUfH+kNK0R3Ad hOb0DB8tbBszeP
Message-ID: <4DFB7D62.5060804@gmx.de>
Date: Fri, 17 Jun 2011 18:14:26 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Boris Zbarsky <bzbarsky@MIT.EDU>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com>	<4DF8D6C6.5080005@mit.edu> <4DF9C5EE.9010703@lachy.id.au>	<4DFAD1F6.70203@gmail.com> <4DFAD8CD.2030402@mit.edu>
In-Reply-To: <4DFAD8CD.2030402@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 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, 17 Jun 2011 16:14:30 -0000

On 2011-06-17 06:32, Boris Zbarsky wrote:
> ...
>>>> and because the
>>>> normalization is not defined in the spec.
>> Normalization is defined in RFC 3986.
>
> Browsers don't actually implement RFC 3986 in practice because it's not
> compatible with web content, last I checked.... Pretending like they do
> doesn't seem to be productive.
> ...

It would be very helpful for the IRI WG if browser vendors actually 
reported what this incompatibility is; and whether UAs indeed agree on 
what the "right" thing to do is.

So far I'm aware of certain kinds of preprocessing, and workarounds for 
specific schemes like "data" and "file", but that's it...

Best regards, Julian

From klensin@jck.com  Fri Jun 17 09:50:03 2011
Return-Path: <klensin@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 BADB511E81A7 for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 09:50:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.657
X-Spam-Level: 
X-Spam-Status: No, score=-2.657 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tidXljkmuvQE for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 09:50:01 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 5269A11E80E2 for <ietf@ietf.org>; Fri, 17 Jun 2011 09:50:01 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QXcF4-000AiT-UJ; Fri, 17 Jun 2011 12:49:59 -0400
Date: Fri, 17 Jun 2011 12:49:58 -0400
From: John C Klensin <klensin@jck.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
Message-ID: <0EC26EB10287E2A20769C9CC@PST.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: draft-holsten-about-uri-scheme@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, 17 Jun 2011 16:50:03 -0000

Given the controversies, I decided I needed to do a careful
reading of this document.  While I respect and appreciate what
the authors are trying to do, as a would-be standards track
specification, it is pretty troubling.  It is troubling
editorially as well.

I think all or most of the specific issues have been identified
by others, so let me try a different perspective and a 10 km
view.

(1) There seems to be consensus that registering this URI as a
mechanism for accessing built-in functionality and configuration
information such as application information, preferences, or
settings.   (Text derived from the Abstract with "configuration
information", which may mean more to some readers, added and
"easter eggs" dropped.  Dropping "easter eggs" reflects other
comments on the list and my opinion that it isn't worth the
trouble to define.

Recommendation: Let's get it registered.


(2)  The document itself reflects an attempt to define the
undefinable.  There is no cross-implementation interoperability
issue here; if anything, the document should me more clear that
it would be stupid to assume it.  The document, nonetheless,
tries to define what is done with some specific URIs in some
places and then has to turn around and indicate that they may be
used in entirely different ways in other places and should not
be relied upon.  In the process, it skips back and forth between
being descriptive and being normative, with some definitions
becoming circular in the process.   That just isn't a good
combination and some of it actually looks pretty silly.  

"about:blank" is particularly troubling in that regard because
the text essentially says that it is reserved except where it
isn't.

Recommendation:  Choose one of the following and redo the
document to match.

Option 1: Do this descriptively.  Strip it down as much as
possible, more or less repeating the suggested language above.
If the Wikipedia article really contains a better and more
authoritative list of applications than the I-D text (and
especially if it is being kept up to date), just reference it as
a place where a non-normative listing and examples can be found.
The effect of doing this at all would be to reserve the name for
purposes internal to particular implementations of particular
applications, not unlike RFC 1918 addresses.

Option 2: Really try to make this normative wrt some subset of
URI values.  In this approach, stop the extremely confusing
circling around.  Indicate explicitly that "about" URIs have
been used enough and in enough different circumstances that no
application should assume that an "about" URI, if encountered,
is actually its own and that due caution needs to be taken about
non-conforming implementations.  Then explicitly reserve, not
only "about:blank", but  everything the authors think is worth
listing in Examples _and_ create an IANA registry for more of
them.  

But, even the second approach is taken, the document should be
really clear that all that the use of "about:" really tells
someone is that it is application-specific and that a particular
implementation of a particular application may do whatever it
pleases with them.


 ---- 
Smaller issues:

(i) Section 6, Normalization, sadly really doesn't belong here
unless the authors can show that everyone interprets "about:"
according to those rules.  Otherwise, it would be better to say
that the URI is interpreted in an implementation-specific way
and that implementations would be well-advised to conform to
normal URI syntax rules unless there is a strong reason not to.

(ii) IMO, Section 7, Security Considerations, should be modified
to include an explicit statement that, since these things are
intended for convenience use within an implementation of an
application, passing them between systems (embedded in files or
otherwise) is very risky behavior and should generally be
discouraged except, possibly, in documentation contexts.

(iii) I know this is partially a problem with the general URI
and IRI definitions, but I'm supposed to know something about
i18n and  encoding and Section 4, Encoding Considerations, is
almost incomprehensible to me.  It isn't quite clear what "this
syntax" refers to (if it is "the 'about' variation on the
general URI syntax described in Section 3", say that).   Then I
think it says I may use any Unicode character, but I have to
%-encode it, but, if it isn't unreserved, it shouldn't be
%-encoded.  If there isn't a clearer way to say that, I suggest
that almost anyone trying to figure out how to use this URI from
the spec is in trouble.  And, fwiw, I've seen "about:" URIs that
use non-ASCII strings without %-encoding.   Whether one calls
those IRIs, URIs, or pumpkins, I see absolutely no reason why an
implementation that knows it is UTF-8 capable (and clean) should
require that an xRI that is intended only for internal use
should require %-encoding of UTF-8 strings... especially since,
in practice, these URIs are often expected to be direct user
input.

  best,
     john




From d3e3e3@gmail.com  Fri Jun 17 13:31:52 2011
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 F319821F8496; Fri, 17 Jun 2011 13:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iFXci2nnfQIx; Fri, 17 Jun 2011 13:31:51 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1C50121F8498; Fri, 17 Jun 2011 13:31:51 -0700 (PDT)
Received: by ywp31 with SMTP id 31so2036247ywp.31 for <multiple recipients>; Fri, 17 Jun 2011 13:31:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=XgrnMs6M2OQPcSmwbDB+RYC1ptdKIN/NBOEUnlLRkW4=; b=VeI/Yp04vcFseqGRUB8dS/tjzpPKV/GzxdeK/lMQsfGml8DODE0txfOVkWdUaaF6fz agKjvgFh5aP4V3/fOGXO+RTqoIqQZ0KzNYQ12AK29L2nguMTDSw22hnf1jlOI+6CtgDM XMMHOYgPPMC6HOTTIjCsuA3wTJoNGg8OVyqzM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=oydJC33TnsU+gz0TTLS6ezdVwHDsxYJNhJ0eLS95f+Cbs8a7sLnzeqEN48EEdf49FQ Mh2nWGRuLWCzaRL4NlWul28lBud0vXENt0JMgGdvUiqzSkPsUqzkpyOMmDCMIhvRD7PB 2nIS4HbQn0JTSTdqYaBUpqE/QE+SEbU+lJQL0=
Received: by 10.150.136.2 with SMTP id j2mr2942837ybd.125.1308342709130; Fri, 17 Jun 2011 13:31:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.14.8 with HTTP; Fri, 17 Jun 2011 13:31:29 -0700 (PDT)
In-Reply-To: <003e01cc2c65$ea831540$bf893fc0$@uni-tuebingen.de>
References: <003e01cc2c65$ea831540$bf893fc0$@uni-tuebingen.de>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 17 Jun 2011 16:31:29 -0400
Message-ID: <BANLkTimLCvhnWp6D_6ZYmK9N_s_yGHr+XQ@mail.gmail.com>
Subject: Re: [codec] Last Call: <draft-ietf-codec-requirements-04.txt> (Codec Requirements) to Informational RFC
To: Christian Hoene <hoene@uni-tuebingen.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: codec@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 Jun 2011 20:31:52 -0000

On Thu, Jun 16, 2011 at 4:42 PM, Christian Hoene <hoene@uni-tuebingen.de> w=
rote:
> Hello,
>
> In this draft, the editors of draft are not named as editors but as autho=
rs.
> Thus, I would suggest to follow the example given in
> http://www.rfc-editor.org/rfc/rfc5620.txt and add an ", Ed." behind the
> names. A list of authors is given in the acknowledgement section of the
> draft.

If everyone listed at the upper right of the first page is going to be
an Editor, then adding "Ed." after their name is completely
superfluous and adds only clutter.

Traditionally, those listed at the upper right of the first page of an
RFC have been called "authors" in most cases, regardless of their
actual role, and those listed in an Acknowledgements section have
frequently been called "contributors" or the like. So I think it s
perfectly fine the way it is in regards to this non-issue.

Donald

> With best regards,
>
> =A0Christian Hoene
>
>
>> -----Original Message-----
>> From: codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] On Behalf
>> Of The IESG
>> Sent: Thursday, June 16, 2011 9:24 PM
>> To: IETF-Announce
>> Cc: codec@ietf.org
>> Subject: [codec] Last Call: <draft-ietf-codec-requirements-04.txt> (Code=
c
>> Requirements) to Informational RFC
>>
>>
>> The IESG has received a request from the Internet Wideband Audio Codec
>> WG
>> (codec) to consider the following document:
>> - 'Codec Requirements'
>> =A0 <draft-ietf-codec-requirements-04.txt> as an 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 2011-06-30. Exceptionally, comments may b=
e
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>> =A0 =A0This document provides specific requirements for an Internet audi=
o
>> =A0 =A0codec. =A0These requirements address quality, sampling rate, bit-=
rate,
>> =A0 =A0and packet loss robustness, as well as other desirable properties=
.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-codec-requirements/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-codec-requirements/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>> _______________________________________________
>> codec mailing list
>> codec@ietf.org
>> https://www.ietf.org/mailman/listinfo/codec
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From johnl@iecc.com  Fri Jun 17 17:09:18 2011
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 7875121F84B7 for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 17:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.132
X-Spam-Level: 
X-Spam-Status: No, score=-110.132 tagged_above=-999 required=5 tests=[AWL=-0.422, BAYES_05=-1.11, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pXMohic-X9Cl for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 17:09:17 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id 02E7B21F84B5 for <ietf@ietf.org>; Fri, 17 Jun 2011 17:09:16 -0700 (PDT)
Received: (qmail 42098 invoked from network); 18 Jun 2011 00:09:14 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 18 Jun 2011 00:09:14 -0000
Date: 18 Jun 2011 00:08:52 -0000
Message-ID: <20110618000852.16048.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Getting to Quebec City
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 00:09:18 -0000

As you may have noticed, flying to Quebec City (YQB) is incredibly
expensive.  That's because it's a regional airport with little
competion.  Flying to Montreal is usuallly a lot cheaper.  Getting
from Trudeau airport in Montreal involves some planning, but it's not
hard.  The trip is about four hours; Quebec is big, bigger than any
state in the US.

By bus: Orleans Express has five buses a day.  You can buy tickets
online or at the ICE America desk in the airport lobby:

   https://www.orleansexpress.com/search.aspx

By train: there are four trains a day from Montreal to Quebec.
Although there is a train station in Dorval, close to the airport, it
doesn't have any through trains to Quebec so it's easier to go
downtown.  The 747 city bus runs every 10 to 15 minutes express to
downtown.  Get off at Mansfield for the central train station.  The
fare is $8, most easily paid by getting a day transit pass, which also
costs $8, at the currency exchange booth in the airport lobby.  For
train schedules and fares, see the Via Rail web site.

The Quebec train station is a medium walk or a short taxi trip from
the convention centre.

   http://www.stm.info/english/info/a-747.htm
   http://www.viarail.ca

You can rent a car and drive, but unless you're planning to do som
touring before or after the meeting, e.g., to the Saguenay fjord,
Montreal to Quebec not a very interesting drive so I wouldn't bother.

R's,
John

From ekr@rtfm.com  Fri Jun 17 17:32:21 2011
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66BFE11E819B for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 17:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iin7HmGQuZIy for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 17:32:20 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7F08111E8197 for <ietf@ietf.org>; Fri, 17 Jun 2011 17:32:20 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2384718wyb.31 for <ietf@ietf.org>; Fri, 17 Jun 2011 17:32:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.236.157 with SMTP id w29mr2933021weq.18.1308357139610; Fri, 17 Jun 2011 17:32:19 -0700 (PDT)
Received: by 10.216.175.213 with HTTP; Fri, 17 Jun 2011 17:32:19 -0700 (PDT)
In-Reply-To: <20110618000852.16048.qmail@joyce.lan>
References: <20110618000852.16048.qmail@joyce.lan>
Date: Fri, 17 Jun 2011 17:32:19 -0700
Message-ID: <BANLkTikttkO7tZSoF63Xnk66LjagqgZF7Q@mail.gmail.com>
Subject: Re: Getting to Quebec City
From: Eric Rescorla <ekr@rtfm.com>
To: John Levine <johnl@iecc.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 00:32:21 -0000

On Fri, Jun 17, 2011 at 5:08 PM, John Levine <johnl@iecc.com> wrote:
> As you may have noticed, flying to Quebec City (YQB) is incredibly
> expensive. =A0That's because it's a regional airport with little
> competion. =A0Flying to Montreal is usuallly a lot cheaper. =A0Getting
> from Trudeau airport in Montreal involves some planning, but it's not
> hard. =A0The trip is about four hours; Quebec is big, bigger than any
> state in the US.

Nitpick alert:

http://en.wikipedia.org/wiki/Quebec
http://en.wikipedia.org/wiki/List_of_U.S._states_and_territories_by_area

Quebec:   Land area=3D1,365,128 km2   Water Area=3D176,928 km2
Alaska:  Land Area: 1,481,347 km2  Water Area=3D236,507 km2

Perhaps you meant Continental US.

Best,
-Ekr

From melinda.shore@gmail.com  Fri Jun 17 17:50:12 2011
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 07BDF21F8534 for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 17:50: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LA8ap1imt7Wu for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 17:50:11 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by ietfa.amsl.com (Postfix) with ESMTP id 656A221F8530 for <ietf@ietf.org>; Fri, 17 Jun 2011 17:50:11 -0700 (PDT)
Received: by pvh18 with SMTP id 18so2550019pvh.31 for <ietf@ietf.org>; Fri, 17 Jun 2011 17:50:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=31iSQE4Zkd+BepveRYvmVQ9rvHK09Bq2YAfyBSTNkV0=; b=i1MNGwAl5z5tOaLkAc/sARR+08afeJf7VMQVMYYU0Cpr6GFuLIPhrxDMUEAlIhDSU8 AstcZQPqadlFx4NPXYpyrCuvAjQQJEkjW7LpMglOdOIJWbjnSydpke8+2eVA14bMYhz2 a+SDGHzxrP53J3BrL8Jk563CfH6faaMdYuNCM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Q0yyjhaeCeMTuOEhlMf3ZBV7qzdEUy0ZFxV22rlgbLAD6dp16egkq4SZATP7lEeWlg s1xqr7tBoYY2IVmRqZznpzdKrmJQ833HVX/nINLH5/g2Xop0clrLq0qsNZe6lExcjZNW w8QIC7ONSM2lCyoGvWjLXE4pqAhMYizkKTku8=
Received: by 10.142.234.14 with SMTP id g14mr469621wfh.230.1308358210984; Fri, 17 Jun 2011 17:50:10 -0700 (PDT)
Received: from [137.229.12.236] (drake.swits.alaska.edu [137.229.12.236]) by mx.google.com with ESMTPS id d15sm3352810wfl.6.2011.06.17.17.50.09 (version=SSLv3 cipher=OTHER); Fri, 17 Jun 2011 17:50:10 -0700 (PDT)
Message-ID: <4DFBF640.4060204@gmail.com>
Date: Fri, 17 Jun 2011 16:50:08 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: Eric Rescorla <ekr@rtfm.com>
Subject: Re: Getting to Quebec City
References: <20110618000852.16048.qmail@joyce.lan> <BANLkTikttkO7tZSoF63Xnk66LjagqgZF7Q@mail.gmail.com>
In-Reply-To: <BANLkTikttkO7tZSoF63Xnk66LjagqgZF7Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John Levine <johnl@iecc.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, 18 Jun 2011 00:50:12 -0000

On 06/17/2011 04:32 PM, Eric Rescorla wrote:
> Quebec:   Land area=1,365,128 km2   Water Area=176,928 km2
> Alaska:  Land Area: 1,481,347 km2  Water Area=236,507 km2
> Perhaps you meant Continental US.

Until recently if you tried to sign up for Google Voice
from Alaska you were informed that the service is not
available in your country.  People ask what the local
currency is.  John's oversight is a trivial one by
comparison.

Melinda

From ajs@anvilwalrusden.com  Fri Jun 17 18:31:38 2011
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 44DF011E8126 for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 18:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8bVJm39WJsGO for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 18:31:37 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 9C58F11E80BF for <ietf@ietf.org>; Fri, 17 Jun 2011 18:31:37 -0700 (PDT)
Received: from shinkuro.com (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 30B731ECB41C for <ietf@ietf.org>; Sat, 18 Jun 2011 01:31:35 +0000 (UTC)
Date: Fri, 17 Jun 2011 21:31:29 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Getting to Quebec City
Message-ID: <20110618013129.GA73132@shinkuro.com>
References: <20110618000852.16048.qmail@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110618000852.16048.qmail@joyce.lan>
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: Sat, 18 Jun 2011 01:31:38 -0000

On Sat, Jun 18, 2011 at 12:08:52AM -0000, John Levine wrote:

> By train: there are four trains a day from Montreal to Quebec.
> Although there is a train station in Dorval, close to the airport, it
> doesn't have any through trains to Quebec so it's easier to go
> downtown.

Note that if you plan to use Via Rail, you should treat the train
timetables as rough guidelines rather than something on which to rely.
The train usually does not run exactly on time, although the
timetables might be close enough for IETF arrival purposes.  But
worse, there are occasional equipment failures that make things fail
in big ways.  Via runs on tracks shared with (and owned by) the
freight lines, so if Via has an equipment failure that causes them a
delay, they can miss a window completely.  I have arrived over 4 hours
late on a trip that should not have taken 4 hours total.

One history of Canada suggests that we were only stitched together in
order to enable the CPR to be built.  Now we can barely run trains.
Sir Sanford Fleming must be unhappy.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From hamza.gharsallah@gmail.com  Fri Jun 17 19:14:01 2011
Return-Path: <hamza.gharsallah@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0FF811E811F for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 19:14:00 -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.833, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a8f91hskfjNS for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 19:14:00 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 41A9A11E8102 for <ietf@ietf.org>; Fri, 17 Jun 2011 19:14:00 -0700 (PDT)
Received: by iyn15 with SMTP id 15so3253499iyn.31 for <ietf@ietf.org>; Fri, 17 Jun 2011 19:13:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=J+DZB9nnk0chcaAszcYIAQzfnYfO1c+L6joIlSFcDX8=; b=S1pAVUAnz2CgiNxd58706SVqtnhU7xEZ16KjkQeK9U0aMS5R9bnaQY1owErehxyuDT UfwU0pVZhr2t5Tu3Tidl9/B2zIMmMUc2q3KKutRf3kjJfoSZRFKh4v5SBN5jcuOp7ARo kCJwSEkOg2i9qYVNMT4mVTi8BgJ9WTjrMEN1M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=KzoyuJtroPkU/FCDuJAfiKpFNJXRUA0SM8/2RhwajT4Ke0pUlgegvx3aQBaFAe2v3v DIV5RZYTTwCi1iHrMYeUvuiLOCzbLySu28zuORAnu3TPS1b2jDUPpFwpsaNuo+AHlZgq vQ6uxUKKrSPcHN9fZXFTChxbDGeB0672GZfHE=
MIME-Version: 1.0
Received: by 10.231.81.140 with SMTP id x12mr2511301ibk.31.1308363239813; Fri, 17 Jun 2011 19:13:59 -0700 (PDT)
Received: by 10.231.130.26 with HTTP; Fri, 17 Jun 2011 19:13:59 -0700 (PDT)
In-Reply-To: <4DFBF640.4060204@gmail.com>
References: <20110618000852.16048.qmail@joyce.lan> <BANLkTikttkO7tZSoF63Xnk66LjagqgZF7Q@mail.gmail.com> <4DFBF640.4060204@gmail.com>
Date: Sat, 18 Jun 2011 03:13:59 +0100
Message-ID: <BANLkTik9myir-uTojSO+m3TH7fe8VqFPrg@mail.gmail.com>
Subject: Re: Getting to Quebec City
From: Hamza GHARSALLAH <hamza.gharsallah@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=000e0cd482ce25712104a5f30e49
Cc: John Levine <johnl@iecc.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, 18 Jun 2011 02:14:01 -0000

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

Perhaps, the real surface is becoming smaller and smaller due to green house
effect! I wonder if Eye Pi Vee Six is greener!

On Sat, Jun 18, 2011 at 1:50 AM, Melinda Shore <melinda.shore@gmail.com>wrote:

> On 06/17/2011 04:32 PM, Eric Rescorla wrote:
>
>> Quebec:   Land area=1,365,128 km2   Water Area=176,928 km2
>> Alaska:  Land Area: 1,481,347 km2  Water Area=236,507 km2
>> Perhaps you meant Continental US.
>>
>
> Until recently if you tried to sign up for Google Voice
> from Alaska you were informed that the service is not
> available in your country.  People ask what the local
> currency is.  John's oversight is a trivial one by
> comparison.
>
> Melinda
>
> ______________________________**_________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/**listinfo/ietf<https://www.ietf.org/mailman/listinfo/ietf>
>

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

<div dir=3D"ltr">Perhaps, the real surface is becoming smaller and smaller =
due to green house effect! I wonder if Eye Pi Vee Six is greener!<br><br><d=
iv class=3D"gmail_quote">On Sat, Jun 18, 2011 at 1:50 AM, Melinda Shore <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:melinda.shore@gmail.com">melinda.shore=
@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div class=3D"im">On 06/17/2011 04:32 PM, E=
ric Rescorla wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Quebec: =A0 Land area=3D1,365,128 km2 =A0 Water Area=3D176,928 km2<br>
Alaska: =A0Land Area: 1,481,347 km2 =A0Water Area=3D236,507 km2<br>
Perhaps you meant Continental US.<br>
</blockquote>
<br></div>
Until recently if you tried to sign up for Google Voice<br>
from Alaska you were informed that the service is not<br>
available in your country. =A0People ask what the local<br>
currency is. =A0John&#39;s oversight is a trivial one by<br>
comparison.<br><font color=3D"#888888">
<br>
Melinda</font><div><div></div><div class=3D"h5"><br>
______________________________<u></u>_________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org" target=3D"_blank">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/ietf</a><br>
</div></div></blockquote></div><br></div>

--000e0cd482ce25712104a5f30e49--

From gwz@net-zen.net  Fri Jun 17 23:27:18 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C30B611E80DC for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 23:27: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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PWg0jmH+7B3A for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 23:27:18 -0700 (PDT)
Received: from p3plsmtpa01-05.prod.phx3.secureserver.net (p3plsmtpa01-05.prod.phx3.secureserver.net [72.167.82.85]) by ietfa.amsl.com (Postfix) with SMTP id 3672811E807C for <ietf@ietf.org>; Fri, 17 Jun 2011 23:27:17 -0700 (PDT)
Received: (qmail 29284 invoked from network); 18 Jun 2011 06:27:17 -0000
Received: from unknown (124.120.207.253) by p3plsmtpa01-05.prod.phx3.secureserver.net (72.167.82.85) with ESMTP; 18 Jun 2011 06:27:16 -0000
Message-ID: <4DFC4540.7030604@net-zen.net>
Date: Sat, 18 Jun 2011 13:27:12 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: John Levine <johnl@iecc.com>
Subject: Re: Getting to Quebec City
References: <20110618000852.16048.qmail@joyce.lan>
In-Reply-To: <20110618000852.16048.qmail@joyce.lan>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------040108050002020004030205"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2011 06:27:18 -0000

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

On 6/18/2011 7:08 AM, John Levine wrote:

> As you may have noticed, flying to Quebec City (YQB) is incredibly
> expensive.  

Hmm.  My ticket to QC was only ~$40 CAD > than the equivalent one to
Montreal, far less than R/T bus or train fare...

...

--------------040108050002020004030205
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------040108050002020004030205--

From gwz@net-zen.net  Fri Jun 17 23:30:48 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D969B11E811E for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 23:30: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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p7dd+P9ZCnWo for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 23:30:48 -0700 (PDT)
Received: from p3plsmtpa01-03.prod.phx3.secureserver.net (p3plsmtpa01-03.prod.phx3.secureserver.net [72.167.82.83]) by ietfa.amsl.com (Postfix) with SMTP id 39D8211E807C for <ietf@ietf.org>; Fri, 17 Jun 2011 23:30:47 -0700 (PDT)
Received: (qmail 11979 invoked from network); 18 Jun 2011 06:30:46 -0000
Received: from unknown (124.120.207.253) by p3plsmtpa01-03.prod.phx3.secureserver.net (72.167.82.83) with ESMTP; 18 Jun 2011 06:30:45 -0000
Message-ID: <4DFC4612.9080704@net-zen.net>
Date: Sat, 18 Jun 2011 13:30:42 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: Getting to Quebec City
References: <20110618000852.16048.qmail@joyce.lan> <20110618013129.GA73132@shinkuro.com>
In-Reply-To: <20110618013129.GA73132@shinkuro.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------080902030701010109070609"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2011 06:30:49 -0000

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

On 6/18/2011 8:31 AM, Andrew Sullivan wrote:
> On Sat, Jun 18, 2011 at 12:08:52AM -0000, John Levine wrote:
> 
>> By train: there are four trains a day from Montreal to Quebec.
>> Although there is a train station in Dorval, close to the airport, it
>> doesn't have any through trains to Quebec so it's easier to go
>> downtown.
> 
> Note that if you plan to use Via Rail, you should treat the train
> timetables as rough guidelines rather than something on which to rely.
> The train usually does not run exactly on time, although the
> timetables might be close enough for IETF arrival purposes.  But
> worse, there are occasional equipment failures that make things fail
> in big ways.  Via runs on tracks shared with (and owned by) the
> freight lines, so if Via has an equipment failure that causes them a
> delay, they can miss a window completely.  I have arrived over 4 hours
> late on a trip that should not have taken 4 hours total.

Sounds like air travel in China ;-)

...

--------------080902030701010109070609
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------080902030701010109070609--

From moore@network-heretics.com  Sat Jun 18 07:52:59 2011
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 87E3521F84CE for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 07:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DYb88xiyLcg0 for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 07:52:59 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id E5F4B21F84CD for <ietf@ietf.org>; Sat, 18 Jun 2011 07:52:58 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 20E1B2052D for <ietf@ietf.org>; Sat, 18 Jun 2011 10:52:58 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 18 Jun 2011 10:52:58 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=from:content-type:content-transfer-encoding:date:subject:to:message-id:mime-version; s=smtpout; bh=cjAwNb09w1cCDmyKGZDT4g4lpZY=; b=RKYjx/7cXRaq90yYKu+MTU9ERpYL2M66vqNrVaa5EZMouo1OV25Lrk2eMgX3Jy02KTQlUuH288E9tnphJeEd1skDfdAmgA+71uAwubGl6B3AkMG8izVrvFfz80nsK5urEDSe/fyjfM13JA/UZGxbSmLKbfPg+Gse72g8QOwAn7E=
X-Sasl-enc: ljHw/2niZDuirkBx1rHfd313sEfo1sBwF15zZHvCHSk4 1308408777
Received: from [10.5.50.71] (97-89-187-195.static.gnvl.sc.charter.com [97.89.187.195]) by mail.messagingengine.com (Postfix) with ESMTPA id D389E442F41; Sat, 18 Jun 2011 10:52:57 -0400 (EDT)
From: Keith Moore <moore@network-heretics.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Sat, 18 Jun 2011 10:52:50 -0400
Subject: Has anyone found a hotel for Quebec City that isn't exorbitant?
To: IETF Discussion <ietf@ietf.org>
Message-Id: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2011 14:52:59 -0000

Frankly, I'm appalled at the prices and think it's highly inappropriate =
for IETF to be meeting in venues where the "conference hotels" are so =
expensive.


From johnl@iecc.com  Sat Jun 18 08:23:04 2011
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 C3E3411E8132 for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 08:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.841
X-Spam-Level: 
X-Spam-Status: No, score=-110.841 tagged_above=-999 required=5 tests=[AWL=0.358, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NS1BbgciFD6V for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 08:23:04 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id ACA6D11E812B for <ietf@ietf.org>; Sat, 18 Jun 2011 08:23:03 -0700 (PDT)
Received: (qmail 65510 invoked from network); 18 Jun 2011 15:23:01 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 18 Jun 2011 15:23:01 -0000
Date: 18 Jun 2011 15:22:39 -0000
Message-ID: <20110618152239.47574.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
In-Reply-To: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
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 Jun 2011 15:23:04 -0000

I'm staying in the Delta for $209.  That doesn't seem out of line to
me.

People who are very price sensitive can stay in the Laval university
dorms for $52/night.  I know people who've stayed there for a
conference in the convention centre and said that it was fine.  It's
too far to walk, so you will need to take the bus back and forth, or
if there are several people, share a taxi.

http://www.residences.ulaval.ca/hebergement_hotelier/

I also see a fair number of B&B's in the old city for around $100.
That's an easy walk to the convention centre.

http://www.bonjourquebec.com/qc-en/accommodation-directory/bed-and-breakfast/quebec/


R's,
John

From mary.ietf.barnes@gmail.com  Sat Jun 18 08:43:49 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ACA011E816C for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 08:43:49 -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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HowNftJgIUIV for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 08:43:48 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id B12D411E818A for <ietf@ietf.org>; Sat, 18 Jun 2011 08:43:47 -0700 (PDT)
Received: by vxg33 with SMTP id 33so3223955vxg.31 for <ietf@ietf.org>; Sat, 18 Jun 2011 08:43:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4xe/trUVJYb1WDjsyCMDLE2O6Yt2bhWoIUru2EgHhRA=; b=WG5aB2yMXw3vgdRUAKxP1FTDrEBwyzXmiVbvEJo89i+v6IOc1x3Kn9fx2nUH78wVBc v6mxy9fJDmviqxV9Mr4Xa+b0IGsoocJ5l0Hb5HxDzyrXuQIRyDo3qqXHa0HQb5KmVfuU jHAeEzvQ4M1nbaEvR6A+TXvhARqBSwSLxgIjw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=HqQHF5AAXm4pvCUfmFcesLHnPXiFj5BLbFAh2FnOlwtfZPz1LkGEmNESFsjRvnzxB0 vHjNjIfCf6lXswjwO7YYZty2c996P70yp883zQTptm3AM06t464dhVmBBL9P4UIbVYuq AnN8AX5t5+RgqAg/frFyDBjCXBd7/WY8NbjPg=
MIME-Version: 1.0
Received: by 10.52.185.231 with SMTP id ff7mr5028220vdc.103.1308411826680; Sat, 18 Jun 2011 08:43:46 -0700 (PDT)
Received: by 10.52.158.39 with HTTP; Sat, 18 Jun 2011 08:43:46 -0700 (PDT)
In-Reply-To: <20110618000852.16048.qmail@joyce.lan>
References: <20110618000852.16048.qmail@joyce.lan>
Date: Sat, 18 Jun 2011 10:43:46 -0500
Message-ID: <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com>
Subject: Re: Getting to Quebec City
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: John Levine <johnl@iecc.com>
Content-Type: multipart/alternative; boundary=bcaec548a6cd2631d304a5fe5e92
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2011 15:43:49 -0000

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

As far as renting a car, it is likely a very good choice for anyone that is
arriving in Montreal later in the day.  I have a choice of one direct flight
to Montreal that puts me arriving in Montreal > 7pm.  Even a one stop flight
still puts me arriving around that time.  So, given my experience in
Maastricht with trains and a trip that took about 18 hours gate to gate, I
plan to rent a car (and drop it off in QC on Sunday), which results in a
trip < 8 hours gate to gate.  Whereas, flying into QC ends up taking nearly
12 hours with layovers/connections.  While Quebec might be bigger than
states other than Alaska., the distances between QC, Montreal, Toronto, etc.
are very similar to Dallas, Austin, San Antonio and Houston, which are all
reasonable drive times for some of us.

Regards,
Mary.

On Fri, Jun 17, 2011 at 7:08 PM, John Levine <johnl@iecc.com> wrote:

> As you may have noticed, flying to Quebec City (YQB) is incredibly
> expensive.  That's because it's a regional airport with little
> competion.  Flying to Montreal is usuallly a lot cheaper.  Getting
> from Trudeau airport in Montreal involves some planning, but it's not
> hard.  The trip is about four hours; Quebec is big, bigger than any
> state in the US.
>
> By bus: Orleans Express has five buses a day.  You can buy tickets
> online or at the ICE America desk in the airport lobby:
>
>   https://www.orleansexpress.com/search.aspx
>
> By train: there are four trains a day from Montreal to Quebec.
> Although there is a train station in Dorval, close to the airport, it
> doesn't have any through trains to Quebec so it's easier to go
> downtown.  The 747 city bus runs every 10 to 15 minutes express to
> downtown.  Get off at Mansfield for the central train station.  The
> fare is $8, most easily paid by getting a day transit pass, which also
> costs $8, at the currency exchange booth in the airport lobby.  For
> train schedules and fares, see the Via Rail web site.
>
> The Quebec train station is a medium walk or a short taxi trip from
> the convention centre.
>
>   http://www.stm.info/english/info/a-747.htm
>   http://www.viarail.ca
>
> You can rent a car and drive, but unless you're planning to do som
> touring before or after the meeting, e.g., to the Saguenay fjord,
> Montreal to Quebec not a very interesting drive so I wouldn't bother.
>
> R's,
> John
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

As far as renting a car, it is likely a very good choice for anyone that is=
 arriving in Montreal later in the day. =A0I have a choice of one direct fl=
ight to Montreal that puts me arriving in Montreal &gt; 7pm. =A0Even a one =
stop flight still puts me arriving around that time. =A0So, given my experi=
ence in Maastricht with trains and a trip that took about 18 hours gate to =
gate, I plan to rent a car (and drop it off in QC on Sunday), which results=
 in a trip &lt; 8 hours gate to gate. =A0Whereas, flying into QC ends up ta=
king nearly 12 hours with layovers/connections. =A0While Quebec might be bi=
gger than states other than Alaska., the distances between QC, Montreal, To=
ronto, etc. are very similar to Dallas, Austin, San Antonio and Houston, wh=
ich are all reasonable drive times for some of us.=A0<div>
<div><br></div><div>Regards,</div><div>Mary.=A0<br><div><br></div><div><div=
 class=3D"gmail_quote">On Fri, Jun 17, 2011 at 7:08 PM, John Levine <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:johnl@iecc.com">johnl@iecc.com</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">As you may have noticed, flying to Quebec C=
ity (YQB) is incredibly<br>
expensive. =A0That&#39;s because it&#39;s a regional airport with little<br=
>
competion. =A0Flying to Montreal is usuallly a lot cheaper. =A0Getting<br>
from Trudeau airport in Montreal involves some planning, but it&#39;s not<b=
r>
hard. =A0The trip is about four hours; Quebec is big, bigger than any<br>
state in the US.<br>
<br>
By bus: Orleans Express has five buses a day. =A0You can buy tickets<br>
online or at the ICE America desk in the airport lobby:<br>
<br>
 =A0 <a href=3D"https://www.orleansexpress.com/search.aspx" target=3D"_blan=
k">https://www.orleansexpress.com/search.aspx</a><br>
<br>
By train: there are four trains a day from Montreal to Quebec.<br>
Although there is a train station in Dorval, close to the airport, it<br>
doesn&#39;t have any through trains to Quebec so it&#39;s easier to go<br>
downtown. =A0The 747 city bus runs every 10 to 15 minutes express to<br>
downtown. =A0Get off at Mansfield for the central train station. =A0The<br>
fare is $8, most easily paid by getting a day transit pass, which also<br>
costs $8, at the currency exchange booth in the airport lobby. =A0For<br>
train schedules and fares, see the Via Rail web site.<br>
<br>
The Quebec train station is a medium walk or a short taxi trip from<br>
the convention centre.<br>
<br>
 =A0 <a href=3D"http://www.stm.info/english/info/a-747.htm" target=3D"_blan=
k">http://www.stm.info/english/info/a-747.htm</a><br>
 =A0 <a href=3D"http://www.viarail.ca" target=3D"_blank">http://www.viarail=
.ca</a><br>
<br>
You can rent a car and drive, but unless you&#39;re planning to do som<br>
touring before or after the meeting, e.g., to the Saguenay fjord,<br>
Montreal to Quebec not a very interesting drive so I wouldn&#39;t bother.<b=
r>
<br>
R&#39;s,<br>
John<br>
_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
</blockquote></div><br></div></div></div>

--bcaec548a6cd2631d304a5fe5e92--

From johnl@iecc.com  Sat Jun 18 09:08:39 2011
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 CB34121F84B9 for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 09:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.913
X-Spam-Level: 
X-Spam-Status: No, score=-110.913 tagged_above=-999 required=5 tests=[AWL=0.286, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nn28zMXT3HhX for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 09:08:39 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id AE9F321F84A7 for <ietf@ietf.org>; Sat, 18 Jun 2011 09:08:38 -0700 (PDT)
Received: (qmail 76368 invoked from network); 18 Jun 2011 16:08:36 -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:vbr-info:user-agent:cleverness; s=12a4f.4dfccd84.k1106; i=johnl@submit.iecc.com; bh=L8tD100pvcPi6PNWsXl0xl+pjMxmKrqlj2oZFeZAUZQ=; b=kBWt8YS/AOKsPgIgm9IhXApy1H7/gJ5B/dOkrspnkVwqaCWWR84Lix+RdIE6nvcboRxjRIkg5VQuA0qeNdL5E3jR55mnlrx9q4dOUbnJle/h8YExQRkNxIMWy73d9IeLbApALPIoGrmVQDsBzRZPRDeErLAa/icD8WoGpudtPtE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 18 Jun 2011 16:08:14 -0000
Date: 18 Jun 2011 12:08:36 -0400
Message-ID: <alpine.BSF.2.00.1106181202470.48766@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Mary Barnes" <mary.ietf.barnes@gmail.com>
Subject: Re: Getting to Quebec City
In-Reply-To: <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com>
References: <20110618000852.16048.qmail@joyce.lan> <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2011 16:08:39 -0000

> As far as renting a car, it is likely a very good choice for anyone that is
> arriving in Montreal later in the day.  I have a choice of one direct flight
> to Montreal that puts me arriving in Montreal > 7pm.

FYI, there is a direct bus from YUL to Quebec that leaves at 20:30.  With 
Wifi, even.  It's a reasonable choice, and about $100 less than a one way 
car rental.  The Quebec bus station is adjacent to the train station and a 
quick taxi to hotels.

R's,
John

From scott.brim@gmail.com  Sat Jun 18 09:10:51 2011
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 9642011E81BA for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 09:10:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79u1gtedqCS8 for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 09:10:50 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD1011E81A2 for <ietf@ietf.org>; Sat, 18 Jun 2011 09:10:50 -0700 (PDT)
Received: by iye7 with SMTP id 7so383074iye.31 for <ietf@ietf.org>; Sat, 18 Jun 2011 09:10:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=RUqh/GDWxPfbfTMIYevAIB5h45IUXTVjWOwcpaCmM3c=; b=FyXdlofLmodyt+vxHCVJ9Kwe2AWdqQxjULeaMSBeaKmYQ/OJ8wLkLmAbaEwQKJK0xM 5QlP6KMqyNxxP1OGg2RmHdlYQAwr8YVljkaKi6JwxNz1b6+9obVbZ6Msp0VSUj0ovPJL q9DLE+nLcPMd4377YG57ImnsNNdLr7mGqOvdw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=wjnNKAPxDFfA/oIhU197bosrQ8xAx51rOT2gnm5Ml8RNOuKslP9Mj0eWCRhpd6X0Pq a0r1STu0ic8AJr6ltzZ68Ajt3fKKoUX4TYMu1wSiMtYYT5DEqtyIq2q/MhYHj/+NlXft YoRXt40nhalEU5kos4a5TKQ8w9qlI3C4bpcJk=
Received: by 10.231.61.83 with SMTP id s19mr3174630ibh.19.1308413450120; Sat, 18 Jun 2011 09:10:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.15.198 with HTTP; Sat, 18 Jun 2011 09:10:30 -0700 (PDT)
In-Reply-To: <20110618152239.47574.qmail@joyce.lan>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <20110618152239.47574.qmail@joyce.lan>
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 18 Jun 2011 12:10:30 -0400
Message-ID: <BANLkTimiVLBkE1fFKkdwiOHg4tJgUy5q2g@mail.gmail.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
To: John Levine <johnl@iecc.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, 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 Jun 2011 16:10:51 -0000

Chateau Laurier $135 via booking.com

From ole@cisco.com  Sat Jun 18 09:20:14 2011
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 47F9911E81D1 for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 09:20:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.986
X-Spam-Level: 
X-Spam-Status: No, score=-110.986 tagged_above=-999 required=5 tests=[AWL=-0.387, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dycao0MfqhOS for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 09:20:13 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6726F11E81CE for <ietf@ietf.org>; Sat, 18 Jun 2011 09:20:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=679; q=dns/txt; s=iport; t=1308414013; x=1309623613; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=yurfL5yXWaT7Q7YmTH58fMHHVFRYBsaMCY1DR/BCB2w=; b=doD/UTW4hcKtm2vqap3ExDrLwrf8+KHv7cW6kZAAiLeKY3TDTKi8HIqw owtXw9YG2XRpk75bvRCyeJuQ1C8yN4FGFiL2FbN9ziR0mt616hR5U7R5O 7H4hbob/lQaE3NlIPChNeO7eTltObwbf0aCTtgtNPdTpA5Upo6KEnLPL9 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAMnP/E1Io8UR/2dsb2JhbABMBpkFjVp3qRuDDw8Bmh2DN4JzBIcgjx6LQQ
X-IronPort-AV: E=Sophos;i="4.65,386,1304294400"; d="scan'208";a="35848151"
Received: from bgl-core-2.cisco.com ([72.163.197.17]) by ams-iport-2.cisco.com with ESMTP; 18 Jun 2011 16:20:08 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5IGK4Dc007110; Sat, 18 Jun 2011 16:20:06 GMT
Date: Sat, 18 Jun 2011 09:20:04 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Getting to Quebec City
In-Reply-To: <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com>
Message-ID: <alpine.OSX.2.01.1106180913300.66041@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <20110618000852.16048.qmail@joyce.lan> <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: John Levine <johnl@iecc.com>, 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: Sat, 18 Jun 2011 16:20:14 -0000

Here is what I am doing:

* Fly SFO-ORD and ORD-YUL, gets me to Montreal at 21:14

* Spend the night at the Hilton Montreal, this is very close to the 
  train station.

* Take Train 620 @ 0830 from Montreal, arrives 11:35 in Quebec City 
  (if it runs on time :-)

That should at least get me to the meeting before the opening 
reception, we'll see...

Yes, this involves an extra hotel night etc, but I think it will be 
a lot less stressful.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo



From mstjohns@comcast.net  Sat Jun 18 11:50:43 2011
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 572A311E814F for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 11:50: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6XISBaosWFnI for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 11:50:42 -0700 (PDT)
Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by ietfa.amsl.com (Postfix) with ESMTP id 745F911E80E0 for <ietf@ietf.org>; Sat, 18 Jun 2011 11:50:42 -0700 (PDT)
Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta14.emeryville.ca.mail.comcast.net with comcast id xWTA1g0061wfjNsAEWqgza; Sat, 18 Jun 2011 18:50:40 +0000
Received: from Mike-PC3.comcast.net ([68.83.217.57]) by omta23.emeryville.ca.mail.comcast.net with comcast id xWqo1g00G1EtFYL8jWqqnk; Sat, 18 Jun 2011 18:50:52 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sat, 18 Jun 2011 14:50:28 -0400
To: Ole Jacobsen <ole@cisco.com>,Mary Barnes <mary.ietf.barnes@gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Getting to Quebec City
In-Reply-To: <alpine.OSX.2.01.1106180913300.66041@173-11-110-132-sfba.hf c.comcastbusiness.net>
References: <20110618000852.16048.qmail@joyce.lan> <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com> <alpine.OSX.2.01.1106180913300.66041@173-11-110-132-sfba.hfc.comcastbusiness.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20110618185042.745F911E80E0@ietfa.amsl.com>
Cc: John Levine <johnl@iecc.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, 18 Jun 2011 18:50:43 -0000

Why didn't you fly ORD-YQB? There's a 7pm flight that gets in around 10:23.  It had to be cheaper than a hotel and train ride.

Mike


At 12:20 PM 6/18/2011, Ole Jacobsen wrote:

>Here is what I am doing:
>
>* Fly SFO-ORD and ORD-YUL, gets me to Montreal at 21:14
>
>* Spend the night at the Hilton Montreal, this is very close to the 
>  train station.
>
>* Take Train 620 @ 0830 from Montreal, arrives 11:35 in Quebec City 
>  (if it runs on time :-)
>
>That should at least get me to the meeting before the opening 
>reception, we'll see...
>
>Yes, this involves an extra hotel night etc, but I think it will be 
>a lot less stressful.
>
>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
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf



From aj@sneep.net  Sat Jun 18 12:09:16 2011
Return-Path: <aj@sneep.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31FED11E81F7 for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 12:09:16 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EIpgoqvRDW0N for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 12:09:15 -0700 (PDT)
Received: from sonic.sneep.net (sonic.sneep.net [202.180.80.82]) by ietfa.amsl.com (Postfix) with ESMTP id 6935811E80E0 for <ietf@ietf.org>; Sat, 18 Jun 2011 12:09:15 -0700 (PDT)
Received: from [10.0.1.4] (c-69-181-160-132.hsd1.ca.comcast.net [69.181.160.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by sonic.sneep.net (Postfix) with ESMTP id DBC4D37FD1; Sun, 19 Jun 2011 07:09:11 +1200 (NZST)
References: <20110618000852.16048.qmail@joyce.lan> <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com> <alpine.OSX.2.01.1106180913300.66041@173-11-110-132-sfba.hfc.comcastbusiness.net> <20110618185042.745F911E80E0@ietfa.amsl.com>
In-Reply-To: <20110618185042.745F911E80E0@ietfa.amsl.com>
Mime-Version: 1.0 (iPad Mail 8J3)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <4539C55B-FD50-412E-AF06-43C3E377FC31@sneep.net>
X-Mailer: iPad Mail (8J3)
From: Alastair Johnson <aj@sneep.net>
Subject: Re: Getting to Quebec City
Date: Sat, 18 Jun 2011 12:09:25 -0700
To: Michael StJohns <mstjohns@comcast.net>
Cc: John Levine <johnl@iecc.com>, Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 19:09:16 -0000

That's what I'm doing - the SFO-ORD-YQB fare was the same as flying to YUL.

AJ

On 18/06/2011, at 11:50 AM, Michael StJohns <mstjohns@comcast.net> wrote:

> Why didn't you fly ORD-YQB? There's a 7pm flight that gets in around 10:23=
.  It had to be cheaper than a hotel and train ride.
>=20
> Mike
>=20
>=20
> At 12:20 PM 6/18/2011, Ole Jacobsen wrote:
>=20
>> Here is what I am doing:
>>=20
>> * Fly SFO-ORD and ORD-YUL, gets me to Montreal at 21:14
>>=20
>> * Spend the night at the Hilton Montreal, this is very close to the=20
>> train station.
>>=20
>> * Take Train 620 @ 0830 from Montreal, arrives 11:35 in Quebec City=20
>> (if it runs on time :-)
>>=20
>> That should at least get me to the meeting before the opening=20
>> reception, we'll see...
>>=20
>> Yes, this involves an extra hotel night etc, but I think it will be=20
>> a lot less stressful.
>>=20
>> Ole
>>=20
>>=20
>> 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
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From ole@cisco.com  Sat Jun 18 12:39:38 2011
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 7A28911E8217 for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 12:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.951
X-Spam-Level: 
X-Spam-Status: No, score=-110.951 tagged_above=-999 required=5 tests=[AWL=-0.352, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nN3GYioQOVhd for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 12:39:38 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id B401711E820F for <ietf@ietf.org>; Sat, 18 Jun 2011 12:39:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=252; q=dns/txt; s=iport; t=1308425977; x=1309635577; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=xr445B8Or6ijFsfdfOQNMCykQA+72ToS9r9OKVfTGQ8=; b=GeLDdmwQyuKKKMnrnHrKBYlfXCUL8cq/+CEPef0u+JBeXZVqRyd9/E0T UjOXugVLiwi+FQY1g3sXSNBtJXEQPYECKAXO3KNQRnkvzakkFk/akuRDF KE63OTNydr/MC2bRTkq88ERA8AYCBQuKHLCBwEIi00BdpxcUSG+AYrIsd Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EALL+/E1Io8UT/2dsb2JhbABRmQWNWneIc58Ygw8PAZoHhioEhyCPHotB
X-IronPort-AV: E=Sophos;i="4.65,386,1304294400"; d="scan'208";a="35856906"
Received: from bgl-core-4.cisco.com ([72.163.197.19]) by ams-iport-2.cisco.com with ESMTP; 18 Jun 2011 19:39:35 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by bgl-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p5IJdVm6032407; Sat, 18 Jun 2011 19:39:32 GMT
Date: Sat, 18 Jun 2011 12:39:30 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Getting to Quebec City
In-Reply-To: <20110618185042.745F911E80E0@ietfa.amsl.com>
Message-ID: <alpine.OSX.2.01.1106181238100.66339@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <20110618000852.16048.qmail@joyce.lan> <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com> <alpine.OSX.2.01.1106180913300.66041@173-11-110-132-sfba.hfc.comcastbusiness.net> <20110618185042.745F911E80E0@ietfa.amsl.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: John Levine <johnl@iecc.com>, 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: Sat, 18 Jun 2011 19:39:38 -0000

On Sat, 18 Jun 2011, Michael StJohns wrote:

> Why didn't you fly ORD-YQB? There's a 7pm flight that gets in around 
> 10:23.  It had to be cheaper than a hotel and train ride.

Probably not available at the time I made the booking...


Ole

From johnl@iecc.com  Sat Jun 18 12:46:54 2011
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 6F1CE11E822C for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 12:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.931
X-Spam-Level: 
X-Spam-Status: No, score=-110.931 tagged_above=-999 required=5 tests=[AWL=0.268, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yQ7o89iAjevq for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 12:46:53 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id 9528511E820F for <ietf@ietf.org>; Sat, 18 Jun 2011 12:46:53 -0700 (PDT)
Received: (qmail 17349 invoked from network); 18 Jun 2011 19:46:51 -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:vbr-info:user-agent:cleverness; s=43c4.4dfd00ab.k1106; i=johnl@submit.iecc.com; bh=tBWCTstjbwuTjqpc4GSnyAHMSg5cf/pxF3PXIHlZN+A=; b=shqBRVRI8S224kSiuG+le0T1BpDFOTYxeeUMbzBhpn66HG5SIqbQSTE8j06UCjkhayWu99elHuaIg2zm3icR0a2Sq4HdA/065gaXiQSexE6MvGAtMhYikTE3esNaLXQWCnXkuxGZe+XZgv5t4NfSt9Mp3EJdoVNOQcCve9az3bY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 18 Jun 2011 19:46:29 -0000
Date: 18 Jun 2011 15:46:50 -0400
Message-ID: <alpine.BSF.2.00.1106181543100.55626@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Ole Jacobsen" <ole@cisco.com>
Subject: Re: Getting to Quebec City
In-Reply-To: <alpine.OSX.2.01.1106181238100.66339@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <20110618000852.16048.qmail@joyce.lan> <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com> <alpine.OSX.2.01.1106180913300.66041@173-11-110-132-sfba.hfc.comcastbusiness.net> <20110618185042.745F911E80E0@ietfa.amsl.com> <alpine.OSX.2.01.1106181238100.66339@173-11-110-132-sfba.hfc.comcastbusiness.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2011 19:46:54 -0000

>> Why didn't you fly ORD-YQB? There's a 7pm flight that gets in around
>> 10:23.  It had to be cheaper than a hotel and train ride.
>
> Probably not available at the time I made the booking...

Expert flyer says it still has four seats available, with fares in Y B M U 
H Q V classes and one way fare of $307.  You can change your ticket and 
save the hassle.

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 tjc@ecs.soton.ac.uk  Sat Jun 18 15:12:42 2011
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 DEE0B11E80DB for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 15:12: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id reotYGTfUdY0 for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 15:12:42 -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 8AFC711E80BC for <ietf@ietf.org>; Sat, 18 Jun 2011 15:12:40 -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 p5IMCbRb012480 for <ietf@ietf.org>; Sat, 18 Jun 2011 23:12:37 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p5IMCbRb012480
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1308435157; bh=iHmXYlln396eoqxtd6pkRJXyI6w=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=WUVeYjFG4KX3PqtkX1baW92o3FEauhAV8/nLO5JfUwVhlwcu+jJAtgTM5DjvrfkQf SEXmynPdAvctFUZUn/vUTcLq+DolldMtta7uIEHt5XsgFQXGnPhWaFOCzApJceF3c3 lUfVNc/EncgUfB7wjmdvTLwfzNyNcluiE24ThU+s=
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 id n5HNCb0366107706zi ret-id none; Sat, 18 Jun 2011 23:12:37 +0100
Received: from [192.168.1.18] (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 p5IMBDdL004004 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 18 Jun 2011 23:11:17 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Getting to Quebec City
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <alpine.BSF.2.00.1106181202470.48766@joyce.lan>
Date: Sat, 18 Jun 2011 23:11:13 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|12dd9d65a0606d9ad53ba075ffe54bdbn5HNCb03tjc|ecs.soton.ac.uk|0963964C-CC57-43F3-89F6-86B64D115969@ecs.soton.ac.uk>
References: <20110618000852.16048.qmail@joyce.lan> <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com> <alpine.BSF.2.00.1106181202470.48766@joyce.lan> <0963964C-CC57-43F3-89F6-86B64D115969@ecs.soton.ac.uk>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n5HNCb036610770600; tid=n5HNCb0366107706zi; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p5IMCbRb012480
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2011 22:12:43 -0000

On 18 Jun 2011, at 17:08, John R. Levine wrote:

>> As far as renting a car, it is likely a very good choice for anyone =
that is
>> arriving in Montreal later in the day.  I have a choice of one direct =
flight
>> to Montreal that puts me arriving in Montreal > 7pm.
>=20
> FYI, there is a direct bus from YUL to Quebec that leaves at 20:30.  =
With Wifi, even.  It's a reasonable choice, and about $100 less than a =
one way car rental.  The Quebec bus station is adjacent to the train =
station and a quick taxi to hotels.

I'm flying internationally to Montreal and have a connecting flight from =
there to Quebec City with Air Canada (if they're not on strike, though =
the planes still to be flying despite that).  The connect is listed at =
50 mins so is probably about 30-40 in the air.

Tim=

From gwz@net-zen.net  Sat Jun 18 23:01:45 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C989911E80E9 for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 23:01: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1U3tuzsf7IRm for <ietf@ietfa.amsl.com>; Sat, 18 Jun 2011 23:01:45 -0700 (PDT)
Received: from p3plsmtpa01-07.prod.phx3.secureserver.net (p3plsmtpa01-07.prod.phx3.secureserver.net [72.167.82.87]) by ietfa.amsl.com (Postfix) with SMTP id BDC5511E807D for <ietf@ietf.org>; Sat, 18 Jun 2011 23:01:44 -0700 (PDT)
Received: (qmail 22284 invoked from network); 19 Jun 2011 06:01:42 -0000
Received: from unknown (115.87.106.237) by p3plsmtpa01-07.prod.phx3.secureserver.net (72.167.82.87) with ESMTP; 19 Jun 2011 06:01:42 -0000
Message-ID: <4DFD90C1.7010903@net-zen.net>
Date: Sun, 19 Jun 2011 13:01:37 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>
In-Reply-To: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------070705060009020606000602"
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Jun 2011 06:01:45 -0000

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

On 6/18/2011 9:52 PM, Keith Moore wrote:

> Frankly, I'm appalled at the prices and think it's highly inappropriate for IETF to be meeting in venues where the "conference hotels" are so expensive.

Don't get me started on the negotiating "skills" of the IAOC.  More to
the point, there are a lot of hotels that are half the price of the
conference hotels (or less) within walking distance.  Here's one:
http://www.autrejardin.com/quebec-hotel/index.php

--------------070705060009020606000602
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------070705060009020606000602--

From bob.hinden@gmail.com  Sun Jun 19 23:00:09 2011
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 C724E21F8451 for <ietf@ietfa.amsl.com>; Sun, 19 Jun 2011 23:00:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UyRt5YE2X7dZ for <ietf@ietfa.amsl.com>; Sun, 19 Jun 2011 23:00:09 -0700 (PDT)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 0658721F844A for <ietf@ietf.org>; Sun, 19 Jun 2011 23:00:08 -0700 (PDT)
Received: by wwg11 with SMTP id 11so1886668wwg.1 for <ietf@ietf.org>; Sun, 19 Jun 2011 23:00:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=oIC8j1SjCMWoXu9eOZB6I38LXM5u2BDew07GCD86rnQ=; b=YcHgARaY06kKOMnnRmOar2VQZKgoxsw4avxYwNoqf0o+W91Bijs8oojQ4lBNDgootU 4XgVYsWXK6xOXx3IJzTsnPbVsTJKkzxDjPl2h/ArR8X4kID9eAo0eXqC6T4Ho3+MmSX4 HYMpNFE2PEXrzo/DsK1Q6bD09bx4OkkvAxoYc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=u2dU7Q6V3OHwa7REKqs3FW40m7ArGhCx1jaELUxY/V2TmfJmvXbgQfZAXoWZcuyi9+ dgSGk5deeh1kRvkSNybA2cYkCEuMeU7KTmczp2ojA+toGesI65t712HvgcksL9elaF6g IRbKqSGVnJkkRB46yt/IvWcFz6/ZoG4Xc7Ass=
Received: by 10.216.239.68 with SMTP id b46mr4574047wer.38.1308549606733; Sun, 19 Jun 2011 23:00:06 -0700 (PDT)
Received: from [10.0.0.37] (c-24-130-225-13.hsd1.ca.comcast.net [24.130.225.13]) by mx.google.com with ESMTPS id t79sm2686346weq.29.2011.06.19.23.00.03 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 19 Jun 2011 23:00:05 -0700 (PDT)
Subject: Re: Getting to Quebec City
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4539C55B-FD50-412E-AF06-43C3E377FC31@sneep.net>
Date: Sun, 19 Jun 2011 23:00:01 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B523F127-E4D4-484B-9063-EFF2D4909D2E@gmail.com>
References: <20110618000852.16048.qmail@joyce.lan> <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com> <alpine.OSX.2.01.1106180913300.66041@173-11-110-132-sfba.hfc.comcastbusiness.net> <20110618185042.745F911E80E0@ietfa.amsl.com> <4539C55B-FD50-412E-AF06-43C3E377FC31@sneep.net>
To: Alastair Johnson <aj@sneep.net>
X-Mailer: Apple Mail (2.1084)
Cc: John Levine <johnl@iecc.com>, Ole Jacobsen <ole@cisco.com>, Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 06:00:09 -0000

On Jun 18, 2011, at 12:09 PM, Alastair Johnson wrote:

> That's what I'm doing - the SFO-ORD-YQB fare was the same as flying to =
YUL.

+1

Bob


>=20
> AJ
>=20
> On 18/06/2011, at 11:50 AM, Michael StJohns <mstjohns@comcast.net> =
wrote:
>=20
>> Why didn't you fly ORD-YQB? There's a 7pm flight that gets in around =
10:23.  It had to be cheaper than a hotel and train ride.
>>=20
>> Mike
>>=20
>>=20
>> At 12:20 PM 6/18/2011, Ole Jacobsen wrote:
>>=20
>>> Here is what I am doing:
>>>=20
>>> * Fly SFO-ORD and ORD-YUL, gets me to Montreal at 21:14
>>>=20
>>> * Spend the night at the Hilton Montreal, this is very close to the=20=

>>> train station.
>>>=20
>>> * Take Train 620 @ 0830 from Montreal, arrives 11:35 in Quebec City=20=

>>> (if it runs on time :-)
>>>=20
>>> That should at least get me to the meeting before the opening=20
>>> reception, we'll see...
>>>=20
>>> Yes, this involves an extra hotel night etc, but I think it will be=20=

>>> a lot less stressful.
>>>=20
>>> Ole
>>>=20
>>>=20
>>> 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
>>>=20
>>>=20
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From simon.perreault@viagenie.ca  Mon Jun 20 05:56:41 2011
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFBAA1F0C37 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 05:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.856
X-Spam-Level: 
X-Spam-Status: No, score=-1.856 tagged_above=-999 required=5 tests=[AWL=-0.745, BAYES_05=-1.11, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gxLcgd-s0+5U for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 05:56:41 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id BC9641F0C3F for <ietf@ietf.org>; Mon, 20 Jun 2011 05:56:40 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:21d:60ff:fed7:e732]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 201412151B for <ietf@ietf.org>; Mon, 20 Jun 2011 08:56:37 -0400 (EDT)
Message-ID: <4DFF4382.5010004@viagenie.ca>
Date: Mon, 20 Jun 2011 08:56:34 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110320 Fedora/3.1.9-4.fc16 Lightning/1.0b3pre Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Getting to Quebec City
References: <20110618000852.16048.qmail@joyce.lan>
In-Reply-To: <20110618000852.16048.qmail@joyce.lan>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 12:56:42 -0000

We wrote these instructions for those who want to fly to Montréal
instead of Québec:

http://ietf81.ca/?page_id=423

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From fluffy@cisco.com  Mon Jun 20 06:31:50 2011
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 D12A511E80AC; Mon, 20 Jun 2011 06:31:50 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d6SRJ8QrMyb5; Mon, 20 Jun 2011 06:31:49 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id DCE4211E8082; Mon, 20 Jun 2011 06:31:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=4104; q=dns/txt; s=iport; t=1308576709; x=1309786309; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=YyRCgEeYyo1JyZqyj3JWiMiKU+H2wtqgVnJNAUdFEno=; b=EuPvrcsj8Wz6h+QKKb+wjcv4FDYs1pFhkHaDHq45il9qgJG04aSvCS2+ lYfVtjS+DPIfwlg2dojGsdE9hq3AoMVHrGgx4Up4woqY8au4BM+NEugdw CdbVXXpZKZa7DB50hycPEADKutGewDg3uLFpITn/0EUfelc4lsbZjemAD w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvUAAHJL/02rRDoJ/2dsb2JhbABGDZdRjwt3iHOhGp1jgx6DDASHIIo+hGCLQA
X-IronPort-AV: E=Sophos;i="4.65,394,1304294400"; d="scan'208";a="717282598"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-6.cisco.com with ESMTP; 20 Jun 2011 13:31:48 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p5KDVlQx021477; Mon, 20 Jun 2011 13:31:47 GMT
Subject: Re: [codec] Last Call: <draft-ietf-codec-requirements-04.txt>	(Codec	Requirements) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <003e01cc2c65$ea831540$bf893fc0$@uni-tuebingen.de>
Date: Mon, 20 Jun 2011 07:31:47 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C1BBE56-DC0A-47A0-9F2C-A622AAB77EAA@cisco.com>
References: <003e01cc2c65$ea831540$bf893fc0$@uni-tuebingen.de>
To: Christian Hoene <hoene@uni-tuebingen.de>
X-Mailer: Apple Mail (2.1084)
Cc: codec@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, 20 Jun 2011 13:31:50 -0000

This is all a sort of confusing point of many IETF documents and not =
unique to this one. I think the important points is that for many IETF =
documents, the people listed on the front page are not the authors. =
Typically the list of authors is a much longer list. And to clarify what =
I mean by Author, I mean it in the sense that it would used in copyright =
law. I do think the Acknowledgements section needs to identity anyone =
who is a contributor to the document. The limit on number of people on =
the front pages makes it impossible to even put all the authors on the =
front page if we wanted to.=20

So my main point is, just because someone is listed on front page or =
not, should not be used to decide if they are an author or not.=20

The use of "Ed." has been a bit inconsistent at the IETF and I'm not =
aware of good guidelines on how and when to use it. Traditionally when =
we have had a few people producing the drafts and incorporating work =
from the multiple people in on the mailing list, the people where were =
actively editing the document have often been listed on the front page. =
There are many exception to this - I was a bit cheesed to not be listed =
on the front page of RFC 4244.=20

Back to the matter at hand ... This is a pretty classic sort of document =
where an individual draft got selected as a basis for the WG document, =
multiple people in the WG contributed text, a final draft was produced. =
Historically, most IETF docs like this do not put "Ed" after all the =
people on the front page. However, perhaps we should, I don't really =
have any strong opinion one way or the other. I can confirm that this =
document, like many documents coming out of a WG,  includes contribution =
from people beyond the list of names on the front page.=20

Cullen


On Jun 16, 2011, at 2:42 PM, Christian Hoene wrote:

> Hello,
>=20
> In this draft, the editors of draft are not named as editors but as =
authors.
> Thus, I would suggest to follow the example given in
> http://www.rfc-editor.org/rfc/rfc5620.txt and add an ", Ed." behind =
the
> names. A list of authors is given in the acknowledgement section of =
the
> draft.
>=20
> With best regards,
>=20
> Christian Hoene
>=20
>=20
>> -----Original Message-----
>> From: codec-bounces@ietf.org [mailto:codec-bounces@ietf.org] On =
Behalf
>> Of The IESG
>> Sent: Thursday, June 16, 2011 9:24 PM
>> To: IETF-Announce
>> Cc: codec@ietf.org
>> Subject: [codec] Last Call: <draft-ietf-codec-requirements-04.txt> =
(Codec
>> Requirements) to Informational RFC
>>=20
>>=20
>> The IESG has received a request from the Internet Wideband Audio =
Codec
>> WG
>> (codec) to consider the following document:
>> - 'Codec Requirements'
>>  <draft-ietf-codec-requirements-04.txt> as an Informational RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf@ietf.org mailing lists by 2011-06-30. Exceptionally, comments =
may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>   This document provides specific requirements for an Internet audio
>>   codec.  These requirements address quality, sampling rate, =
bit-rate,
>>   and packet loss robustness, as well as other desirable properties.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-codec-requirements/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-codec-requirements/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>> _______________________________________________
>> codec mailing list
>> codec@ietf.org
>> https://www.ietf.org/mailman/listinfo/codec
>=20
> _______________________________________________
> codec mailing list
> codec@ietf.org
> https://www.ietf.org/mailman/listinfo/codec


From bzbarsky@mit.edu  Fri Jun 17 09:53:56 2011
Return-Path: <bzbarsky@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 AD08011E8210 for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 09:53: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.800, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_16=0.6, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1-rrC+Pe4tYz for <ietf@ietfa.amsl.com>; Fri, 17 Jun 2011 09:53:56 -0700 (PDT)
Received: from dmz-mailsec-scanner-3.mit.edu (DMZ-MAILSEC-SCANNER-3.MIT.EDU [18.9.25.14]) by ietfa.amsl.com (Postfix) with ESMTP id 0841C11E820E for <ietf@ietf.org>; Fri, 17 Jun 2011 09:53:54 -0700 (PDT)
X-AuditID: 1209190e-b7c39ae000000a8c-72-4dfb868d998f
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id C3.B1.02700.D868BFD4; Fri, 17 Jun 2011 12:53:33 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id p5HGrrLR026700;  Fri, 17 Jun 2011 12:53:53 -0400
Received: from Boris-Zbarskys-MacBook-Pro-2.local (pool-71-184-125-56.bstnma.fios.verizon.net [71.184.125.56]) (authenticated bits=0) (User authenticated as bzbarsky@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p5HGrpYm027980 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 17 Jun 2011 12:53:53 -0400 (EDT)
Message-ID: <4DFB869F.4050401@mit.edu>
Date: Fri, 17 Jun 2011 12:53:51 -0400
From: Boris Zbarsky <bzbarsky@MIT.EDU>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI	scheme) to Proposed Standard
References: <4D3A64FF.1020000@mit.edu> <4DF87637.2000301@gmail.com> <4DF8D6C6.5080005@mit.edu> <4DF9C5EE.9010703@lachy.id.au> <4DFAD1F6.70203@gmail.com> <4DFAD8CD.2030402@mit.edu> <4DFB39A6.5050105@lachy.id.au>
In-Reply-To: <4DFB39A6.5050105@lachy.id.au>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFIsWRmVeSWpSXmKPExsUixG6nrtvb9tvXoPM/l8WzjfNZLNbN/Mbs wOSxZMlPJo95hzqZA5iiuGxSUnMyy1KL9O0SuDKWH/vCXNAkWTF1yQa2BsZ7Ql2MnBwSAiYS d/49YoWwxSQu3FvP1sXIxSEksI9RYsuFaawQzgZGiTOfDjFBOK+YJA4/n8cO0sIroCbRtKGV EcRmEVCV6D8zGWwUG1D8/ulGJhBbVKBQYsb3mYwQ9YISJ2c+YQGxRQS0JR697QKrYRZQlvgy 5w0biC0skC/Rsh7mjEuMEqt3TARbxgnU8Hv6e2aIBjOJrq1djBC2vMT2t3OYJzAKzkKyYxaS sllIyhYwMq9ilE3JrdLNTczMKU5N1i1OTszLSy3SNdbLzSzRS00p3cQICmJOSb4djF8PKh1i FOBgVOLhXVDw21eINbGsuDL3EKMkB5OSKK96E1CILyk/pTIjsTgjvqg0J7X4EKMEB7OSCO95 M6Acb0piZVVqUT5MSpqDRUmcd6akuq+QQHpiSWp2ampBahFMVoaDQ0mCVw0YrUKCRanpqRVp mTklCGkmDk6Q4TxAwwNAaniLCxJzizPTIfKnGBWlxHldQBICIImM0jy4XliSecUoDvSKMK8K SBUPMEHBdb8CGswENPjfr18gg0sSEVJSDYxCmfH3M+wbL3n5nThzjHOHybTgk+m7r4hm7y/u +cJ/5dHyB40Z2+ft0P3L5RC+rqOr4sfdhxvOmTg9ehHw9anbtd7z5k+vWvyOn7K3/KiHZ/X0 26Ud2xYUh9VWqE7f/fNJxNLqTtd5M07MFIljqT0UM/erteP+OZPWVS+Lk6lkWDP7heMt8XRb JZbijERDLeai4kQA60Iraw0DAAA=
X-Mailman-Approved-At: Mon, 20 Jun 2011 07:34:06 -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: Fri, 17 Jun 2011 16:53:56 -0000

On 6/17/11 7:25 AM, Lachlan Hunt wrote:
> On 2011-06-17 06:32, Boris Zbarsky wrote:
>> On 6/17/11 12:03 AM, Mykyta Yevstifeyev wrote:
>>>>> not
>>>>> clearly compatible with the web security model,
>>> How?
>>
>> "about:blank" in particular is magic with respect to security on the web
>> in various ways (e.g. it can end up same-origin with http:// pages). So
>> I think we do need to specify exactly when this magic security behavior
>> takes place.
>
> The spec is not meant to imply that the special same-origin behaviour
> for about:blank is to be inherited by any other about URI, even if other
> URIs also return a blank document. Perhaps, I need to make that clearer
> in the spec.

Yes, but is it meant to be inherited by "about:blan%6b" ?  That's the 
issue that needs sorting out in terms of normalization, for example.

The current spec draft explicitly says that "about:blan%6b" and 
"about:blank" are equivalent.

I just did some testing on that, since it looks like it won't happen 
otherwise.  You can see the testcase I used at the end of the mail. 
Results are:

Gecko all versions: URI not loaded at all
Chrome 11 stable: document URI is still shown as escaped,
                   security magic is done
Chrome 14 dev: same as Chrome 11 stable
WebKit tip: same as Chrome 11 stable
Safari 5: same as Chrome 11 stable
Opera 11.11: URI not loaded at all (or at least the subframe's load
              event doesn't fire).
IE9: Loads error page in the subframe and alerts an access denied error.
      This is the same in stadards, IE8, IE7, and quirks modes (though
      the textual representation of the error varies).

I didn't bother testing older Opera versions; if someone cares please 
feel free to do so.

Note that some browsers have behavior that differs between iframes and 
the url bar.  For the url bar, I observe the following behaviors for 
"about:blan%6b":

Firefox all versions: alert saying the URI is invalid and cannot be
                       loaded.
Chrome 11: URL bar shows "about:blank", content area shows a blank
            document.
Chrome 14: redirects to chrome://blank which then gives an "invalid
            URI" error page
WebKit tip: URL bar shows "about:blan%6b", content area shows a blank
             document.
Safari 5: As WebKit tip.
Opera 11.11: Redirects to "opera:blank" which gives an "Invalid address"
              error page.
IE9: URL bar shows "about:blan%6b" and an error page is shown.

So it could be argued that Chrome 11, WebKit tip, and Safari 5 do what 
the spec currently calls for.  No other browser does.  And Chrome 14 is 
inconsistent in how it handles this URI depending on the context it's 
encountered in.

-Boris

Testcase:

<!DOCTYPE HTML>
<body>
   <iframe id="iframe"></iframe>
   <script>
     var i;
     onload = function() {
       i = document.getElementById("iframe");
       i.onload = function() {
         try {
           alert(this.contentDocument.documentURI);
           alert(this.contentDocument.documentElement);
         } catch(e) { alert(e); }
       }
       i.src = "about:blan%6b";
     }
   </script>
</body>

From ben@nostrum.com  Fri Jun 17 12:24:36 2011
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 0C7589E8030; Fri, 17 Jun 2011 12:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f3Uimor1-TP8; Fri, 17 Jun 2011 12:24:35 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 144E19E8023; Fri, 17 Jun 2011 12:24:34 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5HJOW66076206 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 17 Jun 2011 14:24:33 -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-v6ops-6to4-to-historic-04
Date: Fri, 17 Jun 2011 14:24:32 -0500
Message-Id: <AE70A313-F36C-4870-A0E8-8F3172F35D53@nostrum.com>
To: draft-ietf-v6ops-6to4-to-historic.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Mon, 20 Jun 2011 07:34:06 -0700
Cc: The 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, 17 Jun 2011 19:24:36 -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-v6ops-6to4-to-historic-04
Reviewer: Ben Campbell
Review Date: 2011-06-17
IETF LC End Date: 2011-06-20
IESG Telechat date: 2011-06-23

Summary:

The draft is essentially ready for publication as an informational RFC. =
I have a few editorial comments that may be worth considering prior to =
final publication.

Major issues: None

Minor issues: None

Nits/editorial comments:

-- general:=20

Idnits reports some potential issues. please check.

-- abstract:

The headers say this draft obsoletes these RFCs. Does moving to =
historical obsolete then in that sense? Perhaps the abstract should say =
something like "obsoletes, and moves to historical"

-- section 1, 2nd paragraph: "...designed to help transitioning the =
Internet..."

Help transition, help in transitioning, or help the transition of

-- section 1, last paragraph:

Please expand 6rd on first mention. Also, Is this meant as an explicit =
recommendation of 6rd as an alternative?

-- section 3, third paragraph: "...same operational burden has manually =
configured tunnels..."

s/has/as

-- section 3, first bullet: "... and in the case the relay is overloaded =
packet loss."

"overloaded, packet loss."

-- section 3, third bullet: "...customer relationship or..."

"... customer relationship between the end-user and the relay operator, =
or..."

-- section 3, 4th bullet: "In case of the reverse path 6to4 relay and =
the anycast forward 6to4 relay, these have to be open for any address. =
Only limited by the scope of the routing advertisement. "

Awkward sentence followed by a sentence fragment. Can these be reworded?

-- section 3, 5th bullet: "black hole"

Please define "black hole" in this context, or use a more descriptive =
(I.e. less jargony) term.


-- section 4, 2nd paragraph: "It is expected that disabling 6to4 in the =
IPv6 Internet will take some time."

Who expects it? The IETF? v6ops? The authors? (or can we just drop "It =
is expected that")

"...deploy native IPv6 service."

s/service/services

-- section 4, numbered list:

It's not clear to me why this is a numbered list rather than an ordinary =
paragraph


From ben@nostrum.com  Fri Jun 17 14:44:32 2011
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 C75C711E80B9; Fri, 17 Jun 2011 14:44:32 -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.100,  BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I9K9QUcW5Y6g; Fri, 17 Jun 2011 14:44:32 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id DABA311E807F; Fri, 17 Jun 2011 14:44:31 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5HLiTHI088638 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 17 Jun 2011 16:44:30 -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-law-rfc4869bis-01
Date: Fri, 17 Jun 2011 16:44:29 -0500
Message-Id: <11976922-3BC1-4094-9F6C-D287DD5D0926@nostrum.com>
To: draft-law-rfc4869bis.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Mon, 20 Jun 2011 07:34:06 -0700
Cc: The 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, 17 Jun 2011 21:44:32 -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-law-rfc4869bis-01
Reviewer: Ben Campbell=09
Review Date: 2011-06-17
IETF LC End Date: 2011-06-13

Summary: This draft is ready for publication as an informational RFC.


Major issues: None

Minor issues: None

Nits/editorial comments:

-- section 4, 2nd paragraph:

Is this paragraph intended to recommend any specific action for =
implementors?=

From ben@nostrum.com  Fri Jun 17 15:10:59 2011
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 1B63411E8122; Fri, 17 Jun 2011 15:10:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level: 
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OnYW0CVAmnUD; Fri, 17 Jun 2011 15:10:58 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 23F2211E807F; Fri, 17 Jun 2011 15:10:56 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5HMAsQx091038 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 17 Jun 2011 17:10:55 -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-dime-ikev2-psk-diameter-08
Date: Fri, 17 Jun 2011 17:10:54 -0500
Message-Id: <EEBDA95D-FC72-4498-A9D1-D7F4E7596314@nostrum.com>
To: draft-ietf-dime-ikev2-psk-diameter.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Mon, 20 Jun 2011 07:34:06 -0700
Cc: The 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, 17 Jun 2011 22:10:59 -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-dime-ikev2-psk-diameter-08
Reviewer: Ben Campbell
Review Date: 2011-06-17
IESG Telechat date: 2011-06-23

Summary: This draft is almost ready for publication as a proposed =
standard. I still have a concern about the generation of the PSK.

Major issues:

In my initial Gen-ART review, I made the following comment: The draft =
says that the procedure that the HAAA follows to generate the PSK is out =
of scope. But doesn't the IKE2 initiator need to understand the =
procedure? If the procedure is not defined somewhere, how you achieve =
any degree of interoperability?

The author responded that the PSK generation was in fact important for =
interoperability, but that the specific procedures have been =
intentionally left to other specifications. It is up to specifications =
that use this Diameter application to define the PSK generation =
mechanism. Further, the author indicated 2 3GPP2 specs that have done =
this.

I am still concerned that this means that this specification cannot be =
implemented in an interoperable way without effectively profiling it. =
There is no apparent coordination on how such profiling may be done, and =
by whom. I think this is likely to result in implementation islands that =
can't talk to each other. I recognize that there is precedent for doing =
this, but I think it is something that should not be done without =
careful consideration, particularly in a standards track RFC. I leave it =
to the IESG to confirm whether it is appropriate in this circumstance.

I further note that there is  no apparent way to negotiate or declare =
what PSK generation mechanism might be used, if an implementation =
supports more than one.

Minor Issues: None
Editorial Comments: None



From henk@uijterwaal.nl  Sun Jun 19 18:55:53 2011
Return-Path: <henk@uijterwaal.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 CB63711E8081 for <ietf@ietfa.amsl.com>; Sun, 19 Jun 2011 18:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.115
X-Spam-Level: 
X-Spam-Status: No, score=0.115 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qkyha0T-JAJP for <ietf@ietfa.amsl.com>; Sun, 19 Jun 2011 18:55:53 -0700 (PDT)
Received: from smtp-vbr14.xs4all.nl (smtp-vbr14.xs4all.nl [194.109.24.34]) by ietfa.amsl.com (Postfix) with ESMTP id F12E011E80DF for <ietf@ietf.org>; Sun, 19 Jun 2011 18:55:52 -0700 (PDT)
Received: from geir.local ([61.8.214.4]) (authenticated bits=0) by smtp-vbr14.xs4all.nl (8.13.8/8.13.8) with ESMTP id p5K1tIFY020261 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 20 Jun 2011 03:55:20 +0200 (CEST) (envelope-from henk@uijterwaal.nl)
Message-ID: <4DFEA880.6080403@uijterwaal.nl>
Date: Mon, 20 Jun 2011 03:55:12 +0200
From: Henk Uijterwaal <henk@uijterwaal.nl>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net>
In-Reply-To: <4DFD90C1.7010903@net-zen.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by XS4ALL Virus Scanner
X-Mailman-Approved-At: Mon, 20 Jun 2011 07:34:06 -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, 20 Jun 2011 01:55:53 -0000

On 19/06/2011 08:01, Glen Zorn wrote:
> On 6/18/2011 9:52 PM, Keith Moore wrote:
> 
>> Frankly, I'm appalled at the prices and think it's highly inappropriate for
>> IETF to be meeting in venues where the "conference hotels" are so
>> expensive.

May I point out that there has been a survey on the topic and the community
expressed a clear preference for Quebec over other Canadian cities, knowing
that travel would be longer and the number of cheap alternative hotels
smaller.

Henk

-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
                                          http://www.uijterwaal.nl
                                          Phone: +31.6.55861746
------------------------------------------------------------------------------

There appears to have been a collective retreat from reality that day.
                                 (John Glanfield, on an engineering project)

From jdrake@juniper.net  Mon Jun 20 08:51:14 2011
Return-Path: <jdrake@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3836621F84DC for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 08:51:14 -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, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6vH-heyJo70U for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 08:51:09 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB7F21F84E5 for <ietf@ietf.org>; Mon, 20 Jun 2011 08:51:08 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKTf9sZVnKZkKKOYcA/EoYV4Gjla6GjPoo@postini.com; Mon, 20 Jun 2011 08:51:08 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Mon, 20 Jun 2011 08:49:03 -0700
From: John E Drake <jdrake@juniper.net>
To: Henk Uijterwaal <henk@uijterwaal.nl>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 20 Jun 2011 08:49:01 -0700
Subject: RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Topic: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Index: AcwvV/MJEntXok6rQIqO+z58Yolj+gACNKaA
Message-ID: <5E893DB832F57341992548CDBB333163A0A7AE283A@EMBX01-HQ.jnpr.net>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>
In-Reply-To: <4DFEA880.6080403@uijterwaal.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 15:51:14 -0000

But that was then and now is now 8->.  One could simply say "suck it up".

Sent from my iPhone


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Henk Uijterwaal
> Sent: Sunday, June 19, 2011 6:55 PM
> To: ietf@ietf.org
> Subject: Re: Has anyone found a hotel for Quebec City that isn't
> exorbitant?
>=20
> On 19/06/2011 08:01, Glen Zorn wrote:
> > On 6/18/2011 9:52 PM, Keith Moore wrote:
> >
> >> Frankly, I'm appalled at the prices and think it's highly
> inappropriate for
> >> IETF to be meeting in venues where the "conference hotels" are so
> >> expensive.
>=20
> May I point out that there has been a survey on the topic and the
> community
> expressed a clear preference for Quebec over other Canadian cities,
> knowing
> that travel would be longer and the number of cheap alternative hotels
> smaller.
>=20
> Henk
>=20
> --
> -----------------------------------------------------------------------
> -------
> Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
>                                           http://www.uijterwaal.nl
>                                           Phone: +31.6.55861746
> -----------------------------------------------------------------------
> -------
>=20
> There appears to have been a collective retreat from reality that day.
>                                  (John Glanfield, on an engineering
> project)
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From cabo@tzi.org  Mon Jun 20 09:02:20 2011
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 06E4F1F0C37; Mon, 20 Jun 2011 09:02:20 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cKgJK1pzRoFE; Mon, 20 Jun 2011 09:02: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 7CB321F0C36; Mon, 20 Jun 2011 09:02: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.3/8.14.3) with ESMTP id p5KG25GI025780; Mon, 20 Jun 2011 18:02:05 +0200 (CEST)
Received: from [192.168.217.112] (p5489BE09.dip.t-dialin.net [84.137.190.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 739D21EF; Mon, 20 Jun 2011 18:02:05 +0200 (CEST)
Subject: Re: [codec] Last Call: <draft-ietf-codec-requirements-04.txt>	(Codec	Requirements) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <2C1BBE56-DC0A-47A0-9F2C-A622AAB77EAA@cisco.com>
Date: Mon, 20 Jun 2011 18:02:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8FB8964F-1752-4D34-8C90-932DE7BE1484@tzi.org>
References: <003e01cc2c65$ea831540$bf893fc0$@uni-tuebingen.de> <2C1BBE56-DC0A-47A0-9F2C-A622AAB77EAA@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: Christian Hoene <hoene@uni-tuebingen.de>, codec@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, 20 Jun 2011 16:02:20 -0000

On Jun 20, 2011, at 15:31, Cullen Jennings wrote:

> This is all a sort of confusing point of many IETF documents and not =
unique to this one. I think the important points is that for many IETF =
documents, the people listed on the front page are not the authors. =
Typically the list of authors is a much longer list. And to clarify what =
I mean by Author, I mean it in the sense that it would used in copyright =
law. I do think the Acknowledgements section needs to identity anyone =
who is a contributor to the document. The limit on number of people on =
the front pages makes it impossible to even put all the authors on the =
front page if we wanted to.=20

Ceterum censeo: A situation that is untenable.

(And that may actually be problematic in countries with droit =
d'auteur/Urheberrecht such as Germany, but that's not my point.)

Gruesse, Carsten


From moore@network-heretics.com  Mon Jun 20 09:42:27 2011
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 39B9E11E8087 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 09:42:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.398
X-Spam-Level: 
X-Spam-Status: No, score=-3.398 tagged_above=-999 required=5 tests=[AWL=0.201,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 76jEWZjAUijH for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 09:42:26 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 6306511E80A6 for <ietf@ietf.org>; Mon, 20 Jun 2011 09:42:26 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id AF6DB20529; Mon, 20 Jun 2011 12:42:25 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 20 Jun 2011 12:42:25 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=EveXde9Qaa/GSu5BvGQX7SHiUWE=; b=N9plh0rmxG+YFa6EEdTIXbpLTAC8T+48TXSsfBTlUl9CvNHtXbDddJ9s9dIgO0KhwzMv09VsZrD7UfNARUFFIsYdR65/axfC4Jnnqtky2VTimuzB0uD2mMs/4fUbgvHP8E47iP7d4TAjJCLp4h9xx7HS25cVuoAg2vbwEQNZqDI=
X-Sasl-enc: rnViwZy6jcSVENxlm5lghpKeZuujnhjX7/YIQHE3s0JR 1308588145
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 065FC40A6EE; Mon, 20 Jun 2011 12:42:24 -0400 (EDT)
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4DFEA880.6080403@uijterwaal.nl>
Date: Mon, 20 Jun 2011 12:42:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>
To: Henk Uijterwaal <henk@uijterwaal.nl>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 16:42:27 -0000

On Jun 19, 2011, at 9:55 PM, Henk Uijterwaal wrote:

> On 19/06/2011 08:01, Glen Zorn wrote:
>> On 6/18/2011 9:52 PM, Keith Moore wrote:
>>=20
>>> Frankly, I'm appalled at the prices and think it's highly =
inappropriate for
>>> IETF to be meeting in venues where the "conference hotels" are so
>>> expensive.
>=20
> May I point out that there has been a survey on the topic and the =
community
> expressed a clear preference for Quebec over other Canadian cities, =
knowing
> that travel would be longer and the number of cheap alternative hotels
> smaller.

Is it necessary to remind "the community" that consensus of the =
community is meaningless if the community isn't inclusive?

Keith


From ole@cisco.com  Mon Jun 20 09:54:39 2011
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 DD6B911E8087 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 09:54:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K44Jet6XjEiJ for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 09:54:38 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfa.amsl.com (Postfix) with ESMTP id 234061F0C59 for <ietf@ietf.org>; Mon, 20 Jun 2011 09:54:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1739; q=dns/txt; s=iport; t=1308588878; x=1309798478; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=vG11z0KYBqxs6QYxm6Nqejmop04ABJcntqGVbSesnaE=; b=ECm10OA2jdFN3tr6JuALaurni91joWRkM4H5twXEfser3iBdWuxD+Vwe GfJYxOZzuTjgGYAVqzcUK7DVcinOOPaUtQ7/B71t5ASqggtWDgxWgSnRQ hYP2nbn/y6ejOFmW/zrl6pFX160F+re2Xu5B+mQquShuMiQYCPXucXEIU I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFABx6/02rRDoJ/2dsb2JhbABNBpkFjVt3iHOhSYMPDwGaXYM3gnMEhyCPHotB
X-IronPort-AV: E=Sophos;i="4.65,395,1304294400"; d="scan'208";a="381011257"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-2.cisco.com with ESMTP; 20 Jun 2011 16:54:36 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p5KGsZW0013683; Mon, 20 Jun 2011 16:54:35 GMT
Date: Mon, 20 Jun 2011 09:54:35 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
In-Reply-To: <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com>
Message-ID: <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, 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: Mon, 20 Jun 2011 16:54:39 -0000

Keith,

Here is the tradeoff:

"The community" has expressed a strong preference for one-roof venues 
[which often translates to convention center + hotel next door in our
case] in a city setting (City West and Maastricht being non-examples).

This leads to (generally speaking):

* Somewhat expensive main hotel rates (although I agree that hotel 
  rates seem to be as variable and unpredictable as airline rates, and 
  I would hope we could do better even if we sign the contract several 
  years in advance.)

* More choices in the city nearby ranging from apartment rentals, 
  smaller hotels etc, etc.

The second item is intended to address your "inclusive" point. As has 
been pointed out, QC offers a good range of hotels at various price 
points.

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 Mon, 20 Jun 2011, Keith Moore wrote:

> On Jun 19, 2011, at 9:55 PM, Henk Uijterwaal wrote:
> 
> >> On 6/18/2011 9:52 PM, Keith Moore wrote:
> >> 
> >>> Frankly, I'm appalled at the prices and think it's highly inappropriate for
> >>> IETF to be meeting in venues where the "conference hotels" are so
> >>> expensive.
> > 
> > May I point out that there has been a survey on the topic and the community
> > expressed a clear preference for Quebec over other Canadian cities, knowing
> > that travel would be longer and the number of cheap alternative hotels
> > smaller.
> 
> Is it necessary to remind "the community" that consensus of the 
> community is meaningless if the community isn't inclusive?
> 
> Keith
> 

From tnadeau@lucidvision.com  Mon Jun 20 10:26:22 2011
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 AB69421F84FD for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 10:26: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jDfZgmKBfQ85 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 10:26:21 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id AAFAE21F84FA for <ietf@ietf.org>; Mon, 20 Jun 2011 10:26:21 -0700 (PDT)
Received: from [192.168.1.133] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 4F14E1BF2E6B; Mon, 20 Jun 2011 13:26:20 -0400 (EDT)
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <5E893DB832F57341992548CDBB333163A0A7AE283A@EMBX01-HQ.jnpr.net>
Date: Mon, 20 Jun 2011 13:26:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C3647B4-64CE-4D98-A539-04D884ECE94B@lucidvision.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <5E893DB832F57341992548CDBB333163A0A7AE283A@EMBX01-HQ.jnpr.net>
To: John E Drake <jdrake@juniper.net>
X-Mailer: Apple Mail (2.1084)
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, "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, 20 Jun 2011 17:26:22 -0000

	BTW, I found that like with many previous IETF meetings, if you =
call your local travel department, they can often get far cheaper rates =
for the rooms at the hotel. For some reason, the IETF "negotiates" rates =
that seem to be MSRP.  For this one, for example, I got something like a =
%40 discount on the IETF rate.

	--Tom


> But that was then and now is now 8->.  One could simply say "suck it =
up".
>=20
> Sent from my iPhone
>=20
>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
>> Henk Uijterwaal
>> Sent: Sunday, June 19, 2011 6:55 PM
>> To: ietf@ietf.org
>> Subject: Re: Has anyone found a hotel for Quebec City that isn't
>> exorbitant?
>>=20
>> On 19/06/2011 08:01, Glen Zorn wrote:
>>> On 6/18/2011 9:52 PM, Keith Moore wrote:
>>>=20
>>>> Frankly, I'm appalled at the prices and think it's highly
>> inappropriate for
>>>> IETF to be meeting in venues where the "conference hotels" are so
>>>> expensive.
>>=20
>> May I point out that there has been a survey on the topic and the
>> community
>> expressed a clear preference for Quebec over other Canadian cities,
>> knowing
>> that travel would be longer and the number of cheap alternative =
hotels
>> smaller.
>>=20
>> Henk
>>=20
>> --
>> =
-----------------------------------------------------------------------
>> -------
>> Henk Uijterwaal                           Email: =
henk(at)uijterwaal.nl
>>                                          http://www.uijterwaal.nl
>>                                          Phone: +31.6.55861746
>> =
-----------------------------------------------------------------------
>> -------
>>=20
>> There appears to have been a collective retreat from reality that =
day.
>>                                 (John Glanfield, on an engineering
>> project)
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From mcr@sandelman.ca  Mon Jun 20 10:33:01 2011
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 A01B111E818D for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 10:33:01 -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=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZgvUkrQPJUKE for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 10:33:00 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 99C0911E8178 for <ietf@ietf.org>; Mon, 20 Jun 2011 10:33:00 -0700 (PDT)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 04CA7341F8 for <ietf@ietf.org>; Mon, 20 Jun 2011 13:33:00 -0400 (EDT)
Received: from marajade.sandelman.ca (marajade.sandelman.ca [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id C7EA09841F for <ietf@ietf.org>; Mon, 20 Jun 2011 13:32:57 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: ietf@ietf.org
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
In-Reply-To: <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Mon, 20 Jun 2011 13:32:57 -0400
Message-ID: <12629.1308591177@marajade.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: Mon, 20 Jun 2011 17:33:01 -0000

>>>>> "Ole" == Ole Jacobsen <ole@cisco.com> writes:
    Ole> Here is the tradeoff:

    Ole> "The community" has expressed a strong preference for one-roof
    Ole> venues [which often translates to convention center + hotel
    Ole> next door in our case] in a city setting (City West and
    Ole> Maastricht being non-examples).

    Ole> This leads to (generally speaking):

    Ole> * Somewhat expensive main hotel rates (although I agree that
    Ole> hotel rates seem to be as variable and unpredictable as airline
    Ole> rates, and I would hope we could do better even if we sign the
    Ole> contract several years in advance.)

okay, but why Quebec City in the summer?
It's a peak season destination.  We seem to do this a lot.  
March would be no better, but early November there would be, I think, low peak.
What's a non-peak destination for July?  Maybe I'm wrong about Quebec.

    Ole> * More choices in the city nearby ranging from apartment
    Ole> rentals, smaller hotels etc, etc.

    Ole> The second item is intended to address your "inclusive"
    Ole> point. As has been pointed out, QC offers a good range of
    Ole> hotels at various price points.

I'm staying at Laval University resident for $61/night.  Hotwire did
find a few places equal in distance for ~$108, but the trip was harder
in my opinion.  I might bring my folding bike, or not (I'm coming by
train).  There are apparently dozens of buses that travel the 6km
stretch of Rene Levesque, but I'm doubtful that many will run after 8pm,
so I'm counting on a few taxi rides.

I think we will be relatively happy in Quebec.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From simon.perreault@viagenie.ca  Mon Jun 20 10:41:49 2011
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9230E11E81A8 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 10:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id chkqK3dyc5B3 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 10:41:48 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 93E2C11E81A5 for <ietf@ietf.org>; Mon, 20 Jun 2011 10:41:48 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:21d:60ff:fed7:e732]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 7EB7420D1F for <ietf@ietf.org>; Mon, 20 Jun 2011 13:41:47 -0400 (EDT)
Message-ID: <4DFF865B.4030606@viagenie.ca>
Date: Mon, 20 Jun 2011 13:41:47 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110320 Fedora/3.1.9-4.fc16 Lightning/1.0b3pre Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com>	<alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <12629.1308591177@marajade.sandelman.ca>
In-Reply-To: <12629.1308591177@marajade.sandelman.ca>
X-Enigmail-Version: 1.1.2
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, 20 Jun 2011 17:41:49 -0000

On 2011-06-20 13:32, Michael Richardson wrote:
> I'm staying at Laval University resident for $61/night.  Hotwire did
> find a few places equal in distance for ~$108, but the trip was harder
> in my opinion.  I might bring my folding bike, or not (I'm coming by
> train).  There are apparently dozens of buses that travel the 6km
> stretch of Rene Levesque, but I'm doubtful that many will run after 8pm,
> so I'm counting on a few taxi rides.

Bus to/from Laval University is very frequent and quick. You'll be fine
until around midnight.

This summer a new "bike boulevard" will also be introduced to make it
super easy to bike from the university to the parliament (across the
street from the IETF venue). So that would be another good solution. Let
me know if you want more information.

> I think we will be relatively happy in Quebec.

:)

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From rbarnes@bbn.com  Mon Jun 20 10:52:09 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4731211E8183 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 10:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.413
X-Spam-Level: 
X-Spam-Status: No, score=-106.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CLBejEBgcbD6 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 10:52:08 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 4189311E809B for <ietf@ietf.org>; Mon, 20 Jun 2011 10:52:02 -0700 (PDT)
Received: from [128.89.253.103] (port=59621 helo=[172.27.17.202]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1QYidl-000BKy-Oe for ietf@ietf.org; Mon, 20 Jun 2011 13:52:01 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: IETF-meta (Was: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?)
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <12629.1308591177@marajade.sandelman.ca>
Date: Mon, 20 Jun 2011 13:52:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4BA8FE42-F95D-4268-B53C-0BD8F4FE90F5@bbn.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <12629.1308591177@marajade.sandelman.ca>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 17:52:09 -0000

Just a reminder, originally posted September 2010:

NEW NON-IETF LIST ANNOUNCEMENT

IETF Meta-Discussions=20

This group is dedicated to the discussion of ancillary issues of =
interest to the IETF community, especially discussions about how IETF =
discussions and meetings should work.=20
-- IETF meeting locations / travel=20
-- Email composition design patterns=20
-- Anything related to DiffServ politics

<http://groups.google.com/group/ietf-meta>



On Jun 20, 2011, at 1:32 PM, Michael Richardson wrote:

>=20
>>>>>> "Ole" =3D=3D Ole Jacobsen <ole@cisco.com> writes:
>    Ole> Here is the tradeoff:
>=20
>    Ole> "The community" has expressed a strong preference for one-roof
>    Ole> venues [which often translates to convention center + hotel
>    Ole> next door in our case] in a city setting (City West and
>    Ole> Maastricht being non-examples).
>=20
>    Ole> This leads to (generally speaking):
>=20
>    Ole> * Somewhat expensive main hotel rates (although I agree that
>    Ole> hotel rates seem to be as variable and unpredictable as =
airline
>    Ole> rates, and I would hope we could do better even if we sign the
>    Ole> contract several years in advance.)
>=20
> okay, but why Quebec City in the summer?
> It's a peak season destination.  We seem to do this a lot. =20
> March would be no better, but early November there would be, I think, =
low peak.
> What's a non-peak destination for July?  Maybe I'm wrong about Quebec.
>=20
>    Ole> * More choices in the city nearby ranging from apartment
>    Ole> rentals, smaller hotels etc, etc.
>=20
>    Ole> The second item is intended to address your "inclusive"
>    Ole> point. As has been pointed out, QC offers a good range of
>    Ole> hotels at various price points.
>=20
> I'm staying at Laval University resident for $61/night.  Hotwire did
> find a few places equal in distance for ~$108, but the trip was harder
> in my opinion.  I might bring my folding bike, or not (I'm coming by
> train).  There are apparently dozens of buses that travel the 6km
> stretch of Rene Levesque, but I'm doubtful that many will run after =
8pm,
> so I'm counting on a few taxi rides.
>=20
> I think we will be relatively happy in Quebec.
>=20
> --=20
> ]       He who is tired of Weird Al is tired of life!           |  =
firewalls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net =
architect[
> ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ =
|device driver[
>   Kyoto Plus: watch the video =
<http://www.youtube.com/watch?v=3Dkzx1ycLXQSE>
> 	               then sign the petition.=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From john-ietf@jck.com  Mon Jun 20 11:55:47 2011
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 159F611E81B4 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 11:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xEfMEpx3Edd3 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 11:55:46 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 6B05311E815C for <ietf@ietf.org>; Mon, 20 Jun 2011 11:55:46 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QYjdM-000DTg-1t; Mon, 20 Jun 2011 14:55:40 -0400
Date: Mon, 20 Jun 2011 14:55:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael Richardson <mcr@sandelman.ca>, ietf@ietf.org
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
Message-ID: <B7D833155E943151B52610C6@PST.JCK.COM>
In-Reply-To: <12629.1308591177@marajade.sandelman.ca>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <12629.1308591177@marajade.sandelman.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 18:55:47 -0000

--On Monday, June 20, 2011 13:32 -0400 Michael Richardson
<mcr@sandelman.ca> wrote:

>...
> It's a peak season destination.  We seem to do this a lot.  
> March would be no better, but early November there would be, I
> think, low peak. 
> What's a non-peak destination for July?

Phoenix.  Probably Houston or Fort Worth.  Wellington or
somewhere on the South Island that doesn't attract skiers.
Amundsen-Scott base: although I doubt that they have adequate
conference facilities, yesterday's mean temperature was circa
-89F and "daytime" is still several months off.  Other silly
suggestions on request (although I don't personally consider
some of the first few silly).

   john




From mary.ietf.barnes@gmail.com  Mon Jun 20 12:02:56 2011
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8913611E81E2 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 12:02:56 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aOU3LQy+sTbv for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 12:02:55 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id C837A11E81D8 for <ietf@ietf.org>; Mon, 20 Jun 2011 12:02:24 -0700 (PDT)
Received: by vxi40 with SMTP id 40so1126599vxi.31 for <ietf@ietf.org>; Mon, 20 Jun 2011 12:02:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=iN6tNwyxqPO+Us1kjbqj4mAbZWQh+EdE8k8ZYzL5kz0=; b=TaCYNg77zZiEDb29KGgOcR+6Uu8BwVkvknWs0G3Wz5ZsZuh43wXCq/yNhVtLAfJp5U kMWiywZJVu6+8bgN0vz1HS1xUIT5n4wGT3UYX3DXLj9rTqDyx+B2FzDWyUAWtRA3ae+8 EDcIGvfpkWmCGD6T/G/pvvEts2jy2n+h/Wurw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=T8P4RWnqJOAhv4KUZhg2Tbp0+y/9/FiOuXmMzL/oLrKRRdDocnEADCmXn0+4FHlphv ylewSB2rRujsjHo7IvPVxpGszqCY8yyMsxK4BgY8dcaZSo7nxY/aPliBJVPNdsXB668O h71kTjhIeSWFqoUf1GLXlkGnrFQ9CE01pCRW0=
MIME-Version: 1.0
Received: by 10.52.98.33 with SMTP id ef1mr7778977vdb.23.1308596544113; Mon, 20 Jun 2011 12:02:24 -0700 (PDT)
Received: by 10.52.158.39 with HTTP; Mon, 20 Jun 2011 12:02:24 -0700 (PDT)
In-Reply-To: <B7D833155E943151B52610C6@PST.JCK.COM>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <12629.1308591177@marajade.sandelman.ca> <B7D833155E943151B52610C6@PST.JCK.COM>
Date: Mon, 20 Jun 2011 14:02:24 -0500
Message-ID: <BANLkTinPKSx08NaLdshuw8=NRZRMjNsMag@mail.gmail.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=20cf307f354a2a8acd04a62960b5
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 19:02:56 -0000

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

Exactly.   Given that we spend most of our days in air conditioned meeting
rooms, Phoenix or Dallas are not bad choices. Dallas is slightly better due
to air connections.  Houston is not a good choice under any circumstance
IMHO - I don't think A/C can remove enough humidity to make it comfortable
in July.

Personally, I have no issue with Minneapolis in November or March - again we
spend most of the time in meeting rooms, so do we really care that much
about the weather outside?

Mary.

On Mon, Jun 20, 2011 at 1:55 PM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Monday, June 20, 2011 13:32 -0400 Michael Richardson
> <mcr@sandelman.ca> wrote:
>
> >...
> > It's a peak season destination.  We seem to do this a lot.
> > March would be no better, but early November there would be, I
> > think, low peak.
> > What's a non-peak destination for July?
>
> Phoenix.  Probably Houston or Fort Worth.  Wellington or
> somewhere on the South Island that doesn't attract skiers.
> Amundsen-Scott base: although I doubt that they have adequate
> conference facilities, yesterday's mean temperature was circa
> -89F and "daytime" is still several months off.  Other silly
> suggestions on request (although I don't personally consider
> some of the first few silly).
>
>   john
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

Exactly. =A0 Given that we spend most of our days in air conditioned meetin=
g rooms, Phoenix or Dallas are not bad choices. Dallas is slightly better d=
ue to air connections. =A0Houston is not a good choice under any circumstan=
ce IMHO - I don&#39;t think A/C can remove enough humidity to make it comfo=
rtable in July. =A0<div>
<br></div><div>Personally, I have no issue with Minneapolis in November or =
March - again we spend most of the time in meeting rooms, so do we really c=
are that much about the weather outside?<br><div><div><br></div><div><div>
Mary.=A0<br><div><br></div><div><div class=3D"gmail_quote">On Mon, Jun 20, =
2011 at 1:55 PM, John C Klensin <span dir=3D"ltr">&lt;<a href=3D"mailto:joh=
n-ietf@jck.com">john-ietf@jck.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex;">
<br>
<br>
--On Monday, June 20, 2011 13:32 -0400 Michael Richardson<br>
&lt;<a href=3D"mailto:mcr@sandelman.ca">mcr@sandelman.ca</a>&gt; wrote:<br>
<br>
&gt;...<br>
&gt; It&#39;s a peak season destination. =A0We seem to do this a lot.<br>
&gt; March would be no better, but early November there would be, I<br>
&gt; think, low peak.<br>
&gt; What&#39;s a non-peak destination for July?<br>
<br>
Phoenix. =A0Probably Houston or Fort Worth. =A0Wellington or<br>
somewhere on the South Island that doesn&#39;t attract skiers.<br>
Amundsen-Scott base: although I doubt that they have adequate<br>
conference facilities, yesterday&#39;s mean temperature was circa<br>
-89F and &quot;daytime&quot; is still several months off. =A0Other silly<br=
>
suggestions on request (although I don&#39;t personally consider<br>
some of the first few silly).<br>
<br>
 =A0 john<br>
<br>
<br>
<br>
_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
</blockquote></div><br></div></div></div></div></div>

--20cf307f354a2a8acd04a62960b5--

From nurit.sprecher@nsn.com  Mon Jun 20 13:14:51 2011
Return-Path: <nurit.sprecher@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1DA31F0C39 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 13:14:51 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4zPiqXKo0haN for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 13:14:51 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 875871F0C38 for <ietf@ietf.org>; Mon, 20 Jun 2011 13:14:50 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p5KKEmV3004685 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 20 Jun 2011 22:14:48 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p5KKEh7P014164; Mon, 20 Jun 2011 22:14:47 +0200
Received: from DEMUEXC014.nsn-intra.net ([10.150.128.25]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 20 Jun 2011 22:14:43 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
Date: Mon, 20 Jun 2011 22:14:41 +0200
Message-ID: <077E41CFFD002C4CAB7DFA4386A532640400223A@DEMUEXC014.nsn-intra.net>
In-Reply-To: <2C3647B4-64CE-4D98-A539-04D884ECE94B@lucidvision.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Index: Acwvb0v1PnpscOLnT06wj1sEsjo86AAF1yKA
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com><4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl><5E893DB832F57341992548CDBB333163A0A7AE283A@EMBX01-HQ.jnpr.net> <2C3647B4-64CE-4D98-A539-04D884ECE94B@lucidvision.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Thomas Nadeau" <tnadeau@lucidvision.com>, "John E Drake" <jdrake@juniper.net>
X-OriginalArrivalTime: 20 Jun 2011 20:14:43.0050 (UTC) FILETIME=[B11D1CA0:01CC2F86]
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 20:14:51 -0000

Same in my case!

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Thomas Nadeau
Sent: Monday, June 20, 2011 8:26 PM
To: John E Drake
Cc: Henk Uijterwaal; ietf@ietf.org
Subject: Re: Has anyone found a hotel for Quebec City that isn't
exorbitant?


	BTW, I found that like with many previous IETF meetings, if you
call your local travel department, they can often get far cheaper rates
for the rooms at the hotel. For some reason, the IETF "negotiates" rates
that seem to be MSRP.  For this one, for example, I got something like a
%40 discount on the IETF rate.

	--Tom


> But that was then and now is now 8->.  One could simply say "suck it
up".
>=20
> Sent from my iPhone
>=20
>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of
>> Henk Uijterwaal
>> Sent: Sunday, June 19, 2011 6:55 PM
>> To: ietf@ietf.org
>> Subject: Re: Has anyone found a hotel for Quebec City that isn't
>> exorbitant?
>>=20
>> On 19/06/2011 08:01, Glen Zorn wrote:
>>> On 6/18/2011 9:52 PM, Keith Moore wrote:
>>>=20
>>>> Frankly, I'm appalled at the prices and think it's highly
>> inappropriate for
>>>> IETF to be meeting in venues where the "conference hotels" are so
>>>> expensive.
>>=20
>> May I point out that there has been a survey on the topic and the
>> community
>> expressed a clear preference for Quebec over other Canadian cities,
>> knowing
>> that travel would be longer and the number of cheap alternative
hotels
>> smaller.
>>=20
>> Henk
>>=20
>> --
>>
-----------------------------------------------------------------------
>> -------
>> Henk Uijterwaal                           Email:
henk(at)uijterwaal.nl
>>                                          http://www.uijterwaal.nl
>>                                          Phone: +31.6.55861746
>>
-----------------------------------------------------------------------
>> -------
>>=20
>> There appears to have been a collective retreat from reality that
day.
>>                                 (John Glanfield, on an engineering
>> project)
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From ajs@anvilwalrusden.com  Mon Jun 20 14:47:28 2011
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 1C20711E81A2 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 14:47:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZVuP0qGxocZo for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 14:47:27 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 7E13C11E80AD for <ietf@ietf.org>; Mon, 20 Jun 2011 14:47:27 -0700 (PDT)
Received: from shinkuro.com (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 35B1F1ECB41D for <ietf@ietf.org>; Mon, 20 Jun 2011 21:47:25 +0000 (UTC)
Date: Mon, 20 Jun 2011 17:47:20 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: location preferences (was: Has anyone found a hotel for Quebec City that isn't exorbitant?)
Message-ID: <20110620214720.GH79936@shinkuro.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <12629.1308591177@marajade.sandelman.ca> <B7D833155E943151B52610C6@PST.JCK.COM> <BANLkTinPKSx08NaLdshuw8=NRZRMjNsMag@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BANLkTinPKSx08NaLdshuw8=NRZRMjNsMag@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 21:47:28 -0000

On Mon, Jun 20, 2011 at 02:02:24PM -0500, Mary Barnes wrote:
> rooms, Phoenix or Dallas are not bad choices. Dallas is slightly better due
> to air connections.  Houston is not a good choice under any circumstance

Speaking only for myself, I will note that the worst IETF experience I
ever had was in Dallas: the location was remote and poor, we were
flooded out of the hotel, alternatives nearby were few, and you needed
a car to go anywhere.  Also, the crime statistics for the city made me
uneasy.  

All this goes, I think, to show that one cannot satisfy everyone at once.

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From dhc2@dcrocker.net  Mon Jun 20 14:56:42 2011
Return-Path: <dhc2@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 3262C9E800F for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 14:56:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Uxn7B4Eq6rH for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 14:56:41 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7D1969E800D for <ietf@ietf.org>; Mon, 20 Jun 2011 14:56:41 -0700 (PDT)
Received: from [192.168.1.7] (ppp-68-120-198-5.dsl.pltn13.pacbell.net [68.120.198.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p5KLuY1k029945 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 20 Jun 2011 14:56:39 -0700
Message-ID: <4DFFC210.7090209@dcrocker.net>
Date: Mon, 20 Jun 2011 14:56:32 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: location preferences
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com>	<alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net>	<12629.1308591177@marajade.sandelman.ca>	<B7D833155E943151B52610C6@PST.JCK.COM>	<BANLkTinPKSx08NaLdshuw8=NRZRMjNsMag@mail.gmail.com> <20110620214720.GH79936@shinkuro.com>
In-Reply-To: <20110620214720.GH79936@shinkuro.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 20 Jun 2011 14:56:39 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 21:56:42 -0000

On 6/20/2011 2:47 PM, Andrew Sullivan wrote:
> Speaking only for myself, I will note that the worst IETF experience I
> ever had was in Dallas: the location was remote and poor, we were
> flooded out of the hotel, alternatives nearby were few, and you needed
> a car to go anywhere.

It was, indeed, a horrible venue, along any number of parameters.  Fortunately, 
Dallas has a few other choices that are likely to work better, along every 
parameter we care about.


 > Also, the crime statistics for the city made me
> uneasy.

The crime statistics for most American cities and most major European cities 
make me uneasy.  In 1983 I moved to Toronto from Washington DC and was amused by 
the different perspectives about crime.  I was told there were a couple of 
blocks in downtown Toronto that weren't very safe for women alone at night.  By 
contract, perhaps 1/3-1/2 of DC was unsafe for almost anyone at night and maybe 
1/4 for most folk during the day...

I've been ripped off twice in Paris including a double-team pocket-picking. 
Purses and backpacks of IETF have been stolen -- including from the middle of 
meeting rooms(!) -- in Munich, Stockholm and I believe some other places.

In any event, if crime statistics are to become a factor in choosing IETF 
venues, the IETF community needs to develop some consensus about this, including 
what the acceptable parameters are.  As of now, I believe that's not generally 
part of the discussion in choosing a venue.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From msk@cloudmark.com  Mon Jun 20 15:47:14 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A91C11E80B5 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 15:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.611
X-Spam-Level: 
X-Spam-Status: No, score=-103.611 tagged_above=-999 required=5 tests=[AWL=-0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5EzNbpnvCt-U for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 15:47:14 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 0338721F8540 for <ietf@ietf.org>; Mon, 20 Jun 2011 15:47:13 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Mon, 20 Jun 2011 15:47:13 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, Andrew Sullivan <ajs@anvilwalrusden.com>
Date: Mon, 20 Jun 2011 15:47:12 -0700
Subject: RE: location preferences
Thread-Topic: location preferences
Thread-Index: AcwvlPxShuBivuDVSraYKVoQQhTZuAABtQdg
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC48D7@EXCH-C2.corp.cloudmark.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net>	<4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <12629.1308591177@marajade.sandelman.ca> <B7D833155E943151B52610C6@PST.JCK.COM> <BANLkTinPKSx08NaLdshuw8=NRZRMjNsMag@mail.gmail.com> <20110620214720.GH79936@shinkuro.com> <4DFFC210.7090209@dcrocker.net>
In-Reply-To: <4DFFC210.7090209@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 20 Jun 2011 22:47:14 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of D=
ave CROCKER
> Sent: Monday, June 20, 2011 2:57 PM
> To: Andrew Sullivan
> Cc: ietf@ietf.org
> Subject: Re: location preferences
>=20
> In any event, if crime statistics are to become a factor in choosing IETF
> venues, the IETF community needs to develop some consensus about this, in=
cluding
> what the acceptable parameters are.  As of now, I believe that's not gene=
rally
> part of the discussion in choosing a venue.

Unfortunately, I suspect adding "low crime" to the requirements list, with =
even the weakest of definitions of that, risks dramatically limiting our sh=
ort list of potential venues.


From randy@qualcomm.com  Mon Jun 20 15:49:49 2011
Return-Path: <randy@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 7F47521F8543 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 15:49: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y2fIwDP3uE-h for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 15:49:48 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 77AC021F8541 for <ietf@ietf.org>; Mon, 20 Jun 2011 15:49:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1308610188; x=1340146188; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p06240604ca257e2ac067@loud.pensive.org> |In-Reply-To:=20<BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail .gmail.com>|References:=20<20110618000852.16048.qmail@joy ce.lan>=0D=0A=20<BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail .gmail.com>|X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date: =20Mon,=2020=20Jun=202011=2015:48:40=20-0700|To:=20Mary =20Barnes=20<mary.ietf.barnes@gmail.com>,=20John=20Levine =20<johnl@iecc.com>|From:=20Randall=20Gellens=20<randy@qu alcomm.com>|Subject:=20Re:=20Getting=20to=20Quebec=20City |CC:=20<ietf@ietf.org>|MIME-Version:=201.0|Content-Type: =20text/plain=3B=20charset=3D"us-ascii"=3B=20format=3Dflo wed|X-Random-Sig-Tag:=201.0b28|X-Originating-IP:=20[172.3 0.39.5]; bh=ACCq5NI67E1/tGKjFdTq/LOBfW4LAVFsadbYSS04Ve4=; b=rUVnUWZgXrfX81dLN3qxmweH7NTh/lcpfbvnb+m3Nm3WGZ3s5WXq+x0L emcqikCN8LkVQHPCuD/mim3PKda6ocZrMeRxto9NqZOwatR/+pVjsj4qa Ihai4aUgklr3dXid+q/st2Hv8gkVn9IlOi5xqp3rcH/hWv6rs4vSlLthq 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,6383"; a="98941430"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine01.qualcomm.com with ESMTP; 20 Jun 2011 15:49:48 -0700
X-IronPort-AV: E=Sophos;i="4.65,394,1304319600"; d="scan'208";a="80726892"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 20 Jun 2011 15:49:48 -0700
Received: from loud.pensive.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 20 Jun 2011 15:49:46 -0700
Message-ID: <p06240604ca257e2ac067@loud.pensive.org>
In-Reply-To: <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com>
References: <20110618000852.16048.qmail@joyce.lan> <BANLkTinhuE+NsD6-tKZfZmrA0USoSzSkRA@mail.gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Mon, 20 Jun 2011 15:48:40 -0700
To: Mary Barnes <mary.ietf.barnes@gmail.com>, John Levine <johnl@iecc.com>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: Getting to Quebec City
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 22:49:49 -0000

At 10:43 AM -0500 6/18/11, Mary Barnes wrote:

>  As far as renting a car, it is likely a very good choice for anyone 
> that is arriving in Montreal later in the day.  I have a choice of 
> one direct flight to Montreal that puts me arriving in Montreal > 
> 7pm.  Even a one stop flight still puts me arriving around that 
> time.  So, given my experience in Maastricht with trains and a trip 
> that took about 18 hours gate to gate, I plan to rent a car (and 
> drop it off in QC on Sunday), which results in a trip < 8 hours 
> gate to gate.

I was considering flying to Montreal and taking the train to Quebec 
City, but the only schedule that was reasonable for me involved an 
overnight in Montreal.  I am planning to take the train from Quebec 
City to Montreal on Friday, and fly home from Montreal on Saturday.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Few ideas are really bad.  Most are either pre- or post-mature.
                                                   --Jon Postel

From dhc2@dcrocker.net  Mon Jun 20 16:01:09 2011
Return-Path: <dhc2@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 4F65311E80F2 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 16:01: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Z8BKYBXOlhB for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 16:01:08 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B0FD011E80B5 for <ietf@ietf.org>; Mon, 20 Jun 2011 16:01:08 -0700 (PDT)
Received: from [192.168.1.7] (ppp-68-120-198-5.dsl.pltn13.pacbell.net [68.120.198.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p5KN12hf031366 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 20 Jun 2011 16:01:07 -0700
Message-ID: <4DFFD12D.1040502@dcrocker.net>
Date: Mon, 20 Jun 2011 16:01:01 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: location preferences
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net>	<4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com>	<alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net>	<12629.1308591177@marajade.sandelman.ca>	<B7D833155E943151B52610C6@PST.JCK.COM>	<BANLkTinPKSx08NaLdshuw8=NRZRMjNsMag@mail.gmail.com>	<20110620214720.GH79936@shinkuro.com> <4DFFC210.7090209@dcrocker.net> <F5833273385BB34F99288B3648C4F06F134EBC48D7@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134EBC48D7@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 20 Jun 2011 16:01:08 -0700 (PDT)
Cc: "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, 20 Jun 2011 23:01:09 -0000

On 6/20/2011 3:47 PM, Murray S. Kucherawy wrote:
> Unfortunately, I suspect adding "low crime" to the requirements list, with even the weakest of definitions of that, risks dramatically limiting our short list of potential venues.


Especially if the definition of low crime means that the venue hotel isn't 
allowed to rip us off by charging $35 for a hamburger...

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From julien.ietf@gmail.com  Mon Jun 20 16:29:31 2011
Return-Path: <julien.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 457FA11E812A for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 16:29: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qotp6gO5HDvJ for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 16:29:30 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD8011E80B5 for <ietf@ietf.org>; Mon, 20 Jun 2011 16:29:29 -0700 (PDT)
Received: by bwz13 with SMTP id 13so4714428bwz.31 for <ietf@ietf.org>; Mon, 20 Jun 2011 16:29:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=FrvD22YYLDWfhhESmCcMWo6s4oBhsf9M4l9w97IMLb4=; b=PB5TgfGrceVAL+5bSdBZRUTnqJdtUYPVKh7shmVf4Uyl3bZwgeH3bn3OXmSmRMaKRR n2F27jMUd8/uekiad56zQaaVKe/1BU7ZUTEYTNNVfaZ2DWrjpu5sfFkG50fLT0/jqAWd MTpViQcnakkkzemLI98DnF1CijNVbmARvw6dg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=PAwAYRonlAlJtHQfhNlsf1gLUZe0+Qm4jEWMkxAKPGnYZEzvEykXkFFlQZRTXGutTK YOzbRFkAz6b5ZMqy5ssuKvo0Dd+LLqVr33a0RzdafyAXTq2ydMHMf+xntKjM//BgLJKb S2Pj/UG37bSeiB+xxNZeVYq2935Ck0UZwRoqg=
MIME-Version: 1.0
Received: by 10.204.145.18 with SMTP id b18mr4574651bkv.26.1308612568714; Mon, 20 Jun 2011 16:29:28 -0700 (PDT)
Received: by 10.204.176.77 with HTTP; Mon, 20 Jun 2011 16:29:28 -0700 (PDT)
In-Reply-To: <BANLkTikttkO7tZSoF63Xnk66LjagqgZF7Q@mail.gmail.com>
References: <20110618000852.16048.qmail@joyce.lan> <BANLkTikttkO7tZSoF63Xnk66LjagqgZF7Q@mail.gmail.com>
Date: Mon, 20 Jun 2011 16:29:28 -0700
Message-ID: <BANLkTimdi0ZBxFzpCEFWmNvzzLkBuv+rAQ@mail.gmail.com>
Subject: Re: Getting to Quebec City
From: Julien Laganier <julien.ietf@gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: John Levine <johnl@iecc.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, 20 Jun 2011 23:29:31 -0000

On Fri, Jun 17, 2011 at 5:32 PM, Eric Rescorla <ekr@rtfm.com> wrote:
> On Fri, Jun 17, 2011 at 5:08 PM, John Levine <johnl@iecc.com> wrote:
>> As you may have noticed, flying to Quebec City (YQB) is incredibly
>> expensive. =A0That's because it's a regional airport with little
>> competion. =A0Flying to Montreal is usuallly a lot cheaper. =A0Getting
>> from Trudeau airport in Montreal involves some planning, but it's not
>> hard. =A0The trip is about four hours; Quebec is big, bigger than any
>> state in the US.
>
> Nitpick alert:
>
> http://en.wikipedia.org/wiki/Quebec
> http://en.wikipedia.org/wiki/List_of_U.S._states_and_territories_by_area
>
> Quebec: =A0 Land area=3D1,365,128 km2 =A0 Water Area=3D176,928 km2
> Alaska: =A0Land Area: 1,481,347 km2 =A0Water Area=3D236,507 km2
>
> Perhaps you meant Continental US.

...or Contiguous US, to rule out any misunderstanding :)

http://en.wikipedia.org/wiki/Contiguous_United_States

--julien

From jmpolk@cisco.com  Mon Jun 20 17:24:24 2011
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 9319111E8115 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 17:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.384
X-Spam-Level: 
X-Spam-Status: No, score=-110.384 tagged_above=-999 required=5 tests=[AWL=0.215, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5eebMuPe2uqr for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 17:24:23 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id BD96F11E80B5 for <ietf@ietf.org>; Mon, 20 Jun 2011 17:24:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=2241; q=dns/txt; s=iport; t=1308615863; x=1309825463; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=z6ijnpEUNJjYYQg7/5WEFK03bPfGVlmUIHBji3mUSDs=; b=kOqBOz9wrmMe9HcdQTTGhr7HZi2mJ99zqu9yCPVJXugmxQikXh5Ideoi rbkRhTBx4eb3HMStB3MRjz86iVbAWenhYsfC8MAFaROV/R/uGIT5k429i Jpf9OY3VFZKaEtTLK3msvXLD8AtCLmWqiCgVaIVkyQOKjOqQp/6FCm3JT E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAMTj/02rRDoG/2dsb2JhbABTpmd3iHOhX54nhioEhyCaXQ
X-IronPort-AV: E=Sophos;i="4.65,397,1304294400"; d="scan'208";a="717901786"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-6.cisco.com with ESMTP; 21 Jun 2011 00:24:23 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p5L0OMpL018975; Tue, 21 Jun 2011 00:24:23 GMT
Message-Id: <201106210024.p5L0OMpL018975@mtv-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 20 Jun 2011 19:24:21 -0500
To: dcrocker@bbiw.net, Andrew Sullivan <ajs@anvilwalrusden.com>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: location preferences
In-Reply-To: <4DFFC210.7090209@dcrocker.net>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <12629.1308591177@marajade.sandelman.ca> <B7D833155E943151B52610C6@PST.JCK.COM> <BANLkTinPKSx08NaLdshuw8=NRZRMjNsMag@mail.gmail.com> <20110620214720.GH79936@shinkuro.com> <4DFFC210.7090209@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 Jun 2011 00:24:24 -0000

At 04:56 PM 6/20/2011, Dave CROCKER wrote:


>On 6/20/2011 2:47 PM, Andrew Sullivan wrote:
>>Speaking only for myself, I will note that the worst IETF experience I
>>ever had was in Dallas: the location was remote and poor, we were
>>flooded out of the hotel, alternatives nearby were few, and you needed
>>a car to go anywhere.
>
>It was, indeed, a horrible venue, along any number of parameters.

Andrew

rumor has it that IETF65 was supposed to be in New Orleans that 
November, but got hit by a little event called Katrina, so (again - 
only rumors) there had to be a mad scramble to find any hotel that 
could take 1400 in 2 months notice.

Don't hold Dallas being hit by a freak storm against the city's 
ability to have a decent conference - especially given more time to 
plan which hotel to stay in.

>Fortunately, Dallas has a few other choices that are likely to work 
>better, along every parameter we care about.

yes it does

James

> > Also, the crime statistics for the city made me
>>uneasy.
>
>The crime statistics for most American cities and most major 
>European cities make me uneasy.  In 1983 I moved to Toronto from 
>Washington DC and was amused by the different perspectives about 
>crime.  I was told there were a couple of blocks in downtown Toronto 
>that weren't very safe for women alone at night.  By contract, 
>perhaps 1/3-1/2 of DC was unsafe for almost anyone at night and 
>maybe 1/4 for most folk during the day...
>
>I've been ripped off twice in Paris including a double-team 
>pocket-picking. Purses and backpacks of IETF have been stolen -- 
>including from the middle of meeting rooms(!) -- in Munich, 
>Stockholm and I believe some other places.
>
>In any event, if crime statistics are to become a factor in choosing 
>IETF venues, the IETF community needs to develop some consensus 
>about this, including what the acceptable parameters are.  As of 
>now, I believe that's not generally part of the discussion in choosing a venue.
>
>d/
>
>--
>
>   Dave Crocker
>   Brandenburg InternetWorking
>   bbiw.net
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf


From randy@qualcomm.com  Mon Jun 20 18:25:45 2011
Return-Path: <randy@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 AA88F21F84C5 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 18:25:45 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RaPo1qgycoQs for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 18:25:45 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 0275821F846F for <ietf@ietf.org>; Mon, 20 Jun 2011 18:25:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1308619545; x=1340155545; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p06240609ca25a200267d@loud.pensive.org> |In-Reply-To:=20<4DFEA880.6080403@uijterwaal.nl> |References:=20<98C69027-EC6D-48AC-A5E5-F801DB2467D6@netw ork-heretics.com>=0D=0A=20<4DFD90C1.7010903@net-zen.net> =20<4DFEA880.6080403@uijterwaal.nl>|X-Mailer:=20Eudora=20 for=20Mac=20OS=20X|Date:=20Mon,=2020=20Jun=202011=2018:24 :52=20-0700|To:=20Henk=20Uijterwaal=20<henk@uijterwaal.nl >,=20<ietf@ietf.org>|From:=20Randall=20Gellens=20<randy@q ualcomm.com>|Subject:=20Re:=20Has=20anyone=20found=20a=20 hotel=20for=20Quebec=20City=20that=20isn't=0D=0A=20exorbi tant?|CC:=20Dave=20Crocker=20<dcrocker@bbiw.net> |MIME-Version:=201.0|Content-Type:=20text/plain=3B=20char set=3D"us-ascii"=3B=20format=3Dflowed|X-Random-Sig-Tag: =201.0b28|X-Originating-IP:=20[172.30.39.5]; bh=BoTrGLGnKU7GIVAYCEXQUJYZgeY4kI7R2EjquD4lTNA=; b=PBrfTFJXpzn46lHLKtDD1kdMil1QWrJGrF7CdGbPG9wPTxZV3w3p0MN7 xxeFLhPVbwDcKtCp3CiF7IFBFslftZ7YdXPovM2CYBHaZ6Dsi4mYJpvF1 U3sudBg87wNkHHSOGGeQCBYmS+JMIZnLt1bjzxIZ3OTzlbJ4dNj5oo9hG I=;
X-IronPort-AV: E=McAfee;i="5400,1158,6383"; a="98780374"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 20 Jun 2011 18:25:44 -0700
X-IronPort-AV: E=Sophos;i="4.65,394,1304319600"; d="scan'208";a="80755719"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 20 Jun 2011 18:25:44 -0700
Received: from loud.pensive.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 20 Jun 2011 18:25:44 -0700
Message-ID: <p06240609ca25a200267d@loud.pensive.org>
In-Reply-To: <4DFEA880.6080403@uijterwaal.nl>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>
X-Mailer: Eudora for Mac OS X
Date: Mon, 20 Jun 2011 18:24:52 -0700
To: Henk Uijterwaal <henk@uijterwaal.nl>, <ietf@ietf.org>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 01:25:45 -0000

At 3:55 AM +0200 6/20/11, Henk Uijterwaal wrote:

>  May I point out that there has been a survey on the topic and the community
>  expressed a clear preference for Quebec over other Canadian cities, knowing
>  that travel would be longer and the number of cheap alternative hotels
>  smaller.

My recollection, which of course could easily be flawed, is that the 
survey did not make clear that travel is significantly more difficult 
to Quebec than other Canadian cities, nor that hotels are more 
expensive.  My recollection is that after the survey there was much 
discussion of this issue, with a number of people pointing out a 
number of fairly important problems with the survey.  Off the top of 
my head, in addition to not mentioning the travel issue, also 
included lumping together into "this group" or "that group" cities 
which are very different in terms of travel connection, venue 
suitability, cost, etc.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Learn from your parents' mistake -- use birth control.

From henk.uijterwaal@gmail.com  Mon Jun 20 18:49:58 2011
Return-Path: <henk.uijterwaal@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36DCF9E8018 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 18:49:58 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i99voB0HfQop for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 18:49:57 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6A3C79E8007 for <ietf@ietf.org>; Mon, 20 Jun 2011 18:49:57 -0700 (PDT)
Received: by pzk5 with SMTP id 5so4443808pzk.31 for <ietf@ietf.org>; Mon, 20 Jun 2011 18:49:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:reply-to:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=/wqLyNZPzXH3wyOH+n4B9CklP0H1ZdIPmquIo3YXE7U=; b=a95XBWDkqiwRW/a/jT7H+2OouI3ONu9417j16g3zH6+JDQeu9I1ERwimGArQlFBRRx Xzd/Hh5XqDI3T2npYGd18AzAgrKmH/P/yNsnLJ1HtkEo857W5blvt68Qqyt/6bZGcFIi 20Xafu1KyiOVAPQhcU4P5RyGfoip88/9mFg9I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=JnbBJWibd1EtEHWBkH7JWJjqGsBeWRuk1p6qmdY9s2uO8vIG1rRdz43kZkVGaU9UbI n/s7mCu218Zkl8WN/AU5hja/G8Tk5MlLg8NsZNold99tYNGdIsiMUncc5/W6xKsSiAAg IPQT/ZKal6nEK0aWPOX9DU13yEdDXOK7IO3aw=
Received: by 10.142.166.20 with SMTP id o20mr971654wfe.121.1308620996756; Mon, 20 Jun 2011 18:49:56 -0700 (PDT)
Received: from geir.local ([61.8.214.4]) by mx.google.com with ESMTPS id d15sm6781459wfl.6.2011.06.20.18.49.53 (version=SSLv3 cipher=OTHER); Mon, 20 Jun 2011 18:49:55 -0700 (PDT)
Message-ID: <4DFFF8BE.3080802@gmail.com>
Date: Tue, 21 Jun 2011 03:49:50 +0200
From: Henk Uijterwaal <henk.uijterwaal@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <p06240609ca25a200267d@loud.pensive.org>
In-Reply-To: <p06240609ca25a200267d@loud.pensive.org>
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: henk@uijterwaal.nl
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 01:49:58 -0000

On 21/06/2011 03:24, Randall Gellens wrote:
> At 3:55 AM +0200 6/20/11, Henk Uijterwaal wrote:
> 
>>  May I point out that there has been a survey on the topic and the community
>>  expressed a clear preference for Quebec over other Canadian cities, knowing
>>  that travel would be longer and the number of cheap alternative hotels
>>  smaller.
> 
> My recollection, which of course could easily be flawed, is that the survey did
> not make clear that travel is significantly more difficult to Quebec than other
> Canadian cities, nor that hotels are more expensive.  My recollection is that
> after the survey there was much discussion of this issue, with a number of
> people pointing out a number of fairly important problems with the survey.  Off
> the top of my head, in addition to not mentioning the travel issue, also
> included lumping together into "this group" or "that group" cities which are
> very different in terms of travel connection, venue suitability, cost, etc.

I checked and the survey said that the advantage of Vancouver (the alternative
for Quebec) was that travel to Vancouver was a lot easier than to Quebec.

At the time when the survey was taken, Quebec had the advantage that there was
a much wider range of alternative/cheaper hotels available than in Vancouver
within reasonable distance of the meeting venue.

Of course, room rates outside the host hotel are not under the control of the
IETF and can change in the 2 years between fixing the location and the actual
meeting.

Henk

-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
                                          http://www.uijterwaal.nl
                                          Phone: +31.6.55861746
------------------------------------------------------------------------------

There appears to have been a collective retreat from reality that day.
                                 (John Glanfield, on an engineering project)

From stewe@stewe.org  Mon Jun 20 18:56:51 2011
Return-Path: <stewe@stewe.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 989B011E8090 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 18:56:51 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uooBnCoLqDPi for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 18:56:50 -0700 (PDT)
Received: from stewe.org (stewe.org [85.214.122.234]) by ietfa.amsl.com (Postfix) with ESMTP id 3F30311E8071 for <ietf@ietf.org>; Mon, 20 Jun 2011 18:56:49 -0700 (PDT)
Received: from [75.198.166.108] (unverified [75.198.166.108])  by stewe.org (SurgeMail 3.9e) with ESMTP id 4074-1743317  for multiple; Tue, 21 Jun 2011 03:56:45 +0200
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <p06240609ca25a200267d@loud.pensive.org> <4DFFF8BE.3080802@gmail.com>
In-Reply-To: <4DFFF8BE.3080802@gmail.com>
Mime-Version: 1.0 (iPad Mail 8J2)
Content-Type: text/plain; charset=us-ascii
Message-Id: <E746C5D0-CD56-4F3E-AF88-C0F5F9C5DDB4@stewe.org>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (8J2)
From: Stephan Wenger <stewe@stewe.org>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
Date: Mon, 20 Jun 2011 21:56:41 -0400
To: "henk@uijterwaal.nl" <henk@uijterwaal.nl>
X-Originating-IP: 75.198.166.108
X-Authenticated-User: stewe@stewe.org 
X-ORBS-Stamp: Your IP (75.198.166.108) was found in the spamhaus database. http://www.spamhaus.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: Tue, 21 Jun 2011 01:56:51 -0000

Vancouver is pretty expensive in summer. Can be twice the rate of November. =
 Weather.
Stephan
S.

Sent from my iPad

On Jun 20, 2011, at 21:49, Henk Uijterwaal <henk.uijterwaal@gmail.com> wrote=
:

> On 21/06/2011 03:24, Randall Gellens wrote:
>> At 3:55 AM +0200 6/20/11, Henk Uijterwaal wrote:
>>=20
>>> May I point out that there has been a survey on the topic and the commun=
ity
>>> expressed a clear preference for Quebec over other Canadian cities, know=
ing
>>> that travel would be longer and the number of cheap alternative hotels
>>> smaller.
>>=20
>> My recollection, which of course could easily be flawed, is that the surv=
ey did
>> not make clear that travel is significantly more difficult to Quebec than=
 other
>> Canadian cities, nor that hotels are more expensive.  My recollection is t=
hat
>> after the survey there was much discussion of this issue, with a number o=
f
>> people pointing out a number of fairly important problems with the survey=
.  Off
>> the top of my head, in addition to not mentioning the travel issue, also
>> included lumping together into "this group" or "that group" cities which a=
re
>> very different in terms of travel connection, venue suitability, cost, et=
c.
>=20
> I checked and the survey said that the advantage of Vancouver (the alterna=
tive
> for Quebec) was that travel to Vancouver was a lot easier than to Quebec.
>=20
> At the time when the survey was taken, Quebec had the advantage that there=
 was
> a much wider range of alternative/cheaper hotels available than in Vancouv=
er
> within reasonable distance of the meeting venue.
>=20
> Of course, room rates outside the host hotel are not under the control of t=
he
> IETF and can change in the 2 years between fixing the location and the act=
ual
> meeting.
>=20
> Henk
>=20
> --=20
> --------------------------------------------------------------------------=
----
> Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
>                                          http://www.uijterwaal.nl
>                                          Phone: +31.6.55861746
> --------------------------------------------------------------------------=
----
>=20
> There appears to have been a collective retreat from reality that day.
>                                 (John Glanfield, on an engineering project=
)
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From johnl@iecc.com  Mon Jun 20 20:52:44 2011
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 A306421F84A2 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 20:52:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.551
X-Spam-Level: 
X-Spam-Status: No, score=-110.551 tagged_above=-999 required=5 tests=[AWL=0.648, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fvfA15mQWXK8 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 20:52:44 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id DE54A21F849C for <ietf@ietf.org>; Mon, 20 Jun 2011 20:52:43 -0700 (PDT)
Received: (qmail 61796 invoked from network); 21 Jun 2011 03:52:42 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 21 Jun 2011 03:52:42 -0000
Date: 21 Jun 2011 03:52:20 -0000
Message-ID: <20110621035220.13199.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: whine, whine, whine
In-Reply-To: <p06240609ca25a200267d@loud.pensive.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: randy@qualcomm.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 03:52:44 -0000

>My recollection, which of course could easily be flawed, is that the 
>survey did not make clear that travel is significantly more difficult 
>to Quebec than other Canadian cities, nor that hotels are more 
>expensive.

The hotels in Quebec are no more expensive than hotels in other cities
where the IETF might meet such as Montreal, Toronto, or Vancouver.  If
anything, they're cheaper.  Look up some prices on Hotwire ($101/night
for three stars within 1/2 mi of convention centre) or Expedia or
Orbitz if you don't believe it.  The Laval university dorms, which
people tell me are pretty nice, are a reasonable option if you want
cheap, and are a steal at $51.

Quebec has been in the exact same location for over 400 years.  It's
not like its a secret to anyone who can look at a map.  It may not be
as easy to get to as, say, Toronto or Chicago, but (at least from
where I live) it's a lot easier to get to than a remote armpit like,
oh, San Diego.

Since I am your pal, here is a preview of more things to complain
about:

* There is no usable bus from the airport (it runs only at commuter
  hours) and a taxi costs C$32.50

* Nobody will accept US money at par any more, if they accept it at
  all. Your bank probably does not have a branch in Quebec.

* The social event is in the lower city, which is down steep and
  inconvenient streets, stairs, and/or funicular from the upper city
  where the meeting and most hotels are.  Even worse, you will have to
  go up those steep streets, stairs, and/or funicular after the event
  when you are too drunk to remember where your hotel is.

* The city has historic monuments which are insulting to the Americans
  who failed to capture the city in 1775.

* And worst of all, everyone speaks French.

See you all there,
John


From gwz@net-zen.net  Mon Jun 20 21:07:45 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86B1221F85BD for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:07: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8+io6AnCyJV for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:07:45 -0700 (PDT)
Received: from p3plsmtpa06-09.prod.phx3.secureserver.net (p3plsmtpa06-09.prod.phx3.secureserver.net [173.201.192.110]) by ietfa.amsl.com (Postfix) with SMTP id 0B2E121F85BB for <ietf@ietf.org>; Mon, 20 Jun 2011 21:07:44 -0700 (PDT)
Received: (qmail 31458 invoked from network); 21 Jun 2011 04:01:03 -0000
Received: from unknown (124.120.86.123) by p3plsmtpa06-09.prod.phx3.secureserver.net (173.201.192.110) with ESMTP; 21 Jun 2011 04:01:02 -0000
Message-ID: <4E001776.1020600@net-zen.net>
Date: Tue, 21 Jun 2011 11:00:54 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------020505050301060109010403"
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 04:07:45 -0000

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

On 6/20/2011 11:54 PM, Ole Jacobsen wrote:

> 
> Keith,
> 
> Here is the tradeoff:
> 
> "The community" has expressed a strong preference for one-roof venues 
> [which often translates to convention center + hotel next door in our
> case] in a city setting (City West and Maastricht being non-examples).
> 
> This leads to (generally speaking):
> 
> * Somewhat expensive main hotel rates (although I agree that hotel 
>   rates seem to be as variable and unpredictable as airline rates, and 
>   I would hope we could do better even if we sign the contract several 
>   years in advance.)

Actually, it seems that the conference rates at IETF hotels are quite
predictable: a couple of months ago it was possible to book a room at
the QC Hilton for $176 CAD/night _during the IETF meeting_; if you check
the Hilton Web site right now, you will find that equivalent rooms at
the Hilton the week before the IETF run about $100 less than during the
meeting.  It's possible that IETF week marks the transition to high
season rates, but in that case why not move the meeting by a week?  This
is not an isolated case: in Beijing, rooms at the Shangri-La were
significantly cheaper both the week before and the week after the IETF;
in Hiroshima, I got a room at the conference hotel the week of the
meeting for ~$50/night less than the conference rate by eschewing "free"
breakfast.  Admittedly the breakfast in Hiroshima was both tasty and
plentiful, but $50?  Not even in Japan.  It seems apparent that the IAOC
"negotiators" are wearing signs around their necks during the hotel
negotiations; the only question is what is written on the signs.  Is it
"I am a moron" or the simple but effective "F*&k Me"?

...

--------------020505050301060109010403
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------020505050301060109010403--

From gwz@net-zen.net  Mon Jun 20 21:12:17 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EF8811E8147 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:12: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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exrB2WZp0SLx for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:12:16 -0700 (PDT)
Received: from p3plsmtpa07-02.prod.phx3.secureserver.net (p3plsmtpa07-02.prod.phx3.secureserver.net [173.201.192.231]) by ietfa.amsl.com (Postfix) with SMTP id 26CA711E8098 for <ietf@ietf.org>; Mon, 20 Jun 2011 21:12:16 -0700 (PDT)
Received: (qmail 16407 invoked from network); 21 Jun 2011 04:12:12 -0000
Received: from unknown (124.120.86.123) by p3plsmtpa07-02.prod.phx3.secureserver.net (173.201.192.231) with ESMTP; 21 Jun 2011 04:12:11 -0000
Message-ID: <4E001A16.3030208@net-zen.net>
Date: Tue, 21 Jun 2011 11:12:06 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com>	<alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net>	<12629.1308591177@marajade.sandelman.ca>	<B7D833155E943151B52610C6@PST.JCK.COM> <BANLkTinPKSx08NaLdshuw8=NRZRMjNsMag@mail.gmail.com>
In-Reply-To: <BANLkTinPKSx08NaLdshuw8=NRZRMjNsMag@mail.gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------060304090902050306060106"
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 Jun 2011 04:12:17 -0000

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

On 6/21/2011 2:02 AM, Mary Barnes wrote:
> Exactly.   Given that we spend most of our days in air conditioned
> meeting rooms, Phoenix or Dallas are not bad choices. Dallas is slightly
> better due to air connections.  Houston is not a good choice under any
> circumstance IMHO - I don't think A/C can remove enough humidity to make
> it comfortable in July.  
> 
> Personally, I have no issue with Minneapolis in November or March -
> again we spend most of the time in meeting rooms, so do we really care
> that much about the weather outside?

Some of us actually like to go outside occasionally without being either
blistered or frozen.  Please speak for yourself (or are we using the
royal "we"?

...

--------------060304090902050306060106
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------060304090902050306060106--

From gwz@net-zen.net  Mon Jun 20 21:17:50 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 547AF11E81B0 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LIxNwead0paC for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:17:49 -0700 (PDT)
Received: from smtpauth21.prod.mesa1.secureserver.net (smtpauth21.prod.mesa1.secureserver.net [64.202.165.38]) by ietfa.amsl.com (Postfix) with SMTP id A222111E819F for <ietf@ietf.org>; Mon, 20 Jun 2011 21:17:49 -0700 (PDT)
Received: (qmail 24695 invoked from network); 21 Jun 2011 04:17:48 -0000
Received: from unknown (124.120.86.123) by smtpauth21.prod.mesa1.secureserver.net (64.202.165.38) with ESMTP; 21 Jun 2011 04:17:48 -0000
Message-ID: <4E001B65.5070404@net-zen.net>
Date: Tue, 21 Jun 2011 11:17:41 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com><4DFD90C1.7010903@net-zen.net>	<4DFEA880.6080403@uijterwaal.nl><5E893DB832F57341992548CDBB333163A0A7AE283A@EMBX01-HQ.jnpr.net>	<2C3647B4-64CE-4D98-A539-04D884ECE94B@lucidvision.com> <077E41CFFD002C4CAB7DFA4386A532640400223A@DEMUEXC014.nsn-intra.net>
In-Reply-To: <077E41CFFD002C4CAB7DFA4386A532640400223A@DEMUEXC014.nsn-intra.net>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------040700050106040206000303"
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 04:17:50 -0000

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

On 6/21/2011 3:14 AM, Sprecher, Nurit (NSN - IL/Hod HaSharon) wrote:

> Same in my case!

So why is that the case?  The IAOC is virtually guaranteeing a a
sold-out hotel the week of the IETF meeting, a thing that has not
inconsiderable value in the hospitality.  How can they possibly not do
better?

...

--------------040700050106040206000303
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------040700050106040206000303--

From msk@cloudmark.com  Mon Jun 20 21:26:11 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4C4C11E81EC for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.61
X-Spam-Level: 
X-Spam-Status: No, score=-103.61 tagged_above=-999 required=5 tests=[AWL=-0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PuEZy3Lx99KB for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:26:11 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 639DC11E81D7 for <ietf@ietf.org>; Mon, 20 Jun 2011 21:26:11 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Mon, 20 Jun 2011 21:26:11 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 20 Jun 2011 21:26:09 -0700
Subject: RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Topic: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Index: Acwve7guj2CvHv1ZRh6TCrqnsUYfHQAT4k8w
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC48DE@EXCH-C2.corp.cloudmark.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <12629.1308591177@marajade.sandelman.ca> <B7D833155E943151B52610C6@PST.JCK.COM>
In-Reply-To: <B7D833155E943151B52610C6@PST.JCK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 04:26:11 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of J=
ohn C Klensin
> Sent: Monday, June 20, 2011 11:56 AM
> To: Michael Richardson; ietf@ietf.org
> Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbita=
nt?
>=20
> > What's a non-peak destination for July?
>=20
> Phoenix.  Probably Houston or Fort Worth.  Wellington or
> somewhere on the South Island that doesn't attract skiers.

I was going to suggest Las Vegas.  Certainly has adequate conference facili=
ties and plenty of room availability these days.


From joelja@bogus.com  Mon Jun 20 21:30:59 2011
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 2950A21F85F8 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.106
X-Spam-Level: 
X-Spam-Status: No, score=-102.106 tagged_above=-999 required=5 tests=[AWL=0.493, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3m40DcMzpDQP for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:30:58 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3475E21F85F6 for <ietf@ietf.org>; Mon, 20 Jun 2011 21:30:58 -0700 (PDT)
Received: from [192.168.1.171] (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5L4Utw6097591 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 21 Jun 2011 04:30:55 GMT (envelope-from joelja@bogus.com)
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4E001776.1020600@net-zen.net>
Date: Mon, 20 Jun 2011 21:30:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <4E001776.1020600@net-zen.net>
To: Glen Zorn <gwz@net-zen.net>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 21 Jun 2011 04:30:56 +0000 (UTC)
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, Ole Jacobsen <ole@cisco.com>, Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 04:30:59 -0000

On Jun 20, 2011, at 9:00 PM, Glen Zorn wrote:

> On 6/20/2011 11:54 PM, Ole Jacobsen wrote:
>=20
>>=20
>> Keith,
>>=20
>> Here is the tradeoff:
>>=20
>> "The community" has expressed a strong preference for one-roof venues=20=

>> [which often translates to convention center + hotel next door in our
>> case] in a city setting (City West and Maastricht being =
non-examples).
>>=20
>> This leads to (generally speaking):
>>=20
>> * Somewhat expensive main hotel rates (although I agree that hotel=20
>>  rates seem to be as variable and unpredictable as airline rates, and=20=

>>  I would hope we could do better even if we sign the contract several=20=

>>  years in advance.)
>=20
> Actually, it seems that the conference rates at IETF hotels are quite
> predictable: a couple of months ago it was possible to book a room at
> the QC Hilton for $176 CAD/night _during the IETF meeting_; if you =
check
> the Hilton Web site right now, you will find that equivalent rooms at
> the Hilton the week before the IETF run about $100 less than during =
the
> meeting.  It's possible that IETF week marks the transition to high
> season rates, but in that case why not move the meeting by a week?  =
This
> is not an isolated case: in Beijing, rooms at the Shangri-La were
> significantly cheaper both the week before and the week after the =
IETF;
> in Hiroshima, I got a room at the conference hotel the week of the
> meeting for ~$50/night less than the conference rate by eschewing =
"free"
> breakfast.  Admittedly the breakfast in Hiroshima was both tasty and
> plentiful, but $50?  Not even in Japan.  It seems apparent that the =
IAOC
> "negotiators" are wearing signs around their necks during the hotel
> negotiations; the only question is what is written on the signs.  Is =
it
> "I am a moron" or the simple but effective "F*&k Me"


It has been repeated ad-nausieum that "conference rates" subsidize the =
rental of the meeting room block... The fact that the conference rates =
are more expensive ( on a contract signed 24 months out) than a spot =
check of the room rate at any given time should come as no surprise to =
anyone. You can cruise the IETF finances if for some reason you don't =
believe this. If the room block doesn't get filled you can expect your =
fees to go up accordingly over time. I will observe that I have =
generally  not paid the conference rate or stayed in the meeting hotel =
while attending the IETF on my own dime (and have stayed in some rather =
nicer hotels (paris, stockholm, etc) for less money as a result. When I =
attend on behalf my employer I make it clear what we paying for when =
participating.

please look at the balance sheet here:

http://iaoc.ietf.org/documents/Meeting-Financials-2010-77.pdf

and note both the hotel commission, a credit, and the zero charge =
associated with meeting rooms.

It's not clear to me that this can be made more transparent, but if =
you'd like to try I'm sure that someone would be happy to nominate you =
for an open iaoc position when available.

joel=

From msk@cloudmark.com  Mon Jun 20 21:31:31 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EC0E21F8601 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.609
X-Spam-Level: 
X-Spam-Status: No, score=-103.609 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rGJ5vdrx3WQ4 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:31:30 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 8B8B321F8602 for <ietf@ietf.org>; Mon, 20 Jun 2011 21:31:30 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Mon, 20 Jun 2011 21:31:30 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 20 Jun 2011 21:31:29 -0700
Subject: RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Topic: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Index: AcwvsjQVKpwi3yyzTb6GU2s47yToPgAGWM2g
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC48DF@EXCH-C2.corp.cloudmark.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <p06240609ca25a200267d@loud.pensive.org>
In-Reply-To: <p06240609ca25a200267d@loud.pensive.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 04:31:31 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of R=
andall Gellens
> Sent: Monday, June 20, 2011 6:25 PM
> To: Henk Uijterwaal; ietf@ietf.org
> Cc: Dave Crocker
> Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbita=
nt?
>=20
> My recollection, which of course could easily be flawed, is that the
> survey did not make clear that travel is significantly more difficult
> to Quebec than other Canadian cities, nor that hotels are more
> expensive.

How is travel significantly more difficult to Quebec City?  It's one plane =
change from most US and Canadian points of origin that I checked, or even d=
irect if you're close enough.

My flight in changes in Newark and out in Chicago, both major intercontinen=
tal hubs which means there are plenty of long-range connections that are no=
 more difficult.

From moore@network-heretics.com  Mon Jun 20 21:51:03 2011
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 7915311E80B9 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.708
X-Spam-Level: 
X-Spam-Status: No, score=-2.708 tagged_above=-999 required=5 tests=[AWL=-0.499, BAYES_00=-2.599, PLING_QUERY=1.39, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KsC5k9LMmpg9 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:51:03 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id DE3BC11E809D for <ietf@ietf.org>; Mon, 20 Jun 2011 21:51:02 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id B7130207EA for <ietf@ietf.org>; Tue, 21 Jun 2011 00:51:01 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute5.internal (MEProxy); Tue, 21 Jun 2011 00:51:01 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=k/r+0GIh6TZZ5ULJFzKG3FflyF4=; b=NJfEdMYmBw/DdyD7g1yIowsVeuk7ZHhhDNjLXcCr1A6tN2jhQchNIl8zipjisF6ge9ITGxZUavcQY3BOyxr0gciHhe5blGZgeg9n2r/I1J40DfZnKcyzq04idka4/IpCihwBy7+zft/KTM/qJuZ4roorYC8oD2Ip9qv/4lqhWcE=
X-Sasl-enc: RgU7YrrOpng28M0gRXKP52Yc/qlCTXYJgXveUWLlhHXa 1308631861
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 3BDA844361D; Tue, 21 Jun 2011 00:51:01 -0400 (EDT)
Subject: Thanks! (was: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>
Date: Tue, 21 Jun 2011 00:50:56 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <BCFBC0B3-6169-485E-B13B-4804ACBB88E7@network-heretics.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
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, 21 Jun 2011 04:51:03 -0000

Thanks to those who replied with suggestions for accommodations.

Keith


From henk.uijterwaal@gmail.com  Mon Jun 20 21:52:58 2011
Return-Path: <henk.uijterwaal@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C10D11E8209 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.29
X-Spam-Level: 
X-Spam-Status: No, score=-3.29 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Id4ISaRK+WX0 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 21:52:57 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0400711E81F7 for <ietf@ietf.org>; Mon, 20 Jun 2011 21:52:56 -0700 (PDT)
Received: by iye7 with SMTP id 7so2900632iye.31 for <ietf@ietf.org>; Mon, 20 Jun 2011 21:52:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:reply-to:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=alog57VicRA2ShEJW1eazb0ANRzZPcXRNyxDTzLaLzo=; b=s9hsSFIKHt61tyjm1jUsN1rhnX8yo7CMfxmEHckVLWcPeXCImh11PurJb4ZASXCwNY hU8iJ0OXTCPm8U5zz2CUHbBIPpGs5vJNyu2KCY9bwaGfA2ZoaMhyoCAAK9eH+cG8k1hk EFONfuE44wBeit5BI0IHTeHu1YOhuTNs3Z0D4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=I1L4aKcognBu0y03Gi4nsCV5olLjgrzj12rjV1omtMNwPQ52WfJeMplXs+/ErN42Fh HvS4RVCHgX8EOr9mNTwnleayxCRvy4PuCUzAO/HNHu96MINCUvvniHCIsXxOxWPytIAN T0izbnBG05nroX+DORzTnY6z6XUlE2ujUmkgk=
Received: by 10.43.48.137 with SMTP id uw9mr5778278icb.87.1308631974704; Mon, 20 Jun 2011 21:52:54 -0700 (PDT)
Received: from geir.local ([61.8.214.5]) by mx.google.com with ESMTPS id fw9sm3607151ibb.30.2011.06.20.21.52.52 (version=SSLv3 cipher=OTHER); Mon, 20 Jun 2011 21:52:53 -0700 (PDT)
Message-ID: <4E00239F.4030000@gmail.com>
Date: Tue, 21 Jun 2011 06:52:47 +0200
From: Henk Uijterwaal <henk.uijterwaal@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>	<p06240609ca25a200267d@loud.pensive.org> <F5833273385BB34F99288B3648C4F06F134EBC48DF@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134EBC48DF@EXCH-C2.corp.cloudmark.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
Reply-To: henk@uijterwaal.nl
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 04:52:58 -0000

On 21/06/2011 06:31, Murray S. Kucherawy wrote:

> How is travel significantly more difficult to Quebec City?  It's one plane
> change from most US and Canadian points of origin that I checked, or even
> direct if you're close enough.

If you look at the number of cities served by direct flights from Vancouver and
Quebec, you will see that the number for Vancouver is much higher.  Vancouver
also has lots of direct flights to Europe.

And each extra hop in a flight path, gives the chance of missing a connection,
the airline losing your bag and all that.

> My flight in changes in Newark and out in Chicago, both major
> intercontinental hubs which means there are plenty of long-range connections
> that are no more difficult.

In my case, coming from Europe, that means that I have to go through US
customs, recheck my bags and wait for the next plane.  That is a minimum
of 2-3 hours extra.

Henk

-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
                                          http://www.uijterwaal.nl
                                          Phone: +31.6.55861746
------------------------------------------------------------------------------

There appears to have been a collective retreat from reality that day.
                                 (John Glanfield, on an engineering project)

From johnl@iecc.com  Mon Jun 20 22:04:46 2011
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 A22DA11E8081 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 22:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.579
X-Spam-Level: 
X-Spam-Status: No, score=-110.579 tagged_above=-999 required=5 tests=[AWL=0.620, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cuw1QB6K5Efn for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 22:04:46 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id EE59111E80D5 for <ietf@ietf.org>; Mon, 20 Jun 2011 22:04:45 -0700 (PDT)
Received: (qmail 70239 invoked from network); 21 Jun 2011 05:04:44 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 21 Jun 2011 05:04:44 -0000
Date: 21 Jun 2011 05:04:22 -0000
Message-ID: <20110621050422.15617.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: getting there
In-Reply-To: <4E00239F.4030000@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: henk@uijterwaal.nl
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 05:04:46 -0000

>> My flight in changes in Newark and out in Chicago, both major
>> intercontinental hubs which means there are plenty of long-range
>> connections that are no more difficult.

>In my case, coming from Europe, that means that I have to go through US
>customs, recheck my bags and wait for the next plane.  That is a minimum
>of 2-3 hours extra.

So get flights that connect in Montreal or Toronto.

Surely this crowd can figure out how to use online booking engines.

R's,
John

From marka@isc.org  Mon Jun 20 22:04:46 2011
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 C99EB11E80A8 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 22:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[AWL=0.198,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IfCF0DtyTyMT for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 22:04:46 -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 E387E11E80CF for <ietf@ietf.org>; Mon, 20 Jun 2011 22:04:45 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 891415F98B1; Tue, 21 Jun 2011 05:04:18 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 AA939216C7B; Tue, 21 Jun 2011 05:04:16 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 5F6BA10F4761; Tue, 21 Jun 2011 15:04:13 +1000 (EST)
To: henk@uijterwaal.nl
From: Mark Andrews <marka@isc.org>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <p06240609ca25a200267d@loud.pensive.org> <F5833273385BB34F99288B3648C4F06F134EBC48DF@EXCH-C2.corp.cloudmark.com> <4E00239F.4030000@gmail.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
In-reply-to: Your message of "Tue, 21 Jun 2011 06:52:47 +0200." <4E00239F.4030000@gmail.com>
Date: Tue, 21 Jun 2011 15:04:13 +1000
Message-Id: <20110621050413.5F6BA10F4761@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 Jun 2011 05:04:46 -0000

Why is this being discussed here?  Logistics about Quebec and how to
get there should be discussed on 81attendees.

	https://www.ietf.org/mailman/listinfo/81attendees

In message <4E00239F.4030000@gmail.com>, Henk Uijterwaal writes:
> On 21/06/2011 06:31, Murray S. Kucherawy wrote:
> 
> > How is travel significantly more difficult to Quebec City?  It's one plane
> > change from most US and Canadian points of origin that I checked, or even
> > direct if you're close enough.
> 
> If you look at the number of cities served by direct flights from Vancouver a
> nd
> Quebec, you will see that the number for Vancouver is much higher.  Vancouver
> also has lots of direct flights to Europe.
> 
> And each extra hop in a flight path, gives the chance of missing a connection
> ,
> the airline losing your bag and all that.
> 
> > My flight in changes in Newark and out in Chicago, both major
> > intercontinental hubs which means there are plenty of long-range connection
> s
> > that are no more difficult.
> 
> In my case, coming from Europe, that means that I have to go through US
> customs, recheck my bags and wait for the next plane.  That is a minimum
> of 2-3 hours extra.
> 
> Henk
> 
> -- 
> -----------------------------------------------------------------------------
> -
> Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
>                                           http://www.uijterwaal.nl
>                                           Phone: +31.6.55861746
> -----------------------------------------------------------------------------
> -
> 
> There appears to have been a collective retreat from reality that day.
>                                  (John Glanfield, on an engineering project)
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From randy@qualcomm.com  Mon Jun 20 22:09:25 2011
Return-Path: <randy@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 A5AA611E809D for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 22:09:25 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cWFyuZniejAC for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 22:09:25 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id E58C711E80D7 for <ietf@ietf.org>; Mon, 20 Jun 2011 22:09:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1308632964; x=1340168964; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p0624060dca25d4aa0695@loud.pensive.org> |In-Reply-To:=20<20110621035220.13199.qmail@joyce.lan> |References:=20<20110621035220.13199.qmail@joyce.lan> |X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date:=20Mon,=202 0=20Jun=202011=2022:06:23=20-0700|To:=20John=20Levine=20< johnl@iecc.com>,=20<ietf@ietf.org>|From:=20Randall=20Gell ens=20<randy@qualcomm.com>|Subject:=20Re:=20whine,=20whin e,=20whine|MIME-Version:=201.0|Content-Type:=20text/plain =3B=20charset=3D"us-ascii"=3B=20format=3Dflowed |X-Random-Sig-Tag:=201.0b28|X-Originating-IP:=20[172.30.4 8.1]; bh=oss5QRzj6YwbM5lbURUwJmqsGeMMI1DqKHQpg4q97ZQ=; b=ujvnjR8OYtpIwScCDGm08mbP5HILRyNUAdaeRWOutOGXSrtpMDiB0y2/ 10GPE1CNB30ApXE7KpRAw7zTv06iw3j3cBXGsB7ZacS4A+8irWmwM1RIG kEo7cs0kdIFtpYUNhyr2syb7jt0GOxJ9A3CaEGFT7Ke6QmqUzc+lYY4jG 4=;
X-IronPort-AV: E=McAfee;i="5400,1158,6383"; a="98804400"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 20 Jun 2011 22:09:24 -0700
X-IronPort-AV: E=Sophos;i="4.65,397,1304319600"; d="scan'208";a="80779661"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 20 Jun 2011 22:09:24 -0700
Received: from loud.pensive.org (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 20 Jun 2011 22:06:43 -0700
Message-ID: <p0624060dca25d4aa0695@loud.pensive.org>
In-Reply-To: <20110621035220.13199.qmail@joyce.lan>
References: <20110621035220.13199.qmail@joyce.lan>
X-Mailer: Eudora for Mac OS X
Date: Mon, 20 Jun 2011 22:06:23 -0700
To: John Levine <johnl@iecc.com>, <ietf@ietf.org>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: whine, whine, whine
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 05:09:25 -0000

At 3:52 AM +0000 6/21/11, John Levine wrote:

>  Quebec has been in the exact same location for over 400 years.  It's
>  not like its a secret to anyone who can look at a map.  It may not be
>  as easy to get to as, say, Toronto or Chicago, but (at least from
>  where I live) it's a lot easier to get to than a remote armpit like,
>  oh, San Diego.

San Diego is much easier to get to than Quebec City, since multiple 
air carriers serve it.  Vancouver is a lot better than San Diego 
because it has a number of direct international flights, making it 
much easier still for those from outside North America.  I'd agree 
that San Diego isn't a great location for an IETF, for one reason 
because  we'd have to be at either a hotel too far to walk anywhere 
or in a conference center.

(By the way, BA just resumed non-stop flights between London and San 
Diego, but I discount that because it's only one flight on one 
airline.)

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
2 + 2 = 5 for extremely large values of 2.

From johnl@iecc.com  Mon Jun 20 22:09:51 2011
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 3EB0511E81E4 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 22:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.605
X-Spam-Level: 
X-Spam-Status: No, score=-110.605 tagged_above=-999 required=5 tests=[AWL=0.594, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66rT1Q3RWAtc for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 22:09:49 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id EA1CC11E81AC for <ietf@ietf.org>; Mon, 20 Jun 2011 22:09:48 -0700 (PDT)
Received: (qmail 70890 invoked from network); 21 Jun 2011 05:09:48 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 21 Jun 2011 05:09:48 -0000
Date: 21 Jun 2011 05:09:26 -0000
Message-ID: <20110621050926.15797.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
In-Reply-To: <20110621050413.5F6BA10F4761@drugs.dv.isc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 05:09:51 -0000

>Why is this being discussed here?  Logistics about Quebec and how to
>get there should be discussed on 81attendees.
>
>	https://www.ietf.org/mailman/listinfo/81attendees

The archive link on that page is 404. Has anyone ever posted a
message to that list?


From johnl@iecc.com  Mon Jun 20 22:20:18 2011
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 1F3CE11E8141 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 22:20:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.329
X-Spam-Level: 
X-Spam-Status: No, score=-106.329 tagged_above=-999 required=5 tests=[AWL=-3.730, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y7B9WsFqOrRc for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 22:20:17 -0700 (PDT)
Received: from leila.iecc.com (leila.iecc.com [64.57.183.34]) by ietfa.amsl.com (Postfix) with ESMTP id 5DBA911E8144 for <ietf@ietf.org>; Mon, 20 Jun 2011 22:20:17 -0700 (PDT)
Received: (qmail 61090 invoked by uid 125); 21 Jun 2011 05:20:14 -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:vbr-info:user-agent:cleverness; s=eea1.4e002a0e.k1106; bh=SrIM5LzXzjAfP63m+NV7d1QfcdnGBp0ZV+bJlJ04Y5o=; b=J60NjsmRp+fpzBvdSMSOqCtAL9ixeFm6LhhjxsNWtH2bppjngZ07ZwuDe9Wy/pXegC9/RfcQRnDzRwofXtgeyN5kriHUStR5Rx/n73v08XSFdgUaH4Hv6zR0xp00KHTjqwAVzyuv9UiW5qxW4mxrsE25E1bdtDe9dR0y06r0Cks=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 21 Jun 2011 05:19:52 -0000
Date: 21 Jun 2011 01:20:14 -0400
Message-ID: <alpine.BSF.2.00.1106210119390.16120@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Randall Gellens" <randy@qualcomm.com>
Subject: Re: whine, whine, whine
In-Reply-To: <p0624060dca25d4aa0695@loud.pensive.org>
References: <20110621035220.13199.qmail@joyce.lan> <p0624060dca25d4aa0695@loud.pensive.org>
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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 05:20:18 -0000

> San Diego is much easier to get to than Quebec City, since multiple air 
> carriers serve it.

You can't fool me.  I've been to both.  Quebec is a lot closer, and the 
food is better.

R's,
John

From ietf@thomasclausen.org  Mon Jun 20 22:31:15 2011
Return-Path: <ietf@thomasclausen.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 50DE111E80B6 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 22:31: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U07EAJFc-4NM for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 22:31:14 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob-ipv6.tigertech.net [IPv6:2604:4f00::1:0:0:22]) by ietfa.amsl.com (Postfix) with ESMTP id 7A93611E80B1 for <ietf@ietf.org>; Mon, 20 Jun 2011 22:31:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 6B3DC32465C7; Mon, 20 Jun 2011 22:31:13 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.0.1.5] (sphinx.lix.polytechnique.fr [129.104.11.1]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 1BE9232464AF; Mon, 20 Jun 2011 22:31:11 -0700 (PDT)
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Thomas Heide Clausen <ietf@thomasclausen.org>
In-Reply-To: <8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com>
Date: Tue, 21 Jun 2011 07:31:10 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C9EDB29-0849-464C-B54A-ACF7C77F3A1C@thomasclausen.org>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <4E001776.1020600@net-zen.net> <8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1084)
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, Ole Jacobsen <ole@cisco.com>, ietf@ietf.org, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 05:31:15 -0000

On Jun 21, 2011, at 06:30 , Joel Jaeggli wrote:
> It has been repeated ad-nausieum that "conference rates" subsidize the =
rental of the meeting room block... The fact that the conference rates =
are more expensive ( on a contract signed 24 months out) than a spot =
check of the room rate at any given time should come as no surprise to =
anyone. You can cruise the IETF finances if for some reason you don't =
believe this. If the room block doesn't get filled you can expect your =
fees to go up accordingly over time. I will observe that I have =
generally  not paid the conference rate or stayed in the meeting hotel =
while attending the IETF on my own dime (and have stayed in some rather =
nicer hotels (paris, stockholm, etc) for less money as a result. When I =
attend on behalf my employer I make it clear what we paying for when =
participating.
>=20

Just one additional data-point here.=20

For some of us, getting reimbursed for a higher meeting fee is actually =
a lot easier than getting reimbursed for a higher hotel-fee. Such would =
be the case when, for example, traveling on a fixed per-diem intended =
for covering accommodation/food, but reimbursed on cost for the meeting =
fee.=20

For me, not an eyelid would be bat if I presented a quadruple (or more) =
meeting-fee-bill -- whereas it is a recurring administrative hassle to =
actually get a hotel-bill exceeding the per-diem to pass accounting =
(and, actually quite a lottery each time if it will be reimbursed....)

Not wanting to criticize, but  I would encourage that such situations =
also be considered when making plans for the IETF meeting payment =
structure.

Sincerely yours

Thomas

ps: Other than that, I am actually excited to go to Quebec City which - =
for those who've never been there - is a very very pleasant place to be. =
Also, when there, my French colleagues tend to mock me a whole lot less =
for my accent ;)

> please look at the balance sheet here:
>=20
> http://iaoc.ietf.org/documents/Meeting-Financials-2010-77.pdf
>=20
> and note both the hotel commission, a credit, and the zero charge =
associated with meeting rooms.
>=20
> It's not clear to me that this can be made more transparent, but if =
you'd like to try I'm sure that someone would be happy to nominate you =
for an open iaoc position when available.
>=20
> joel
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From gwz@net-zen.net  Mon Jun 20 23:17:04 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D94D11E80CF for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 23:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.349
X-Spam-Level: 
X-Spam-Status: No, score=-102.349 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, GB_PAYLESS=0.5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d2YmyxgLvq6B for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 23:17:03 -0700 (PDT)
Received: from p3plsmtpa06-05.prod.phx3.secureserver.net (p3plsmtpa06-05.prod.phx3.secureserver.net [173.201.192.106]) by ietfa.amsl.com (Postfix) with SMTP id 4935A11E809D for <ietf@ietf.org>; Mon, 20 Jun 2011 23:17:03 -0700 (PDT)
Received: (qmail 4541 invoked from network); 21 Jun 2011 06:17:02 -0000
Received: from unknown (124.120.86.123) by p3plsmtpa06-05.prod.phx3.secureserver.net (173.201.192.106) with ESMTP; 21 Jun 2011 06:17:02 -0000
Message-ID: <4E003753.50105@net-zen.net>
Date: Tue, 21 Jun 2011 13:16:51 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <4E001776.1020600@net-zen.net> <8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com>
In-Reply-To: <8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------030304020606010502070004"
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, Ole Jacobsen <ole@cisco.com>, Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 06:17:04 -0000

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

On 6/21/2011 11:30 AM, Joel Jaeggli wrote:
...

>> Actually, it seems that the conference rates at IETF hotels are quite
>> predictable: a couple of months ago it was possible to book a room at
>> the QC Hilton for $176 CAD/night _during the IETF meeting_; if you check
>> the Hilton Web site right now, you will find that equivalent rooms at
>> the Hilton the week before the IETF run about $100 less than during the
>> meeting.  It's possible that IETF week marks the transition to high
>> season rates, but in that case why not move the meeting by a week?  This
>> is not an isolated case: in Beijing, rooms at the Shangri-La were
>> significantly cheaper both the week before and the week after the IETF;
>> in Hiroshima, I got a room at the conference hotel the week of the
>> meeting for ~$50/night less than the conference rate by eschewing "free"
>> breakfast.  Admittedly the breakfast in Hiroshima was both tasty and
>> plentiful, but $50?  Not even in Japan.  It seems apparent that the IAOC
>> "negotiators" are wearing signs around their necks during the hotel
>> negotiations; the only question is what is written on the signs.  Is it
>> "I am a moron" or the simple but effective "F*&k Me"
> 
> 
> It has been repeated ad-nausieum that "conference rates" subsidize the rental of the meeting room block... 

So you believe that that is a good way to negotiate?  That could explain
a lot by itself...

The fact that the conference rates are more expensive ( on a contract
signed 24 months out) than a spot check of the room rate at any given
time should come as no surprise to anyone.

Really?  So I should expect to pay less as an individual renting a room
than as a member of a group renting 200?  In what universe does that
make sense?

> You can cruise the IETF finances if for some reason you don't believe this. If the room block doesn't get filled you can expect your fees to go up accordingly over time.


IEEE 802 had that problem; the last time I checked, their "solution" was
to raise the meeting fee ($1000 at the recent meeting in Singapore, for
example, without early-bird discounts) and discount it if one could
prove that they spent at least 1 night in the conference hotel.  Of
course, their excuse was a corrupt meeting arranger who locked them into
exorbitant prices years in advance....

> I will observe that I have generally  not paid the conference rate or stayed in the meeting hotel while attending the IETF on my own dime (and have stayed in some rather nicer hotels (paris, stockholm, etc) for less money as a result. When I attend on behalf my employer I make it clear what we paying for when participating.
> 
> please look at the balance sheet here:
> 
> http://iaoc.ietf.org/documents/Meeting-Financials-2010-77.pdf
> 
> and note both the hotel commission, a credit, and the zero charge associated with meeting rooms.
> 
> It's not clear to me that this can be made more transparent, but if you'd like to try I'm sure that someone would be happy to nominate you for an open iaoc position when available.

Thanks for the non-answer.  My comment had nothing to do with
"transparency", however, and everything to do with competence...I do
wonder what the difference is to us if we pay for the meeting rooms
directly (through meeting fees) or indirectly (through increased room
rates)?

> 
> joel
> 

--------------030304020606010502070004
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------030304020606010502070004--

From moore@network-heretics.com  Mon Jun 20 23:37:41 2011
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 6954811E80CF for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 23:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.391
X-Spam-Level: 
X-Spam-Status: No, score=-3.391 tagged_above=-999 required=5 tests=[AWL=0.208,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zH+rDWw9udpZ for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 23:37:40 -0700 (PDT)
Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id C9C5411E8071 for <ietf@ietf.org>; Mon, 20 Jun 2011 23:37:40 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 64B9F2084C; Tue, 21 Jun 2011 02:37:40 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute4.internal (MEProxy); Tue, 21 Jun 2011 02:37:40 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=NQuNmfoXyToWhKxoDsoh0fJci10=; b=gZn0aF9/VtTrYuDDbzvbmavqy/CQf3Tz88OD0zSyBTqvdE41OPNvAl0Rw6yYpW/y+Wk4GjWaz5Tfn5p8SfDKOOg3XxQW6uR2inmKjtcLRPu2mji3d8AAr66r7GqXEjgd6Irj9MKrmQnqIPkboipjpoVM8oRok8BPuuKAV4uB8+Y=
X-Sasl-enc: 54uYWKu26MLotQxhg3Ktm0Nu1LJMIwkFG41XBZ7Xl+nS 1308638259
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 151CB44597E; Tue, 21 Jun 2011 02:37:38 -0400 (EDT)
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <0C9EDB29-0849-464C-B54A-ACF7C77F3A1C@thomasclausen.org>
Date: Tue, 21 Jun 2011 02:37:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0AB55211-8658-4E68-9C85-8664BE079D98@network-heretics.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <4E001776.1020600@net-zen.net> <8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com> <0C9EDB29-0849-464C-B54A-ACF7C77F3A1C@thomasclausen.org>
To: Thomas Heide Clausen <ietf@thomasclausen.org>
X-Mailer: Apple Mail (2.1084)
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, Ole Jacobsen <ole@cisco.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 Jun 2011 06:37:41 -0000

On Jun 21, 2011, at 1:31 AM, Thomas Heide Clausen wrote:

> On Jun 21, 2011, at 06:30 , Joel Jaeggli wrote:
>> It has been repeated ad-nausieum that "conference rates" subsidize =
the rental of the meeting room block... The fact that the conference =
rates are more expensive ( on a contract signed 24 months out) than a =
spot check of the room rate at any given time should come as no surprise =
to anyone. You can cruise the IETF finances if for some reason you don't =
believe this. If the room block doesn't get filled you can expect your =
fees to go up accordingly over time. I will observe that I have =
generally  not paid the conference rate or stayed in the meeting hotel =
while attending the IETF on my own dime (and have stayed in some rather =
nicer hotels (paris, stockholm, etc) for less money as a result. When I =
attend on behalf my employer I make it clear what we paying for when =
participating.
>>=20
>=20
> Just one additional data-point here.=20
>=20
> For some of us, getting reimbursed for a higher meeting fee is =
actually a lot easier than getting reimbursed for a higher hotel-fee. =
Such would be the case when, for example, traveling on a fixed per-diem =
intended for covering accommodation/food, but reimbursed on cost for the =
meeting fee.=20

Then again, for others of us, staying at a cheaper hotel a short =
distance away is actually a lot easier than paying out the wazoo for an =
overpriced meeting venue.

Keith


From joelja@bogus.com  Mon Jun 20 23:48:18 2011
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 234BC11E8137 for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 23:48:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.955
X-Spam-Level: 
X-Spam-Status: No, score=-101.955 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, GB_PAYLESS=0.5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y0qbs-jbcDNl for <ietf@ietfa.amsl.com>; Mon, 20 Jun 2011 23:48:17 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6D711E8100 for <ietf@ietf.org>; Mon, 20 Jun 2011 23:48:16 -0700 (PDT)
Received: from [192.168.1.171] (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5L6mCNA000520 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 21 Jun 2011 06:48:13 GMT (envelope-from joelja@bogus.com)
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4E003753.50105@net-zen.net>
Date: Mon, 20 Jun 2011 23:48:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <791F5CBE-FFE0-4148-8DE9-01BC64D86E60@bogus.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <4E001776.1020600@net-zen.net> <8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com> <4E003753.50105@net-zen.net>
To: Glen Zorn <gwz@net-zen.net>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 21 Jun 2011 06:48:15 +0000 (UTC)
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, Ole Jacobsen <ole@cisco.com>, Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 06:48:18 -0000

On Jun 20, 2011, at 11:16 PM, Glen Zorn wrote:

> On 6/21/2011 11:30 AM, Joel Jaeggli wrote:
> ...
>=20
>>> Actually, it seems that the conference rates at IETF hotels are =
quite
>>> predictable: a couple of months ago it was possible to book a room =
at
>>> the QC Hilton for $176 CAD/night _during the IETF meeting_; if you =
check
>>> the Hilton Web site right now, you will find that equivalent rooms =
at
>>> the Hilton the week before the IETF run about $100 less than during =
the
>>> meeting.  It's possible that IETF week marks the transition to high
>>> season rates, but in that case why not move the meeting by a week?  =
This
>>> is not an isolated case: in Beijing, rooms at the Shangri-La were
>>> significantly cheaper both the week before and the week after the =
IETF;
>>> in Hiroshima, I got a room at the conference hotel the week of the
>>> meeting for ~$50/night less than the conference rate by eschewing =
"free"
>>> breakfast.  Admittedly the breakfast in Hiroshima was both tasty and
>>> plentiful, but $50?  Not even in Japan.  It seems apparent that the =
IAOC
>>> "negotiators" are wearing signs around their necks during the hotel
>>> negotiations; the only question is what is written on the signs.  Is =
it
>>> "I am a moron" or the simple but effective "F*&k Me"
>>=20
>>=20
>> It has been repeated ad-nausieum that "conference rates" subsidize =
the rental of the meeting room block...=20
>=20
> So you believe that that is a good way to negotiate?  That could =
explain
> a lot by itself...

nope, factual reporting should not be construed as approval.

> The fact that the conference rates are more expensive ( on a contract
> signed 24 months out) than a spot check of the room rate at any given
> time should come as no surprise to anyone.
>=20
> Really?  So I should expect to pay less as an individual renting a =
room
> than as a member of a group renting 200?  In what universe does that
> make sense?

In the universe where you sign a contract with a hotel for use of their =
facilities  two years you are in effect paying a risk premium since you =
a enjoining them from selling the facility out from under you. If you've =
ever entered into a futures contract you might be familiar with this... =
The customer who soaks up unused capacity 3 weeks out will pay less for =
the privledge they may not be able to book a meeting room however...

The feedback that I provided into the IASA when the management of the =
activity moved from CNRI to the IAOC/IAD was that more flexibility on =
dates made it easier to negotiate with hotels  on both fees and the use =
of facilities. The IETF community indicated unequically that meeting =
dates be known as far in advance as feasible, and in particular, the =
dates are fixed considerably ahead of hotel contracts, this does not =
increase your flexibility in negioating.

>> You can cruise the IETF finances if for some reason you don't believe =
this. If the room block doesn't get filled you can expect your fees to =
go up accordingly over time.
>=20
>=20
> IEEE 802 had that problem; the last time I checked, their "solution" =
was
> to raise the meeting fee ($1000 at the recent meeting in Singapore, =
for
> example, without early-bird discounts) and discount it if one could
> prove that they spent at least 1 night in the conference hotel.  Of
> course, their excuse was a corrupt meeting arranger who locked them =
into
> exorbitant prices years in advance....
>=20
>> I will observe that I have generally  not paid the conference rate or =
stayed in the meeting hotel while attending the IETF on my own dime (and =
have stayed in some rather nicer hotels (paris, stockholm, etc) for less =
money as a result. When I attend on behalf my employer I make it clear =
what we paying for when participating.
>>=20
>> please look at the balance sheet here:
>>=20
>> http://iaoc.ietf.org/documents/Meeting-Financials-2010-77.pdf
>>=20
>> and note both the hotel commission, a credit, and the zero charge =
associated with meeting rooms.
>>=20
>> It's not clear to me that this can be made more transparent, but if =
you'd like to try I'm sure that someone would be happy to nominate you =
for an open iaoc position when available.
>=20
> Thanks for the non-answer.  My comment had nothing to do with
> "transparency", however, and everything to do with competence...

Which you are qualified to asses on the basis of you long experience in =
meeting booking...

> I do
> wonder what the difference is to us if we pay for the meeting rooms
> directly (through meeting fees) or indirectly (through increased room
> rates)?
>=20
>>=20
>> joel
>>=20
> <gwz.vcf>


From gwz@net-zen.net  Tue Jun 21 00:00:43 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF71811E80CE for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 00:00:43 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KLVKZoJMetos for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 00:00:43 -0700 (PDT)
Received: from p3plsmtpa01-09.prod.phx3.secureserver.net (p3plsmtpa01-09.prod.phx3.secureserver.net [72.167.82.89]) by ietfa.amsl.com (Postfix) with SMTP id 0BF9511E80A7 for <ietf@ietf.org>; Tue, 21 Jun 2011 00:00:42 -0700 (PDT)
Received: (qmail 19756 invoked from network); 21 Jun 2011 07:00:42 -0000
Received: from unknown (124.120.86.123) by p3plsmtpa01-09.prod.phx3.secureserver.net (72.167.82.89) with ESMTP; 21 Jun 2011 07:00:41 -0000
Message-ID: <4E004191.6000306@net-zen.net>
Date: Tue, 21 Jun 2011 14:00:33 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net>	<4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com>	<alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net>	<4E001776.1020600@net-zen.net>	<8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com> <4E003753.50105@net-zen.net>
In-Reply-To: <4E003753.50105@net-zen.net>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------070000080108050209050006"
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, Ole Jacobsen <ole@cisco.com>, Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 07:00:43 -0000

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

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

On 6/21/2011 1:16 PM, Glen Zorn wrote:

...

>> please look at the balance sheet here:
>>
>> http://iaoc.ietf.org/documents/Meeting-Financials-2010-77.pdf
>>
>> and note both the hotel commission, a credit, and the zero charge associated with meeting rooms.
>>
>> It's not clear to me that this can be made more transparent, but if you'd like to try I'm sure that someone would be happy to nominate you for an open iaoc position when available.
> 
> Thanks for the non-answer.  

It seems that your response was even less responsive than I had thought:
 according to the meeting Web site, the meeting is actually to be held
at the Quebec City Convention Center.  This makes it rather unsurprising
that there is a zero charge associated with meeting rooms at the Hilton
but begs the question: what, exactly, _is_ being subsidized by the extra
~$70/night?

...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOAEGRAAoJEG4XtfZZU7RfVqEH/iUlVjbkKhxRnROzTNZjre69
eNfCpMIeK745Mvme0RyhO+ycApo+x4aWEi36mNB8p1IyIpjLZz65LgBY2TGI7tQN
6Mmv38FYDoJnruEIpjmuuvuAZQyMVzanDHINCsAAk20ytD7zgUPwtCfk91R6gOVW
XnIQxlDBZcHLj+t12PBB8UuXuQ+VyxIaBZWxsM59G5s8uFlMoSgjOomU/vI8lVJR
ouXcUdc5HSPwUITrU+XbfWQxrck3QJoC6WfNAYhkVpEBhxrgcm33uVZOwMH/PKY3
t1A7VErp4u8+QjphPfEy9XEhP08pYQaGufW3vpTmhyXSkXnOSzr2fK6ssbnQpNc=
=aCK6
-----END PGP SIGNATURE-----

--------------070000080108050209050006
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------070000080108050209050006--

From gwz@net-zen.net  Tue Jun 21 00:17:16 2011
Return-Path: <gwz@net-zen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EEAB11E80A7 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 00:17:16 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eiMdmbDjZ7Qt for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 00:17:15 -0700 (PDT)
Received: from p3plsmtpa06-05.prod.phx3.secureserver.net (p3plsmtpa06-05.prod.phx3.secureserver.net [173.201.192.106]) by ietfa.amsl.com (Postfix) with SMTP id 7C29111E80AA for <ietf@ietf.org>; Tue, 21 Jun 2011 00:17:13 -0700 (PDT)
Received: (qmail 26961 invoked from network); 21 Jun 2011 07:10:25 -0000
Received: from unknown (124.120.86.123) by p3plsmtpa06-05.prod.phx3.secureserver.net (173.201.192.106) with ESMTP; 21 Jun 2011 07:10:24 -0000
Message-ID: <4E0043D9.8090000@net-zen.net>
Date: Tue, 21 Jun 2011 14:10:17 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <4E001776.1020600@net-zen.net> <8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com> <4E003753.50105@net-zen.net> <791F5CBE-FFE0-4148-8DE9-01BC64D86E60@bogus.com>
In-Reply-To: <791F5CBE-FFE0-4148-8DE9-01BC64D86E60@bogus.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------000205000801010304030006"
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, Ole Jacobsen <ole@cisco.com>, Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 07:17:16 -0000

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

On 6/21/2011 1:48 PM, Joel Jaeggli wrote:

...

> 
> Which you are qualified to asses on the basis of you long experience in meeting booking...
> 

As a matter of fact, yes.

...

--------------000205000801010304030006
Content-Type: text/x-vcard; charset=utf-8;
 name="gwz.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="gwz.vcf"

begin:vcard
fn:Glen Zorn
n:Zorn;Glen
org:Network Zen
adr:;;;Seattle;WA;;USA
email;internet:gwz@net-zen.net
tel;cell:+66 87 040 4617
note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C  2EE1 6E17 B5F6 5953 B45F 
version:2.1
end:vcard


--------------000205000801010304030006--

From joelja@bogus.com  Tue Jun 21 00:25:40 2011
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 E828911E81AC for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 00:25:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.229
X-Spam-Level: 
X-Spam-Status: No, score=-102.229 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2sj+ZGEJYQzf for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 00:25:40 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 81EF111E80A7 for <ietf@ietf.org>; Tue, 21 Jun 2011 00:25:39 -0700 (PDT)
Received: from [192.168.1.171] (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5L7PXUB001270 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 21 Jun 2011 07:25:34 GMT (envelope-from joelja@bogus.com)
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4E004191.6000306@net-zen.net>
Date: Tue, 21 Jun 2011 00:25:33 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E27D4D2E-B308-471C-8E87-F9A215B62D17@bogus.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net>	<4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com>	<alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net>	<4E001776.1020600@net-zen.net>	<8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com> <4E003753.50105@net-zen.net> <4E004191.6000306@net-zen.net>
To: Glen Zorn <gwz@net-zen.net>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 21 Jun 2011 07:25:38 +0000 (UTC)
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, Ole Jacobsen <ole@cisco.com>, Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 07:25:41 -0000

On Jun 21, 2011, at 12:00 AM, Glen Zorn wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On 6/21/2011 1:16 PM, Glen Zorn wrote:
>=20
> ...
>=20
>>> please look at the balance sheet here:
>>>=20
>>> http://iaoc.ietf.org/documents/Meeting-Financials-2010-77.pdf
>>>=20
>>> and note both the hotel commission, a credit, and the zero charge =
associated with meeting rooms.
>>>=20
>>> It's not clear to me that this can be made more transparent, but if =
you'd like to try I'm sure that someone would be happy to nominate you =
for an open iaoc position when available.
>>=20
>> Thanks for the non-answer. =20
>=20
> It seems that your response was even less responsive than I had =
thought:
> according to the meeting Web site, the meeting is actually to be held
> at the Quebec City Convention Center.  This makes it rather =
unsurprising
> that there is a zero charge associated with meeting rooms at the =
Hilton
> but begs the question: what, exactly, _is_ being subsidized by the =
extra
> ~$70/night?

I'll see the financials the same as everyone else, when they are =
published... it wouldn't shock me if they were similar to another =
canadian city owned  meeting venue which we  visited in 2006 which of =
course you can see here:

http://iaoc.ietf.org/documents/IETF66_Montreal_Financial_Statement.pdf

inclusive of the unbudgeted $2,475 in meeting room expenses.

City owned conference facilties are part and parcel of the fee structure =
of the associated businesses.

>=20
> ...
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>=20
> iQEcBAEBAgAGBQJOAEGRAAoJEG4XtfZZU7RfVqEH/iUlVjbkKhxRnROzTNZjre69
> eNfCpMIeK745Mvme0RyhO+ycApo+x4aWEi36mNB8p1IyIpjLZz65LgBY2TGI7tQN
> 6Mmv38FYDoJnruEIpjmuuvuAZQyMVzanDHINCsAAk20ytD7zgUPwtCfk91R6gOVW
> XnIQxlDBZcHLj+t12PBB8UuXuQ+VyxIaBZWxsM59G5s8uFlMoSgjOomU/vI8lVJR
> ouXcUdc5HSPwUITrU+XbfWQxrck3QJoC6WfNAYhkVpEBhxrgcm33uVZOwMH/PKY3
> t1A7VErp4u8+QjphPfEy9XEhP08pYQaGufW3vpTmhyXSkXnOSzr2fK6ssbnQpNc=3D
> =3DaCK6
> -----END PGP SIGNATURE-----
> <gwz.vcf>


From joelja@bogus.com  Tue Jun 21 01:09:45 2011
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 7135E11E80E6 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 01:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.282
X-Spam-Level: 
X-Spam-Status: No, score=-102.282 tagged_above=-999 required=5 tests=[AWL=0.317, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h3xZkyMfv0rJ for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 01:09:44 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 801E411E807F for <ietf@ietf.org>; Tue, 21 Jun 2011 01:09:44 -0700 (PDT)
Received: from [192.168.1.171] (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5L89QWZ002101 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 21 Jun 2011 08:09:27 GMT (envelope-from joelja@bogus.com)
Subject: Re: location preferences
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <201106210024.p5L0OMpL018975@mtv-core-1.cisco.com>
Date: Tue, 21 Jun 2011 01:09:25 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8AFF051E-C119-47FF-9123-25402EEFD8C3@bogus.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <12629.1308591177@marajade.sandelman.ca> <B7D833155E943151B52610C6@PST.JCK.COM> <BANLkTinPKSx08NaLdshuw8=NRZRMjNsMag@mail.gmail.com> <20110620214720.GH79936@shinkuro.com> <4DFFC210.7090209@dcrocker.net> <201106210024.p5L0OMpL018975@mtv-core-1.cisco.com>
To: "James M. Polk" <jmpolk@cisco.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 21 Jun 2011 08:09:28 +0000 (UTC)
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: Tue, 21 Jun 2011 08:09:45 -0000

On Jun 20, 2011, at 5:24 PM, James M. Polk wrote:
>=20
> rumor has it that IETF65 was supposed to be in New Orleans that =
November, but got hit by a little event called Katrina, so (again - only =
rumors) there had to be a mad scramble to find any hotel that could take =
1400 in 2 months notice.
>=20
> Don't hold Dallas being hit by a freak storm against the city's =
ability to have a decent conference - especially given more time to plan =
which hotel to stay in.
>=20
>> Fortunately, Dallas has a few other choices that are likely to work =
better, along every parameter we care about.
>=20
> yes it does
>=20
> James

Having surveyed three of the downtown dallas venues suitable for a =
meeting the size of the ietf including the one where we did IETF 34 and =
done another meeting in a 4th, there is some horrible network plant in =
several of them among other things. So like all venues there's not a =
unequivocal slam-dunk.=

From lberger@labn.net  Tue Jun 21 04:47:51 2011
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 C995411E80D6 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 04:47:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.198
X-Spam-Level: 
X-Spam-Status: No, score=-102.198 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FVj++BZMQW15 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 04:47:51 -0700 (PDT)
Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id D7A2F11E80D4 for <ietf@ietf.org>; Tue, 21 Jun 2011 04:47:50 -0700 (PDT)
Received: (qmail 24112 invoked by uid 0); 21 Jun 2011 11:47:36 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy7.bluehost.com with SMTP; 21 Jun 2011 11:47:36 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=labn.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=W3ZvcnQcSTZgbpNegrS6B1s02uY4KshPGMUVB8+o5Xx3c6FmL7cWQGfS6jvB4tKl2tGAix7kW9pUtM9iKoaVymEg3479a226IUEggZxJwzZ9doAmY3X8s3d0mUc5amC1;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.69) (envelope-from <lberger@labn.net>) id 1QYzQd-0008B7-RS; Tue, 21 Jun 2011 05:47:36 -0600
Message-ID: <4E0084DD.9070907@labn.net>
Date: Tue, 21 Jun 2011 07:47:41 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Thomas Heide Clausen <ietf@thomasclausen.org>,  Joel Jaeggli <joelja@bogus.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net>	<4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com>	<alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net>	<4E001776.1020600@net-zen.net>	<8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com> <0C9EDB29-0849-464C-B54A-ACF7C77F3A1C@thomasclausen.org>
In-Reply-To: <0C9EDB29-0849-464C-B54A-ACF7C77F3A1C@thomasclausen.org>
X-Enigmail-Version: 1.0.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: Henk Uijterwaal <henk@uijterwaal.nl>, Ole Jacobsen <ole@cisco.com>, ietf@ietf.org, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 11:47:51 -0000

I agree with Thomas, the meeting fees should cover the meetings and the
hotel bill should cover only an individual's room.  This would be more
transparent!

Please feel free to take this as criticism (of the current fee
distribution policy).

Lou

On 6/21/2011 1:31 AM, Thomas Heide Clausen wrote:
> 
> On Jun 21, 2011, at 06:30 , Joel Jaeggli wrote:
>> It has been repeated ad-nausieum that "conference rates" subsidize
>> the rental of the meeting room block... The fact that the
>> conference rates are more expensive ( on a contract signed 24
>> months out) than a spot check of the room rate at any given time
>> should come as no surprise to anyone. You can cruise the IETF
>> finances if for some reason you don't believe this. If the room
>> block doesn't get filled you can expect your fees to go up
>> accordingly over time. I will observe that I have generally  not
>> paid the conference rate or stayed in the meeting hotel while
>> attending the IETF on my own dime (and have stayed in some rather
>> nicer hotels (paris, stockholm, etc) for less money as a result.
>> When I attend on behalf my employer I make it clear what we paying
>> for when participating.
>> 
> 
> Just one additional data-point here.
> 
> For some of us, getting reimbursed for a higher meeting fee is
> actually a lot easier than getting reimbursed for a higher hotel-fee.
> Such would be the case when, for example, traveling on a fixed
> per-diem intended for covering accommodation/food, but reimbursed on
> cost for the meeting fee.
> 
> For me, not an eyelid would be bat if I presented a quadruple (or
> more) meeting-fee-bill -- whereas it is a recurring administrative
> hassle to actually get a hotel-bill exceeding the per-diem to pass
> accounting (and, actually quite a lottery each time if it will be
> reimbursed....)
> 
> Not wanting to criticize, but  I would encourage that such situations
> also be considered when making plans for the IETF meeting payment
> structure.
> 
> Sincerely yours
> 
> Thomas
> 
> ps: Other than that, I am actually excited to go to Quebec City which
> - for those who've never been there - is a very very pleasant place
> to be. Also, when there, my French colleagues tend to mock me a whole
> lot less for my accent ;)
> 
>> please look at the balance sheet here:
>> 
>> http://iaoc.ietf.org/documents/Meeting-Financials-2010-77.pdf
>> 
>> and note both the hotel commission, a credit, and the zero charge
>> associated with meeting rooms.
>> 
>> It's not clear to me that this can be made more transparent, but if
>> you'd like to try I'm sure that someone would be happy to nominate
>> you for an open iaoc position when available.
>> 
>> joel _______________________________________________ Ietf mailing
>> list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
> 
> _______________________________________________ Ietf mailing list 
> Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
> 
> 
> 
> 

From adrian@olddog.co.uk  Tue Jun 21 05:48:12 2011
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 00B709E8022 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 05:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.451
X-Spam-Level: 
X-Spam-Status: No, score=-2.451 tagged_above=-999 required=5 tests=[AWL=0.148,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kS40qugoCvFB for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 05:48:05 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id ADAC09E8014 for <ietf@ietf.org>; Tue, 21 Jun 2011 05:48:04 -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 p5LCl0QW030209;  Tue, 21 Jun 2011 13:47:00 +0100
Received: from 950129200 ([149.254.180.104]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id p5LCku9J030170 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 21 Jun 2011 13:46:58 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Lou Berger'" <lberger@labn.net>, "'Thomas Heide Clausen'" <ietf@thomasclausen.org>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com>	<4DFD90C1.7010903@net-zen.net>	<4DFEA880.6080403@uijterwaal.nl>	<1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com>	<alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net>	<4E001776.1020600@net-zen.net>	<8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com>	<0C9EDB29-0849-464C-B54A-ACF7C77F3A1C@thomasclausen.org> <4E0084DD.9070907@labn.net>
In-Reply-To: <4E0084DD.9070907@labn.net>
Subject: RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
Date: Tue, 21 Jun 2011 13:47:57 +0100
Message-ID: <03ec01cc3011$74301ff0$5c905fd0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: en-gb
Thread-index: AQHeBqpEUC9y0AVO1vy5NLRKbf0mbAH61nfnARZPgv0BupKz5QJQ6s3zArwdJ78B7l5cmgGvIESZAXcnnEuULKgOwA==
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 12:48:12 -0000

+1

And aware this might mean a sizeable hike in meeting fees.

The *only* wrinkle I can see is that it might be considered useful for a hotel
to block out a number of rooms for booking exclusively by IETF participants, and
the hotel might want to increase the price for that service (because it is a
risk for them that they will not sell all the rooms). The counterpart to this is
that we might have to take whatever rooms are available in nearby hotels if the
"IETF" hotel sells out.

But we have to go down this path anyway. An increasing number of IETF
participants are booking their rooms independently, either in the IETF hotels or
in nearby hotels. The result of this would appear to be the distribution of the
meeting room costs across a smaller number of guest rooms leading to still
higher guest room prices. Loop until done.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Lou
> Berger
> Sent: 21 June 2011 12:48
> To: Thomas Heide Clausen; Joel Jaeggli
> Cc: Henk Uijterwaal; Ole Jacobsen; ietf@ietf.org; Keith Moore
> Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
> 
> I agree with Thomas, the meeting fees should cover the meetings and the
> hotel bill should cover only an individual's room.  This would be more
> transparent!
> 
> Please feel free to take this as criticism (of the current fee
> distribution policy).
> 
> Lou
> 
> On 6/21/2011 1:31 AM, Thomas Heide Clausen wrote:
> >
> > On Jun 21, 2011, at 06:30 , Joel Jaeggli wrote:
> >> It has been repeated ad-nausieum that "conference rates" subsidize
> >> the rental of the meeting room block... The fact that the
> >> conference rates are more expensive ( on a contract signed 24
> >> months out) than a spot check of the room rate at any given time
> >> should come as no surprise to anyone. You can cruise the IETF
> >> finances if for some reason you don't believe this. If the room
> >> block doesn't get filled you can expect your fees to go up
> >> accordingly over time. I will observe that I have generally  not
> >> paid the conference rate or stayed in the meeting hotel while
> >> attending the IETF on my own dime (and have stayed in some rather
> >> nicer hotels (paris, stockholm, etc) for less money as a result.
> >> When I attend on behalf my employer I make it clear what we paying
> >> for when participating.
> >>
> >
> > Just one additional data-point here.
> >
> > For some of us, getting reimbursed for a higher meeting fee is
> > actually a lot easier than getting reimbursed for a higher hotel-fee.
> > Such would be the case when, for example, traveling on a fixed
> > per-diem intended for covering accommodation/food, but reimbursed on
> > cost for the meeting fee.
> >
> > For me, not an eyelid would be bat if I presented a quadruple (or
> > more) meeting-fee-bill -- whereas it is a recurring administrative
> > hassle to actually get a hotel-bill exceeding the per-diem to pass
> > accounting (and, actually quite a lottery each time if it will be
> > reimbursed....)
> >
> > Not wanting to criticize, but  I would encourage that such situations
> > also be considered when making plans for the IETF meeting payment
> > structure.
> >
> > Sincerely yours
> >
> > Thomas
> >
> > ps: Other than that, I am actually excited to go to Quebec City which
> > - for those who've never been there - is a very very pleasant place
> > to be. Also, when there, my French colleagues tend to mock me a whole
> > lot less for my accent ;)
> >
> >> please look at the balance sheet here:
> >>
> >> http://iaoc.ietf.org/documents/Meeting-Financials-2010-77.pdf
> >>
> >> and note both the hotel commission, a credit, and the zero charge
> >> associated with meeting rooms.
> >>
> >> It's not clear to me that this can be made more transparent, but if
> >> you'd like to try I'm sure that someone would be happy to nominate
> >> you for an open iaoc position when available.
> >>
> >> joel _______________________________________________ Ietf mailing
> >> list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
> >
> > _______________________________________________ Ietf mailing list
> > Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
> >
> >
> >
> >
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From simon.perreault@viagenie.ca  Tue Jun 21 05:58:14 2011
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73E4B11E8083 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 05:58: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zTy+f0-P82TQ for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 05:58:13 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id AC14D11E80D8 for <ietf@ietf.org>; Tue, 21 Jun 2011 05:58:13 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:21d:60ff:fed7:e732]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 1E13C20D35 for <ietf@ietf.org>; Tue, 21 Jun 2011 08:58:11 -0400 (EDT)
Message-ID: <4E009562.5040905@viagenie.ca>
Date: Tue, 21 Jun 2011 08:58:10 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110320 Fedora/3.1.9-4.fc16 Lightning/1.0b3pre Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: whine, whine, whine
References: <20110621035220.13199.qmail@joyce.lan>
In-Reply-To: <20110621035220.13199.qmail@joyce.lan>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 12:58:14 -0000

On 2011-06-20 23:52, John Levine wrote:
> * There is no usable bus from the airport (it runs only at commuter
>   hours) and a taxi costs C$32.50

You're absolutely right about this. The people of Québec are not happy
about this situation and often complain in the media. It makes for a bad
first impression. We'll try to organize taxi pools somehow, stay tuned
and read 81attendees@ietf.org.

Assuming the others bullets were jokes... ;)

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From simon.perreault@viagenie.ca  Tue Jun 21 06:02:12 2011
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B06811E80D6 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 06:02:12 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xNfvbPgs3zkg for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 06:02:11 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 85CA711E8083 for <ietf@ietf.org>; Tue, 21 Jun 2011 06:02:11 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:21d:60ff:fed7:e732]) by jazz.viagenie.ca (Postfix) with ESMTPSA id E34E520D35 for <ietf@ietf.org>; Tue, 21 Jun 2011 09:02:10 -0400 (EDT)
Message-ID: <4E009652.1020503@viagenie.ca>
Date: Tue, 21 Jun 2011 09:02:10 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110320 Fedora/3.1.9-4.fc16 Lightning/1.0b3pre Thunderbird/3.1.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: whine, whine, whine
References: <20110621035220.13199.qmail@joyce.lan> <p0624060dca25d4aa0695@loud.pensive.org>
In-Reply-To: <p0624060dca25d4aa0695@loud.pensive.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 13:02:12 -0000

On 2011-06-21 01:06, Randall Gellens wrote:
> San Diego is much easier to get to than Quebec City, since multiple air
> carriers serve it.

Not going to argue about "San Diego vs Québec", but just going to point
out that multiple carriers do serve Québec. Among them are Air Canada,
United, Continental, Delta, and US Airways.
See http://ietf81.ca/?page_id=10

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From christer.holmberg@ericsson.com  Tue Jun 21 06:04:59 2011
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9767311E811B for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 06:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.489
X-Spam-Level: 
X-Spam-Status: No, score=-6.489 tagged_above=-999 required=5 tests=[AWL=0.110,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tZorovQ4fhZr for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 06:04:59 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id BB00311E811A for <ietf@ietf.org>; Tue, 21 Jun 2011 06:04:58 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-cc-4e0096f9a944
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 69.09.20773.9F6900E4; Tue, 21 Jun 2011 15:04:57 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.2.138]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Tue, 21 Jun 2011 15:04:57 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Simon Perreault <simon.perreault@viagenie.ca>, "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 21 Jun 2011 15:04:56 +0200
Subject: RE: whine, whine, whine
Thread-Topic: whine, whine, whine
Thread-Index: AcwwEvdHElPK1HnKSPW7TYUA02nYOQAALc4A
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05851DB5336E9F@ESESSCMS0356.eemea.ericsson.se>
References: <20110621035220.13199.qmail@joyce.lan> <4E009562.5040905@viagenie.ca>
In-Reply-To: <4E009562.5040905@viagenie.ca>
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-Brightmail-Tracker: AAAAAA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 13:04:59 -0000

=20
>>* There is no usable bus from the airport (it runs only at commuter
>>   hours) and a taxi costs C$32.50
>=20
>You're absolutely right about this. The people of Qu=E9bec are=20
>not happy about this situation and often complain in the=20
>media. It makes for a bad first impression. We'll try to=20
>organize taxi pools somehow, stay tuned and read 81attendees@ietf.org.
>=20
>Assuming the others bullets were jokes... ;)

One could wish so, but you obviously haven't seen what kind of things peopl=
e use to whine about when it comes to IETF meetings... :)

Regards,

Christer

From Ray.Bellis@nominet.org.uk  Tue Jun 21 06:29:00 2011
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 897A721F843F for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 06:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IksYQCBJ61z6 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 06:28:59 -0700 (PDT)
Received: from mx1.knowthenet.org.uk (mx1.knowthenet.org.uk [213.248.199.2]) by ietfa.amsl.com (Postfix) with ESMTP id 6726321F843E for <ietf@ietf.org>; Tue, 21 Jun 2011 06:28:58 -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:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=z9igWq9hxkGoyCQ+ORz0mzk8kfGZt2tKB7UbmDl6jxannco20wK97/AB 64B7MCt1mNSH2qaTdRbfKvVjefyNCnQ/p4mYK4RIHP2qj9v6//6BLdgu9 VkDQFi2WZbmRCXr;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1308662939; x=1340198939; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20whine,=20whine,=20whine|Date:=20Tue,=20 21=20Jun=202011=2013:28:55=20+0000|Message-ID:=20<EEC3E51 C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk>|To:=20"ietf @ietf.org"=20<ietf@ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |Content-ID:=20<63382331-1bb8-4ec8-b3cf-e68bdda14472> |In-Reply-To:=20<4E009652.1020503@viagenie.ca> |References:=20<20110621035220.13199.qmail@joyce.lan>=0D =0A=20<p0624060dca25d4aa0695@loud.pensive.org>=20<4E00965 2.1020503@viagenie.ca>; bh=qMVceb9z7schJoSqIKgztV2C72zTEZDXXWLnsPRJTH8=; b=krMPvJ2jOIxroLnM/CBXaQ5MIAXxEtdkxPhrHQ6OB0hpYt9nnLjtwE2d W/FNmzq7CZvMZG2Gi994VP1iNutYv6o4+Lg4NKRUbJbiYaLg1JVE53O05 s0UBTCqQbjx3JXT;
X-IronPort-AV: E=Sophos;i="4.65,401,1304290800"; d="scan'208";a="33651476"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx3.nominet.org.uk with ESMTP; 21 Jun 2011 14:28:56 +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%19]) with mapi; Tue, 21 Jun 2011 14:28:56 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: whine, whine, whine
Thread-Topic: whine, whine, whine
Thread-Index: AQHML8ba/QbBneMv0ESHCqHTsduvAJTHMZyAgACE7wCAAAd5gA==
Date: Tue, 21 Jun 2011 13:28:55 +0000
Message-ID: <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk>
References: <20110621035220.13199.qmail@joyce.lan> <p0624060dca25d4aa0695@loud.pensive.org> <4E009652.1020503@viagenie.ca>
In-Reply-To: <4E009652.1020503@viagenie.ca>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <63382331-1bb8-4ec8-b3cf-e68bdda14472>
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, 21 Jun 2011 13:29:00 -0000

On 21 Jun 2011, at 14:02, Simon Perreault wrote:

> Not going to argue about "San Diego vs Qu=E9bec", but just going to point
> out that multiple carriers do serve Qu=E9bec. Among them are Air Canada,
> United, Continental, Delta, and US Airways.

The only European operator into YBQ appears to be Air Transat (whoever the =
heck they are) and they only fly from Marseille and Paris.

I'm flying BA to Montreal and taking the short city hopper flight to YBQ fr=
om there.

Ray



From gregory.cauchie@orange-ftgroup.com  Tue Jun 21 06:39:05 2011
Return-Path: <gregory.cauchie@orange-ftgroup.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEEC711E80C1 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 06:39:05 -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=[BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wejFuj4cHA3V for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 06:39:05 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by ietfa.amsl.com (Postfix) with ESMTP id AE69011E8096 for <ietf@ietf.org>; Tue, 21 Jun 2011 06:39:04 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 96B8DFC4081 for <ietf@ietf.org>; Tue, 21 Jun 2011 15:38:10 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id 3599AFC40B6 for <ietf@ietf.org>; Tue, 21 Jun 2011 15:36:06 +0200 (CEST)
Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 21 Jun 2011 15:36:05 +0200
Received: from [10.193.118.30] ([10.193.118.30]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 21 Jun 2011 15:36:05 +0200
Message-ID: <4E009E44.5030105@orange-ftgroup.com>
Date: Tue, 21 Jun 2011 15:36:04 +0200
From: =?ISO-8859-1?Q?CAUCHIE_Gr=E9gory?= <gregory.cauchie@orange-ftgroup.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: whine, whine, whine
References: <20110621035220.13199.qmail@joyce.lan>	<p0624060dca25d4aa0695@loud.pensive.org> <4E009652.1020503@viagenie.ca> <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk>
In-Reply-To: <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040000090001020209020208"
X-OriginalArrivalTime: 21 Jun 2011 13:36:05.0720 (UTC) FILETIME=[2BAFED80:01CC3018]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gregory.cauchie@orange-ftgroup.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, 21 Jun 2011 13:39:06 -0000

This is a cryptographically signed message in MIME format.

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

Le 21/06/2011 15:28, Ray Bellis a =E9crit :
> On 21 Jun 2011, at 14:02, Simon Perreault wrote:
>> Not going to argue about "San Diego vs Qu=E9bec", but just going to po=
int
>> out that multiple carriers do serve Qu=E9bec. Among them are Air Canad=
a,
>> United, Continental, Delta, and US Airways.
> The only European operator into YBQ appears to be Air Transat (whoever =
the heck they are) and they only fly from Marseille and Paris.

Wikipedia says Air Transat is a Canadian company.
http://en.wikipedia.org/wiki/Air_Transat

> I'm flying BA to Montreal and taking the short city hopper flight to YB=
Q from there.
>
> Ray
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf



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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIOHDCC
BIgwggNwoAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwVDELMAkGA1UEBhMCRlIxFzAVBgNVBAoT
DkZyYW5jZSBUZWxlY29tMRMwEQYDVQQLEwpGVFJELUFzcGljMRcwFQYDVQQDEw5GVFJEIEFD
IFJhY2luZTAeFw0wMjEwMDMwNzE1MjBaFw0xMjEwMDIwNzE1MjBaMFwxCzAJBgNVBAYTAkZS
MRcwFQYDVQQKEw5GcmFuY2UgVGVsZWNvbTETMBEGA1UECxMKRlRSRC1Bc3BpYzEfMB0GA1UE
AxMWRlRSRCBBQyBvcGVyYXRpb25uZWxsZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBAPKErrcyQf+tgRGBsiBQKGGnvheMF+E74XARkkDrNnL/oA5w6e96Nj5eF7TdoiE7AIQR
vOUrJkI9xP74szDUP/CPBPVxxL0855pyoH/qBcgdVCVWBDKGGroc9A5OeXsKCietb1y4+PV5
JeQVw3e41vqJ06Ut81QYPkZ84uJSIiRNoaZG+dBYBOfP8pL3Gj2jnX53eslfdiXjslMk7icb
vcvAuBlzHU/LkLNHZV/iEJGGfj3X8kOMF0e3v1OlAX+TXEYlvA46wnffqVMIgiiFbAHPOBMI
qOMOVQXx2SdokRcpAsHtb8LcaLrSseDf/bmzvhkufp6qYoUoNC9s4g48J9ECAwEAAaOCAVsw
ggFXMBIGA1UdEwEB/wQIMAYBAf8CAQAwHQYDVR0OBBYEFKeHuNCL9G/jwcDa7Y604KcQKfzY
MHwGA1UdIwR1MHOAFLdJ7pNBIn/ZqJeVJz5kZp6uGD8DoVikVjBUMQswCQYDVQQGEwJGUjEX
MBUGA1UEChMORnJhbmNlIFRlbGVjb20xEzARBgNVBAsTCkZUUkQtQXNwaWMxFzAVBgNVBAMT
DkZUUkQgQUMgUmFjaW5lggEAMA4GA1UdDwEB/wQEAwIBBjCBgAYDVR0fBHkwdzA/oD2gO4Y5
aHR0cDovL2x1Y2lmZXIucmQuZnJhbmNldGVsZWNvbS5mci9yZXZvcXVlcy9jcmxyYWNpbmUu
Y3JsMDSgMqAwhi5odHRwOi8vcGtpLWwucmQuZnJhbmNldGVsZWNvbS5mci9jcmxyYWNpbmUu
Y3JsMBEGCWCGSAGG+EIBAQQEAwIABzANBgkqhkiG9w0BAQUFAAOCAQEAto0WYTNPzNN/XrdT
255IwPKbYLZD/YRfQwwcbB4Ff6F9Km+J69KLpZZZx0Z/8rTsjVFc3A2QHTMy4OB2vJ1qPMUO
+JlahqhHbun4GHxM0xl9qzGAaveo5xvIMqHYUnnRZ6s8LadQVbkcHxgw4oPkwRGbKoGyT6WE
dFhWmn4BOBuwURN/JL4LynTkwHEklDbheEyAVTOrJIbZ88rWAKOoSzDhD+Wu/ZVvbcYuYNev
qafJceD1g6rQhaz7O4HnGdmiau3/ayV7ZNDqxnm0Sfli4r4ltTi6GkxmEoT7X1JdKuH0na0Z
dYRoqxRopM8uLsFMOHc46GT7HwsNcqXctRpORDCCBKIwggOKoAMCAQICAwCKZTANBgkqhkiG
9w0BAQUFADBcMQswCQYDVQQGEwJGUjEXMBUGA1UEChMORnJhbmNlIFRlbGVjb20xEzARBgNV
BAsTCkZUUkQtQXNwaWMxHzAdBgNVBAMTFkZUUkQgQUMgb3BlcmF0aW9ubmVsbGUwHhcNMTAw
NzEyMTAzOTI0WhcNMTMwNzExMTAzOTI0WjCBojELMAkGA1UEBhMCRlIxFzAVBgNVBAoTDkZy
YW5jZSBUZWxlY29tMRMwEQYDVQQLEwpGVFJELUFTUElDMRgwFgYDVQQDEw9HcmVnb3J5IENB
VUNISUUxGDAWBgoJkiaJk/IsZAEBEwhHT0lDNzMwMDExMC8GCSqGSIb3DQEJARYiZ3JlZ29y
eS5jYXVjaGllQG9yYW5nZS1mdGdyb3VwLmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkC
gYEAt5FjyQyPyGn4d2i7iP9R6e3V+XWkmLUir7VkVtsyG+/2W/tas6gILdx6NKv30sfWQ3+g
huBF+Pkhxh9qBy3vjLtKysYX1OYlEi3YRfus6MGAWu1+1updfKwQLZpZD5ctp8CYOXGS9F+S
GW3Gf8EB1z+RB6LX2vxNBiN2XUXLz8UCAwEAAaOCAagwggGkMA8GA1UdDwEB/wQFAwMHMAAw
EwYDVR0lBAwwCgYIKwYBBQUHAwQwHQYDVR0OBBYEFBAt5fHNt/+8hqAE+aZD4e4TEHOWMGMG
A1UdIwRcMFqAFKeHuNCL9G/jwcDa7Y604KcQKfzYoT+BPUM9RlIsTz1GcmFuY2UgVGVsZWNv
bSxPVT1GVFJELUFzcGljLENOPUZUUkQgQUMgb3BlcmF0aW9ubmVsbGWCAQEwgZIGA1UdHwSB
ijCBhzBHoEWgQ4ZBaHR0cDovL2x1Y2lmZXIucmQuZnJhbmNldGVsZWNvbS5mci9yZXZvcXVl
cy9jcmxvcGVyYXRpb25uZWxsZS5jcmwwPKA6oDiGNmh0dHA6Ly9wa2ktbC5yZC5mcmFuY2V0
ZWxlY29tLmZyL2NybG9wZXJhdGlvbm5lbGxlLmNybDARBglghkgBhvhCAQEEBAMCBSAwUAYD
VR0RBEkwR4EiZ3JlZ29yeS5jYXVjaGllQG9yYW5nZS1mdGdyb3VwLmNvbYEhZ3JlZ29yeS5j
YXVjaGllQGZyYW5jZXRlbGVjb20uY29tMA0GCSqGSIb3DQEBBQUAA4IBAQDEYI80Q1FsKFpy
0P7ugRdyAyrkpi38t0rcktZvM9mL3LL4GYSEn7QeZZdVz/iYiA+eCtQkQQL9HZTV2U+5ehn/
Lhb9AnUfdj9LeF4HuEjsulPiTJdtIJPAyskNPi+Q7RC5prJadXJ48LIQa9OXZF8R9oHs70/P
Q/+r6GuAAS3+Ywzx8mS1HKHsMKW/WwrSUnh257UXLF++yfz5g0bjaJrEqDXXVxFBKwP76lYk
FS2nDWLNceqtFlt4UlQ2rP112C+gW+qmmidKYZYdxj5KOtV1MB6h0euQrrpfI8Eiiaxlkrtd
qyUckSCFke9tgd99FVZcvoPrvCf2SolNot1Dk4ExMIIE5jCCA86gAwIBAgIDAIpkMA0GCSqG
SIb3DQEBBQUAMFwxCzAJBgNVBAYTAkZSMRcwFQYDVQQKEw5GcmFuY2UgVGVsZWNvbTETMBEG
A1UECxMKRlRSRC1Bc3BpYzEfMB0GA1UEAxMWRlRSRCBBQyBvcGVyYXRpb25uZWxsZTAeFw0x
MDA3MTIxMDM5MjRaFw0xMzA3MTExMDM5MjRaMIGiMQswCQYDVQQGEwJGUjEXMBUGA1UEChMO
RnJhbmNlIFRlbGVjb20xEzARBgNVBAsTCkZUUkQtQVNQSUMxGDAWBgNVBAMTD0dyZWdvcnkg
Q0FVQ0hJRTEYMBYGCgmSJomT8ixkAQETCEdPSUM3MzAwMTEwLwYJKoZIhvcNAQkBFiJncmVn
b3J5LmNhdWNoaWVAb3JhbmdlLWZ0Z3JvdXAuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB
iQKBgQDWbC6qSGTDAlz7mVMPpr6JRIu058v6o2jnKOmqSNoMxMikiqRbXGNXZpaK5muLSWSe
nn+teWuIfm4alQNgvSATFF0uvmxqSysTpdAGVsjiHJLzXmrQXK5y6BCSyyT3iixopWPMvUK1
JqhMdGkBvfUtlRdzlSXSsSoVfLUFR2tvcwIDAQABo4IB7DCCAegwDwYDVR0PAQH/BAUDAwfA
ADApBgNVHSUEIjAgBggrBgEFBQcDAgYIKwYBBQUHAwQGCisGAQQBgjcUAgIwHQYDVR0OBBYE
FLurIHxEuJvLQPzIXhWcUyrFt+jUMGMGA1UdIwRcMFqAFKeHuNCL9G/jwcDa7Y604KcQKfzY
oT+BPUM9RlIsTz1GcmFuY2UgVGVsZWNvbSxPVT1GVFJELUFzcGljLENOPUZUUkQgQUMgb3Bl
cmF0aW9ubmVsbGWCAQEwgZIGA1UdHwSBijCBhzBHoEWgQ4ZBaHR0cDovL2x1Y2lmZXIucmQu
ZnJhbmNldGVsZWNvbS5mci9yZXZvcXVlcy9jcmxvcGVyYXRpb25uZWxsZS5jcmwwPKA6oDiG
Nmh0dHA6Ly9wa2ktbC5yZC5mcmFuY2V0ZWxlY29tLmZyL2NybG9wZXJhdGlvbm5lbGxlLmNy
bDARBglghkgBhvhCAQEEBAMCBaAwfgYDVR0RBHcwdaAsBgorBgEEAYI3FAIDoB4MHGdvaWM3
MzAwQHJkLmZyYW5jZXRlbGVjb20uZnKBImdyZWdvcnkuY2F1Y2hpZUBvcmFuZ2UtZnRncm91
cC5jb22BIWdyZWdvcnkuY2F1Y2hpZUBmcmFuY2V0ZWxlY29tLmNvbTANBgkqhkiG9w0BAQUF
AAOCAQEAMjStlnSNuwD+8rrhh2x/MUitjMWsaZlkIw1K2TDhxlS8JVF+aY/Cls0fbdcQsw/J
zrSFlzHC5cBqHyXvlTtj5cCva0/zlDTBhr+eDuyibyHxBYFvKVM37esX0d1ogl6Iwt1Lh3Yx
houNe+5Krpd9NdSUMwX1oO+9VCO8I9cscCHGwTT5Yst8/RFdphZZo2JVVxdLBw6Wn9dNQUf7
Vpx8P1Dt5TRwkU+ByvIOCIGxbBvn8vGng0melSrRrccAKmFI1T5J122ewdaifQRDyd5N6T0a
k0el5dKIs1Arxh+UpOpLFIv39VJqwoQ1t2XL7fduu7HBEnEwfoQt+PJnyfDcLTGCArUwggKx
AgEBMGMwXDELMAkGA1UEBhMCRlIxFzAVBgNVBAoTDkZyYW5jZSBUZWxlY29tMRMwEQYDVQQL
EwpGVFJELUFzcGljMR8wHQYDVQQDExZGVFJEIEFDIG9wZXJhdGlvbm5lbGxlAgMAimQwCQYF
Kw4DAhoFAKCCAagwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTEwNjIxMTMzNjA0WjAjBgkqhkiG9w0BCQQxFgQUCj5e9CZKDqLwljVYPP9LRCmDKpkwXwYJ
KoZIhvcNAQkPMVIwUDALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA
MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMHIGCSsGAQQBgjcQBDFl
MGMwXDELMAkGA1UEBhMCRlIxFzAVBgNVBAoTDkZyYW5jZSBUZWxlY29tMRMwEQYDVQQLEwpG
VFJELUFzcGljMR8wHQYDVQQDExZGVFJEIEFDIG9wZXJhdGlvbm5lbGxlAgMAimUwdAYLKoZI
hvcNAQkQAgsxZaBjMFwxCzAJBgNVBAYTAkZSMRcwFQYDVQQKEw5GcmFuY2UgVGVsZWNvbTET
MBEGA1UECxMKRlRSRC1Bc3BpYzEfMB0GA1UEAxMWRlRSRCBBQyBvcGVyYXRpb25uZWxsZQID
AIplMA0GCSqGSIb3DQEBAQUABIGARUrG/q4OlEF/DIDkhYw1uaFQ0+PW+cWmV6w3ly7SmOwg
aH3HlmEA4V0IRWM4dBPOZx8GkKpiwra872l/74D8pqhtVSM2kkUf4mtFYFfxza0Zt/xBr7H+
kCF1uGxujjY50T0uRaycgz6gk1Xe0S6EEqkZbLMKRyMThbsaZdfpd4EAAAAAAAA=
--------------ms040000090001020209020208--

From tjc@ecs.soton.ac.uk  Tue Jun 21 06:39:22 2011
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 6E14411E8121 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 06:39:22 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FUrsBdErPibw for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 06:39:14 -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 2C5F011E8113 for <ietf@ietf.org>; Tue, 21 Jun 2011 06:39:12 -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 p5LDd9cm031374 for <ietf@ietf.org>; Tue, 21 Jun 2011 14:39:09 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p5LDd9cm031374
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1308663549; bh=u5in4Vcyz5bUwIS9EhJwH5RX7eQ=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=VoyZxKKNlrkSBLai3XC4gxW9mjS6l1oOs5/Upj9YH309FE1G1jmYnP4eE6COQSPzO fhQD8m4rJg4ezK9VI3RQki48WhGBrdiU0h/XSYIqOG9pEQcftkXH5G2EGxTFazckt2 kAVbd1URclgE6wYJ7eshkpbBdQMlORA2iqE2TJ7c=
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 id n5KEd90366123113yD ret-id none; Tue, 21 Jun 2011 14:39:09 +0100
Received: from dhcp-guest-bdlk09-144-254-102-23.cisco.com (dhcp-guest-bdlk09-144-254-102-23.cisco.com [144.254.102.23]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p5LDbo9w001955 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 21 Jun 2011 14:37:50 +0100
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: whine, whine, whine
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk>
Date: Tue, 21 Jun 2011 14:37:50 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|3b077d68481fdabb154f8635f6d67189n5KEd903tjc|ecs.soton.ac.uk|0D30D2D8-773E-4083-AF28-3ED0411FD4B7@ecs.soton.ac.uk>
References: <20110621035220.13199.qmail@joyce.lan> <p0624060dca25d4aa0695@loud.pensive.org> <4E009652.1020503@viagenie.ca> <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk> <0D30D2D8-773E-4083-AF28-3ED0411FD4B7@ecs.soton.ac.uk>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n5KEd9036612311300; tid=n5KEd90366123113yD; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p5LDd9cm031374
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 13:39:22 -0000

On 21 Jun 2011, at 14:28, Ray Bellis wrote:

>=20
> On 21 Jun 2011, at 14:02, Simon Perreault wrote:
>=20
>> Not going to argue about "San Diego vs Qu=E9bec", but just going to =
point
>> out that multiple carriers do serve Qu=E9bec. Among them are Air =
Canada,
>> United, Continental, Delta, and US Airways.
>=20
> The only European operator into YBQ appears to be Air Transat (whoever =
the heck they are) and they only fly from Marseille and Paris.
>=20
> I'm flying BA to Montreal and taking the short city hopper flight to =
YBQ from there.

For a single operator trip from the UK to Quebec City, there's Air =
Canada out of Heathrow.   You can go via Montreal or other cities.

Tim=

From johnl@iecc.com  Tue Jun 21 07:14:44 2011
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 A913D11E815A for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 07:14:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.485
X-Spam-Level: 
X-Spam-Status: No, score=-110.485 tagged_above=-999 required=5 tests=[AWL=0.714, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RhMOpi-T8KmC for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 07:14:44 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id C8F7911E8149 for <ietf@ietf.org>; Tue, 21 Jun 2011 07:14:41 -0700 (PDT)
Received: (qmail 64339 invoked from network); 21 Jun 2011 14:14:39 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 21 Jun 2011 14:14:39 -0000
Date: 21 Jun 2011 14:14:17 -0000
Message-ID: <20110621141417.2124.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: whine, whine, whine
In-Reply-To: <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 14:14:45 -0000

>The only European operator into YQB appears to be Air Transat (whoever
>the heck they are) and they only fly from Marseille and Paris.

Air Transat is a Montreal-based quasi-charter carrier that specialize
in holiday travel.  Their A330s have kneecap killing 31" seat pitch so
I would only fly them if I had a premium seat or at least a guaranteed
exit row.  But their fares are often quite cheap.

R's,
John

From Ray.Bellis@nominet.org.uk  Tue Jun 21 07:19:46 2011
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 3D35711E80AC for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 07:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level: 
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OQJPO5MfZTEp for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 07:19:45 -0700 (PDT)
Received: from mx4.nominet.org.uk (mail.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id 4D35B11E8082 for <ietf@ietf.org>; Tue, 21 Jun 2011 07:19:44 -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:Content-Type: MIME-Version; b=XMzAG6TuJ4sHsU4tvo4gkw+uPg9aQj0EVcNPcTL9QXGWKMFJ/4HQuGQT s5KV0Tl5VRNSe8uyOQLjyAsuEwlShWOTwqMrx8X4BXTZLZqYrSCBQaA6g vRgqRW4ysdwN/ev;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1308665985; x=1340201985; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20whine,=20whine,=20whine|Date:=20Tue,=20 21=20Jun=202011=2014:19:41=20+0000|Message-ID:=20<5841ACC 8-E24E-4FD6-8714-FE941EF069C8@nominet.org.uk>|To:=20Tim =20Chown=20<tjc@ecs.soton.ac.uk>|CC:=20"<ietf@ietf.org>" =20<ietf@ietf.org>|MIME-Version:=201.0|In-Reply-To:=20<EM EW3=7C3b077d68481fdabb154f8635f6d67189n5KEd903tjc=7Cecs.s oton.ac.uk=7C0D30D2D8-773E-4083-AF28-3ED0411FD4B7@ecs.sot on.ac.uk>|References:=20<20110621035220.13199.qmail@joyce .lan>=0D=0A=20<p0624060dca25d4aa0695@loud.pensive.org>=20 <4E009652.1020503@viagenie.ca>=0D=0A=20<EEC3E51C-E295-4A6 D-935D-1D4346F222B6@nominet.org.uk>=0D=0A=20<0D30D2D8-773 E-4083-AF28-3ED0411FD4B7@ecs.soton.ac.uk>=0D=0A=20<EMEW3 =7C3b077d68481fdabb154f8635f6d67189n5KEd903tjc=7Cecs.soto n.ac.uk=7C0D30D2D8-773E-4083-AF28-3ED0411FD4B7@ecs.soton. ac.uk>; bh=Yco7v0is1jHkimCEnNT8+D6TA+vl2fDnfDKMxTPqN0g=; b=P9WJBri90wdXGrH2l2Kh4TFd0Otej3zj1cOC0ixoreXF7cwrr5PDnnHE GXbK1YOI47/IuEAPP1wnpySqKIJEU9Yb48m/XiJAEneCGq8pnNvB9ZzMs NLssCIIbidZNNRc;
X-IronPort-AV: E=Sophos;i="4.65,401,1304290800"; d="scan'208,217";a="26924450"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx4.nominet.org.uk with ESMTP; 21 Jun 2011 15:19:43 +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%19]) with mapi; Tue, 21 Jun 2011 15:19:43 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: whine, whine, whine
Thread-Topic: whine, whine, whine
Thread-Index: AQHML8ba/QbBneMv0ESHCqHTsduvAJTHMZyAgACE7wCAAAd5gIAAAn4AgAALsYA=
Date: Tue, 21 Jun 2011 14:19:41 +0000
Message-ID: <5841ACC8-E24E-4FD6-8714-FE941EF069C8@nominet.org.uk>
References: <20110621035220.13199.qmail@joyce.lan> <p0624060dca25d4aa0695@loud.pensive.org> <4E009652.1020503@viagenie.ca> <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk> <0D30D2D8-773E-4083-AF28-3ED0411FD4B7@ecs.soton.ac.uk> <EMEW3|3b077d68481fdabb154f8635f6d67189n5KEd903tjc|ecs.soton.ac.uk|0D30D2D8-773E-4083-AF28-3ED0411FD4B7@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|3b077d68481fdabb154f8635f6d67189n5KEd903tjc|ecs.soton.ac.uk|0D30D2D8-773E-4083-AF28-3ED0411FD4B7@ecs.soton.ac.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_5841ACC8E24E4FD68714FE941EF069C8nominetorguk_"
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 14:19:46 -0000

--_000_5841ACC8E24E4FD68714FE941EF069C8nominetorguk_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


On 21 Jun 2011, at 14:37, Tim Chown wrote:

For a single operator trip from the UK to Quebec City, there's Air Canada o=
ut of Heathrow.   You can go via Montreal or other cities.

I seem to recall that it was actually somewhat cheaper to fly BA.  Although=
 I didn't check economy class...

Ray


--_000_5841ACC8E24E4FD68714FE941EF069C8nominetorguk_
Content-Type: text/html; charset="us-ascii"
Content-ID: <76aab1b6-f1b3-41b4-a12b-d0915e842e5b>
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -we=
bkit-line-break: after-white-space; "><br><div><div>On 21 Jun 2011, at 14:3=
7, Tim Chown wrote:</div><blockquote type=3D"cite"><div><font class=3D"Appl=
e-style-span" color=3D"#000000"><br></font>For a single operator trip from =
the UK to Quebec City, there's Air Canada out of Heathrow. &nbsp;&nbsp;You =
can go via Montreal or other cities.<br></div></blockquote></div><br><div>I=
 seem to recall that it was actually somewhat cheaper to fly BA. &nbsp;Alth=
ough I didn't check economy class...</div><div><br></div><div>Ray</div><div=
><br></div></body></html>=

--_000_5841ACC8E24E4FD68714FE941EF069C8nominetorguk_--

From lear@cisco.com  Tue Jun 21 07:41:06 2011
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 A840911E8180 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 07:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.561
X-Spam-Level: 
X-Spam-Status: No, score=-110.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5gpc8xajf-mz for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 07:41:06 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id DF42A11E8185 for <ietf@ietf.org>; Tue, 21 Jun 2011 07:41:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=290; q=dns/txt; s=iport; t=1308667266; x=1309876866; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=jqFcJ4pFdTWId3AZREXVlz6SHGOW29LPzXAoQXMwnl0=; b=Hn/ZrEivrrazezFSrWkjz0ofKZLV+0Vs/Fm9BFnkOd6PTFwUSehmmdy5 W0FV3KuqaM7wr+JGyAs6ZDYSqrZb6sfCYD5/tMLUjFfZYRNN4UclqIfiO p380c51bDtM2LG27ybCjV8r8LuAwa2CWpnt/4G+rmVQKzhwwMJa6r+ug7 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EACWtAE6Q/khR/2dsb2JhbABUhEmiJ3eqO40skR6BK4N1gQoEkWaQCA
X-IronPort-AV: E=Sophos;i="4.65,401,1304294400"; d="scan'208";a="36647050"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 21 Jun 2011 14:38:57 +0000
Received: from dhcp-10-61-103-204.cisco.com (dhcp-10-61-103-204.cisco.com [10.61.103.204]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p5LEcvne010907; Tue, 21 Jun 2011 14:38:57 GMT
Message-ID: <4E00AD00.9020800@cisco.com>
Date: Tue, 21 Jun 2011 16:38:56 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: "John R. Levine" <johnl@iecc.com>
Subject: Re: whine, whine, whine
References: <20110621035220.13199.qmail@joyce.lan>	<p0624060dca25d4aa0695@loud.pensive.org> <alpine.BSF.2.00.1106210119390.16120@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1106210119390.16120@joyce.lan>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Randall Gellens <randy@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: Tue, 21 Jun 2011 14:41:06 -0000

On 6/21/11 7:20 AM, John R. Levine wrote:
>> San Diego is much easier to get to than Quebec City, since multiple
>> air carriers serve it.
>
> You can't fool me.  I've been to both.  Quebec is a lot closer, and
> the food is better.
>

Hey!  Then you haven't been to DZ Akins!

From dhc2@dcrocker.net  Tue Jun 21 07:42:39 2011
Return-Path: <dhc2@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 DD25C11E8167 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 07:42:39 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F6dLzUOrbHVo for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 07:42:36 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8943711E815A for <ietf@ietf.org>; Tue, 21 Jun 2011 07:42:36 -0700 (PDT)
Received: from [192.168.1.7] (ppp-68-120-198-5.dsl.pltn13.pacbell.net [68.120.198.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p5LEgVw1025615 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 21 Jun 2011 07:42:36 -0700
Message-ID: <4E00ADD4.4000306@dcrocker.net>
Date: Tue, 21 Jun 2011 07:42:28 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: location preferences
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <12629.1308591177@marajade.sandelman.ca> <B7D833155E943151B52610C6@PST.JCK.COM> <BANLkTinPKSx08NaLdshuw8=NRZRMjNsMag@mail.gmail.com> <20110620214720.GH79936@shinkuro.com> <4DFFC210.7090209@dcrocker.net> <201106210024.p5L0OMpL018975@mtv-core-1.cisco.com> <8AFF051E-C119-47FF-9123-25402EEFD8C3@bogus.com>
In-Reply-To: <8AFF051E-C119-47FF-9123-25402EEFD8C3@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 21 Jun 2011 07:42:36 -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, 21 Jun 2011 14:42:40 -0000

Folks,


> Having surveyed three of the downtown dallas venues suitable for a meeting
> the size of the ietf including the one where we did IETF 34 and done another
> meeting in a 4th, there is some horrible network plant in several of them
> among other things. So like all venues there's not a unequivocal slam-dunk.


As long as the IETF community prefers to travel to new venues, each meeting will
run the risk of the unknown and the effort to adapt to it.  We will not get any
of the benefit of a learning curve that accrues from re-visiting venues.

As for Vancouver vs. Quebec City, note that there was a survey.  I believe that
respondents stated a roughly 2:1 preference for Quebec City, primarily along the
lines of liking that it was a new place.  In effect, that said that tourism is a
high priority for IETF attendees.

There is a disconnect between attendees' desire for easy and inexpensive travel
and convenient IETF work environments, versus the desire for "interesting" venues.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From john-ietf@jck.com  Tue Jun 21 07:57:43 2011
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 558B711E8249 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 07:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RAzufD7S6kBk for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 07:57:42 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 53B9111E807E for <ietf@ietf.org>; Tue, 21 Jun 2011 07:57:42 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QZ2Ob-0009iW-Fm; Tue, 21 Jun 2011 10:57:41 -0400
Date: Tue, 21 Jun 2011 10:57:40 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>, ietf@ietf.org
Subject: RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
Message-ID: <E1C29FCBE1F1C0F593934A69@PST.JCK.COM>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134EBC48DE@EXCH-C2.corp.cloudmark.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <12629.1308591177@marajade.sandelman.ca> <B7D833155E943151B52610C6@PST.JCK.COM> <F5833273385BB34F99288B3648C4F06F134EBC48DE@EXCH-C2.corp.cloudmark.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: Tue, 21 Jun 2011 14:57:43 -0000

--On Monday, June 20, 2011 21:26 -0700 "Murray S. Kucherawy"
<msk@cloudmark.com> wrote:

>...
>> Phoenix.  Probably Houston or Fort Worth.  Wellington or
>> somewhere on the South Island that doesn't attract skiers.
> 
> I was going to suggest Las Vegas.  Certainly has adequate
> conference facilities and plenty of room availability these
> days.

For better or worse, there are certain meeting destinations that
are classified as boggles under many corporate travel policies.
A meeting in one of them tends to be one for which it is much
harder to get travel approval, especially in difficult times,
and it may be rejected entirely (often the default except for
sales and marketing types attending major "expositions".

For the US, Vegas almost always tops the list... or to fall
right after meetings on luxury cruise ships (for which there is
special, unfavorable, tax treatment).

Usually, that makes Vegas a bad idea.  Reno is often better, but
sometimes tarred with the same brush.

In the hope of avoiding another long thread, I am not advocating
that sort of policy, nor do I believe it is a good idea.  It may
even be completely irrational to the point of not being a useful
subject for debate.  But it is real and has to be a
consideration if one does not want to exclude classes of
participants.

    john



From klaas@wierenga.net  Tue Jun 21 06:44:10 2011
Return-Path: <klaas@wierenga.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 317A211E8092 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 06:44:10 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Gc-D1rawtGj for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 06:44:09 -0700 (PDT)
Received: from out27-ams.mf.surf.net (out27-ams.mf.surf.net [145.0.1.27]) by ietfa.amsl.com (Postfix) with ESMTP id 5A8B311E8078 for <ietf@ietf.org>; Tue, 21 Jun 2011 06:44:09 -0700 (PDT)
Received: from teletubbie.het.net.je (teletubbie.het.net.je [192.87.110.29]) by outgoing1-ams.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p5LDi7Mu028375 for <ietf@ietf.org>; Tue, 21 Jun 2011 15:44:07 +0200
Received: from 64-103-25-233.cisco.com ([64.103.25.233] helo=macmini.wierenga.net) by teletubbie.het.net.je with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from <klaas@wierenga.net>) id 1QZ1DS-0007WU-TB for ietf@ietf.org; Tue, 21 Jun 2011 15:42:06 +0200
Message-ID: <4E00A026.2080208@wierenga.net>
Date: Tue, 21 Jun 2011 15:44:06 +0200
From: Klaas Wierenga <klaas@wierenga.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: whine, whine, whine
References: <20110621035220.13199.qmail@joyce.lan>	<p0624060dca25d4aa0695@loud.pensive.org> <4E009652.1020503@viagenie.ca> <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk>
In-Reply-To: <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Antivirus: no malware found
X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN)
X-CanIt-Geo: ip=192.87.110.29; country=NL; latitude=52.5000; longitude=5.7500; http://maps.google.com/maps?q=52.5000,5.7500&z=6
X-CanItPRO-Stream: p-out:default (inherits from p:default,base:default)
X-Canit-Stats-ID: 0uEWBI71k - d617d1900b12 - 20110621 (trained as not-spam)
X-Scanned-By: CanIt (www . roaringpenguin . com) on 145.0.1.27
X-Mailman-Approved-At: Tue, 21 Jun 2011 08:01:14 -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, 21 Jun 2011 13:44:10 -0000

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

On 6/21/11 3:28 PM, Ray Bellis wrote:
> 
> On 21 Jun 2011, at 14:02, Simon Perreault wrote:
> 
>> Not going to argue about "San Diego vs Québec", but just going to point
>> out that multiple carriers do serve Québec. Among them are Air Canada,
>> United, Continental, Delta, and US Airways.
> 
> The only European operator into YBQ appears to be Air Transat (whoever the heck they are) and they only fly from Marseille and Paris.
> 
> I'm flying BA to Montreal and taking the short city hopper flight to YBQ from there.

otoh, not having to go through US immigrations saves you about as much
time as you would have saved with a direct flight, not to mention the
"terrorist until proven innocent" treatment..... ;-)

Klaas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4AoCYACgkQH2Wy/p4XeFIWogCfW2dn+A+anCx0NIILJ6SPAqLx
J9IAn30Txe/eoIzxaF87lgf/sYKFkeG7
=zVIP
-----END PGP SIGNATURE-----

From daedulus@btconnect.com  Tue Jun 21 09:23:49 2011
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 B553311E8160 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 09:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jYvLpncNul8k for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 09:23:47 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr14.btconnect.com [213.123.20.132]) by ietfa.amsl.com (Postfix) with ESMTP id 2708B11E8082 for <ietf@ietf.org>; Tue, 21 Jun 2011 09:23:46 -0700 (PDT)
Received: from host81-156-207-154.range81-156.btcentralplus.com (HELO pc6) ([81.156.207.154]) by c2bthomr14.btconnect.com with SMTP id DHK76594; Tue, 21 Jun 2011 17:23:39 +0100 (BST)
Message-ID: <00eb01cc3026$e0c37c60$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Mary Barnes" <mary.ietf.barnes@gmail.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com><4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl><1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com><alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net><12629.1308591177@marajade.sandelman.ca><B7D833155E943151B52610C6@PST.JCK.COM> <BANLkTinPKSx08NaLdshuw8=NRZRMjNsMag@mail.gmail.com>
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?
Date: Tue, 21 Jun 2011 17:21:17 +0200
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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4E00C58B.00D4, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.6.21.154815:17:7.586, ip=81.156.207.154, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __FRAUD_BODY_WEBMAIL, __URI_NO_PATH, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr14.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0206.4E00C58E.00E4,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: 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: Tue, 21 Jun 2011 16:23:50 -0000

----- Original Message -----
From: "Mary Barnes" <mary.ietf.barnes@gmail.com>
To: "John C Klensin" <john-ietf@jck.com>
Cc: <ietf@ietf.org>
Sent: Monday, June 20, 2011 9:02 PM
Subject: Re: Has anyone found a hotel for Quebec City that isn't exorbitant?


> Exactly.   Given that we spend most of our days in air conditioned meeting
> rooms, Phoenix or Dallas are not bad choices. Dallas is slightly better due
> to air connections.  Houston is not a good choice under any circumstance
> IMHO - I don't think A/C can remove enough humidity to make it comfortable
> in July.
>
> Personally, I have no issue with Minneapolis in November or March - again we
> spend most of the time in meeting rooms, so do we really care that much
> about the weather outside?

Only when it disrupts the football or the baseball:-)

Tom Petch
>
> Mary.
>
> On Mon, Jun 20, 2011 at 1:55 PM, John C Klensin <john-ietf@jck.com> wrote:
>
> >
> >
> > --On Monday, June 20, 2011 13:32 -0400 Michael Richardson
> > <mcr@sandelman.ca> wrote:
> >
> > >...
> > > It's a peak season destination.  We seem to do this a lot.
> > > March would be no better, but early November there would be, I
> > > think, low peak.
> > > What's a non-peak destination for July?
> >
> > Phoenix.  Probably Houston or Fort Worth.  Wellington or
> > somewhere on the South Island that doesn't attract skiers.
> > Amundsen-Scott base: although I doubt that they have adequate
> > conference facilities, yesterday's mean temperature was circa
> > -89F and "daytime" is still several months off.  Other silly
> > suggestions on request (although I don't personally consider
> > some of the first few silly).
> >
> >   john
> >
> >
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> >
>


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


> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From rja.lists@gmail.com  Tue Jun 21 09:28:14 2011
Return-Path: <rja.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 391EA11E816F for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 09:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.072
X-Spam-Level: 
X-Spam-Status: No, score=-3.072 tagged_above=-999 required=5 tests=[AWL=-0.473, BAYES_00=-2.599, GB_AFFORDABLE=1, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X5YLrAldYikM for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 09:28:13 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3047B11E8082 for <ietf@ietf.org>; Tue, 21 Jun 2011 09:28:13 -0700 (PDT)
Received: by qyk9 with SMTP id 9so2683891qyk.10 for <ietf@ietf.org>; Tue, 21 Jun 2011 09:28:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=YVxPbZLx0HVx9OaMx15q+WIUK9pWMuVQPMDdBoVuPOA=; b=UiaZlf0lxQ8p7k+xv20kHP068z9YWIgHe1TvOnNibrK+w4V4NQreX58yQQQgJ+4ezu ZA6ovZauaVjf2fT5okOJIZUxD4/wbsDR8MEm0Ox5B/hutMxxtjNhko+pZoaptFhz/48K +oKuQgPir0QB5QtiPBN2qHTI1A1n+i32M3PgA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=d48YCzC4PG3juEkRw4uqOu5O9bdWoOn0LUvkSkj0fbvIcw4duq/LUn4c8JgJ/xeND1 Bt0UyIEm8dNlJ9o8WkeHj23tfqZ/KeQTRpBd/5+In2g82tyChu1tdiTAsvCZ0RZUrTs+ rJU/MWjKAl8/QdwwFm8bW2h67yhAa/WKf/LC8=
Received: by 10.224.215.134 with SMTP id he6mr5000240qab.369.1308673692623; Tue, 21 Jun 2011 09:28:12 -0700 (PDT)
Received: from [10.30.20.12] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id t21sm3303408qcs.2.2011.06.21.09.28.11 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Jun 2011 09:28:11 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: whine, whine, whine
Date: Tue, 21 Jun 2011 12:28:10 -0400
Message-Id: <6AE6B3DE-4A62-40B3-AEDC-2E70340B96F7@gmail.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 16:28:14 -0000

Earlier, Ray Bellis wrote:
> The only ... operator into YBQ appears to be Air Transat 
> (whoever the heck they are) and they only fly from Marseille and Paris.

I have been told that Air Transat lacks the many comforts,
low & fully-disclosed fees, and general friendliness of Ryan Air.
I've never flown Air Transat, so perhaps those reports are 
exaggerated.


Earlier, John Levine wrote:
> Their A330s have kneecap killing 31" seat pitch so I would
> only fly them if I had a premium seat or at least a guaranteed 
> exit row.  

If one believes the information available online at SeatExpert.com
or SeatGuru.com, a 31" seat pitch in ordinary Economy cabins is 
not unusual for an overseas flight on a wide range of airlines 
(e.g. AA, BA, KL, LH), depending upon aircraft type, by the way.  

Not all aircraft seats with a given pitch are equally comfortable.
Also, many people opt for various forms of "Premium Economy" 
or select particular aircraft types/configurations -- precisely 
because they prefer more leg room. 


Earlier, Klaas Wierenga wrote:
> otoh, not having to go through US immigrations saves you about
> as much time as you would have saved with a direct flight,
> not to mention the "terrorist until proven innocent" treatment. ;-)

I agree that minimising the set of security-checks and
immigration-steps is desirable for most travel these days.  

[ For my own part, I share the weariness of the "terrorist 
  until proven innocent" treatment -- that I routinely receive 
  at Heathrow, Frankfurt, and a range of other airports
  (Singapore being a notable exception).  :-]


Cheers,

Ran


PS: Singapore would make a great future A/P region meeting
    venue.  It has outstanding international air connectivity, 
    a wide range of hotel options, outstanding (and affordable) food,
    consistently pleasant weather, and consistently friendly
    and helpful local people. :-)



From msk@cloudmark.com  Tue Jun 21 10:23:13 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C03D11E80A6 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 10:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.109
X-Spam-Level: 
X-Spam-Status: No, score=-103.109 tagged_above=-999 required=5 tests=[AWL=-0.510, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N0KZuvMl-Hhd for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 10:23:12 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id B4BDC11E80B0 for <ietf@ietf.org>; Tue, 21 Jun 2011 10:23:12 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Tue, 21 Jun 2011 10:22:51 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 21 Jun 2011 10:22:50 -0700
Subject: RE: whine, whine, whine
Thread-Topic: whine, whine, whine
Thread-Index: AQHML8ba/QbBneMv0ESHCqHTsduvAJTHMZyAgACE7wCAAAd5gIAAUejw
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC48E7@EXCH-C2.corp.cloudmark.com>
References: <20110621035220.13199.qmail@joyce.lan> <p0624060dca25d4aa0695@loud.pensive.org> <4E009652.1020503@viagenie.ca> <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk>
In-Reply-To: <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 17:23:13 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of R=
ay Bellis
> Sent: Tuesday, June 21, 2011 6:29 AM
> To: ietf@ietf.org
> Subject: Re: whine, whine, whine
>=20
> The only European operator into YBQ appears to be Air Transat (whoever
> the heck they are) and they only fly from Marseille and Paris.

They're actually a lesser-known Canadian airline, based out of Montreal.


From msk@cloudmark.com  Tue Jun 21 10:34:36 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB16F11E8245 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 10:34:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.585
X-Spam-Level: 
X-Spam-Status: No, score=-103.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJUiCjTcG+bt for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 10:34:36 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 873F511E81BD for <ietf@ietf.org>; Tue, 21 Jun 2011 10:34:36 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Tue, 21 Jun 2011 10:34:35 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 21 Jun 2011 10:34:34 -0700
Subject: RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Topic: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Index: AcwwI5YOrqnAzrN5RpuFrlr5Bx1cfQAFZ5Dg
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC48E9@EXCH-C2.corp.cloudmark.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net> <4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <12629.1308591177@marajade.sandelman.ca> <B7D833155E943151B52610C6@PST.JCK.COM> <F5833273385BB34F99288B3648C4F06F134EBC48DE@EXCH-C2.corp.cloudmark.com> <E1C29FCBE1F1C0F593934A69@PST.JCK.COM>
In-Reply-To: <E1C29FCBE1F1C0F593934A69@PST.JCK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 17:34:37 -0000

> -----Original Message-----
> From: John C Klensin [mailto:john-ietf@jck.com]
> Sent: Tuesday, June 21, 2011 7:58 AM
> To: Murray S. Kucherawy; ietf@ietf.org
> Subject: RE: Has anyone found a hotel for Quebec City that isn't exorbita=
nt?
>=20
> For better or worse, there are certain meeting destinations that
> are classified as boggles under many corporate travel policies.
> A meeting in one of them tends to be one for which it is much
> harder to get travel approval, especially in difficult times,
> and it may be rejected entirely (often the default except for
> sales and marketing types attending major "expositions".
>=20
> For the US, Vegas almost always tops the list... or to fall
> right after meetings on luxury cruise ships (for which there is
> special, unfavorable, tax treatment).
>=20
> Usually, that makes Vegas a bad idea.  Reno is often better, but
> sometimes tarred with the same brush.

That's probably generally true, but I've had less-to-no trouble getting Las=
 Vegas approval the few times I've needed to recently because the cost is s=
o low these days.  It's reeling from a depressed economy, so cheap but good=
 rooms are readily available as are conference facilities and air fares, an=
d prices of things like food are down a bit to match.

I'm sure though that this audience would just complain about the heat and n=
oise anyway.

From msk@cloudmark.com  Tue Jun 21 11:07:09 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E76D11E8145 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 11:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.585
X-Spam-Level: 
X-Spam-Status: No, score=-103.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9nkUAlXIafTc for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 11:07:09 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 0322811E8114 for <ietf@ietf.org>; Tue, 21 Jun 2011 11:07:09 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Tue, 21 Jun 2011 11:07:08 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 21 Jun 2011 11:07:07 -0700
Subject: RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Topic: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Index: Acwv41wdttSxr05rQQis8cuI448F1wAVUBGw
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC48F2@EXCH-C2.corp.cloudmark.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net>	<4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <4E001776.1020600@net-zen.net> <8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com> <4E003753.50105@net-zen.net> <791F5CBE-FFE0-4148-8DE9-01BC64D86E60@bogus.com> <4E0043D9.8090000@net-zen.net>
In-Reply-To: <4E0043D9.8090000@net-zen.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 18:07:09 -0000

I'm pretty amazed at the angry tone in this thread.

Are you sound-and-fury types willing to roll up your sleeves and actually h=
elp the IAOC do a better job, or perhaps join the NomCom to ensure selectio=
n of people that can, or is this just capitalizing on the fact that's easy =
to be antagonistic on a mailing list?

Or perhaps to satisfy the repeatedly-asserted requirements of relatively in=
expensive, low crime, caters to all kinds of dietary needs and restrictions=
, doesn't use glass for water bottles, exceptionally powerful air purifiers=
 to accommodate smokers and non-smokers alike, outstanding yet cheap food w=
ith plenty of cookies, isn't too hot or too cold and has few immigration pr=
oblems, you think the IAOC should direct AMS to construct a moderate island=
-meeting-venue off the coast of San Diego in international waters with its =
own state-of-the-art airport and airline operating nothing but high-speed t=
urbulence-avoiding extra-comfort Airbus A380s to all other major world hubs=
, fully insured, and all future meetings will be held there, magically at l=
ittle or no cost to us.  For those who like variety, this island Utopia can=
 be made relocatable, giving it 3-4 months to reach its next position after=
 we all leave.

As that's probably impractical, do we think we could maybe take it down a n=
otch?


From dworley@avaya.com  Tue Jun 21 13:23:08 2011
Return-Path: <dworley@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 75EB711E80E0 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 13:23:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.955
X-Spam-Level: 
X-Spam-Status: No, score=-102.955 tagged_above=-999 required=5 tests=[AWL=-0.356, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id id9xmsQgfwB3 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 13:23:07 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id CAC1F11E80DA for <ietf@ietf.org>; Tue, 21 Jun 2011 13:23:07 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EABf9AE6HCzI1/2dsb2JhbABUpnt3iHOjdwKbXoYqBJZliyM
X-IronPort-AV: E=Sophos;i="4.65,402,1304308800"; d="scan'208";a="194545287"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 21 Jun 2011 16:23:06 -0400
X-IronPort-AV: E=Sophos;i="4.65,402,1304308800"; d="scan'208";a="668598792"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 21 Jun 2011 16:23:06 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Tue, 21 Jun 2011 16:23:06 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Thomas Heide Clausen <ietf@thomasclausen.org>, Joel Jaeggli <joelja@bogus.com>
Date: Tue, 21 Jun 2011 16:23:04 -0400
Subject: RE: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Topic: Has anyone found a hotel for Quebec City that isn't exorbitant?
Thread-Index: Acwv1Hm74TrQrKJTTtWdkwLLyCDpsgAe1INy
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F56D4@DC-US1MBEX4.global.avaya.com>
References: <98C69027-EC6D-48AC-A5E5-F801DB2467D6@network-heretics.com> <4DFD90C1.7010903@net-zen.net>	<4DFEA880.6080403@uijterwaal.nl> <1CF475CC-293E-4EC2-8CD6-BC9C340B3907@network-heretics.com> <alpine.OSX.2.01.1106200946570.70611@173-11-110-132-sfba.hfc.comcastbusiness.net> <4E001776.1020600@net-zen.net> <8423C6E6-6E2E-4C07-83F2-8F6FEBEBC3AC@bogus.com>, <0C9EDB29-0849-464C-B54A-ACF7C77F3A1C@thomasclausen.org>
In-Reply-To: <0C9EDB29-0849-464C-B54A-ACF7C77F3A1C@thomasclausen.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Henk Uijterwaal <henk@uijterwaal.nl>, Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2011 20:23:08 -0000

> From: Thomas Heide Clausen [ietf@thomasclausen.org]
>=20
> For some of us, getting reimbursed for a higher meeting fee is
> actually a lot easier than getting reimbursed for a higher
> hotel-fee. Such would be the case when, for example, traveling on a
> fixed per-diem intended for covering accommodation/food, but
> reimbursed on cost for the meeting fee.

A good point, but part of the reasoning for the current fee structure
(subsidizing the meeting proper via the hotel rooms) is to make it
possible to attend cheaply by locals and people on limited budgets who
are willing to book inexpensive accommodations.

> From: John C Klensin [john-ietf@jck.com]
>=20
> > What's a non-peak destination for July?
>=20
> Phoenix.  Probably Houston or Fort Worth.

I think that rooms could be obtained cheaply in Maimi in July.  (The
typical daily high is around 34 C, with high humidity.)

Dale

From jari.arkko@piuha.net  Tue Jun 21 14:41:34 2011
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 BD50E11E80DA for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 14:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.459
X-Spam-Level: 
X-Spam-Status: No, score=-102.459 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KTpsuKWPKtb3 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 14:41:34 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id E1EE911E8096 for <ietf@ietf.org>; Tue, 21 Jun 2011 14:41:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 756B02CC3B; Wed, 22 Jun 2011 00:41:26 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59ZhmUIIKHpl; Wed, 22 Jun 2011 00:41:23 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id D93FC2CC2F; Wed, 22 Jun 2011 00:41:22 +0300 (EEST)
Message-ID: <4E011002.4070002@piuha.net>
Date: Wed, 22 Jun 2011 00:41:22 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Ray Bellis <Ray.Bellis@nominet.org.uk>
Subject: Re: whine, whine, whine
References: <20110621035220.13199.qmail@joyce.lan>	<p0624060dca25d4aa0695@loud.pensive.org> <4E009652.1020503@viagenie.ca> <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk>
In-Reply-To: <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk>
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: Tue, 21 Jun 2011 21:41:34 -0000

Ray,

> The only European operator into YBQ appears to be Air Transat (whoever the heck they are) and they only fly from Marseille and Paris.
>   

They are pretty famous, for running out of fuel over the Atlantic. 
(Luckily, everyone survived.)

> I'm flying BA to Montreal and taking the short city hopper flight to YBQ from there.
>   

I'm still wondering what route to take, the alliance that I use 
(OneWorld) does not serve Quebec City too well. Maybe I'll pick some two 
hop solution to a nearby city such as Montreal and then drive the rest 
of the way, or a three hop approach that involves Air Canada for the 
last leg. Apparently, Iceland Air could also deliver me to Quebec in 
three hops.

In any case, looking very much forward to Quebec City!

Jari


From stpeter@stpeter.im  Tue Jun 21 14:47:06 2011
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 7DE3E11E810E for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 14:47:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.681
X-Spam-Level: 
X-Spam-Status: No, score=-102.681 tagged_above=-999 required=5 tests=[AWL=-0.082, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vUSCdi5rfEU0 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 14:47:05 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 87D7411E810D for <ietf@ietf.org>; Tue, 21 Jun 2011 14:47:05 -0700 (PDT)
Received: from dhcp-64-101-72-207.cisco.com (dhcp-64-101-72-207.cisco.com [64.101.72.207]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 55234400F9; Tue, 21 Jun 2011 15:47:43 -0600 (MDT)
Message-ID: <4E011156.1080303@stpeter.im>
Date: Tue, 21 Jun 2011 15:47:02 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: 25 or 6to4
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010709000105020207090100"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 21:47:06 -0000

This is a cryptographically signed message in MIME format.

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

A bit of levity about migration to IPv6, with apologies to Robert Lamm
and with thanks to Dan Wing and Joe Hildebrand...

###

"Waiting for the break of day" (yes, the dawn will come with the
universal deployment of IPv6)

"Searching for something to say" (how will we communicate once IPv4 is
gone?)

"Flashing lights against the sky" (hoping for extraterrestrial
intervention to solve the problem)

"Giving up I close my eyes" (ignoring IPv4 address exhaustion)

"Staring blindly into space" (have you ever read all the IPv6-related
specifications in one sitting?)

"Getting up to splash my face" (February 3, 2011 was a wakeup call, no?)

"Wanting just to stay awake" (simply wishing for the Internet to keep
working)

"Wondering how much I can take" (these v4 to v6 discussions are
interminable, aren't they?)

"Should I try to do some more?" (pondering the idea of writing an
Internet-Draft)

"25 or 6to4" (yes, port 25 is the answer -- perhaps the problem will
solve itself if we all just send more email to ietf@ietf.org!)

###



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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDYy
MTIxNDcwMlowIwYJKoZIhvcNAQkEMRYEFKecBooaTkk2TD8grjM1nUXdqPSeMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQBmGebO9R7gqdOAlF8ui8SpiioczFSoYhfr31JIAy7LIVp7cKLg63OQNcgn
fQVVgApCy7z33E4+ilrqonv1RgyZuZqOcMp6b+DDC3ZGOBe9h2iV2G3eITDh7Vy7ShYlfmOf
3DmTbnZbu++umkhx5TiW8l9B7DYmN9r5BKtsfnl2hCCWGNIWcUxVGzMBi7R6hHHoSMyHQh9g
26qrK32Sd3PbYUvJEHFdI2ULlHUPifzi7/j25j/kUoveOptIU0TKoAxlcr3Z4wsEYtev8a3B
r7wAfhHxEtf4fegwA1gOL3iYGQUE2rOzx2a3IXTXHRuwn+4dkViEe5Nnfie0oRonsxD4AAAA
AAAA
--------------ms010709000105020207090100--

From rdroms.ietf@gmail.com  Tue Jun 21 15:14:59 2011
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 22F8822800E for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 15:14:59 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KfJRPMdgbfRf for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 15:14:50 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0455922800D for <ietf@ietf.org>; Tue, 21 Jun 2011 15:14:49 -0700 (PDT)
Received: by qwc23 with SMTP id 23so154636qwc.31 for <ietf@ietf.org>; Tue, 21 Jun 2011 15:14:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=1ZmqGZNgaABu5+R5gplCxbX2HL3zyUVD8jFoM7cStuM=; b=aRxYUqrFM8S7g5fGVYU7rSdkf7sdAO7KJywMuZk+vBFypRzKpHJFK+LLlpjK4s3fqR reLeVweADePx+Zk4/kwI+gmbS6ZzrmV2U9dvTtjFxRP77PfWwx6TeIMtwTo0Rk6xdSCL SQBDRAi2O4m+aXSv5MAFgO5m6jvJuOQcV2/I4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=tiCEh0Hu1Hs3f5XLQA76qb+2KIIw7MMAqbDbb7aVY4jjSxH+QlgsnsVQ1U3U2nHAGm kWzCNhOKtFD6DabI0esS3B54iOp/K1LJzh4fCckdCFtYPv0OFxRqDZrfpbM/WOgell0T +qmt8SbIAEDB89L/CLY8xkqYsNIvzXcW91ht8=
Received: by 10.224.212.71 with SMTP id gr7mr5340875qab.198.1308694489197; Tue, 21 Jun 2011 15:14:49 -0700 (PDT)
Received: from [192.168.1.147] (c-24-62-225-5.hsd1.ma.comcast.net [24.62.225.5]) by mx.google.com with ESMTPS id u15sm5253676qcq.36.2011.06.21.15.14.48 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Jun 2011 15:14:48 -0700 (PDT)
Subject: Re: 25 or 6to4
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <4E011156.1080303@stpeter.im>
Date: Tue, 21 Jun 2011 18:14:46 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3AA0CFBE-3774-46CB-AE78-382C4F923C6A@gmail.com>
References: <4E011156.1080303@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1084)
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, 21 Jun 2011 22:14:59 -0000

Wow.  An absolute tour de force from someone who *clearly* has too much =
time on his hands.

Thanks; made my day.  Well, except for now I've got that long-forgotten =
tune stuck in my head...

- Ralph

On Jun 21, 2011, at 5:47 PM 6/21/11, Peter Saint-Andre wrote:

> A bit of levity about migration to IPv6, with apologies to Robert Lamm
> and with thanks to Dan Wing and Joe Hildebrand...
>=20
> ###
>=20
> "Waiting for the break of day" (yes, the dawn will come with the
> universal deployment of IPv6)
>=20
> "Searching for something to say" (how will we communicate once IPv4 is
> gone?)
>=20
> "Flashing lights against the sky" (hoping for extraterrestrial
> intervention to solve the problem)
>=20
> "Giving up I close my eyes" (ignoring IPv4 address exhaustion)
>=20
> "Staring blindly into space" (have you ever read all the IPv6-related
> specifications in one sitting?)
>=20
> "Getting up to splash my face" (February 3, 2011 was a wakeup call, =
no?)
>=20
> "Wanting just to stay awake" (simply wishing for the Internet to keep
> working)
>=20
> "Wondering how much I can take" (these v4 to v6 discussions are
> interminable, aren't they?)
>=20
> "Should I try to do some more?" (pondering the idea of writing an
> Internet-Draft)
>=20
> "25 or 6to4" (yes, port 25 is the answer -- perhaps the problem will
> solve itself if we all just send more email to ietf@ietf.org!)
>=20
> ###
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From stpeter@stpeter.im  Tue Jun 21 15:18:11 2011
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 88BD49E800B for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 15:18:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.678
X-Spam-Level: 
X-Spam-Status: No, score=-102.678 tagged_above=-999 required=5 tests=[AWL=-0.079, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W4A1045hOTn1 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 15:18:11 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id EE77D22800D for <ietf@ietf.org>; Tue, 21 Jun 2011 15:18:10 -0700 (PDT)
Received: from dhcp-64-101-72-207.cisco.com (dhcp-64-101-72-207.cisco.com [64.101.72.207]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A8DC6400F9; Tue, 21 Jun 2011 16:18:45 -0600 (MDT)
Message-ID: <4E01189D.6010100@stpeter.im>
Date: Tue, 21 Jun 2011 16:18:05 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: 25 or 6to4
References: <4E011156.1080303@stpeter.im> <3AA0CFBE-3774-46CB-AE78-382C4F923C6A@gmail.com>
In-Reply-To: <3AA0CFBE-3774-46CB-AE78-382C4F923C6A@gmail.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms080606060604090306040908"
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, 21 Jun 2011 22:18:11 -0000

This is a cryptographically signed message in MIME format.

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

I needed a diversion from reviewing draft-ietf-v6ops-6to4-to-historic
and its associated IETF LC comments. Back to my IESG duties now... ;-)

On 6/21/11 4:14 PM, Ralph Droms wrote:
> Wow.  An absolute tour de force from someone who *clearly* has too much=
 time on his hands.
>=20
> Thanks; made my day.  Well, except for now I've got that long-forgotten=
 tune stuck in my head...
>=20
> - Ralph
>=20
> On Jun 21, 2011, at 5:47 PM 6/21/11, Peter Saint-Andre wrote:
>=20
>> A bit of levity about migration to IPv6, with apologies to Robert Lamm=

>> and with thanks to Dan Wing and Joe Hildebrand...
>>
>> ###
>>
>> "Waiting for the break of day" (yes, the dawn will come with the
>> universal deployment of IPv6)
>>
>> "Searching for something to say" (how will we communicate once IPv4 is=

>> gone?)
>>
>> "Flashing lights against the sky" (hoping for extraterrestrial
>> intervention to solve the problem)
>>
>> "Giving up I close my eyes" (ignoring IPv4 address exhaustion)
>>
>> "Staring blindly into space" (have you ever read all the IPv6-related
>> specifications in one sitting?)
>>
>> "Getting up to splash my face" (February 3, 2011 was a wakeup call, no=
?)
>>
>> "Wanting just to stay awake" (simply wishing for the Internet to keep
>> working)
>>
>> "Wondering how much I can take" (these v4 to v6 discussions are
>> interminable, aren't they?)
>>
>> "Should I try to do some more?" (pondering the idea of writing an
>> Internet-Draft)
>>
>> "25 or 6to4" (yes, port 25 is the answer -- perhaps the problem will
>> solve itself if we all just send more email to ietf@ietf.org!)
>>
>> ###
>>


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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDYy
MTIyMTgwNVowIwYJKoZIhvcNAQkEMRYEFFcbtHmBJmHE9D+g15MjaZUgPmdAMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQAEXPGA/FbMVvjHt31vv5Xs9iHFJQ8Xse4pR9gulh4nEyHNE8Yr74XVB4+2
LxdWeURJdWNN4fJ803ysjil9Jphrca7UToIoOmEFbMcSaGqZL2uGAQjg9CzZxE05c8BVpFDj
4hWUNLEJ1noDvF4tTgNPK4tZKxoyk6Y8Vw4XEQnoxO356l9O+FfsamW+5sGPPtGNwcfZqH62
fG8rPkMSzz7qEglY13MSZXPeDvM6VKop3PT4/LuJTCHjqTF1m7YUMUx9xiVvRMJVUy46HnF9
Dxt6FuTydifC5WfjwFkXa032AT7quvRkywwztFN6rCY+iSLfvk/6buK1tshu8TSrm+0tAAAA
AAAA
--------------ms080606060604090306040908--

From rdroms.ietf@gmail.com  Tue Jun 21 15:46:40 2011
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 946E711E80E5 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 15:46:40 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZL6Qmw5dcjn for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 15:46:39 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id B968011E80D1 for <ietf@ietf.org>; Tue, 21 Jun 2011 15:46:39 -0700 (PDT)
Received: by qwc23 with SMTP id 23so168071qwc.31 for <ietf@ietf.org>; Tue, 21 Jun 2011 15:46:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=hLVNGtpaE88RsYn4Tiogkt+NsJUFjIY/APx48R9xmTA=; b=G3SsRLehvpTyca9FK85j7R0pmomyNKLj9/X4T2/KgycP/6bpMPUcR5XaDqkyv2qLqq cmeCRqPvGCgm+/5EtoSw+Z4beoH9KsE3yR7EUUh6IWwiOMNP13E9FjT2dAQ4S1JWMXSX TVE8e+YO4XahDQ/VLKQkR0jfXHNnd5fpLkhVo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=uc2ndTzve5ArNcLiEXwX+DLKLC9lEQTjgpow92o6fNdE06Fx8Ryaf0AUf/zy4lCJ0I Xta2FXsqlgb1MWGWXA1yUKuxUDJt81mtmcIVQ5rIWhrqwRkMcwmXQXdOa14uy4gkzET9 R7kqKySaRg4CZ7A/2QAhQNuogQdhucZfayEe8=
Received: by 10.229.10.200 with SMTP id q8mr2868304qcq.180.1308696399131; Tue, 21 Jun 2011 15:46:39 -0700 (PDT)
Received: from [192.168.1.147] (c-24-62-225-5.hsd1.ma.comcast.net [24.62.225.5]) by mx.google.com with ESMTPS id g11sm1107263qcm.39.2011.06.21.15.46.37 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Jun 2011 15:46:38 -0700 (PDT)
Subject: Re: 25 or 6to4
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <4E01189D.6010100@stpeter.im>
Date: Tue, 21 Jun 2011 18:46:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <526E4E8F-FD9A-40E9-9DE8-25E4D4FC6ECB@gmail.com>
References: <4E011156.1080303@stpeter.im> <3AA0CFBE-3774-46CB-AE78-382C4F923C6A@gmail.com> <4E01189D.6010100@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1084)
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, 21 Jun 2011 22:46:40 -0000

Now that I've swapped back in some more recollections - yes, I did see =
Chicago perform it live when it was first released - I'm glad you =
finally cleared up the meaning behind the lyrics.  I always thought the =
lyrics somehow drug-related ... of course, we thought a lot of lyrics =
were drug-related then.

More recently I thought it was about reading drafts for a telechat.

- Ralph

On Jun 21, 2011, at 6:18 PM 6/21/11, Peter Saint-Andre wrote:

> I needed a diversion from reviewing draft-ietf-v6ops-6to4-to-historic
> and its associated IETF LC comments. Back to my IESG duties now... ;-)
>=20
> On 6/21/11 4:14 PM, Ralph Droms wrote:
>> Wow.  An absolute tour de force from someone who *clearly* has too =
much time on his hands.
>>=20
>> Thanks; made my day.  Well, except for now I've got that =
long-forgotten tune stuck in my head...
>>=20
>> - Ralph
>>=20
>> On Jun 21, 2011, at 5:47 PM 6/21/11, Peter Saint-Andre wrote:
>>=20
>>> A bit of levity about migration to IPv6, with apologies to Robert =
Lamm
>>> and with thanks to Dan Wing and Joe Hildebrand...
>>>=20
>>> ###
>>>=20
>>> "Waiting for the break of day" (yes, the dawn will come with the
>>> universal deployment of IPv6)
>>>=20
>>> "Searching for something to say" (how will we communicate once IPv4 =
is
>>> gone?)
>>>=20
>>> "Flashing lights against the sky" (hoping for extraterrestrial
>>> intervention to solve the problem)
>>>=20
>>> "Giving up I close my eyes" (ignoring IPv4 address exhaustion)
>>>=20
>>> "Staring blindly into space" (have you ever read all the =
IPv6-related
>>> specifications in one sitting?)
>>>=20
>>> "Getting up to splash my face" (February 3, 2011 was a wakeup call, =
no?)
>>>=20
>>> "Wanting just to stay awake" (simply wishing for the Internet to =
keep
>>> working)
>>>=20
>>> "Wondering how much I can take" (these v4 to v6 discussions are
>>> interminable, aren't they?)
>>>=20
>>> "Should I try to do some more?" (pondering the idea of writing an
>>> Internet-Draft)
>>>=20
>>> "25 or 6to4" (yes, port 25 is the answer -- perhaps the problem will
>>> solve itself if we all just send more email to ietf@ietf.org!)
>>>=20
>>> ###
>>>=20
>=20


From steve@shinkuro.com  Tue Jun 21 15:49:54 2011
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 35B9811E812E for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 15:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.47
X-Spam-Level: 
X-Spam-Status: No, score=-1.47 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DSL=1.129]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEoGM+W9BZyE for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 15:49:53 -0700 (PDT)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id A61FE11E812B for <ietf@ietf.org>; Tue, 21 Jun 2011 15:49:53 -0700 (PDT)
Received: from [61.8.214.4] (HELO [10.0.1.2]) by execdsl.com (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 19687900; Tue, 21 Jun 2011 22:51:50 +0000
Subject: Re: 25 or 6to4
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Steve Crocker <steve@shinkuro.com>
In-Reply-To: <526E4E8F-FD9A-40E9-9DE8-25E4D4FC6ECB@gmail.com>
Date: Wed, 22 Jun 2011 06:49:45 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <CAD03E04-BA37-46B6-A9A5-677A5D2906A1@shinkuro.com>
References: <4E011156.1080303@stpeter.im> <3AA0CFBE-3774-46CB-AE78-382C4F923C6A@gmail.com> <4E01189D.6010100@stpeter.im> <526E4E8F-FD9A-40E9-9DE8-25E4D4FC6ECB@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: Apple Mail (2.1084)
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, 21 Jun 2011 22:49:54 -0000

I did an interview for BBC Radio for New Year's Day several years ago =
about the early days of developing the Arpanet.  The closing question =
was why, in 1968, we weren't at Woodstock.  I replied, "For us, =
computers were the drug of choice."

Steve

On Jun 22, 2011, at 6:46 AM, Ralph Droms wrote:

> Now that I've swapped back in some more recollections - yes, I did see =
Chicago perform it live when it was first released - I'm glad you =
finally cleared up the meaning behind the lyrics.  I always thought the =
lyrics somehow drug-related ... of course, we thought a lot of lyrics =
were drug-related then.
>=20
> More recently I thought it was about reading drafts for a telechat.
>=20
> - Ralph
>=20
> On Jun 21, 2011, at 6:18 PM 6/21/11, Peter Saint-Andre wrote:
>=20
>> I needed a diversion from reviewing draft-ietf-v6ops-6to4-to-historic
>> and its associated IETF LC comments. Back to my IESG duties now... =
;-)
>>=20
>> On 6/21/11 4:14 PM, Ralph Droms wrote:
>>> Wow.  An absolute tour de force from someone who *clearly* has too =
much time on his hands.
>>>=20
>>> Thanks; made my day.  Well, except for now I've got that =
long-forgotten tune stuck in my head...
>>>=20
>>> - Ralph
>>>=20
>>> On Jun 21, 2011, at 5:47 PM 6/21/11, Peter Saint-Andre wrote:
>>>=20
>>>> A bit of levity about migration to IPv6, with apologies to Robert =
Lamm
>>>> and with thanks to Dan Wing and Joe Hildebrand...
>>>>=20
>>>> ###
>>>>=20
>>>> "Waiting for the break of day" (yes, the dawn will come with the
>>>> universal deployment of IPv6)
>>>>=20
>>>> "Searching for something to say" (how will we communicate once IPv4 =
is
>>>> gone?)
>>>>=20
>>>> "Flashing lights against the sky" (hoping for extraterrestrial
>>>> intervention to solve the problem)
>>>>=20
>>>> "Giving up I close my eyes" (ignoring IPv4 address exhaustion)
>>>>=20
>>>> "Staring blindly into space" (have you ever read all the =
IPv6-related
>>>> specifications in one sitting?)
>>>>=20
>>>> "Getting up to splash my face" (February 3, 2011 was a wakeup call, =
no?)
>>>>=20
>>>> "Wanting just to stay awake" (simply wishing for the Internet to =
keep
>>>> working)
>>>>=20
>>>> "Wondering how much I can take" (these v4 to v6 discussions are
>>>> interminable, aren't they?)
>>>>=20
>>>> "Should I try to do some more?" (pondering the idea of writing an
>>>> Internet-Draft)
>>>>=20
>>>> "25 or 6to4" (yes, port 25 is the answer -- perhaps the problem =
will
>>>> solve itself if we all just send more email to ietf@ietf.org!)
>>>>=20
>>>> ###
>>>>=20
>>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From moore@network-heretics.com  Tue Jun 21 16:31:29 2011
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 9302111E8083 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 16:31:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.396
X-Spam-Level: 
X-Spam-Status: No, score=-3.396 tagged_above=-999 required=5 tests=[AWL=0.203,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SBunoHbVH5a0 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 16:31:29 -0700 (PDT)
Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 213E211E80A4 for <ietf@ietf.org>; Tue, 21 Jun 2011 16:31:23 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id C015B20575; Tue, 21 Jun 2011 19:31:22 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute4.internal (MEProxy); Tue, 21 Jun 2011 19:31:22 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=t8Pgvd9rCECAn83mpVFNT8dVwyQ=; b=tLNtFzVownDi0EBIBGN7kJukVUMiqpFa6R29Dv6yow5kq1pgxyMrFbptXSIu4Ud3vYlf8HPiocuZzGbq5e11PUHlCZb7ukEIFfu1eDJCgncUueM/x/xJ9w4kNZrmLq2Wi4u/4zVJFHE1N3OMlsFbNkQMCHRHz/v3Rb+/FC56tFk=
X-Sasl-enc: VhmejLysa9tAZiR/D0G57YUQGakbyz44+nzj2iKVhg5r 1308699082
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 26ECF44099D; Tue, 21 Jun 2011 19:31:22 -0400 (EDT)
Subject: Re: 25 or 6to4
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E011156.1080303@stpeter.im>
Date: Tue, 21 Jun 2011 19:31:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA079C4F-D233-4E86-9047-2C1D557029FF@network-heretics.com>
References: <4E011156.1080303@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1084)
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, 21 Jun 2011 23:31:29 -0000

I've been thinking of the protocol as "25" ever since Brian suggested =
the name "6to4"  :)

Keith


From dotis@mail-abuse.org  Tue Jun 21 18:50:49 2011
Return-Path: <dotis@mail-abuse.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 5577121F8590; Tue, 21 Jun 2011 18:50:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id COvzvT6S3pQg; Tue, 21 Jun 2011 18:50:48 -0700 (PDT)
Received: from SJDC-SDIRelay1.sdi.trendmicro.com (sjdc-sdirelay1.sdi.trendmicro.com [150.70.64.59]) by ietfa.amsl.com (Postfix) with ESMTP id 49D0F21F858A; Tue, 21 Jun 2011 18:50:48 -0700 (PDT)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by SJDC-SDIRelay1.sdi.trendmicro.com (Postfix) with ESMTP id 745503B007A; Wed, 22 Jun 2011 01:50:45 +0000 (UTC)
Received: from farside-laptop.local (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id BCFAEA9443B; Wed, 22 Jun 2011 01:51:38 +0000 (UTC)
Message-ID: <4E014A76.5090805@mail-abuse.org>
Date: Tue, 21 Jun 2011 18:50:46 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org, Barry Leiba <barryleiba@computer.org>,  iesg-secretary@ietf.org, Sean Turner <turners@ieca.com>
Subject: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified Mail (DKIM) Signatures) to Draft Standard
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, 22 Jun 2011 01:50:49 -0000

Background on preceding DKIM work--

RFC4686 Introduction states:
,---
The DKIM protocol defines a mechanism by which email messages can be 
cryptographically signed, permitting a signing domain to claim 
responsibility for the use of a given email address.
'---

While several threats to DKIM were considered, multiple From header 
fields were neglected.  This document only focused on use of multiple 
addresses within the From header field.

RFC5585 Introduction states:
,---
DKIM allows an organization to take responsibility for a message in a 
way that can be verified by a recipient. [..] It permits verification of 
the signer of a message, as well as the integrity of its contents.  DKIM 
will also provide a mechanism that permits potential email signers to 
publish information about their email signing practices; this will 
permit email receivers to make additional assessments of unsigned 
messages.  DKIM's authentication of email identity can assist in the 
global control of "spam" and "phishing".
'---

It should be noted that Signing Practices are referenced off a domain 
found in the From header field which also assumes only one will be present.

RFC2119 definition
,---
SHOULD
This word, or the adjective "RECOMMENDED", mean that there
may exist _valid_ reasons in particular circumstances to ignore a
particular item, but the full implications must be understood and
carefully weighed before choosing a different course.
'___

Section 3.8 Input Requirements states that verifiers SHOULD take 
reasonable steps to ensure that the messages they are processing are 
valid according to RFC5322, RFC2045, and any other relevant message 
format standard.

Section 8.14 Attacks Involving Addition of Header Fields

acknowledges:
,---
Many email implementations do not enforce [RFC5322] with strictness as 
discussed in Section 5.3 (Normalize the Message to Prevent Transport 
Conversions), DKIM processing is predicated on a valid
mail message as its input.  However, DKIM implementers should be aware 
of the potential effect of having loose enforcement by email components 
interacting with DKIM modules.
'___

and further states:
,---
An MUA then might elect to render to the user the
value of the first, or "top", From: field.  This may also be done
simply out of the expectation that there is only one, where a "find
first" algorithm would have the same result.  Such code in an MUA can
be exploited to fool the user if it is also known that the other
From: field is the one checked by arriving message filters.  Such is
the case with DKIM; although the From: field must be signed, a
malformed message bearing more than one From: field might only have
the first ("bottom") one signed, in an attempt to show the message
with some "DKIM passed" annotation while also rendering the From:
field that was not authenticated.  (This can also be taken as a
demonstration that DKIM is not designed to support author
validation.)
'___

This indicates the DKIM specification is seriously flawed.  While DKIM 
may not offer author validation, it was intended to establish an 
accountable domain for the signed message content that at a minimum 
includes the From header field.  There are NO valid reasons for a valid 
signature to include multiple From header fields!  Allowing multiple 
 From header fields is _EVIL_ and destroys DKIM's intended purpose as 
defined by prior work.

Free email providers likely use DKIM to gain increased acceptance by 
taking advantage of their "too big to block" volumes.  For these 
domains, their reputation is understood to offer little assurance of 
their overall integrity while perhaps limiting what is allowed in the 
domain portion of the From header field.

By allowing a pre-pended From header field to not affect the validity of 
a DKIM signature according to the specification means the UNDERSTOOD 
source of a message can NEVER be trusted through the aid of DKIM.

Those that phish by taking advantage of this neglected flaw are unlikely 
to affect the acceptance of any exploited high volume domain.  DKIM 
could have avoided offering false assurances by not ignoring illegal 
multiple header fields per RFC5322 and defining such messages as 
resulting in invalid signatures.  Unfortunately, when essential input 
checks are skipped, acceptance based upon DKIM's now potentially 
deceptive results may play an evil role that cannot be repaired through 
the use of reputation.

The general goal of DKIM cryptographically binding at a minimum the From 
header field of the message content to a domain was to act as a trust 
basis for acceptance.  DKIM also purports to allow incremental 
deployment without requiring additional undefined filtering be 
introduced in mail transfer or mail user agents. Clearly, the 
incremental deployment statement conflicts with the original goals due 
to the neglected input validation flaw.

Details of this concern were stated in the tracker at:
http://trac.tools.ietf.org/wg/dkim/trac/ticket/24


This version of DKIM also introduced use of RFC5890 instead of RFC3490, 
which allows use of the German esset and the Greek final sigma, drops 
string-prep, and defines 3,329 invalid code points.  Unfortunately, this 
version of the DKIM also failed to exclude use of Fake A-Labels, which 
when presented to the user may also prove highly deceptive.

Details of this concern were stated in the tracker at:
http://trac.tools.ietf.org/wg/dkim/trac/ticket/24

Regards,
Douglas Otis



From evnikita2@gmail.com  Tue Jun 21 21:38:26 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30EA711E8079 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 21:38:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level: 
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[AWL=-0.188, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jViAAy+-Zjoz for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 21:38:25 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 38B6A11E8090 for <ietf@ietf.org>; Tue, 21 Jun 2011 21:38:24 -0700 (PDT)
Received: by fxm15 with SMTP id 15so398725fxm.31 for <ietf@ietf.org>; Tue, 21 Jun 2011 21:38:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9uIXdAhA26LV+tZ0ahhDYngI5Xh2+KajpyWNroYcjZQ=; b=CX29WXb2rfL5IeQEBdDiMpMafaGtEUzN4esPGi2ERWoek+wmfAuab9YwNR0PZgulfs 2Vf8C1TLlCpKakLH+IBv0UQXD83SzF/83n1sdGJNNLWTlGX3LXdKEfPMfPfNn+vwF4oU 2TYZONYJER4QJKEnGyU+NaoxzAS5/aLGjsUWU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=H3sj3yj1LJJf3EqDWwB3R/Yrvt09RSWGQX0JK1X7Cvde3p7cTpNAH3f0iSZUns84vz cDbyyMPhod7mJpcDb4lizTJhp8IfVyq13iJIok6IZGQsn6t5OuIoLoGG/Ro4EeiT/7/t VP2NfgD1JKnSS4A0wNLy+f4YXC196UCrKA4SQ=
Received: by 10.223.1.201 with SMTP id 9mr242142fag.91.1308717503253; Tue, 21 Jun 2011 21:38:23 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id o23sm75955faa.33.2011.06.21.21.38.20 (version=SSLv3 cipher=OTHER); Tue, 21 Jun 2011 21:38:21 -0700 (PDT)
Message-ID: <4E0171EB.4020109@gmail.com>
Date: Wed, 22 Jun 2011 07:39:07 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
References: <0EC26EB10287E2A20769C9CC@PST.JCK.COM>
In-Reply-To: <0EC26EB10287E2A20769C9CC@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-holsten-about-uri-scheme@tools.ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 04:38:26 -0000

Hello John,

Thanks for your thoughts and proposals.  Please see my comments (as one 
of the document co-authors) in-line.

17.06.2011 19:49, John C Klensin wrote:
> Given the controversies, I decided I needed to do a careful
> reading of this document.  While I respect and appreciate what
> the authors are trying to do, as a would-be standards track
> specification, it is pretty troubling.
I may agree here.
>   It is troubling
> editorially as well.
And here as well.
> I think all or most of the specific issues have been identified
> by others, so let me try a different perspective and a 10 km
> view.
>
> (1) There seems to be consensus that registering this URI as a
> mechanism for accessing built-in functionality and configuration
> information such as application information, preferences, or
> settings.   (Text derived from the Abstract with "configuration
> information", which may mean more to some readers, added and
> "easter eggs" dropped.  Dropping "easter eggs" reflects other
> comments on the list and my opinion that it isn't worth the
> trouble to define.
With regard to easter eggs I have no strong position.  If it is 
troubling, I don't object to remove any mention of them from the document.
> Recommendation: Let's get it registered.
That's what we're trying to do.  But see the paragraph before "Smaller 
issues".
> (2)  The document itself reflects an attempt to define the
> undefinable.  There is no cross-implementation interoperability
> issue here; if anything, the document should me more clear that
> it would be stupid to assume it.  The document, nonetheless,
> tries to define what is done with some specific URIs in some
> places and then has to turn around and indicate that they may be
> used in entirely different ways in other places and should not
> be relied upon.  In the process, it skips back and forth between
> being descriptive and being normative, with some definitions
> becoming circular in the process.   That just isn't a good
> combination and some of it actually looks pretty silly.
I may partly agree with you.  Reading the document for a number of times 
I've also noticed this.  A logical conclusion of everything 
aforementioned is below.
> "about:blank"  is particularly troubling in that regard because
> the text essentially says that it is reserved except where it
> isn't.
>
> Recommendation:  Choose one of the following and redo the
> document to match.
>
> Option 1: Do this descriptively.  Strip it down as much as
> possible, more or less repeating the suggested language above.
> If the Wikipedia article really contains a better and more
> authoritative list of applications than the I-D text (and
> especially if it is being kept up to date), just reference it as
> a place where a non-normative listing and examples can be found.
> The effect of doing this at all would be to reserve the name for
> purposes internal to particular implementations of particular
> applications, not unlike RFC 1918 addresses.
>
> Option 2: Really try to make this normative wrt some subset of
> URI values.  In this approach, stop the extremely confusing
> circling around.  Indicate explicitly that "about" URIs have
> been used enough and in enough different circumstances that no
> application should assume that an "about" URI, if encountered,
> is actually its own and that due caution needs to be taken about
> non-conforming implementations.  Then explicitly reserve, not
> only"about:blank", but  everything the authors think is worth
> listing in Examples _and_ create an IANA registry for more of
> them.
Actually your Option 2 is what we were trying to do all the time.  
However, considered a number of existing implementations, each one 
having their own behavior with regard to about URIs, I actually don' 
think is is possible.  Option 1 seems to be much more realistic; in fact 
what we had in -00 
(http://tools.ietf.org/id/draft-holsten-about-uri-scheme-00.txt) seems 
the best of any further version of the draft.  -00 said that 
"applications are free to resolve any about URI to any resource, either 
internal or external, or redirect to an alternative URI, with 
about:blank being the only exception".  That's indeed better that what 
we have in the -06.  Currently, I even question me whether we need to 
have an RFC published for the purpose of reservation of the scheme.  The 
situation is probably the same as with the view-source URIs.  It was 
ultimately registered with IANA upon a simple request whereas the 
initial intent was to publish the Informational RFC (see 
http://www.iana.org/assignments/uri-schemes/prov/view-source; 
https://datatracker.ietf.org/doc/draft-yevstifeyev-view-source-uri/).  
RFC 4395 intended the URI scheme registration to be lightweight - 
template provided is everything you need.  So we could just process this 
registration in such way, as Permanent registration, without any 
separate specification.
> But, even the second approach is taken, the document should be
> really clear that all that the use of "about:" really tells
> someone is that it is application-specific and that a particular
> implementation of a particular application may do whatever it
> pleases with them.
>
>
>   ----
> Smaller issues:
>
> (i) Section 6, Normalization, sadly really doesn't belong here
> unless the authors can show that everyone interprets "about:"
> according to those rules.  Otherwise, it would be better to say
> that the URI is interpreted in an implementation-specific way
> and that implementations would be well-advised to conform to
> normal URI syntax rules unless there is a strong reason not to.
Agree here.  This thread restarted with the response to Boris's comment 
regarding Gecko's normalization rules.  This was to claim that no 
unified rules for the scheme which is a priori used by the applications 
on their own.  As I proposed below, if no document is to be written, the 
template may contain such statement about implementation-specific 
normalization rules.
> (ii) IMO, Section 7, Security Considerations, should be modified
> to include an explicit statement that, since these things are
> intended for convenience use within an implementation of an
> application, passing them between systems (embedded in files or
> otherwise) is very risky behavior and should generally be
> discouraged except, possibly, in documentation contexts.
I agree here.
> (iii) I know this is partially a problem with the general URI
> and IRI definitions, but I'm supposed to know something about
> i18n and  encoding and Section 4, Encoding Considerations, is
> almost incomprehensible to me.  It isn't quite clear what "this
> syntax" refers to (if it is "the 'about' variation on the
> general URI syntax described in Section 3", say that).   Then I
> think it says I may use any Unicode character, but I have to
> %-encode it, but, if it isn't unreserved, it shouldn't be
> %-encoded.  If there isn't a clearer way to say that, I suggest
> that almost anyone trying to figure out how to use this URI from
> the spec is in trouble.  And, fwiw, I've seen "about:" URIs that
> use non-ASCII strings without %-encoding.   Whether one calls
> those IRIs, URIs, or pumpkins, I see absolutely no reason why an
> implementation that knows it is UTF-8 capable (and clean) should
> require that an xRI that is intended only for internal use
> should require %-encoding of UTF-8 strings... especially since,
> in practice, these URIs are often expected to be direct user
> input.
Section 4 is what is also questionable.  This issue was raised during 
Last Call and I think can be resolved by saying that an about URIs may 
contain UTF-8 encoded characters in the <segment>, as suggested by RFC 
3986 and that's all.

Mykyta Yevstifeyev
>    best,
>       john
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From mnot@mnot.net  Tue Jun 21 22:08:34 2011
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 5B3A111E8079 for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 22:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.515
X-Spam-Level: 
X-Spam-Status: No, score=-105.515 tagged_above=-999 required=5 tests=[AWL=-2.916, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iOOlaEq4RdWi for <ietf@ietfa.amsl.com>; Tue, 21 Jun 2011 22:08:33 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 3B46D11E8074 for <ietf@ietf.org>; Tue, 21 Jun 2011 22:08:33 -0700 (PDT)
Received: from chancetrain-lm.mnot.net (unknown [118.209.34.52]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 6E79322E1F4; Wed, 22 Jun 2011 01:08:26 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host Metadata)	to Proposed Standard -- feedback
Date: Wed, 22 Jun 2011 15:08:22 +1000
Message-Id: <11CBFBA2-434B-43FC-90C4-DADBACB49226@mnot.net>
To: "ietf@ietf.org IETF" <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: Eran Hammer-Lahav <eran@hueniverse.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, 22 Jun 2011 05:08:34 -0000

Generally, it's hard for me to be enthusiastic about this proposal, for =
a few reasons. That doesn't mean it shouldn't be published, but I do =
question the need for it to be Standards Track as a general mechanism.

Mostly, it's because I hasn't really seen much discussion of it as a =
general component of the Web / Internet architecture; AFAICT all of the =
interest in it and discussion of it has happened in more specialised / =
vertical places. The issues below are my concerns; they're not =
insurmountable, but I would have expected to see some discussion of them =
to date on lists like this one and/or the TAG list for something that's =
to be an Internet Standard.


* XRD -- XRD is an OASIS spec that's used by OpenID and OAuth. Maybe I'm =
just scarred by WS-*, but it seems very over-engineered for what it =
does. I understand that the communities had reasons for using it to =
leverage an existing user base for their specific user cases, but I =
don't see any reason to generalise such a beast into a generic =
mechanism.


* Precedence -- In my experience one of the most difficult parts of a =
metadata framework like this is specifying the combination of metadata =
from multiple sources in a way that's usable, complete and clear. =
Hostmeta only briefly mentions precedence rules in the introduction.=20


* Scope of hosts -- The document doesn't crisply define what a "host" =
is.


* Context of metadata -- I've become convinced that the most successful =
uses of .well-known URIs are those that have commonality of use; i.e., =
it makes sense to define a .well-known URI when most of the data =
returned is applicable to a particular use case or set of use cases. =
This is why robots.txt works well, as do most other currently-deployed =
examples of well-known URIs.

Defining a bucket for potentially random, unassociated metadata in a =
single URI is, IMO, asking for trouble; if it is successful, it could =
cause administrative issues on the server (as potentially many parties =
will need control of a single file, for different uses -- tricky when =
ordering is important for precedence), and if the file gets big, it will =
cause performance issues for some use cases.


* Chattiness -- the basic model for resource-specfic metadata in =
hostmeta requires at least two requests; one to get the hostmeta =
document, and one to get the resource-specific metadata after =
interpolating the URI of interest into a template.=20

For some use cases, this might be appropriate; however, for many others =
(most that I have encountered), it's far too chatty. Many use cases find =
the latency of one extra request unacceptable, much less two. Many use =
cases require fetching metadata for a number of distinct resources; in =
this model, that adds a request per resource.

I'd expect a general solution in this space to allow describing a "map" =
of a Web site and applying metadata to it in arbitrary ways, so that a =
client could fetch the document once and determine the metadata for any =
given resource by examining it.=20


If hostmeta is designed for specific use cases and meets them well, =
that's great, but it shouldn't be sold as a general mechanism. So, I'm =
-1 on this going forward as a standards-track general mechanism. I =
wouldn't mind if it were Informational, or if it were Standards-Track =
but with a defined use case.

Apologies for giving this feedback so late in the process; I knew =
hostmeta was there, just didn't have time to step back and think about =
it.


Cheers,

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




From krishnabirth@gmail.com  Wed Jun 22 01:59:15 2011
Return-Path: <krishnabirth@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6A479E801C for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 01:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.073
X-Spam-Level: 
X-Spam-Status: No, score=-3.073 tagged_above=-999 required=5 tests=[AWL=0.526,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ta9Q4TRqohMz for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 01:59:15 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 634169E800F for <ietf@ietf.org>; Wed, 22 Jun 2011 01:59:15 -0700 (PDT)
Received: by yie30 with SMTP id 30so362166yie.31 for <ietf@ietf.org>; Wed, 22 Jun 2011 01:59:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=17hL/kNC+ZJhp2P9lscuPLOM6rSPygQ5GOLWkXxUjv0=; b=gWbg9A9bfDPkvQKLYDS1mEKeF5E6W2xkqN2U/uHyfDqrGXgiuWMMV10moeiz6FKRWI yOWWpxsYDtlBhMysHipcmVMtk+GQ7m1MbDgeJV/3wJChH+/duQAQuGQbnWrnHNLfxdkX jGpA+h90aVwVHbUMUkNRBLlMO1+iZliBUJHNA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=uwZHuQTrGxcLQJJj5BSYRuF8TH8C1IDhuhUQHkB1rV3SnEk8UIIiLkE5dfqHisV+2G dJoaBrljHffQCucTEBonH0gupz4bsb1BxoCzScvoIzJVD0NAXUROu2ohJzqgltnRbtK8 ZCONP5RuTnp9Cy8oE0shcg0zM7qj+49Orr6uc=
MIME-Version: 1.0
Received: by 10.236.78.193 with SMTP id g41mr657368yhe.468.1308733154571; Wed, 22 Jun 2011 01:59:14 -0700 (PDT)
Received: by 10.236.154.225 with HTTP; Wed, 22 Jun 2011 01:59:14 -0700 (PDT)
Date: Wed, 22 Jun 2011 08:59:14 +0000
Message-ID: <BANLkTimdzZ_4d49P5EzWg+bgWFn+7fPgYw@mail.gmail.com>
Subject: My Internet experience in the West at times is comparable to female foeticide
From: Krishna Birth <krishnabirth@gmail.com>
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: Wed, 22 Jun 2011 08:59:16 -0000

I believe that I am being banned, treated badly and threatened to stop
posting from certain Linux, PC, Software and Font internet forums and
mailing lists because I have a beyond religion or spiritual realm
cause in the projects that I am posting about.

When I read / listen about female infanticide / female foeticide, it
shows that this is happening why -- there is the cultural factor
operating.  My content is different and thus that is the reason that
I am being banned, treated badly and threatened to stop posting from
certain Linux, PC, Software and Font internet forums and mailing
lists.

To be fair there are some useful responses on  some internet forums /
mailing lists and threads.  Not all members are the same.

On the other hand for example in Britain Linux User Groups (LUGs) --
Swlug (South Wales) has banned my posting to it's Linux group,
Staffslug (Staffordshire)  only yesterday threatened me with banning.
Oxlug (Oxfordshire) does not allow me to post.  Same with the other
Sheflug (Sheffield).

Some not all internet forums/mailing list organisers need some
educating and need to educate others for example by having some
by-laws and rules so that I am treated without these problems.


Regards


Meeku

From Ray.Bellis@nominet.org.uk  Wed Jun 22 03:37:07 2011
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 C1AAC11E80E6 for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 03:37:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.932
X-Spam-Level: 
X-Spam-Status: No, score=-9.932 tagged_above=-999 required=5 tests=[AWL=0.667,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0-QB9w+rbsrA for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 03:37:07 -0700 (PDT)
Received: from mx4.nominet.org.uk (mail.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id BE1C711E807F for <ietf@ietf.org>; Wed, 22 Jun 2011 03:37:05 -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:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=Ac1iJI3JElMRA/3Sk6rO65m0vgb3RVPA81gdTBygL+7pe3kifpIu+pjn AuAAtzlaUTsvBRLIqdK3+hhVC2Dos87fV4M2u4uQ0N+fHIWW/EQOtY+4V btpSbPAaJKojBc7;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1308739027; x=1340275027; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20whine,=20whine,=20whine|Date:=20Wed,=20 22=20Jun=202011=2010:35:46=20+0000|Message-ID:=20<D3DA739 E-B25A-4AF9-A524-CA84362F39F3@nominet.org.uk>|To:=20Klaas =20Wierenga=20<klaas@wierenga.net>|CC:=20"<ietf@ietf.org> "=20<ietf@ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |Content-ID:=20<5694ade8-254b-4787-b62a-ef070eda926b> |In-Reply-To:=20<4E00A026.2080208@wierenga.net> |References:=20<20110621035220.13199.qmail@joyce.lan>=0D =0A=09<p0624060dca25d4aa0695@loud.pensive.org>=20<4E00965 2.1020503@viagenie.ca>=0D=0A=20<EEC3E51C-E295-4A6D-935D-1 D4346F222B6@nominet.org.uk>=0D=0A=20<4E00A026.2080208@wie renga.net>; bh=66wFlbC2to9ybPIYYkSUCnkOKi510BNQnCF2wFNb1Qs=; b=IpgB8R6y3SF/6/6R0CCgnv+bXvxVMu5clQ4y0DG1ftNWn1s4mTfqKEU2 QarvrIJv0eJVZgS6ak/ZfFm/ru+oVeyP56V9QX1BrM3W0ilVsl8O5zHLs SYJGut7jFEu0WTr;
X-IronPort-AV: E=Sophos;i="4.65,405,1304290800"; d="scan'208";a="26942033"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx4.nominet.org.uk with ESMTP; 22 Jun 2011 11:35:47 +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%19]) with mapi; Wed, 22 Jun 2011 11:35:47 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Klaas Wierenga <klaas@wierenga.net>
Subject: Re: whine, whine, whine
Thread-Topic: whine, whine, whine
Thread-Index: AQHML8ba/QbBneMv0ESHCqHTsduvAJTHMZyAgACE7wCAAAd5gIAABD4AgAFdtgA=
Date: Wed, 22 Jun 2011 10:35:46 +0000
Message-ID: <D3DA739E-B25A-4AF9-A524-CA84362F39F3@nominet.org.uk>
References: <20110621035220.13199.qmail@joyce.lan> <p0624060dca25d4aa0695@loud.pensive.org> <4E009652.1020503@viagenie.ca> <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk> <4E00A026.2080208@wierenga.net>
In-Reply-To: <4E00A026.2080208@wierenga.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5694ade8-254b-4787-b62a-ef070eda926b>
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, 22 Jun 2011 10:37:07 -0000

On 21 Jun 2011, at 14:44, Klaas Wierenga wrote:

> otoh, not having to go through US immigrations saves you about as much
> time as you would have saved with a direct flight, not to mention the
> "terrorist until proven innocent" treatment..... ;-)

Thus far I've been lucky with the TSA and found them courteous and reasonab=
ly efficient.

The longest queue by far I've ever had for immigration was at Vancouver for=
 IETF70, where the shape of the queueing system coincidentally resembled th=
e Hilbert space-filling curves we were playing with at the time.
=20
I am slightly concerned about the relatively short time for my connection a=
t YUL, though - I've only got 1h05 between scheduled landing from LHR and t=
he hop out to YQB.

Ray




From Ray.Bellis@nominet.org.uk  Wed Jun 22 03:42:37 2011
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 CD64811E80CF for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 03:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.098
X-Spam-Level: 
X-Spam-Status: No, score=-10.098 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q5icRsufyIS9 for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 03:42:37 -0700 (PDT)
Received: from mx4.nominet.org.uk (mail.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id 10FEF11E8076 for <ietf@ietf.org>; Wed, 22 Jun 2011 03:42:36 -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:Content-Type: MIME-Version; b=m3QtwcBmw0rzBbPQk3/wotsfHnRthG89F/nKQUcIP6aplOzk6fJPbfES oW6jrSdz4ekEyw0RKKO/xyon52whr+5rzIIa9gIwqBsr+zmwKqwBSpmiq xMItQ2oSzr4aNkk;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1308739357; x=1340275357; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20My=20Internet=20experience=20in=20the =20West=20at=20times=20is=20comparable=20to=0D=0A=20femal e=09foeticide|Date:=20Wed,=2022=20Jun=202011=2010:39:55 =20+0000|Message-ID:=20<94F16EB4-F62D-40BA-8512-4B320F63C B80@nominet.org.uk>|To:=20Krishna=20Birth=20<krishnabirth @gmail.com>|CC:=20"<ietf@ietf.org>"=20<ietf@ietf.org> |MIME-Version:=201.0|In-Reply-To:=20<BANLkTimdzZ_4d49P5Ez Wg+bgWFn+7fPgYw@mail.gmail.com>|References:=20<BANLkTimdz Z_4d49P5EzWg+bgWFn+7fPgYw@mail.gmail.com>; bh=idoSvrK0KNHibVOwn5Nij5Reg2Pj/nTuSC0nKq7gRX4=; b=h3rIfJNVLXnRgfd8HLpg3trJYcIin47aDEuQpnkZmOltv4AxjyAIAXdI Vi7Zr0j54Ch9P2k/ubR/L/tCBeXPBRdDPvMAFd6zqY7hm4Pz0QpjuaAlV Kfl6kfBR2gaiIdr;
X-IronPort-AV: E=Sophos;i="4.65,405,1304290800"; d="scan'208,217";a="26942118"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx4.nominet.org.uk with ESMTP; 22 Jun 2011 11:39:57 +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%19]) with mapi; Wed, 22 Jun 2011 11:39:57 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Krishna Birth <krishnabirth@gmail.com>
Subject: Re: My Internet experience in the West at times is comparable to female	foeticide
Thread-Topic: My Internet experience in the West at times is comparable to female	foeticide
Thread-Index: AQHMMLraQRgkGGE2tUivkhOzf8tjRJTJHzmA
Date: Wed, 22 Jun 2011 10:39:55 +0000
Message-ID: <94F16EB4-F62D-40BA-8512-4B320F63CB80@nominet.org.uk>
References: <BANLkTimdzZ_4d49P5EzWg+bgWFn+7fPgYw@mail.gmail.com>
In-Reply-To: <BANLkTimdzZ_4d49P5EzWg+bgWFn+7fPgYw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_94F16EB4F62D40BA85124B320F63CB80nominetorguk_"
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, 22 Jun 2011 10:42:37 -0000

--_000_94F16EB4F62D40BA85124B320F63CB80nominetorguk_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


On 22 Jun 2011, at 09:59, Krishna Birth wrote:

Some not all internet forums/mailing list organisers need some
educating and need to educate others for example by having some
by-laws and rules so that I am treated without these problems.

Oh, but they do!

The most common rule being that postings are *ON TOPIC*

Ray


--_000_94F16EB4F62D40BA85124B320F63CB80nominetorguk_
Content-Type: text/html; charset="us-ascii"
Content-ID: <2570b4b1-9737-4158-998c-50072683782d>
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -we=
bkit-line-break: after-white-space; "><br><div><div>On 22 Jun 2011, at 09:5=
9, Krishna Birth wrote:</div><blockquote type=3D"cite"><div><font class=3D"=
Apple-style-span" color=3D"#000000"><br></font>Some not all internet forums=
/mailing list organisers need some<br>educating and need to educate others =
for example by having some<br>by-laws and rules so that I am treated withou=
t these problems.<br></div></blockquote></div><br><div>Oh, but they do!</di=
v><div><br></div><div>The most common rule being that postings are *ON TOPI=
C*</div><div><br></div><div>Ray</div><div><br></div></body></html>=

--_000_94F16EB4F62D40BA85124B320F63CB80nominetorguk_--

From scott.brim@gmail.com  Wed Jun 22 05:53:42 2011
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 458C911E811A for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 05:53:42 -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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2NubP3Yxlxzi for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 05:53:37 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 956C711E810B for <ietf@ietf.org>; Wed, 22 Jun 2011 05:53:37 -0700 (PDT)
Received: by iwn39 with SMTP id 39so908967iwn.31 for <ietf@ietf.org>; Wed, 22 Jun 2011 05:53:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=J4i3prXYcJu3Hs8BEQ2G+Nc11r+HLSjInt5OsoaDhH4=; b=cB0SRCfMuGZ1XsWlApTmhjp6MsqcIQIwNfXadE63hiGaybHv2jKNqyEDaWZ++tF3IQ 9ilwGkQylJ76S/Ph9q23t3ViShIyw+nZQ50vwC5T38fJ+vMte6nCqWOLVF4VLZo4JSCf eCEey49MW/dvsYJSVxu0OTXKVcOa1N0QmESUs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=LqsTCIVYsdDmJREp5W6UkFl2G9lrcRSX3F9rNYGLpbLUTdU6UMVyVca96mD6djHNxz hOaSXGMkAvMgvQXtKBrmPYM4V7xP2k4J5/00BEJdBE8zOCEk/fRT08sfNLmnH8VDPBxW Mbqkp3HaF5ARs/pZhuFCC4O0kAWH9YSihNK08=
Received: by 10.231.203.132 with SMTP id fi4mr619280ibb.69.1308747217067; Wed, 22 Jun 2011 05:53:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.15.198 with HTTP; Wed, 22 Jun 2011 05:53:17 -0700 (PDT)
In-Reply-To: <D3DA739E-B25A-4AF9-A524-CA84362F39F3@nominet.org.uk>
References: <20110621035220.13199.qmail@joyce.lan> <p0624060dca25d4aa0695@loud.pensive.org> <4E009652.1020503@viagenie.ca> <EEC3E51C-E295-4A6D-935D-1D4346F222B6@nominet.org.uk> <4E00A026.2080208@wierenga.net> <D3DA739E-B25A-4AF9-A524-CA84362F39F3@nominet.org.uk>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 22 Jun 2011 08:53:17 -0400
Message-ID: <BANLkTinvXpqyjYaNE2pA4sA9wVo0yHAm4Q@mail.gmail.com>
Subject: Re: whine, whine, whine
To: Ray Bellis <Ray.Bellis@nominet.org.uk>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, Klaas Wierenga <klaas@wierenga.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, 22 Jun 2011 12:53:42 -0000

On Wed, Jun 22, 2011 at 06:35, Ray Bellis <Ray.Bellis@nominet.org.uk> wrote:
> I am slightly concerned about the relatively short time for my connection at YUL, though - I've only got 1h05 between scheduled landing from LHR and the hop out to YQB.

First I think you'll make it, but second I would not be too concerned,
apparently there are 15 flights on Sunday.

From dave@cridland.net  Wed Jun 22 06:00:03 2011
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 AB42C11E813C for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 06:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.364
X-Spam-Level: 
X-Spam-Status: No, score=-2.364 tagged_above=-999 required=5 tests=[AWL=0.235,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lcy2246ZHDIL for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 06:00:03 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [IPv6:2001:470:1f09:882:2e0:81ff:fe29:d16a]) by ietfa.amsl.com (Postfix) with ESMTP id 1190E11E8139 for <ietf@ietf.org>; Wed, 22 Jun 2011 06:00:01 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 06BF91168087; Wed, 22 Jun 2011 13:59:52 +0100 (BST)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (peirce.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sqg0jT4HOUBS; Wed, 22 Jun 2011 13:59:49 +0100 (BST)
Received: from puncture (puncture.dave.cridland.net [IPv6:2001:470:1f09:882:221:85ff:fe3f:1696]) by peirce.dave.cridland.net (Postfix) with ESMTPA id BFDBE1168067; Wed, 22 Jun 2011 13:59:49 +0100 (BST)
Subject: Re: My Internet experience in the West at times is comparable to female foeticide
References: <BANLkTimdzZ_4d49P5EzWg+bgWFn+7fPgYw@mail.gmail.com>
In-Reply-To: <BANLkTimdzZ_4d49P5EzWg+bgWFn+7fPgYw@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <4898.1308747589.737163@puncture>
Date: Wed, 22 Jun 2011 13:59:49 +0100
From: Dave Cridland <dave@cridland.net>
To: Krishna Birth <krishnabirth@gmail.com>, IETF-Discussion <ietf@ietf.org>
Content-Type: text/plain; delsp="yes"; 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, 22 Jun 2011 13:00:03 -0000

On Wed Jun 22 09:59:14 2011, Krishna Birth wrote:
> Swlug (South Wales) has banned my posting to it's Linux group,

You were banned there because your posts were (very) off-topic,  
you're not local to South Wales, and finally because we felt like it  
- you have no particular right to post to SWLUG's mailing list, after  
all.

HTH,

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From mathieu.goessens@irisa.fr  Wed Jun 22 06:21:18 2011
Return-Path: <mathieu.goessens@irisa.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 73F7A11E8163 for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 06:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.76
X-Spam-Level: 
X-Spam-Status: No, score=-8.76 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r9Ks--byquWo for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 06:21:17 -0700 (PDT)
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by ietfa.amsl.com (Postfix) with ESMTP id EF8F311E80D4 for <ietf@ietf.org>; Wed, 22 Jun 2011 06:21:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.65,406,1304287200"; d="scan'208";a="97247648"
Received: from arkintoofle.irisa.fr (HELO [131.254.12.159]) ([131.254.12.159]) by mail2-relais-roc.national.inria.fr with ESMTP; 22 Jun 2011 15:21:10 +0200
Message-ID: <4E01EC46.20406@irisa.fr>
Date: Wed, 22 Jun 2011 15:21:10 +0200
From: Mathieu Goessens <mathieu.goessens@irisa.fr>
Organization: IRISA
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20110506 Iceowl/1.0b1 Icedove/3.0.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: tools.ietf.org problem with RFC-to-be6282 (AUTH48)
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, 22 Jun 2011 13:21:18 -0000

Hi folks,

http://tools.ietf.org/html/draft-ietf-6lowpan-hc-15 has a link to 
RFC-to-be as the document looks in AUTH48 phrase:

http://tools.ietf.org/rfcmarkup?rfc-repository=http://www.rfc-editor.org/authors&doc=rfc6282&topmenu=true&document=draft-ietf-6lowpan-hc-15&docreplaces=draft-ietf-6lowpan-hc-15&title=RFC-EDITOR+AUTH48+REVIEW+COPY&extrastyle=body+{background-color:%23fee%3b}

This link is not working and outputs a python error.

Best regards,

-- 
Mathieu Goessens,
IRISA, Campus de Beaulieu, 35042 Rennes cedex, France
Tel: +33 (0) 2 99 84 71 00, Fax: +33 (0) 2 99 84 71 71

From tytso@thunk.org  Wed Jun 22 06:30:26 2011
Return-Path: <tytso@thunk.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 2447211E8100 for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 06:30:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.343
X-Spam-Level: 
X-Spam-Status: No, score=-1.343 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yiUUE-YjUw34 for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 06:30:25 -0700 (PDT)
Received: from test.thunk.org (li9-11.members.linode.com [67.18.176.11]) by ietfa.amsl.com (Postfix) with ESMTP id 5617311E808D for <ietf@ietf.org>; Wed, 22 Jun 2011 06:30:25 -0700 (PDT)
Received: from root (helo=tytso-glaptop) by test.thunk.org with local-esmtp (Exim 4.69) (envelope-from <tytso@thunk.org>) id 1QZNVf-0005QO-1q; Wed, 22 Jun 2011 13:30:23 +0000
Received: from tytso by tytso-glaptop with local (Exim 4.71) (envelope-from <tytso@thunk.org>) id 1QZNVd-0002yp-7T; Wed, 22 Jun 2011 09:30:21 -0400
Date: Wed, 22 Jun 2011 09:30:20 -0400
From: Ted Ts'o <tytso@mit.edu>
To: Dave Cridland <dave@cridland.net>
Subject: Re: My Internet experience in the West at times is comparable to female foeticide
Message-ID: <20110622133020.GJ32133@thunk.org>
References: <BANLkTimdzZ_4d49P5EzWg+bgWFn+7fPgYw@mail.gmail.com> <4898.1308747589.737163@puncture>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4898.1308747589.737163@puncture>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on test.thunk.org); SAEximRunCond expanded to false
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, 22 Jun 2011 13:30:26 -0000

On Wed, Jun 22, 2011 at 01:59:49PM +0100, Dave Cridland wrote:
> On Wed Jun 22 09:59:14 2011, Krishna Birth wrote:
> >Swlug (South Wales) has banned my posting to it's Linux group,
> 
> You were banned there because your posts were (very) off-topic,
> you're not local to South Wales, and finally because we felt like it
> - you have no particular right to post to SWLUG's mailing list,
> after all.

Furthermore, (putting on my IETF's Sargeant at Arms hat) Krishna's
complaint isn't on-topic for the IETF list, either.

     	       		       		- Ted

From mstjohns@comcast.net  Wed Jun 22 08:12:00 2011
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A738711E80A9 for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 08:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.98
X-Spam-Level: 
X-Spam-Status: No, score=-101.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b2nfW-cSRpja for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 08:12:00 -0700 (PDT)
Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by ietfa.amsl.com (Postfix) with ESMTP id 33A2211E80A3 for <ietf@ietf.org>; Wed, 22 Jun 2011 08:12:00 -0700 (PDT)
Received: from omta03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by qmta07.emeryville.ca.mail.comcast.net with comcast id z3971g0060b6N64A73By07; Wed, 22 Jun 2011 15:11:58 +0000
Received: from Mike-PC3.comcast.net ([217.41.228.182]) by omta03.emeryville.ca.mail.comcast.net with comcast id z3BZ1g00C3wlb3t8P3BiU5; Wed, 22 Jun 2011 15:11:53 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 22 Jun 2011 11:11:33 -0400
To: ietf@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: External IPR Disclosures vs IPR disclosures in the document.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20110622151200.33A2211E80A3@ietfa.amsl.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 15:12:00 -0000

A quick couple of questions to the list based on a document I saw recently.

If a document (an ID in this case) contains encumbered material (in this case consists of 90%+ encumbered material), and the document is authored by the organization (or members of the organization) that holds the encumbrance, should the document contain an IPR disclosure itself or is it sufficient to submit a IPR disclosure through the IETF web interface?  

Should the ID Nits tool check for the inclusion of the notices for IPR required by section 5.1 of RFC 3978?

If a document contains primarily encumbered material, is authored by the owner of the encumbered material or its employees and is a non-work group document, is it appropriate to tag such document as "Intended Status: Standards Track"? 

For the first question, RFC3979 appears to say no.  However, I'm not sure the specific case I cite was considered.

For the last question - my guess is that it depends - specifically on the grant of license for the encumbered material and whether or not there are alternatives.  Given that, would RAND terms be sufficient in any case to advance this as a standard?

Thanks - Mike



From john-ietf@jck.com  Wed Jun 22 08:30:47 2011
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 3B70C21F8479 for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 08:30:47 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YLBOUoMdQ1Kz for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 08:30:46 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 20D3921F8478 for <ietf@ietf.org>; Wed, 22 Jun 2011 08:30:46 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QZPO8-0009NX-DN; Wed, 22 Jun 2011 11:30:44 -0400
Date: Wed, 22 Jun 2011 11:30:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael StJohns <mstjohns@comcast.net>, ietf@ietf.org
Subject: Re: External IPR Disclosures vs IPR disclosures in the document.
Message-ID: <8BD7D6CD45A8193E00E63AA7@PST.JCK.COM>
In-Reply-To: <20110622151200.33A2211E80A3@ietfa.amsl.com>
References: <20110622151200.33A2211E80A3@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: Wed, 22 Jun 2011 15:30:47 -0000

Mike,

Answer from a 10Km altitude perspective...

Our rules do not have dependencies on particular licensing
terms, whether RAND, free license, free without any notification
or specific license, defensive/reciprocal, or otherwise.   The
obligation of authors and companies is to disclose whatever it
is they need to disclose and, optionally whatever licensing
terms they feel they want to disclose along with it.  After
that, it is up to the WG and, ultimately, the community on Last
Call.   Absolutely nothing in the rules would prohibit us from
standardizing a technology that requires an expensive license,
negotiated on an individual basis and with no promises of fair
or equitable treatment for license applicants.  

In practice, I have doubts that any technology with those sorts
of restrictions would actually be standardized by the IETF
community, but there is no formal bar to trying (or to
identifying an I-D with an intended Standards-Track status).

  john


--On Wednesday, June 22, 2011 11:11 -0400 Michael StJohns
<mstjohns@comcast.net> wrote:

> A quick couple of questions to the list based on a document I
> saw recently.
> 
> If a document (an ID in this case) contains encumbered
> material (in this case consists of 90%+ encumbered material),
> and the document is authored by the organization (or members
> of the organization) that holds the encumbrance, should the
> document contain an IPR disclosure itself or is it sufficient
> to submit a IPR disclosure through the IETF web interface?  
> 
> Should the ID Nits tool check for the inclusion of the notices
> for IPR required by section 5.1 of RFC 3978?
> 
> If a document contains primarily encumbered material, is
> authored by the owner of the encumbered material or its
> employees and is a non-work group document, is it appropriate
> to tag such document as "Intended Status: Standards Track"? 
> 
> For the first question, RFC3979 appears to say no.  However,
> I'm not sure the specific case I cite was considered.
> 
> For the last question - my guess is that it depends -
> specifically on the grant of license for the encumbered
> material and whether or not there are alternatives.  Given
> that, would RAND terms be sufficient in any case to advance
> this as a standard?
> 
> Thanks - Mike
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf





From johnl@iecc.com  Wed Jun 22 08:37:17 2011
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 5065911E80BC for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 08:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.512
X-Spam-Level: 
X-Spam-Status: No, score=-110.512 tagged_above=-999 required=5 tests=[AWL=0.687, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mWezs5ZaEADC for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 08:37:16 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id 1E25711E80B2 for <ietf@ietf.org>; Wed, 22 Jun 2011 08:37:15 -0700 (PDT)
Received: (qmail 64009 invoked from network); 22 Jun 2011 15:37:13 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 22 Jun 2011 15:37:13 -0000
Date: 22 Jun 2011 15:36:51 -0000
Message-ID: <20110622153651.20782.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: whine, whine, whine
In-Reply-To: <D3DA739E-B25A-4AF9-A524-CA84362F39F3@nominet.org.uk>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 15:37:17 -0000

>I am slightly concerned about the relatively short time for my
>connection at YUL, though - I've only got 1h05 between scheduled
>landing from LHR and the hop out to YQB.

I presume you're coming in on the BA flight, since that's the only one
that has a 1:05 connection.  If you miss the 21:00 flight, there's a
23:00.  If the later flight is full, which seems unlikely since it's
currently showing more than 9 available seats, you can take the 21:45
bus.

R's,
John

From scott.brim@gmail.com  Wed Jun 22 08:42:53 2011
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 2A12E11E80BD for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 08:42: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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FsfBiB5oMQYz for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 08:42:52 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 99FCC11E809F for <ietf@ietf.org>; Wed, 22 Jun 2011 08:42:52 -0700 (PDT)
Received: by iye7 with SMTP id 7so1082891iye.31 for <ietf@ietf.org>; Wed, 22 Jun 2011 08:42:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=rd6c7ILrsD55Se3f2olkhqgE6LNrBOHXxAyfX5AyPmE=; b=kOCi+xaxp7B2/wdvKN1Jalgjjgs2JUcWzPr7Pm6zkJndQHefjWe6gY8zi27P7Dl6Li n3A1zMF5sgfZZKT1KRCWbaXdZtzrLHOB7JU8LeSuGL5bu/B3lYXIlGo5LRpEv9Ytvg3E IS4rmaLWZtNgoXop5pnS/s8p+Ro8AFh/fBBEQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=nAek2VwepJOmQnczWg/SvYpqQWdhEsMX637eJO4/TCBgO68ecNkfuXoj4+ZVuw+zSu wMU5CImuvGhDBVO0MleiErb+7khU8qo54jHGyL4OqWd8iDEcAP1SJvnYjK9mbtG7c+kC PjGYicvTX75wTEp6lXpiN2kPKvyU4QefC7xFg=
Received: by 10.43.49.130 with SMTP id va2mr817432icb.428.1308757372094; Wed, 22 Jun 2011 08:42:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.15.198 with HTTP; Wed, 22 Jun 2011 08:42:31 -0700 (PDT)
In-Reply-To: <20110622151200.33A2211E80A3@ietfa.amsl.com>
References: <20110622151200.33A2211E80A3@ietfa.amsl.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 22 Jun 2011 11:42:31 -0400
Message-ID: <BANLkTi=T0ze_EuE3sZ1Yec5ARSRQN4A6xA@mail.gmail.com>
Subject: Re: External IPR Disclosures vs IPR disclosures in the document.
To: Michael StJohns <mstjohns@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 15:42:53 -0000

On Wed, Jun 22, 2011 at 11:11, Michael StJohns <mstjohns@comcast.net> wrote=
:
> A quick couple of questions to the list based on a document I saw recentl=
y.
>
> If a document (an ID in this case) contains encumbered material (in this =
case consists of 90%+ encumbered material), and the document is authored by=
 the organization (or members of the organization) that holds the encumbran=
ce, should the document contain an IPR disclosure itself or is it sufficien=
t to submit a IPR disclosure through the IETF web interface?

IPR statements are never put in RFCs unless on occasion they are
informational transplants from outside.  The IPR claims or other
aspects might change over time and the right place to track all that
is in the IPR disclosures.

> Should the ID Nits tool check for the inclusion of the notices for IPR re=
quired by section 5.1 of RFC 3978?

IMHO that would be good.

> If a document contains primarily encumbered material, is authored by the =
owner of the encumbered material or its employees and is a non-work group d=
ocument, is it appropriate to tag such document as "Intended Status: Standa=
rds Track"?

As John says, we don't have any rules about what IPR is acceptable,
and actual practice depends on the WG and the situation.  In one case
terms were accepted because the patents were to expire in 2-3 years.
RFC3669 is pretty old but might still be a useful read.

Scott

From ot@cisco.com  Wed Jun 22 03:16:56 2011
Return-Path: <ot@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 41CE111E80DB; Wed, 22 Jun 2011 03:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O2+eh0ko8bYt; Wed, 22 Jun 2011 03:16:55 -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 0650A11E80CF; Wed, 22 Jun 2011 03:16:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=2875; q=dns/txt; s=iport; t=1308737815; x=1309947415; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=95F6SG1wQ8nAyw6TlorXsW8PEKTAgt8tfjjIgVA5CVM=; b=elyDQ9tgVP2q4f21TTLWVur0Socu4ylqTJI/o0VDVzEZpExWiWffO7Yf H+xkJSt9y93CKb8EeovVnIT8wmFp5Kh1aacCSxzs+ggPDmQAzl5cN6PyQ w0gdtxZpUd38mjh0VdX8epVPPuDJc8A+U2SQsxUtsJ2dHqlzU7NgiFWR0 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAIvAAU6Q/khR/2dsb2JhbABUpw53iHOhDJ5Ahi0EkWqQDg
X-IronPort-AV: E=Sophos;i="4.65,405,1304294400"; d="scan'208";a="95896028"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 22 Jun 2011 10:16:23 +0000
Received: from dhcp-osl-vl300-64-103-53-166.cisco.com (dhcp-osl-vl300-64-103-53-166.cisco.com [64.103.53.166]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p5MAGNlm021263; Wed, 22 Jun 2011 10:16:23 GMT
Subject: Re: Gen-ART LC Review of draft-ietf-v6ops-6to4-to-historic-04
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <AE70A313-F36C-4870-A0E8-8F3172F35D53@nostrum.com>
Date: Wed, 22 Jun 2011 12:16:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B5436E8-50C4-45F8-AEC9-56A2C14F19DC@cisco.com>
References: <AE70A313-F36C-4870-A0E8-8F3172F35D53@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Wed, 22 Jun 2011 08:46:50 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-v6ops-6to4-to-historic.all@tools.ietf.org, The 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, 22 Jun 2011 10:16:56 -0000

Ben,

splendid comments! I've tried to incorporate all of them, and will =
either issue a new revision or make the changes during AUTH48 depending =
on other LC feedback.

cheers,
Ole

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document: draft-ietf-v6ops-6to4-to-historic-04
> Reviewer: Ben Campbell
> Review Date: 2011-06-17
> IETF LC End Date: 2011-06-20
> IESG Telechat date: 2011-06-23
>=20
> Summary:
>=20
> The draft is essentially ready for publication as an informational =
RFC. I have a few editorial comments that may be worth considering prior =
to final publication.
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:
>=20
> -- general:=20
>=20
> Idnits reports some potential issues. please check.
>=20
> -- abstract:
>=20
> The headers say this draft obsoletes these RFCs. Does moving to =
historical obsolete then in that sense? Perhaps the abstract should say =
something like "obsoletes, and moves to historical"
>=20
> -- section 1, 2nd paragraph: "...designed to help transitioning the =
Internet..."
>=20
> Help transition, help in transitioning, or help the transition of
>=20
> -- section 1, last paragraph:
>=20
> Please expand 6rd on first mention. Also, Is this meant as an explicit =
recommendation of 6rd as an alternative?
>=20
> -- section 3, third paragraph: "...same operational burden has =
manually configured tunnels..."
>=20
> s/has/as
>=20
> -- section 3, first bullet: "... and in the case the relay is =
overloaded packet loss."
>=20
> "overloaded, packet loss."
>=20
> -- section 3, third bullet: "...customer relationship or..."
>=20
> "... customer relationship between the end-user and the relay =
operator, or..."
>=20
> -- section 3, 4th bullet: "In case of the reverse path 6to4 relay and =
the anycast forward 6to4 relay, these have to be open for any address. =
Only limited by the scope of the routing advertisement. "
>=20
> Awkward sentence followed by a sentence fragment. Can these be =
reworded?
>=20
> -- section 3, 5th bullet: "black hole"
>=20
> Please define "black hole" in this context, or use a more descriptive =
(I.e. less jargony) term.
>=20
>=20
> -- section 4, 2nd paragraph: "It is expected that disabling 6to4 in =
the IPv6 Internet will take some time."
>=20
> Who expects it? The IETF? v6ops? The authors? (or can we just drop "It =
is expected that")
>=20
> "...deploy native IPv6 service."
>=20
> s/service/services
>=20
> -- section 4, numbered list:
>=20
> It's not clear to me why this is a numbered list rather than an =
ordinary paragraph
>=20


From paulej@packetizer.com  Wed Jun 22 09:05:00 2011
Return-Path: <paulej@packetizer.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCB281F0C49 for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 09:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.266
X-Spam-Level: 
X-Spam-Status: No, score=-4.266 tagged_above=-999 required=5 tests=[AWL=-1.667, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AYeze8m06wqI for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 09:04:59 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 97F8D1F0C42 for <ietf@ietf.org>; Wed, 22 Jun 2011 09:04:59 -0700 (PDT)
Received: from sydney (rrcs-98-101-155-83.midsouth.biz.rr.com [98.101.155.83]) (authenticated bits=0) by dublin.packetizer.com (8.14.4/8.14.4) with ESMTP id p5MG4oG6024555 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 22 Jun 2011 12:04:56 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1308758696; bh=1V0ERR4eK+mgF6aMFsZuWEMiKoEkDatVCiW77PlvFlM=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=Xr0DaZFjUStMIieQKFgzVM6KhXw7aVx+KSumklcy3yiX9TBQr3PPV04ejFW2IX2wA 5LXjWyplcYBom+x1FqhDq+zSgLg6YZf8j/XL5v2RAscMD2ZxFSbYnCNLqWH0g/43Wo +ELxrUNAMNDCm8LyhSvQNfu0ZggH8eRfCFym2kR4=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Mark Nottingham'" <mnot@mnot.net>, <ietf@ietf.org>
References: <11CBFBA2-434B-43FC-90C4-DADBACB49226@mnot.net>
In-Reply-To: <11CBFBA2-434B-43FC-90C4-DADBACB49226@mnot.net>
Subject: RE: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host	Metadata)	to Proposed Standard -- feedback
Date: Wed, 22 Jun 2011 12:04:30 -0400
Message-ID: <05c701cc30f6$15841ed0$408c5c70$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIqGTK7xRIbMRtQfVSY6K9+ohMDaZQNnsvQ
Content-Language: en-us
Cc: 'Eran Hammer-Lahav' <eran@hueniverse.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, 22 Jun 2011 16:05:00 -0000

Mark,

> Generally, it's hard for me to be enthusiastic about this proposal, for
> a few reasons. That doesn't mean it shouldn't be published, but I do
> question the need for it to be Standards Track as a general mechanism.

I believe standards track is appropriate, since the objective is to define
procedures that are interoperable and the specification defines a set of
procedures that would be implemented by multiple software products.

> Mostly, it's because I hasn't really seen much discussion of it as a
> general component of the Web / Internet architecture; AFAICT all of the
> interest in it and discussion of it has happened in more specialised /
> vertical places. The issues below are my concerns; they're not
> insurmountable, but I would have expected to see some discussion of them
> to date on lists like this one and/or the TAG list for something that's
> to be an Internet Standard.

You might be right that more discussion has happened off the apps-discuss
list, but I would not equate that with not being a component of the web
architecture.  On the contrary, host-meta has a lot of utility and is an
important building block for the web architecture.  With host-meta, it is
possible to advertise information in a standard way, discover services, etc.
Some of the latter is not fully defined, but cannot be defined without this
standard in place.

> * XRD -- XRD is an OASIS spec that's used by OpenID and OAuth. Maybe I'm
> just scarred by WS-*, but it seems very over-engineered for what it
> does. I understand that the communities had reasons for using it to
> leverage an existing user base for their specific user cases, but I
> don't see any reason to generalise such a beast into a generic
> mechanism.

XRD is not complicated.  It's an XML document spec with about seven elements
defined.  In order to convey metadata, one must have some format defined and
XRD is as good as any other.  I don't think the use of XRD should be
considered as negative aspect.  OpenID uses (through Yadis) a precursor to
XRD called XRDS. I'm not sure about Oauth's usage of XRD.  Either way, does
this matter?

> * Precedence -- In my experience one of the most difficult parts of a
> metadata framework like this is specifying the combination of metadata
> from multiple sources in a way that's usable, complete and clear.
> Hostmeta only briefly mentions precedence rules in the introduction.

I assume you are referring to the processing rules in 1.1.1?  How would you
propose strengthening that text?
 
> * Scope of hosts -- The document doesn't crisply define what a "host"
> is.

This might be deliberate and not really fault of this document.  The
"hostname" that we are all used to using for a "host" may or may not refer
to a physical host.  It might refer to a virtual host or a virtually hosted
domain.  In any case, this term is consistent with the term used on the HTTP
spec and the header line "Host:".

> * Context of metadata -- I've become convinced that the most successful
> uses of .well-known URIs are those that have commonality of use; i.e.,
> it makes sense to define a .well-known URI when most of the data
> returned is applicable to a particular use case or set of use cases.
> This is why robots.txt works well, as do most other currently-deployed
> examples of well-known URIs.
> 
> Defining a bucket for potentially random, unassociated metadata in a
> single URI is, IMO, asking for trouble; if it is successful, it could
> cause administrative issues on the server (as potentially many parties
> will need control of a single file, for different uses -- tricky when
> ordering is important for precedence), and if the file gets big, it will
> cause performance issues for some use cases.

All of the use cases are not defined, but the host-meta document provides
some examples, such as finding the author of a web page, copyright
information, etc.  There has been discussion of finding a user's identity
provider.  The particular uses.  Each of these examples fits well within the
host-meta framework.  It builds upon the "web linking" (RFC 5988) work you
did in a logical and consistent way, and I see these as complementary
documents.  To your concern, host-meta is flexible, but the functionality is
bounded.
 
> * Chattiness -- the basic model for resource-specfic metadata in
> hostmeta requires at least two requests; one to get the hostmeta
> document, and one to get the resource-specific metadata after
> interpolating the URI of interest into a template.

This is true, but the web is all about establishing links to other
information.  I view this is a "good thing" about host-meta: it provides a
very simple syntax with a way to use well-defined link relation types to
discover other information.
 
> For some use cases, this might be appropriate; however, for many others
> (most that I have encountered), it's far too chatty. Many use cases find
> the latency of one extra request unacceptable, much less two. Many use
> cases require fetching metadata for a number of distinct resources; in
> this model, that adds a request per resource.

I think this comes back to use whatever makes most sense for the job.
Consider robots.txt for example.  We could define a "robots" link relation
and query the robots.txt file in a two-step operation, or we can just fetch
it from the well-known location.  A well-known location works fine for
robots.txt, but it does not work well for everything.  The examples of
fetching copyright information or author information are examples.  The
point is that host-meta provides a mechanism for discovering information
about a URI.  This is very useful, IMO.
 
> I'd expect a general solution in this space to allow describing a "map"
> of a Web site and applying metadata to it in arbitrary ways, so that a
> client could fetch the document once and determine the metadata for any
> given resource by examining it.

But what of URIs that do not refer to a document?  One could learn a lot of
metadata about a specific document following RFC 5988, but that does not
work for URIs like "mailto:paulej@packetizer.com" or any non-'http[s]' URI
scheme used.  Even for some URIs that use http[s] as the scheme, there may
or may not be an associated document.  Host-meta could allow one to get
meta-data about any valid URI for a domain.
 
> If hostmeta is designed for specific use cases and meets them well,
> that's great, but it shouldn't be sold as a general mechanism. So, I'm -
> 1 on this going forward as a standards-track general mechanism. I
> wouldn't mind if it were Informational, or if it were Standards-Track
> but with a defined use case.

Perhaps one could have made the same kind of argument about HTTP.  It is a
general mechanism for fetching documents, files, or any data from a
location.  This document is similar, but with a focus on providing metadata
about URIs.  I think the procedures are useful and the document should go
forward as a standards track RFC.

Paul



From wwwrun@ietfa.amsl.com  Wed Jun 22 09:19:01 2011
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id 2B2911F0C52; Wed, 22 Jun 2011 09:19:01 -0700 (PDT)
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: Google to Host IETF Meeting 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110622161901.2B2911F0C52@ietfa.amsl.com>
Date: Wed, 22 Jun 2011 09:19:01 -0700 (PDT)
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 16:19:01 -0000

The IAOC and the Internet Society are very pleased to announce that Google will be be the Host for IETF 84
in Vancouver in 2012.  Google most recently was the Host for IETF 73 in Minneapolis in 2008.

We want to thank our benefactors.  The IETF cannot support its technical standards efforts, including the 
Secretariat and RFC Editor, without the generous support of its hosts and sponsors.

Been thinking about hosting or sponsoring a future meeting?  The meetings calendar through 2017 
<www.ietf.org/meetings/0mtg-sites.txt> shows some of the possibilities. Just send Drew Dvorshak an
email at dvorshak@isoc.org and he can walk you through the opportunity. 

Thanks again Google!  We couldn't do it without you.
 
Hope to see you in Quebec City at IETF 81in 31 days!  More than 500 are currently registered.
Registration is still open!  http://www.ietf.org/meeting/81/index.html

Ray Pelletier
IETF Administrative Director

From msk@cloudmark.com  Wed Jun 22 10:17:19 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09E1911E80AE for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 10:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.566
X-Spam-Level: 
X-Spam-Status: No, score=-103.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9KC1sff+2Fm for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 10:17:18 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB1711E807E for <ietf@ietf.org>; Wed, 22 Jun 2011 10:17:18 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Wed, 22 Jun 2011 10:17:17 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Douglas Otis <dotis@mail-abuse.org>, "ietf@ietf.org" <ietf@ietf.org>, Barry Leiba <barryleiba@computer.org>, Sean Turner <turners@ieca.com>
Date: Wed, 22 Jun 2011 10:17:16 -0700
Subject: RE: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified	Mail (DKIM) Signatures) to Draft Standard
Thread-Topic: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified	Mail (DKIM) Signatures) to Draft Standard
Thread-Index: Acwwf7uoLsjtmsFeR3u6FXSdbcaQUAAf/arA
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC494F@EXCH-C2.corp.cloudmark.com>
References: <4E014A76.5090805@mail-abuse.org>
In-Reply-To: <4E014A76.5090805@mail-abuse.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 17:17:19 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of D=
ouglas Otis
> Sent: Tuesday, June 21, 2011 6:51 PM
> To: ietf@ietf.org; Barry Leiba; iesg-secretary@ietf.org; Sean Turner
> Subject: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Ident=
ified Mail (DKIM) Signatures) to Draft Standard
>=20
> [...]
>=20
> This indicates the DKIM specification is seriously flawed.  While DKIM
> may not offer author validation, it was intended to establish an
> accountable domain for the signed message content that at a minimum
> includes the From header field.  There are NO valid reasons for a valid
> signature to include multiple From header fields!  Allowing multiple
> From header fields is _EVIL_ and destroys DKIM's intended purpose as
> defined by prior work.

This purported security flaw and surrounding FUD was discussed at huge leng=
th in the working group, and consensus was clearly against the idea of deal=
ing with this in DKIM because it's the wrong place to address the problem. =
 The record, both in the issues tracker and in the working group's archive,=
 is quite clear about this, and both are open to public scrutiny.

And I find the tactic of taking a lost battle from a working group to the I=
ETF as a whole to be akin to the "Mom said no, I'll go ask Dad!" strategy t=
hat I outgrew by the time I was a teenager...


From scott@kitterman.com  Wed Jun 22 10:28:11 2011
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 2F41C21F84C4 for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 10:28:11 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uxCSBIMspr5g for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 10:28:09 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 8F39721F84C3 for <ietf@ietf.org>; Wed, 22 Jun 2011 10:28:09 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id C3B7F20E40A3 for <ietf@ietf.org>; Wed, 22 Jun 2011 13:28:08 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1308763688; bh=ND0PgapmmRnT9B3x4iPrU20pXe+6DYDW/x003AxraRE=; h=From:To:Subject:Date:References:In-Reply-To:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=P+tlkIV3FxBs0R0m6/MgpmQ3/rn4NIOJFrAD3MvIQn/E1qrD6B3zreapTrLwKuE9J xT4C9hzx6wbPqEwjtDseELs4lVA2LI9P0AnnBZeO9gYyS1+HbdwYnFckCudQRZUNHo Zdhz9tqlSACLC8PwW9aUc7/Val+kl2uT/xIL+QJY=
Received: from kitterma-desktop.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPS id A51CC20E4089 for <ietf@ietf.org>; Wed, 22 Jun 2011 13:28:08 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
Organization: Kitterman Technical Services
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys  =?iso-8859-1?q?Identified=09Mail?= (DKIM) Signatures) to Draft Standard
Date: Wed, 22 Jun 2011 13:27:51 -0400
User-Agent: KMail/1.13.5 (Linux/2.6.32-32-generic; KDE/4.4.5; i686; ; )
References: <4E014A76.5090805@mail-abuse.org> <F5833273385BB34F99288B3648C4F06F134EBC494F@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134EBC494F@EXCH-C2.corp.cloudmark.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201106221327.51591.scott@kitterman.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: Wed, 22 Jun 2011 17:28:11 -0000

On Wednesday, June 22, 2011 01:17:16 pm Murray S. Kucherawy wrote:
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> > Douglas Otis Sent: Tuesday, June 21, 2011 6:51 PM
> > To: ietf@ietf.org; Barry Leiba; iesg-secretary@ietf.org; Sean Turner
> > Subject: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys
> > Identified Mail (DKIM) Signatures) to Draft Standard
> > 
> > [...]
> > 
> > This indicates the DKIM specification is seriously flawed.  While DKIM
> > may not offer author validation, it was intended to establish an
> > accountable domain for the signed message content that at a minimum
> > includes the From header field.  There are NO valid reasons for a valid
> > signature to include multiple From header fields!  Allowing multiple
> > From header fields is _EVIL_ and destroys DKIM's intended purpose as
> > defined by prior work.
> 
> This purported security flaw and surrounding FUD was discussed at huge
> length in the working group, and consensus was clearly against the idea of
> dealing with this in DKIM because it's the wrong place to address the
> problem.  The record, both in the issues tracker and in the working
> group's archive, is quite clear about this, and both are open to public
> scrutiny.
> 
> And I find the tactic of taking a lost battle from a working group to the
> IETF as a whole to be akin to the "Mom said no, I'll go ask Dad!" strategy
> that I outgrew by the time I was a teenager...

While I'm not thrilled by the post-4871 changes in general, I think on this 
point there's not an issue.  I recently worked through the multiple From case 
for a DKIM implementation I'm helping on and found sufficient guidance in RFC 
4871 to deal with it reasonably.  This was definitely beat to death in the WG.

Scott K

From dhc2@dcrocker.net  Wed Jun 22 11:14:52 2011
Return-Path: <dhc2@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 3CFE6228019; Wed, 22 Jun 2011 11:14: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdlxVpWZRwtm; Wed, 22 Jun 2011 11:14:46 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 85A1422800F; Wed, 22 Jun 2011 11:14:46 -0700 (PDT)
Received: from [192.168.1.7] (ppp-68-120-198-5.dsl.pltn13.pacbell.net [68.120.198.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p5MIEeFH015068 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 22 Jun 2011 11:14:45 -0700
Message-ID: <4E02310C.8060604@dcrocker.net>
Date: Wed, 22 Jun 2011 11:14:36 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified Mail (DKIM) Signatures) to Draft Standard
References: <4E014A76.5090805@mail-abuse.org>
In-Reply-To: <4E014A76.5090805@mail-abuse.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.17]); Wed, 22 Jun 2011 11:14:45 -0700 (PDT)
Cc: iesg <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 18:14:54 -0000

Folks,

The bottom line about Doug's note is that the working group extensively 
considered the basic issue of multiple From: header fields and Doug is raising 
nothing new about the topic.

A quick summary of the technical point at the core of Doug's concern is that the 
presence of multiple rfc5322.From header fields does appear to represent a 
plausible attack vector, but it also violates RFC5322 -- and RFC822, if anyone 
is worried about the history of this issue.  DKIM (RFC4871) requires that the 
signing engine be handed a valid RFC5322 message.  Hence the burden of ensuring 
that there is only one From: field rests outside DKIM.

For reference, Doug posted a related blog recently and I posted a response 
yesterday:

    <http://www.circleid.com/posts/searching_under_lampposts_with_dkim/>

Others are posting responses also. The Comment mechanism, to the Circleid 
article, is being used to list these additional responses.


Inline comments...


On 6/21/2011 6:50 PM, Douglas Otis wrote:But,
> RFC4686 Introduction states:
...
> While several threats to DKIM were considered, multiple From header fields were
> neglected. This document only focused on use of multiple addresses within the
>  From header field.

Any possible omissions in an Informational threats document -- done 6 years ago 
and before the signing specification (RFC4871) was written -- is of marginal 
relevance, at best.


> It should be noted that Signing Practices are referenced off a domain found in
> the From header field which also assumes only one will be present.

It also should be noted that Signing Practices (ADSP) issues are irrelevant to 
the candidate RFC4871bis effort, which pertains only to the signing specification.



> This indicates the DKIM specification is seriously flawed.

It indicates that there is an issue, not that it is DKIM's responsibility to 
solve it.


> While DKIM may notoffer author validation,

Does not.  Not may not.  It's a simple and direct fact.


 >    it was intended to establish an accountable domain for
> the signed message content that at a minimum includes the From header field.

And it does that.  But it does not make any assertions about the /validity/ of 
any of the data it signs, nevermind any of the data it does NOT sign.


> There are NO valid reasons for a valid signature to include multiple From header
> fields! Allowing multiple From header fields is _EVIL_ and destroys DKIM's
> intended purpose as defined by prior work.

It actually has no discernible effect on DKIM's utility, nor have there been 
reports from the field of problems in 6 years of deployed use.


> Free email providers likely use DKIM to gain increased acceptance by taking
> advantage of their "too big to block" volumes. For these domains, their
> reputation is understood to offer little assurance of their overall integrity
> while perhaps limiting what is allowed in the domain portion of the From header
> field.

This appears to be a political rant.


> By allowing a pre-pended From header field to not affect the validity of a DKIM
> signature according to the specification means the UNDERSTOOD source of a
> message can NEVER be trusted through the aid of DKIM.

That statement well might be correct, but that's OK, since DKIM does not make 
assertions about "source" validity, except in terms of the separate DKIM signing 
identifier (in the DKIM-Signature: header field.)  The signer is sometimes 
referred to as a source.  However DKIM makes no assertions concerning the Author 
or Originator [RFC5598].


> The general goal of DKIM cryptographically binding at a minimum the From header
> field of the message content to a domain was to act as a trust basis for
> acceptance.

The general goal is to attach an identifier than is reliable and valid, and it 
does that.  The identifier can be used for developing a reputation assessment of 
message streams signed with that identifier.


>  DKIM also purports to allow incremental deployment without requiring
> additional undefined filtering be introduced in mail transfer or mail user
> agents. Clearly, the incremental deployment statement conflicts with the
> original goals due to the neglected input validation flaw.

I have no idea what the above means.


> Details of this concern were stated in the tracker at:
> http://trac.tools.ietf.org/wg/dkim/trac/ticket/24

And it nicely shows that the working group considered the issue.


> This version of DKIM also introduced use of RFC5890 instead of RFC3490, which
> allows use of the German esset and the Greek final sigma, drops string-prep, and
> defines 3,329 invalid code points. Unfortunately, this version of the DKIM also
> failed to exclude use of Fake A-Labels, which when presented to the user may
> also prove highly deceptive.

Excellent.  Now it is also DKIM's job to fix problems with Unicode...


> Details of this concern were stated in the tracker at:
> http://trac.tools.ietf.org/wg/dkim/trac/ticket/24

wrong citation.


d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From krishnabirth@gmail.com  Wed Jun 22 12:48:36 2011
Return-Path: <krishnabirth@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E59B821F8498 for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 12:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.205
X-Spam-Level: 
X-Spam-Status: No, score=-3.205 tagged_above=-999 required=5 tests=[AWL=0.395,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oDVcfB3J6p1I for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 12:48:36 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 557E521F8495 for <ietf@ietf.org>; Wed, 22 Jun 2011 12:48:36 -0700 (PDT)
Received: by yxp4 with SMTP id 4so124665yxp.31 for <ietf@ietf.org>; Wed, 22 Jun 2011 12:48:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=LHzXL7gp7jPdB+LEu27Ny1m82GcJ7fHMnrfaXBXr6do=; b=SIG2oKO6+yMgRvCJO3rgsMdzg8AZiZstyaZhE8D8d5bwr8+fdthRiqcHatikNtkpwE m4aV3X9c0EphNCQ8eHTzWZmKE5jb3Mc6T9CAnetq+J2q5VUVQ4mt6FN+4VgDWaT/Ndp3 bE+Nll+R6Sc1m//raM5e/0o5AjDF8/evGNN6Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=f41phUUuoithLY4T65tVXB74TdoF0aYM4SfyA318FFDtN7N/k6lA6KlyfXEih+ZERO tN6jx47UVSFuaGi7nI5vEh6DYe02cO8zMFqLFIQZ52I5OJzvjfMyl+bztvO/DIbTxNuf K9QqRz0L/e6xQ6KtVo4wm14pOVbEV3JbrGZJg=
MIME-Version: 1.0
Received: by 10.236.173.7 with SMTP id u7mr1729783yhl.267.1308772115732; Wed, 22 Jun 2011 12:48:35 -0700 (PDT)
Received: by 10.236.154.225 with HTTP; Wed, 22 Jun 2011 12:48:35 -0700 (PDT)
In-Reply-To: <4898.1308747589.737163@puncture>
References: <BANLkTimdzZ_4d49P5EzWg+bgWFn+7fPgYw@mail.gmail.com> <4898.1308747589.737163@puncture>
Date: Wed, 22 Jun 2011 19:48:35 +0000
Message-ID: <BANLkTinOgAwFojZmPgpBX4AHR-2frtj7cQ@mail.gmail.com>
Subject: Re: My Internet experience in the West at times is comparable to female foeticide
From: Krishna Birth <krishnabirth@gmail.com>
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: Wed, 22 Jun 2011 19:48:37 -0000

On Wed, Jun 22, 2011 at 12:59 PM, Dave Cridland <dave@cridland.net> wrote:

> You were banned there because your posts were (very) off-topic, you're not
> local to South Wales, and finally because we felt like it - you have no
> particular right to post to SWLUG's mailing list, after all.
>
> HTH,
>
> Dave.

Your banning with a due process is baseless, there is not any by-laws
or rules quotation from the Swlug main document/s which should be
fixed with an unchangeable date stamp and any amendments to the main
document/s should also have an unchangeable date stamp, for example on
a Usenet public group.  You and other that have banned, intimidated me
need some education on how to run mailing lists.  There are no grounds
for you to ban me.

Alug (Anglian) is another linux user group today in Britain who have
joined the weasel worded racists chants by more or less banning me.

The mid to late banners have questioned my linux projects as to why I
wish to do them? When I have answered them that this is for spiritual
reasons -- they then ban me by conjuring some lies, the rabbit in the
hat trick.  This is cheating and it does not give linux operating
systems a good name.

All the banners should unban me.  This is racial law matter.  Justice
needs to be delivered.  These professional salaried / fee-earning
banners are not honest.  They are cunning in their ways.  I have a
huge evidence against these modern day 'journeymen' at linux user
groups in Britain and also in other areas.

While I write this for the IETF under this subject, I also wish to
complain about IETF being separate from the humanities, for example
the new domain suffix proposed by The Internet Corporation for
Assigned Names and Numbers (ICANN)  .xxx should not be put into use as
it demeans females through pornography.  Senior IETF members must
voice their concerns.


Regards


Meeku

From krishnabirth@gmail.com  Wed Jun 22 12:51:55 2011
Return-Path: <krishnabirth@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD1DD11E80CB for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 12:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.283
X-Spam-Level: 
X-Spam-Status: No, score=-3.283 tagged_above=-999 required=5 tests=[AWL=0.316,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXBxd08xJLyi for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 12:51:53 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0B87F11E8073 for <ietf@ietf.org>; Wed, 22 Jun 2011 12:51:52 -0700 (PDT)
Received: by yie30 with SMTP id 30so699097yie.31 for <ietf@ietf.org>; Wed, 22 Jun 2011 12:51:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=6OvzWPpzx70FYSi/wUrqKXiy6yPNZMCT65XFlF1vBSI=; b=mLxkMGUS3r2CkGJN5g3Vk8KeTgI5O/utOfUUbGkTh1S/j6QttBqMpULR02+Am1Mb0l GyYXvUGB/zvuvRlLp1UBiAiLC3yuadRlzPRqtrivn3DUIhZNA4mW3t9LHhadiBdpCzTu 8+a4pjEyJTeyyKHtzLsgqb6N4W1iU+pRGnOrE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=DQmzTbA1T20A9XP8epsd8DOwJQZmn+uSLbx2yW98VF47Uuz2LkPqq2zexRM9kc1+/T UCWvfcZX6nhplGG1avOpw4SRKy/Xo+dx4vy4bOqtOj4C6+3yU5pCDb/enX14Lmx/DIgG SjfjEMPPz1x4gl92nniQ755MVT5SYsDEJCkSw=
MIME-Version: 1.0
Received: by 10.236.5.206 with SMTP id 54mr1815132yhl.200.1308772309923; Wed, 22 Jun 2011 12:51:49 -0700 (PDT)
Received: by 10.236.154.225 with HTTP; Wed, 22 Jun 2011 12:51:49 -0700 (PDT)
In-Reply-To: <BANLkTinOgAwFojZmPgpBX4AHR-2frtj7cQ@mail.gmail.com>
References: <BANLkTimdzZ_4d49P5EzWg+bgWFn+7fPgYw@mail.gmail.com> <4898.1308747589.737163@puncture> <BANLkTinOgAwFojZmPgpBX4AHR-2frtj7cQ@mail.gmail.com>
Date: Wed, 22 Jun 2011 19:51:49 +0000
Message-ID: <BANLkTik1WiEx4HMevxXrZQg3fpX+C_TCVQ@mail.gmail.com>
Subject: Re: My Internet experience in the West at times is comparable to female foeticide
From: Krishna Birth <krishnabirth@gmail.com>
To: 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, 22 Jun 2011 19:51:55 -0000

Correction:

"Your banning without a due process is baseless...."

On Wed, Jun 22, 2011 at 7:48 PM, Krishna Birth <krishnabirth@gmail.com> wro=
te:
> On Wed, Jun 22, 2011 at 12:59 PM, Dave Cridland <dave@cridland.net> wrote=
:
>
>> You were banned there because your posts were (very) off-topic, you're n=
ot
>> local to South Wales, and finally because we felt like it - you have no
>> particular right to post to SWLUG's mailing list, after all.
>>
>> HTH,
>>
>> Dave.
>
> Your banning with[out] a due process is baseless, there is not any by-law=
s
> or rules quotation from the Swlug main document/s which should be
> fixed with an unchangeable date stamp and any amendments to the main
> document/s should also have an unchangeable date stamp, for example on
> a Usenet public group. =A0You and other that have banned, intimidated me
> need some education on how to run mailing lists. =A0There are no grounds
> for you to ban me.
>
> Alug (Anglian) is another linux user group today in Britain who have
> joined the weasel worded racists chants by more or less banning me.
>
> The mid to late banners have questioned my linux projects as to why I
> wish to do them? When I have answered them that this is for spiritual
> reasons -- they then ban me by conjuring some lies, the rabbit in the
> hat trick. =A0This is cheating and it does not give linux operating
> systems a good name.
>
> All the banners should unban me. =A0This is racial law matter. =A0Justice
> needs to be delivered. =A0These professional salaried / fee-earning
> banners are not honest. =A0They are cunning in their ways. =A0I have a
> huge evidence against these modern day 'journeymen' at linux user
> groups in Britain and also in other areas.
>
> While I write this for the IETF under this subject, I also wish to
> complain about IETF being separate from the humanities, for example
> the new domain suffix proposed by The Internet Corporation for
> Assigned Names and Numbers (ICANN) =A0.xxx should not be put into use as
> it demeans females through pornography. =A0Senior IETF members must
> voice their concerns.
>
>
> Regards
>
>
> Meeku
>

From mstjohns@comcast.net  Wed Jun 22 12:56:43 2011
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE1DF11E808A for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 12:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.29
X-Spam-Level: 
X-Spam-Status: No, score=-102.29 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2UEAHVybwxhQ for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 12:56:43 -0700 (PDT)
Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by ietfa.amsl.com (Postfix) with ESMTP id 52A1F11E8073 for <ietf@ietf.org>; Wed, 22 Jun 2011 12:56:43 -0700 (PDT)
Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta08.emeryville.ca.mail.comcast.net with comcast id z7tJ1g0021smiN4A87whhz; Wed, 22 Jun 2011 19:56:41 +0000
Received: from Mike-PC3.comcast.net ([217.41.235.57]) by omta20.emeryville.ca.mail.comcast.net with comcast id z7x41g0141EygGR8g7xDUF; Wed, 22 Jun 2011 19:57:30 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 22 Jun 2011 15:56:10 -0400
To: Scott Brim <scott.brim@gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: External IPR Disclosures vs IPR disclosures in the document.
In-Reply-To: <BANLkTi=T0ze_EuE3sZ1Yec5ARSRQN4A6xA@mail.gmail.com>
References: <20110622151200.33A2211E80A3@ietfa.amsl.com> <BANLkTi=T0ze_EuE3sZ1Yec5ARSRQN4A6xA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20110622195643.52A1F11E8073@ietfa.amsl.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: Wed, 22 Jun 2011 19:56:43 -0000

At 11:42 AM 6/22/2011, Scott Brim wrote:
>On Wed, Jun 22, 2011 at 11:11, Michael StJohns <mstjohns@comcast.net> wrote:
>> A quick couple of questions to the list based on a document I saw recently.
>>
>> If a document (an ID in this case) contains encumbered material (in this case consists of 90%+ encumbered material), and the document is authored by the organization (or members of the organization) that holds the encumbrance, should the document contain an IPR disclosure itself or is it sufficient to submit a IPR disclosure through the IETF web interface?
>
>IPR statements are never put in RFCs unless on occasion they are
>informational transplants from outside.  The IPR claims or other
>aspects might change over time and the right place to track all that
>is in the IPR disclosures.

Hmm.. even though this was labeled like a normal run of the mill ID, it really was an informational transfer from the outside - at least at this point in the process.  I.e. - single corporate author, long held IPR as opposed to "here's something brand new and never seen before and while parts of it may derive from work from company A, this use of it is new and people from company B and C are figuring out new ways to work with it."

I think tracking disclosures via the IPR system is reasonable for most documents, but something like "This document consists primarily of intellectual property claimed to owned by xxxx.  Please consult the IETF disclosures section for the current terms and conditions for this IPR." may be useful.    It's pretty hard to tell from any given document whether or not consulting the IPR disclosures is useful or somewhat necessary.

Not a big problem, I guess, but somewhat dissonant to the process.

Mike



From sob@harvard.edu  Wed Jun 22 13:04:41 2011
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D611611E8117 for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 13:04: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rR2oOzP7hEyU for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 13:04:41 -0700 (PDT)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by ietfa.amsl.com (Postfix) with ESMTP id DA28F11E8102 for <ietf@ietf.org>; Wed, 22 Jun 2011 13:04:40 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by golem.sobco.com (Postfix) with ESMTP id 7F29C6E29D28; Wed, 22 Jun 2011 16:04:39 -0400 (EDT)
Subject: Re: External IPR Disclosures vs IPR disclosures in the document.
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: "Scott O. Bradner" <sob@harvard.edu>
In-Reply-To: <20110622195643.52A1F11E8073@ietfa.amsl.com>
Date: Wed, 22 Jun 2011 16:04:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3938F0F5-77F0-43B6-B28C-4448259B5835@harvard.edu>
References: <20110622151200.33A2211E80A3@ietfa.amsl.com> <BANLkTi=T0ze_EuE3sZ1Yec5ARSRQN4A6xA@mail.gmail.com> <20110622195643.52A1F11E8073@ietfa.amsl.com>
To: Michael StJohns <mstjohns@comcast.net>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 20:04:42 -0000

see RFC 3979 section 4 A - a note like Mike asks for is called for

but the other Scott is also right - do not be specific - see section 11 =
of the same RFC

Scott

On Jun 22, 2011, at 3:56 PM, Michael StJohns wrote:

> At 11:42 AM 6/22/2011, Scott Brim wrote:
>> On Wed, Jun 22, 2011 at 11:11, Michael StJohns <mstjohns@comcast.net> =
wrote:
>>> A quick couple of questions to the list based on a document I saw =
recently.
>>>=20
>>> If a document (an ID in this case) contains encumbered material (in =
this case consists of 90%+ encumbered material), and the document is =
authored by the organization (or members of the organization) that holds =
the encumbrance, should the document contain an IPR disclosure itself or =
is it sufficient to submit a IPR disclosure through the IETF web =
interface?
>>=20
>> IPR statements are never put in RFCs unless on occasion they are
>> informational transplants from outside.  The IPR claims or other
>> aspects might change over time and the right place to track all that
>> is in the IPR disclosures.
>=20
> Hmm.. even though this was labeled like a normal run of the mill ID, =
it really was an informational transfer from the outside - at least at =
this point in the process.  I.e. - single corporate author, long held =
IPR as opposed to "here's something brand new and never seen before and =
while parts of it may derive from work from company A, this use of it is =
new and people from company B and C are figuring out new ways to work =
with it."
>=20
> I think tracking disclosures via the IPR system is reasonable for most =
documents, but something like "This document consists primarily of =
intellectual property claimed to owned by xxxx.  Please consult the IETF =
disclosures section for the current terms and conditions for this IPR." =
may be useful.    It's pretty hard to tell from any given document =
whether or not consulting the IPR disclosures is useful or somewhat =
necessary.
>=20
> Not a big problem, I guess, but somewhat dissonant to the process.
>=20
> Mike
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From ole@cisco.com  Wed Jun 22 13:04:51 2011
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 F044811E813D for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 13:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.875
X-Spam-Level: 
X-Spam-Status: No, score=-110.875 tagged_above=-999 required=5 tests=[AWL=-0.276, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9oK2VDeZ0aZA for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 13:04:51 -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 0496611E813F for <ietf@ietf.org>; Wed, 22 Jun 2011 13:04:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=166; q=dns/txt; s=iport; t=1308773091; x=1309982691; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=SGNWwJo5nZ8yAzMbDc3N5+6N+GMerxLG0tPGANgwdHs=; b=TyVU6S2z4N+NSsOXJfN2TWQZO/GkbqEPdzbwH1e9SRy7ua+RSTDRiMTA 2G7i5m1WxKRgzlA7G6MdZk77HB5mI7OZ1D7JNokMsVejqnWSTA8gFYbmj kgkNlC5zY96VqQO8NRsAagUCKmcZVDuzYRbLNK55WNvefb7uAL/j3RH0N 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAJtJAk5Io8US/2dsb2JhbABTmSeNanerOYMRDwGbGIYtBIcljyqLRw
X-IronPort-AV: E=Sophos;i="4.65,407,1304294400"; d="scan'208";a="96158620"
Received: from bgl-core-3.cisco.com ([72.163.197.18]) by ams-iport-1.cisco.com with ESMTP; 22 Jun 2011 20:04:49 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by bgl-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p5MK4jWj006658; Wed, 22 Jun 2011 20:04:47 GMT
Date: Wed, 22 Jun 2011 13:04:45 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Krishna Birth <krishnabirth@gmail.com>
Subject: Re: My Internet experience in the West at times is comparable to female foeticide
In-Reply-To: <BANLkTik1WiEx4HMevxXrZQg3fpX+C_TCVQ@mail.gmail.com>
Message-ID: <alpine.OSX.2.01.1106221303460.89414@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <BANLkTimdzZ_4d49P5EzWg+bgWFn+7fPgYw@mail.gmail.com> <4898.1308747589.737163@puncture> <BANLkTinOgAwFojZmPgpBX4AHR-2frtj7cQ@mail.gmail.com> <BANLkTik1WiEx4HMevxXrZQg3fpX+C_TCVQ@mail.gmail.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 20:04:52 -0000

Seargent at Arms:

Please have this individual banned from the IETF list at your earliest 
convenience. He apparently has no idea what "on topic" means.

Ole



From dhc2@dcrocker.net  Wed Jun 22 13:24:49 2011
Return-Path: <dhc2@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 6FE3611E815D for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 13:24:49 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q6iKKhNQAcsA for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 13:24:48 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D337C11E815B for <ietf@ietf.org>; Wed, 22 Jun 2011 13:24:48 -0700 (PDT)
Received: from [192.168.1.7] (ppp-68-120-198-5.dsl.pltn13.pacbell.net [68.120.198.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p5MKOhTv018689 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 22 Jun 2011 13:24:48 -0700
Message-ID: <4E024F88.8040300@dcrocker.net>
Date: Wed, 22 Jun 2011 13:24:40 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: My Internet experience in the West at times is comparable to female	foeticide
References: <BANLkTimdzZ_4d49P5EzWg+bgWFn+7fPgYw@mail.gmail.com> <94F16EB4-F62D-40BA-8512-4B320F63CB80@nominet.org.uk>
In-Reply-To: <94F16EB4-F62D-40BA-8512-4B320F63CB80@nominet.org.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 22 Jun 2011 13:24:48 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 20:24:49 -0000

On 6/22/2011 3:39 AM, Ray Bellis wrote:
>
> On 22 Jun 2011, at 09:59, Krishna Birth wrote:
>>
>> Some not all internet forums/mailing list organisers need some
>> educating and need to educate others for example by having some
>> by-laws and rules so that I am treated without these problems.
>
> Oh, but they do!
>
> The most common rule being that postings are *ON TOPIC*


But the most important rule is to refrain from feeding obviously useless threads.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From mnot@mnot.net  Wed Jun 22 16:18:29 2011
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 DB19D11E8073 for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 16:18:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.666
X-Spam-Level: 
X-Spam-Status: No, score=-105.666 tagged_above=-999 required=5 tests=[AWL=-3.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1bCHAoJ+Cw8W for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 16:18:28 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 59E5D9E800B for <ietf@ietf.org>; Wed, 22 Jun 2011 16:18:28 -0700 (PDT)
Received: from chancetrain-lm.mnot.net (unknown [118.209.34.52]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 8962422E1F4; Wed, 22 Jun 2011 19:18:21 -0400 (EDT)
Subject: Re: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host	Metadata)	to Proposed Standard -- feedback
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <05c701cc30f6$15841ed0$408c5c70$@packetizer.com>
Date: Thu, 23 Jun 2011 09:18:18 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <171028F1-B919-436C-ACEE-B7DFFDC85180@mnot.net>
References: <11CBFBA2-434B-43FC-90C4-DADBACB49226@mnot.net> <05c701cc30f6$15841ed0$408c5c70$@packetizer.com>
To: Paul E. Jones <paulej@packetizer.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ietf@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, 22 Jun 2011 23:18:30 -0000

On 23/06/2011, at 2:04 AM, Paul E. Jones wrote:

> Mark,
>=20
>> Generally, it's hard for me to be enthusiastic about this proposal, =
for
>> a few reasons. That doesn't mean it shouldn't be published, but I do
>> question the need for it to be Standards Track as a general =
mechanism.
>=20
> I believe standards track is appropriate, since the objective is to =
define
> procedures that are interoperable and the specification defines a set =
of
> procedures that would be implemented by multiple software products.

That can be said of pretty much every specification that comes along; =
does this imply that you think everything should be standards track?

At the end of the day, it's standards track if the IESG says it is. They =
asked for feedback on the Last Call, and I gave mine. It's not the end =
of the world if this becomes Standards Track, but I felt that it =
shouldn't pass without comment.


>> Mostly, it's because I hasn't really seen much discussion of it as a
>> general component of the Web / Internet architecture; AFAICT all of =
the
>> interest in it and discussion of it has happened in more specialised =
/
>> vertical places. The issues below are my concerns; they're not
>> insurmountable, but I would have expected to see some discussion of =
them
>> to date on lists like this one and/or the TAG list for something =
that's
>> to be an Internet Standard.
>=20
> You might be right that more discussion has happened off the =
apps-discuss
> list, but I would not equate that with not being a component of the =
web
> architecture. =20

... and I didn't equate it with that either; I said it was concerning =
that it hadn't been discussed broadly.


> On the contrary, host-meta has a lot of utility and is an
> important building block for the web architecture.  With host-meta, it =
is
> possible to advertise information in a standard way, discover =
services, etc.
> Some of the latter is not fully defined, but cannot be defined without =
this
> standard in place.

A "lot of utility" and being "an important building block" are =
completely subjective, of course. I'd agree with a statement that it's =
an important building block of OAuth, for example, but it seems quite =
premature to call it an important building block of the Web arch.=20


>> * XRD -- XRD is an OASIS spec that's used by OpenID and OAuth. Maybe =
I'm
>> just scarred by WS-*, but it seems very over-engineered for what it
>> does. I understand that the communities had reasons for using it to
>> leverage an existing user base for their specific user cases, but I
>> don't see any reason to generalise such a beast into a generic
>> mechanism.
>=20
> XRD is not complicated.  It's an XML document spec with about seven =
elements
> defined.  In order to convey metadata, one must have some format =
defined and
> XRD is as good as any other.  I don't think the use of XRD should be
> considered as negative aspect.  OpenID uses (through Yadis) a =
precursor to
> XRD called XRDS. I'm not sure about Oauth's usage of XRD.  Either way, =
does
> this matter?

Choosing your foundations well matters greatly.


>> * Precedence -- In my experience one of the most difficult parts of a
>> metadata framework like this is specifying the combination of =
metadata
>> from multiple sources in a way that's usable, complete and clear.
>> Hostmeta only briefly mentions precedence rules in the introduction.
>=20
> I assume you are referring to the processing rules in 1.1.1?  How =
would you
> propose strengthening that text?

It's not a matter of strengthening the text, it's a matter of agreeing =
upon and defining an algorithm. As it sits, the document doesn't do much =
more than wave its hands about precedence.


>> * Scope of hosts -- The document doesn't crisply define what a "host"
>> is.
>=20
> This might be deliberate and not really fault of this document.  The
> "hostname" that we are all used to using for a "host" may or may not =
refer
> to a physical host.  It might refer to a virtual host or a virtually =
hosted
> domain.

You use "might" a lot here. Do you know what it is, or are you just =
speculating?


> In any case, this term is consistent with the term used on the HTTP
> spec and the header line "Host:".

The Host header field conveys a host and a port, where this document =
seems to attach a very ephemeral concept to the term.


>> * Context of metadata -- I've become convinced that the most =
successful
>> uses of .well-known URIs are those that have commonality of use; =
i.e.,
>> it makes sense to define a .well-known URI when most of the data
>> returned is applicable to a particular use case or set of use cases.
>> This is why robots.txt works well, as do most other =
currently-deployed
>> examples of well-known URIs.
>>=20
>> Defining a bucket for potentially random, unassociated metadata in a
>> single URI is, IMO, asking for trouble; if it is successful, it could
>> cause administrative issues on the server (as potentially many =
parties
>> will need control of a single file, for different uses -- tricky when
>> ordering is important for precedence), and if the file gets big, it =
will
>> cause performance issues for some use cases.
>=20
> All of the use cases are not defined, but the host-meta document =
provides
> some examples, such as finding the author of a web page, copyright
> information, etc.  There has been discussion of finding a user's =
identity
> provider.  The particular uses.  Each of these examples fits well =
within the
> host-meta framework.  It builds upon the "web linking" (RFC 5988) work =
you
> did in a logical and consistent way, and I see these as complementary
> documents.  To your concern, host-meta is flexible, but the =
functionality is
> bounded.

That's almost a meaningless statement.


>> * Chattiness -- the basic model for resource-specfic metadata in
>> hostmeta requires at least two requests; one to get the hostmeta
>> document, and one to get the resource-specific metadata after
>> interpolating the URI of interest into a template.
>=20
> This is true, but the web is all about establishing links to other
> information.  I view this is a "good thing" about host-meta: it =
provides a
> very simple syntax with a way to use well-defined link relation types =
to
> discover other information.

Again, you really haven't addressed the concern.


>> For some use cases, this might be appropriate; however, for many =
others
>> (most that I have encountered), it's far too chatty. Many use cases =
find
>> the latency of one extra request unacceptable, much less two. Many =
use
>> cases require fetching metadata for a number of distinct resources; =
in
>> this model, that adds a request per resource.
>=20
> I think this comes back to use whatever makes most sense for the job.
> Consider robots.txt for example.  We could define a "robots" link =
relation
> and query the robots.txt file in a two-step operation, or we can just =
fetch
> it from the well-known location.  A well-known location works fine for
> robots.txt, but it does not work well for everything.  The examples of
> fetching copyright information or author information are examples.  =
The
> point is that host-meta provides a mechanism for discovering =
information
> about a URI.  This is very useful, IMO.

It's certainly useful for the cases that people are currently using it =
for, yes. It's less clear to me that it should be promoted as a general =
mechanism.


>> I'd expect a general solution in this space to allow describing a =
"map"
>> of a Web site and applying metadata to it in arbitrary ways, so that =
a
>> client could fetch the document once and determine the metadata for =
any
>> given resource by examining it.
>=20
> But what of URIs that do not refer to a document?  One could learn a =
lot of
> metadata about a specific document following RFC 5988, but that does =
not
> work for URIs like "mailto:paulej@packetizer.com" or any non-'http[s]' =
URI
> scheme used.  Even for some URIs that use http[s] as the scheme, there =
may
> or may not be an associated document.  Host-meta could allow one to =
get
> meta-data about any valid URI for a domain.

Sure. Again, I didn't say that there weren't uses for hostmeta, just =
that it's potentially inappropriate for lots of common ones.


>> If hostmeta is designed for specific use cases and meets them well,
>> that's great, but it shouldn't be sold as a general mechanism. So, =
I'm -
>> 1 on this going forward as a standards-track general mechanism. I
>> wouldn't mind if it were Informational, or if it were Standards-Track
>> but with a defined use case.
>=20
> Perhaps one could have made the same kind of argument about HTTP.  It =
is a
> general mechanism for fetching documents, files, or any data from a
> location.  This document is similar, but with a focus on providing =
metadata
> about URIs.  I think the procedures are useful and the document should =
go
> forward as a standards track RFC.


Wow, you're really stretching there, aren't you?


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




From barryleiba@gmail.com  Wed Jun 22 21:42:04 2011
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF0B49E804C for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 21:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.92
X-Spam-Level: 
X-Spam-Status: No, score=-102.92 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ztrOYpwG4sxd for <ietf@ietfa.amsl.com>; Wed, 22 Jun 2011 21:42:02 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 046BF9E8045 for <ietf@ietf.org>; Wed, 22 Jun 2011 21:42:00 -0700 (PDT)
Received: by yxp4 with SMTP id 4so325100yxp.31 for <ietf@ietf.org>; Wed, 22 Jun 2011 21:42:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=woM9zUl7yCZWcWpvvePb54Kiw7CZZGWbLh+NhmyOOLA=; b=NZZv7hFAh0z5dHuVMtQ90zlg7EYEjkLHB88E5q6PLDOZhoj/mtKvYBYChuf9Arn2Su PYiK2xY9LiNgmCpgzCKSEKypJOeFWgAslJEgNQkZBcIy6aqKifSHMmUhz8UxT7OyKBuP g2HS5wzW798eLfbPMjqgpRnAM/Yo/KPGYKY2Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=qXJ2sDCg90oXChaaiBBG8dH+2UKjUvNinmGNNdz0Z4nXFJ3e7jQOoCyjRPlUD2ECT6 1COx+G27wlm4/d8qzbfPQkf3j/tUK9cj9Ne1SKjAxNmB8eE9wNBLMWepMhu7hXEBUeeU rh79QX1xPIGvKKZBAw+jLbKPAZ7BBpqZnIiZ0=
MIME-Version: 1.0
Received: by 10.236.193.7 with SMTP id j7mr2294804yhn.465.1308804120200; Wed, 22 Jun 2011 21:42:00 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.236.42.133 with HTTP; Wed, 22 Jun 2011 21:41:59 -0700 (PDT)
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134EBC494F@EXCH-C2.corp.cloudmark.com>
References: <4E014A76.5090805@mail-abuse.org> <F5833273385BB34F99288B3648C4F06F134EBC494F@EXCH-C2.corp.cloudmark.com>
Date: Thu, 23 Jun 2011 00:41:59 -0400
X-Google-Sender-Auth: lqG7DwqCUkM9_sjfjBBOTkULThM
Message-ID: <BANLkTi=aJf-TeF7j4zw8ZVdTmgDsDe7Mzw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified Mail (DKIM) Signatures) to Draft Standard
From: Barry Leiba <barryleiba@computer.org>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2011 04:42:04 -0000

To add chair support to Murray's comment:

On Wed, Jun 22, 2011 at 13:17, Murray S. Kucherawy <msk@cloudmark.com> wrot=
e:
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Douglas Otis
>> Sent: Tuesday, June 21, 2011 6:51 PM
>> To: ietf@ietf.org; Barry Leiba; iesg-secretary@ietf.org; Sean Turner
>> Subject: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Iden=
tified Mail (DKIM) Signatures) to Draft Standard
>>
>> [...]
>>
>> This indicates the DKIM specification is seriously flawed. =A0While DKIM
>> may not offer author validation, it was intended to establish an
>> accountable domain for the signed message content that at a minimum
>> includes the From header field. =A0There are NO valid reasons for a vali=
d
>> signature to include multiple From header fields! =A0Allowing multiple
>> From header fields is _EVIL_ and destroys DKIM's intended purpose as
>> defined by prior work.
>
> This purported security flaw and surrounding FUD was discussed at huge le=
ngth
> in the working group, and consensus was clearly against the idea of deali=
ng with
> this in DKIM because it's the wrong place to address the problem. =A0The =
record, both
> in the issues tracker and in the working group's archive, is quite clear =
about this,
> and both are open to public scrutiny.

Indeed.  We gave this issue at least two clear consensus calls, and
it's very clear that the rough consensus considers the kind of
validation that Doug is asking for to be a good idea, but outside the
scope of the DKIM protocol.  That is, the validation ought to be done
in another part of the software system.  The document does actually
advise that, and that advice is all that working group consensus was
behind.  Consensus also is that Doug is severely overstating the
problem.

This has been decided and re-decided.

> And I find the tactic of taking a lost battle from a working group to the=
 IETF as
> a whole to be akin to the "Mom said no, I'll go ask Dad!" strategy that I=
 outgrew
> by the time I was a teenager...

I, too, have a problem with how IETF last call is sometimes being used
by working group participants to rehash issues.  But that's a subject
for a separate conversation, and not for here.

Barry, DKIM working group chair

From doug.mtview@gmail.com  Thu Jun 23 00:41:32 2011
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 0B6E121F84B6 for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 00:41:32 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gZ6KTMqdnJVn for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 00:41:30 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id B335821F84B4 for <ietf@ietf.org>; Thu, 23 Jun 2011 00:41:30 -0700 (PDT)
Received: by pwj5 with SMTP id 5so1156068pwj.31 for <ietf@ietf.org>; Thu, 23 Jun 2011 00:41:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=gyLkSj5YCJCtPvdDsDKfx38VM8NtKO5mphT8Uchtug8=; b=PenFwH83KZFXfSRVdQq5H9zdacnvwArXNpwzgjXLEvOWfw4yqU8Q2veOL4HFa1DznP Q7H/nrtxaeGRWZx5aoQll97FGfYT6l/tIkPjCfXYdXp/Bgu9ulc7AUyqYnFv+qNdMFI9 YVA6ThaMwhK9X7dXjxPU2XvCOR9VSobKAo+zg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=IJ/PrQhsEaKiCVSAN7aPBnWUKdfO79GNdB0MZzzQpzPpdcq1G4pzvzhc7S0UA5ZBiu wKwaHzgqDi3SlU1h3tlyFewL0hdl/lQDSALf+mS2ecR1iisvvKZuM9NYrB6Pz0U3OIws srRnFbDqqC/6ADMTlEwlX92vtFsoDfwTnKqzs=
Received: by 10.142.153.6 with SMTP id a6mr355165wfe.84.1308814889275; Thu, 23 Jun 2011 00:41:29 -0700 (PDT)
Received: from farside-laptop.local (c-24-6-100-11.hsd1.ca.comcast.net [24.6.100.11]) by mx.google.com with ESMTPS id t12sm916069wff.10.2011.06.23.00.41.26 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 23 Jun 2011 00:41:27 -0700 (PDT)
Message-ID: <4E02EE24.2060708@gmail.com>
Date: Thu, 23 Jun 2011 00:41:24 -0700
From: Doug Otis <doug.mtview@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified Mail (DKIM) Signatures) to Draft Standard
References: <4E014A76.5090805@mail-abuse.org> <4E02310C.8060604@dcrocker.net>
In-Reply-To: <4E02310C.8060604@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: Thu, 23 Jun 2011 07:41:32 -0000

On 6/22/11 11:14 AM, Dave CROCKER wrote:
> Folks,
>
> The bottom line about Doug's note is that the working group extensively
> considered the basic issue of multiple From: header fields and Doug is
> raising nothing new about the topic.
>
> A quick summary of the technical point at the core of Doug's concern is
> that the presence of multiple rfc5322.From header fields does appear to
> represent a plausible attack vector, but it also violates RFC5322 -- and
> RFC822, if anyone is worried about the history of this issue. DKIM
> (RFC4871) requires that the signing engine be handed a valid RFC5322
> message. Hence the burden of ensuring that there is only one From: field
> rests outside DKIM.

First, thank you for your response.

I must ask however where do you see this burden being placed?  If not on 
DKIM where?

To clarify, the message format standard authored by you back in 1982 
imposed no limit on the number of header fields and this was not revised 
until 2001.

RFC822 Section 4.1 Syntax states:
,---
This specification permits multiple  occurrences  of  most
fields.   Except  as  noted,  their  interpretation is not
specified here, and their use is discouraged.
'---

The current RFC4871bis only vaguely *recommends* compliance.
3.8. Input Requirements
,---
DKIM's design is predicated on valid input.  Therefore, signers and
verifiers SHOULD take reasonable steps to ensure that the messages
they are processing are valid according to [RFC5322], [RFC2045], and
any other relevant message format standards.
'---

Another decade has passed and SMTP still fails to impose strict message 
format enforcement after limits were imposed on Orig-date, From, Sender, 
Reply-to, To, Cc, Message-id, In-reply-to, References, and Subject. 
Voicing opinions of protocol layering lends permission to DKIM 
implementers to also ignore these limits.  :^(

RFC5321 Section 3.3 states:
,--
When the RFC 822 format ([28], [4]) is being used, the mail data
include the header fields such as those named Date, Subject, To, Cc,
and From.  Server SMTP systems SHOULD NOT reject messages based on
perceived defects in the RFC 822 or MIME (RFC 2045 [21]) message
header section or message body.
'--

It is not reasonable to expect SMTP will impose necessary restrictions 
able to prevent deceptive DKIM results anytime in the near future.  As 
the DKIM draft states, SMTP is not enforcing header limitations now.

You expressed concern over protocol layers.  What do you call the 
protocol layer you expect to be making these needed checks?  Is this 
some highly opaque spam filter protocol layer?  Will this layer guess 
whether DKIM checked RFC5322's header field requirements?  If not 
guessing, how is this check being signaled?

Those wishing to implement secure systems need to know whether a high 
value From header field might be mistakenly accepted based on signatures 
offered by some large free email provider.  Free email providers often 
don't care whether header fields might be pre-pended when their 
reputation is based upon their volume. They are also unlikely to 
implement a wasteful fix of double listings of signed headers which then 
exposes high value domains to abuse well beyond their control.

The DKIM specification claims it can be incrementally deployed.  One 
might presume that acceptance might be based upon the signing domain. 
If not DKIM, what protocol layer ensures header field limitations have 
been imposed to prevent the signing domain's DKIM's assurances from 
becoming deceptive or evil?

> For reference, Doug posted a related blog recently and I posted a
> response yesterday:
>
> <http://www.circleid.com/posts/searching_under_lampposts_with_dkim/>
>
> Others are posting responses also. The Comment mechanism, to the
> Circleid article, is being used to list these additional responses.
>
>
> Inline comments...
>
> On 6/21/2011 6:50 PM, Douglas Otis wrote:But,
>> RFC4686 Introduction states:
> ...
>> While several threats to DKIM were considered, multiple From header
>> fields were
>> neglected. This document only focused on use of multiple addresses
>> within the
>> From header field.
>
> Any possible omissions in an Informational threats document -- done 6
> years ago and before the signing specification (RFC4871) was written --
> is of marginal relevance, at best.

Nevertheless, RFC4686 missed the threat created by multiple From header 
fields.

>> It should be noted that Signing Practices are referenced off a domain
>> found in
>> the From header field which also assumes only one will be present.
>
> It also should be noted that Signing Practices (ADSP) issues are
> irrelevant to the candidate RFC4871bis effort, which pertains only to
> the signing specification.

ADSP depends upon RFC4871's output where it is not possible to achieve 
the desired policies when pre-pended From header fields are ignored.

>> This indicates the DKIM specification is seriously flawed.
>
> It indicates that there is an issue, not that it is DKIM's
> responsibility to solve it.

What protocol do you expect will solve this issue?

>> While DKIM may not offer author validation,
>
> Does not. Not may not. It's a simple and direct fact.

I never said DKIM authenticated the From header.  DKIM is expected to 
authenticate a binding of the signing domain with the From header at a 
minimum.  It might also include other headers and the message body.

>> it was intended to establish an accountable domain for
>> the signed message content that at a minimum includes the From header
>> field.
>
> And it does that. But it does not make any assertions about the
> /validity/ of any of the data it signs, nevermind any of the data it
> does NOT sign.

The intent of DKIM is completely missed when a pre-pended From header is 
ignored in signature validation.  It is also not reasonable to expect 
all subsequent mail handling will retroactively adopt DKIM's bottom-up 
header selection methods.

>> There are NO valid reasons for a valid signature to include multiple
>> From header
>> fields! Allowing multiple From header fields is _EVIL_ and destroys
>> DKIM's
>> intended purpose as defined by prior work.
>
> It actually has no discernible effect on DKIM's utility, nor have there
> been reports from the field of problems in 6 years of deployed use.

Is it reasonable to wait for massive exploitation?  Social engineering 
attacks need not occur at high frequencies before significant damage can 
be created.  It seems users are seeking social network communications in 
part because they don't wish to sort through high levels of fraud.

>> Free email providers likely use DKIM to gain increased acceptance by
>> taking
>> advantage of their "too big to block" volumes. For these domains, their
>> reputation is understood to offer little assurance of their overall
>> integrity
>> while perhaps limiting what is allowed in the domain portion of the
>> From header
>> field.
>
> This appears to be a political rant.

No. This was to counter several who expect reputation systems can deal 
with this type of abuse.  They can't when DKIM reports valid signatures 
when messages contain multiple From header fields.

>> By allowing a pre-pended From header field to not affect the validity
>> of a DKIM
>> signature according to the specification means the UNDERSTOOD source of a
>> message can NEVER be trusted through the aid of DKIM.
>
> That statement well might be correct, but that's OK, since DKIM does not
> make assertions about "source" validity, except in terms of the separate
> DKIM signing identifier (in the DKIM-Signature: header field.) The
> signer is sometimes referred to as a source. However DKIM makes no
> assertions concerning the Author or Originator [RFC5598].

DKIM does assert, at a minimum, a signing domain is bound to the From 
header field.  This is important whenever DKIM is used as a basis for 
acceptance.  However, this binding is rendered meaningless when a 
pre-pended From header field is ignored, and yet is predominately 
displayed to the recipient.

>> The general goal of DKIM cryptographically binding at a minimum the
>> From header
>> field of the message content to a domain was to act as a trust basis for
>> acceptance.
>
> The general goal is to attach an identifier than is reliable and valid,
> and it does that. The identifier can be used for developing a reputation
> assessment of message streams signed with that identifier.

What affect will this have on a massive Free email provider being 
exploited with some pre-pended From header fields?  The answer is NONE. 
Reputation will not solve the issue of abuse of "too big to block" 
providers.

>> DKIM also purports to allow incremental deployment without requiring
>> additional undefined filtering be introduced in mail transfer or mail
>> user
>> agents. Clearly, the incremental deployment statement conflicts with the
>> original goals due to the neglected input validation flaw.
>
> I have no idea what the above means.

The hand waving about something other than DKIM fixing its bogus results 
will not allow for incremental deployment.

>> Details of this concern were stated in the tracker at:
>> http://trac.tools.ietf.org/wg/dkim/trac/ticket/24
>
> And it nicely shows that the working group considered the issue.
>
>
>> This version of DKIM also introduced use of RFC5890 instead of
>> RFC3490, which
>> allows use of the German esset and the Greek final sigma, drops
>> string-prep, and
>> defines 3,329 invalid code points. Unfortunately, this version of the
>> DKIM also
>> failed to exclude use of Fake A-Labels, which when presented to the
>> user may
>> also prove highly deceptive.
>
> Excellent. Now it is also DKIM's job to fix problems with Unicode...

No. DKIM can not safely offer a basis of trust without also ensuing the 
domain conveyed to a recipient is not visually deceptive.  This requires 
ensuring against Fake-A labels as defined by the referenced RFC5890. 
Soon there will be many unfamiliar TLDs where users may have difficulty 
discerning which domains are published within a private zone or are 
registered.  Either way, recipients are better served by ensuring Fake 
A-labels are never used to validate DKIM signatures.

It is also important to ensure against use of U-labels as well.  This 
should not become a problem since the range of the character code-points 
should exclude this problem.

>> Details of this concern were stated in the tracker at:
>> http://trac.tools.ietf.org/wg/dkim/trac/ticket/24
>
> wrong citation.

Thanks. That should have been:

http://trac.tools.ietf.org/wg/dkim/trac/ticket/17

-Doug

From mstjohns@comcast.net  Thu Jun 23 03:17:22 2011
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE5911E80DE for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 03:17: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bAbg46-rd0KR for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 03:17:21 -0700 (PDT)
Received: from qmta05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by ietfa.amsl.com (Postfix) with ESMTP id 86B7111E80DA for <ietf@ietf.org>; Thu, 23 Jun 2011 03:17:21 -0700 (PDT)
Received: from omta12.emeryville.ca.mail.comcast.net ([76.96.30.44]) by qmta05.emeryville.ca.mail.comcast.net with comcast id zNF11g0010x6nqcA5NHJWt; Thu, 23 Jun 2011 10:17:18 +0000
Received: from Mike-PC3.comcast.net ([109.144.244.115]) by omta12.emeryville.ca.mail.comcast.net with comcast id zNGi1g0022W6Wzx8YNGp9x; Thu, 23 Jun 2011 10:17:12 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 23 Jun 2011 06:16:43 -0400
To: "Scott O. Bradner" <sob@harvard.edu>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: External IPR Disclosures vs IPR disclosures in the document.
In-Reply-To: <3938F0F5-77F0-43B6-B28C-4448259B5835@harvard.edu>
References: <20110622151200.33A2211E80A3@ietfa.amsl.com> <BANLkTi=T0ze_EuE3sZ1Yec5ARSRQN4A6xA@mail.gmail.com> <20110622195643.52A1F11E8073@ietfa.amsl.com> <3938F0F5-77F0-43B6-B28C-4448259B5835@harvard.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20110623101721.86B7111E80DA@ietfa.amsl.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 Jun 2011 10:17:22 -0000

Section 4A refers to RFCs.  I'm thinking that it should probably refer to any submission as soon as the IPR is known about.  RFC Editor enforces it for RFC's.  ID submission tool looks up the doc to see if there's an IPR disclosure for any of the previous versions and complains if there isn't an appropriate notice in the document. "An IPR disclosure has been made for this document or its predecessors.  Please see xxx for details."

Mike



At 04:04 PM 6/22/2011, Scott O. Bradner wrote:
>see RFC 3979 section 4 A - a note like Mike asks for is called for
>
>but the other Scott is also right - do not be specific - see section 11 of the same RFC
>
>Scott
>
>On Jun 22, 2011, at 3:56 PM, Michael StJohns wrote:
>
>> At 11:42 AM 6/22/2011, Scott Brim wrote:
>>> On Wed, Jun 22, 2011 at 11:11, Michael StJohns <mstjohns@comcast.net> wrote:
>>>> A quick couple of questions to the list based on a document I saw recently.
>>>> 
>>>> If a document (an ID in this case) contains encumbered material (in this case consists of 90%+ encumbered material), and the document is authored by the organization (or members of the organization) that holds the encumbrance, should the document contain an IPR disclosure itself or is it sufficient to submit a IPR disclosure through the IETF web interface?
>>> 
>>> IPR statements are never put in RFCs unless on occasion they are
>>> informational transplants from outside.  The IPR claims or other
>>> aspects might change over time and the right place to track all that
>>> is in the IPR disclosures.
>> 
>> Hmm.. even though this was labeled like a normal run of the mill ID, it really was an informational transfer from the outside - at least at this point in the process.  I.e. - single corporate author, long held IPR as opposed to "here's something brand new and never seen before and while parts of it may derive from work from company A, this use of it is new and people from company B and C are figuring out new ways to work with it."
>> 
>> I think tracking disclosures via the IPR system is reasonable for most documents, but something like "This document consists primarily of intellectual property claimed to owned by xxxx.  Please consult the IETF disclosures section for the current terms and conditions for this IPR." may be useful.    It's pretty hard to tell from any given document whether or not consulting the IPR disclosures is useful or somewhat necessary.
>> 
>> Not a big problem, I guess, but somewhat dissonant to the process.
>> 
>> Mike
>> 
>> 
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf



From lachlan.hunt@lachy.id.au  Thu Jun 23 04:16:56 2011
Return-Path: <lachlan.hunt@lachy.id.au>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E04C11E8088 for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 04:16:56 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kIKZie3LzvpC for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 04:16:55 -0700 (PDT)
Received: from homiemail-a83.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 151A511E807F for <ietf@ietf.org>; Thu, 23 Jun 2011 04:16:55 -0700 (PDT)
Received: from homiemail-a83.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a83.g.dreamhost.com (Postfix) with ESMTP id 8F8035E06D; Thu, 23 Jun 2011 04:16:53 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=lachy.id.au; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=lachy.id.au; b=iZ2HKYj7XgsrKnOiKle0bzKv/SX1T0HGSIjeCkd4V1yFl7XJ6ScQxwT2KoF/v HWCK7016UOWE/6j8ZYrLJ0LSecifNsa+ipOQgyMMC4krbE1+i6UjJNZ6ki34xnN8 dLtc8i3cTpWzkiZnweNhxfenRus9+REabD0svPVMv4wPyQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=lachy.id.au; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=lachy.id.au; bh=LONUM FdbR//qZpH0GPFDB5rfeYY=; b=LoRfqvOZ8JgPRsyP9o6VgKNEC86FMxPaYJqaT oS6jJpl18P8HPMBocRNWH9nhOxTJVeqF2ewLQTC7kMTkUPlJWymss6PpsdzEjiKp ybppoHsnQIPoonVF9SpqYVIcTYr5ePwjoRDw/OfSO5P+eU54exavRAVV6Y9/W15p dGswT8=
Received: from jonas.eng.oslo.osa (pat-tdc.opera.com [213.236.208.22]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lachlan.hunt@lachy.id.au) by homiemail-a83.g.dreamhost.com (Postfix) with ESMTPSA id EA8B55E060;  Thu, 23 Jun 2011 04:16:51 -0700 (PDT)
Message-ID: <4E0320A2.6030000@lachy.id.au>
Date: Thu, 23 Jun 2011 13:16:50 +0200
From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
References: <0EC26EB10287E2A20769C9CC@PST.JCK.COM> <4E0171EB.4020109@gmail.com>
In-Reply-To: <4E0171EB.4020109@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-holsten-about-uri-scheme@tools.ietf.org, John C Klensin <klensin@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: Thu, 23 Jun 2011 11:16:56 -0000

On 2011-06-22 06:39, Mykyta Yevstifeyev wrote:
>> (1) There seems to be consensus that registering this URI as a
>> mechanism for accessing built-in functionality and configuration
>> information such as application information, preferences, or
>> settings. (Text derived from the Abstract with "configuration
>> information", which may mean more to some readers, added and
>> "easter eggs" dropped. Dropping "easter eggs" reflects other
>> comments on the list and my opinion that it isn't worth the
>> trouble to define.
>
> With regard to easter eggs I have no strong position. If it is
> troubling, I don't object to remove any mention of them from the document.

The easter eggs are mentioned only in non-normative parts of the 
document, including the abstract and examples, and just reflect the 
reality of what some implementations use about URLs for.  I do not 
understand the objection.

>> (2) The document itself reflects an attempt to define the
>> undefinable. There is no cross-implementation interoperability
>> issue here; if anything, the document should me more clear that
>> it would be stupid to assume it. The document, nonetheless,
>> tries to define what is done with some specific URIs in some
>> places and then has to turn around and indicate that they may be
>> used in entirely different ways in other places and should not
>> be relied upon. In the process, it skips back and forth between
>> being descriptive and being normative, with some definitions
>> becoming circular in the process. That just isn't a good
>> combination and some of it actually looks pretty silly.

This feedback is not helpful, as it just vague hand waving and dismissive.

> I may partly agree with you. Reading the document for a number of times
> I've also noticed this. A logical conclusion of everything
> aforementioned is below.
>
>> "about:blank" is particularly troubling in that regard because
>> the text essentially says that it is reserved except where it
>> isn't.

Nonsense.  "about:blank" is clearly defined as reserved, and nowhere 
does it indicate otherwise.  Perhaps you are confused where it excludes 
variations that include query strings?

>> Option 2: Really try to make this normative wrt some subset of
>> URI values. In this approach, stop the extremely confusing
>> circling around.

The circular definitions have been resolved in the editor's draft.

https://github.com/josephholsten/about-uri-scheme/blob/master/draft-holsten-about-uri-scheme-07.txt

>> Indicate explicitly that "about" URIs have been used enough and in
>> enough different circumstances that no application should assume
>> that an "about" URI, if encountered, is actually its own and that
>> due caution needs to be taken about non-conforming implementations.

That's the whole point of the unreserved category.

>> Then explicitly reserve, not only"about:blank", but everything the
>> authors think is worth listing in Examples _and_ create an IANA
>> registry for more of them.

No.  The registry is a completely unnecessary bureaucratic mess that I'm 
strongly fighting against, and will most likely be removing from a 
future draft.  Mykyta added mention of it to the draft* against my 
wishes after I allowed him/her to become an editor even though (s)he has 
still not been able to provide justification for why such a registry is 
necessary.  (However, I allowed the draft to be publicised with it for 
public review and comment.)

* Note: That change hasn't been checked into github, and I don't know
   if Mykyta has those changes somewhere public yet.

The purely informative value of a registry can and has already been 
achieved by Wikipedia.  The three known reserved about URIs (blank, 
legacy-compat and scrdoc) are already documented, as are many other 
unreserved, but recognised application-specific URIs.

Beyond that, the whole concept of reservation only exists to give other 
specifications a clear way to define about URIs for their own purposes 
and doesn't need any formal registration process. It doesn't have any 
impact on any implementations that are not implementing the given 
specification.

>> the document should be really clear that all that the use of
>> "about:" really tells someone is that it is application-specific
>> and that a particular implementation of a particular application
>> may do whatever it pleases with them.

It still says that, though the way it is written is a quite ambiguous 
and convoluted and I understand the confusion here.  I'll rephrase the 
section on recognised URIs to address this.

>> Smaller issues:
>>
>> (i) Section 6, Normalization, sadly really doesn't belong here
>> unless the authors can show that everyone interprets "about:"
>> according to those rules. Otherwise, it would be better to say
>> that the URI is interpreted in an implementation-specific way
>> and that implementations would be well-advised to conform to
>> normal URI syntax rules unless there is a strong reason not

> Agree here. This thread restarted with the response to Boris's comment
> regarding Gecko's normalization rules. This was to claim that no unified
> rules for the scheme which is a priori used by the applications on their
> own. As I proposed below, if no document is to be written, the template
> may contain such statement about implementation-specific normalization
> rules.

Yes, normalisation requirements will be removed.

>> (ii) IMO, Section 7, Security Considerations, should be modified
>> to include an explicit statement that, since these things are
>> intended for convenience use within an implementation of an
>> application, passing them between systems (embedded in files or
>> otherwise) is very risky behavior and should generally be
>> discouraged except, possibly, in documentation contexts.
> I agree here.
> ...
> Section 4 is what is also questionable. This issue was raised during
> Last Call and I think can be resolved by saying that an about URIs may
> contain UTF-8 encoded characters in the <segment>, as suggested by RFC
> 3986 and that's all.

Mykyta, feel free to revise sections 4 and 7 as you see fit.

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/

From ietfdbh@comcast.net  Thu Jun 23 05:29:33 2011
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 104E811E812F for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 05:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.52
X-Spam-Level: 
X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lAxBzULIp9me for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 05:29:31 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [76.96.59.228]) by ietfa.amsl.com (Postfix) with ESMTP id 793B511E80EE for <ietf@ietf.org>; Thu, 23 Jun 2011 05:29:31 -0700 (PDT)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta15.westchester.pa.mail.comcast.net with comcast id zPb61g0041GhbT85FQVXuP; Thu, 23 Jun 2011 12:29:31 +0000
Received: from davidPC ([67.189.235.106]) by omta07.westchester.pa.mail.comcast.net with comcast id zQVV1g01z2JQnJT3TQVWoz; Thu, 23 Jun 2011 12:29:30 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'The IESG'" <iesg@ietf.org>, <ietf@ietf.org>
Subject: TSVDIR review request - draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat
Date: Thu, 23 Jun 2011 08:29:23 -0400
Message-ID: <89FDF7F21F0649C1A304E481720C6D55@davidPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.1.7600.16807
Thread-Index: AcwrjknDHFdlmL6nRFSZC/WI2h3lQwBerDsQAQDBzoAAJSFWkA==
X-Mailman-Approved-At: Thu, 23 Jun 2011 08:04:19 -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 Jun 2011 12:29:33 -0000

Hi,

This review did not get copied to IESG or IETF lists.

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)

-----Original Message-----
From: Woundy, Richard [mailto:Richard_Woundy@cable.comcast.com] 
Sent: Wednesday, June 22, 2011 6:45 PM
To: David Harrington; 'Transport Directorate'
Cc: draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat@tools.ietf.org;
Woundy, Richard
Subject: RE: tsvdir review request -
draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat

> Can you do a tsvdir review of
draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat?

Here are my high level comments on this internet draft.

- The document covers host and gateway requirements, but omits any
service provider requirements (eg DHCPv6 option support).
- The security considerations are weak (eg "evil policy") and should
be more detailed.
- The source address selection drafts are dead or expired, which does
not provide confidence that anyone is working on one of the key
solutions advocated by this draft.
- Someone should review the entire document for English grammar,
especially section 1.

But if these issues were resolved, this would be a good draft that
solves important IPv6 deployment issues.

Detailed comments.

Section 1.

>NAT based multihoming is easily deployable and already deployed
technique.

"an already deployed technique"

>The same situation that depends on NAT technique may be brought to
the IPv6 world.

Maybe should say "The same situations that require the NAT technique
to be used in the IPv4 world may be applicable to the IPv6 world?"

> Whenever a host or small network (which does not meet minimum IPv6
allocation criteria) is connected to multiple upstream networks IPv6
address is assigned by each respective service provider...

"an IPv6 address is assigned"

> resulting in hosts with more than one active IPv6 addresses.

"one active IPv6 address"

> As each service provided is allocated...

"service provider"

> So, the goals for IPv6 multihoming definced in [RFC3582] do not
exactly match the goals of us.

"defined in" and "match the goals of this document"

> If multiple routers exist on a single link the host must
appropriately select next-hop for each connected network.

"must select the appropriate next-hop"

> it is conceivable that the packets that have inappropriate source
address...

"have an inappropriate source address"

> A DNS query sent to an arbitrary upstream resolver may result in
incorrect or poisoned responses

Add a period to the end of the sentence.

> A possible consequence of assigning a host multiple identical-scoped
addresses...

"identically-scoped"

Section 3.3.

> making it essential for the host to correctly resolve these three
criteria before sourcing the first packet.

"resolve these three items..."

Section 4.2.

This section is entitled "Policy providing", which feels like a very
awkward term. Have you considered "Policy distribution" or something
similar?

I think there may be a few missing requirements for "providing
mechanisms". For one, administrators of different networks seem to
need to control policies (and nodes' behaviors) independently of other
administrators. For another, administrators must control only nodes
that are part of their own networks.

Section 5.

General comment. This draft puts requirements on the host (O/S), home
gateway and ISP. Any one missing piece will break this solution. This
all-or-broken approach makes this solution unlikely to be successful
for some time because we can't have an incremental approach. That
said, if we have all the pieces, this "should" work.

Section 5.1.

> Scenario 1: "Host" needs to support the solution for this problem
> Scenario 2: "Host" needs to support the solution for this problem

Missing periods. Also note that the service providers (ie ISP and
enterprise / VPN) must also support this solution
(ietf-6man-addr-select-opt).

Section 5.2.

> Scenario 1: "Host" needs to support the solution for this problem
> Scenario 2: "GW rtr" needs to support the solution for this problem
> Scenario 3: "Host" needs to support the solution for this problem

Missing periods. Also note that the service providers (ie ISP and
enterprise / VPN) must also support this solution
(ietf-mif-dhcpv6-router-option).

Section 5.3.

> [I-D.ietf-mif-dns-server-selection] proposes a solution for DNS
server selection policy providing solution with a DHCPv6 option.

Perhaps it would be simpler to say
"[I-D.ietf-mif-dns-server-selection] proposes a solution for
distributing DNS server selection policy using a DHCPv6 option."

> Scenario 1: "Host" needs to support the solution for this problem
> Scenario 2: "GW rtr" needs to support the solution for this problem
> Scenario 3: "Host" needs to support the solution for this problem

Missing periods. Also note that the service providers (ie ISP and
enterprise / VPN) must also support this solution
(ietf-mif-dns-server-selection).

Section 6.1.

> the staticness of the assumed target network environment.

"static nature of the assumed target..."

Section 6.2.

> The DHCPv6 mechanism does not have these difficulties and has the
advantages of its relaying functionality.

"has the advantage..."

> The alternative of a policy-based approach is documented in
[I-D.ietf-mif-dns-server-selection],where several pairs of DNS

", where..."

Section 7.2.

> 7.2.  Co-exisitence consideration

"Co-existence"

> An idea to achieve this is that GW-rtr identifies the hosts, and
then assigns single prefix to non-MHMP hosts and assigns multiple
prefix to MHMP hosts.

"a single prefix" and "multiple prefixes".

> In this case, GW-rtr can perform IPv6 NAT only for the traffic from
MHMP hosts if its source address is not appropriate.

The MHMP hosts follow the recommendations of this draft, so they don't
need IPv6 NAT by definition. Shouldn't this sentence refer to "traffic
from non-MHMP hosts"?

> Another idea is that GW-rtr assigns multiple prefix to the both
hosts

"multiple prefixes to both hosts"

> In this case, non-MHMP host can access the service through the NAT
box.

"the non-MHMP host"

Section 8.

> A policy receiver may receive an evil policy from a policy
distributor.

The wording of the Security Considerations section indicate to me that
there was no security review of this document. What makes a policy
"evil"? Is it because some third party is pretending to be the
administrator in distributing policies (ie you need authentication)?
Is it because some third party changed the policies in transit, or the
policies were corrupted in transit (ie you need integrity checking)?

The authors should take into consideration these security directorate
review comments:
<http://www.ietf.org/mail-archive/web/secdir/current/msg02739.html>. 

Incidentally, what happens when there are policy conflicts between
independent administrators? Who wins?

> A policy distributor should expect some hosts in his network do not
follow the distributed policy.

Maybe be even stronger: "will not follow". How can this situation be
detected and remediated?

Section 11.1.

> [I-D.ietf-6man-addr-select-opt]
> Matsumoto, A., Fujisaki, T., and J. Kato, "Distributing
> Address Selection Policy using DHCPv6",
> draft-ietf-6man-addr-select-opt-00 (work in progress),
> December 2010.

This normative reference is 'expired'
(http://datatracker.ietf.org/doc/draft-ietf-6man-addr-select-opt/).

> [I-D.ietf-6man-addr-select-sol]
> Matsumoto, A., Fujisaki, T., and R. Hiromi, "Solution
> approaches for address-selection problems",
> draft-ietf-6man-addr-select-sol-03 (work in progress),
> March 2010.

This normative reference is 'dead'
(http://datatracker.ietf.org/doc/draft-ietf-6man-addr-select-sol/).

That tells me that both normative references to the preferred source
address selection solution are invalid. So do we have a solution to
one of the key issues raised by this internet-draft???

-- Rich

-----Original Message-----
From: Woundy, Richard 
Sent: Friday, June 17, 2011 12:11 PM
To: David Harrington
Cc: 'Transport Directorate'; Woundy, Richard
Subject: RE: tsvdir review request -
draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat

I will get this review done by close of business Tuesday 6/21.
________________________________________
From: David Harrington [ietfdbh@comcast.net]
Sent: Wednesday, June 15, 2011 2:59 PM
To: Woundy, Richard
Cc: 'Transport Directorate'
Subject: tsvdir review request -
draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat

Hi Rich,

Can you do a tsvdir review of
draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat?
due date is 6/21

Thanks,
David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)



From johnl@iecc.com  Thu Jun 23 08:26:07 2011
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 5348311E810C for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 08:26:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ITNu+CehMiYT for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 08:26:06 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id 0D41011E8164 for <ietf@ietf.org>; Thu, 23 Jun 2011 08:25:46 -0700 (PDT)
Received: (qmail 41539 invoked from network); 23 Jun 2011 15:25:46 -0000
Received: from pedro.iecc.com (66.152.118.17) by mail1.iecc.com with QMQP; 23 Jun 2011 15:25:46 -0000
Date: 23 Jun 2011 15:24:58 -0000
Message-ID: <20110623152458.19049.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified Mail (DKIM) Signatures) to Draft Standard
In-Reply-To: <4E02EE24.2060708@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2011 15:26:07 -0000

In article <4E02EE24.2060708@gmail.com> you write:
>On 6/22/11 11:14 AM, Dave CROCKER wrote:
>> Folks,
>>
>> The bottom line about Doug's note is that the working group extensively
>> considered the basic issue of multiple From: header fields and Doug is
>> raising nothing new about the topic.

Dave is quite right.  Doug's purported attack just describes one of
the endless ways that a string of bytes could be not quite a valid
5322 message, which might display in some mail programs in ways that
some people might consider misleading.  If it's a problem at all, it's
not a DKIM problem.

R's,
John


From michel@arneill-py.sacramento.ca.us  Thu Jun 23 12:46:35 2011
Return-Path: <michel@arneill-py.sacramento.ca.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 B89DE21F8484 for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 12:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oFEBF2u+u7Wp for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 12:46:35 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [69.12.226.219]) by ietfa.amsl.com (Postfix) with ESMTP id 1610521F8489 for <ietf@ietf.org>; Thu, 23 Jun 2011 12:46:35 -0700 (PDT)
Subject: RE: one data point regarding native IPv6 support
Date: Thu, 23 Jun 2011 12:46:33 -0700
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEF5B9@newserver.arneill-py.local>
In-Reply-To: <4489CB40-0142-467A-9D27-33629F63DD3A@employees.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: one data point regarding native IPv6 support
Content-class: urn:content-classes:message
Thread-Index: Acwquoz8DOYA9aoASqyAPP8N9Z+2vQCV2SHQ
x-mimeole: Produced By Microsoft Exchange V6.5
References: <392CB277BC2EAE4FB83C1206954BA6CEF590@newserver.arneill-py.local> <4489CB40-0142-467A-9D27-33629F63DD3A@employees.org>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Ole Troan" <otroan@employees.org>
Cc: Keith Moore <moore@network-heretics.com>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2011 19:46:35 -0000

Ole,

>> Michel Py wrote:
>> Given the constant references in 6RD to 6to4, I will point
>> out that making 6to4 historic somehow reduces the likeliness
>> of another extremely successful ISP implementation based on it.

> Ole Troan wrote:
> making 6to4 historic does not affect 6rd. I think the draft
> says that much too. I don't think we are saying that native
> necessarily is better than tunnels. we are saying unmanaged
> tunnels crossing the Internet is bad.

That was bad wording from me indeed; instead of "constant references in
6RD to 6to4" I should have said "constant references in RFC5569 to
6to4".

I am curious about one thing though, why didn't you make RFC5969 to
obsolete RFC5569?

Michel.

From paul.hoffman@vpnc.org  Thu Jun 23 15:36:11 2011
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 B5A4911E8078; Thu, 23 Jun 2011 15:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level: 
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c9TllnGjmfBe; Thu, 23 Jun 2011 15:36:11 -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 CCECB11E8081; Thu, 23 Jun 2011 15:36:10 -0700 (PDT)
Received: from [10.20.30.101] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p5NMa3Rd022874 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 23 Jun 2011 15:36:04 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Why ask for IETF Consensus on a WG document?
Date: Thu, 23 Jun 2011 15:36:08 -0700
Message-Id: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>
To: The IESG <iesg@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2011 22:36:11 -0000

Greetings again. The subject line is an honest question, not a gripe.

For those on the ietf@ mailing list, please see =
<https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ballot=
/>. In short, the IESG just approved publication of =
draft-ietf-v6ops-6to4-to-historic, even with what appears to be a lack =
of consensus in the comments on the ietf@ mailing list. One AD called it =
"pretty rough", but my quick count shows that it was not rough at all: =
there were more people on the ietf@ against this than in favor of it. If =
the consensus in a WG for a document was the same as we saw on ietf@ for =
this document, and the WG chair declared consensus anyway, there would =
be some serious talks with that WG AD about the chairs.

For a document such as this, why even ask for IETF consensus if the IETF =
consensus doesn't matter? There was a lot of good discussion and a fair =
number of varied objections to approval of the document. It sounds like =
the WG was strongly in favor of the document, which may be sufficient =
motivation to publish it, but the intermediate step of asking for IETF =
consensus and then not paying attention to the result then seems =
wasteful of IETF time.

If the IESG has a policy that "WG consensus trumps IETF consensus", =
that's fine, but it should be a stated policy so we know where to spend =
our time. If this document is special for some reason (for example, =
because it was about policy instead of being a protocol) and therefore =
the IESG measures consensus differently, that too is fine if we all know =
that ahead of time. Even a policy of "more than a dozen IETF regulars =
must object on ietf@ before we will consider overturning a WG" is fine, =
as long as it is a stated policy. If the IESG has a policy that says =
"the way we count in IETF Last Call is different than the way we expect =
Working Group chairs to count in WG Last call", that's fine as well. =
None of that is obvious from the ballot comments that are visible to the =
community, however.

Guidance from the IESG for our future participation in IETF Last Call =
discussions would be greatly appreciated. We try to save you folks time =
and effort; such guidance would return the favor to us.

--Paul Hoffman


From stpeter@stpeter.im  Thu Jun 23 17:44:43 2011
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 8F13F11E81AE; Thu, 23 Jun 2011 17:44:43 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4q7aJ-3j5BGq; Thu, 23 Jun 2011 17:44:43 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id D3D0B11E8081; Thu, 23 Jun 2011 17:44:42 -0700 (PDT)
Received: from squire.local (dsl-179-111.dynamic-dsl.frii.net [216.17.179.111]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id D33AD4032B; Thu, 23 Jun 2011 18:45:26 -0600 (MDT)
Message-ID: <4E03DDF8.1040806@stpeter.im>
Date: Thu, 23 Jun 2011 18:44:40 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>
In-Reply-To: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>
X-Enigmail-Version: 1.1.1
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Fri, 24 Jun 2011 00:44:43 -0000

On 6/23/11 4:36 PM, Paul Hoffman wrote:
> Greetings again. The subject line is an honest question, not a
> gripe.
> 
> For those on the ietf@ mailing list, please see
> <https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ballot/>.
> In short, the IESG just approved publication of
> draft-ietf-v6ops-6to4-to-historic, even with what appears to be a
> lack of consensus in the comments on the ietf@ mailing list. One AD
> called it "pretty rough", but my quick count shows that it was not
> rough at all: there were more people on the ietf@ against this than
> in favor of it.

I can't speak for other IESG members, but I made a point of reading the
full text of every IETF LC message about this I-D, and I disagree with
the accuracy of your quick count. It's true that the Last Call did not
achieve unanimity or even smooth consensus, but my reading was that a
few folks were in the rough (although quite vocal) and that there was
rough consensus to publish. I would not have ballotted "No Objection"
otherwise. However, I freely admit that I might be wrong.

Peter

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



From melinda.shore@gmail.com  Thu Jun 23 17:58:21 2011
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 0F9CF11E8084; Thu, 23 Jun 2011 17:58:21 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aRw4hsIWTt2A; Thu, 23 Jun 2011 17:58:20 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE7711E807C; Thu, 23 Jun 2011 17:58:20 -0700 (PDT)
Received: by pwj5 with SMTP id 5so1654434pwj.31 for <multiple recipients>; Thu, 23 Jun 2011 17:58:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=qY4QVxZE3iP5vUYGSa73y3HxLnrm2PlYDpsq+qE9eCE=; b=NBVhRvZdxrjYCWxmwZz3PdgnjeadVFK0y3rzc1tLZr5juU6EGXZCTcLWrtE4HdiEj+ lfa+Lmmde/SS2oKnjBJvVheO6736ITSvl9LAcdNNliBi37LEd9+WNVgD/o+B9gdbxFN/ 1IsZXb4YRJeu0GYpwLc2FMM9LUqJKN0sN4mdQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=altqrbIpkRdd2AYCRVv6lsURcyGoUd3LSj6F2hnfxPZXzcRe1+qIvJZ+VZyQ2Ty5rZ 1I0nD3xQbYNLLo4vBFF2AxER9tixmUiNVJuRK6MMv62MK+z9honk60E556qNTuEomOzE ItnqOi8YKvQ9kScylobhqTdwMJZGqYaglS4o4=
Received: by 10.143.66.19 with SMTP id t19mr544562wfk.262.1308877100188; Thu, 23 Jun 2011 17:58:20 -0700 (PDT)
Received: from [137.229.12.236] (drake.swits.alaska.edu [137.229.12.236]) by mx.google.com with ESMTPS id n9sm1502462wfk.20.2011.06.23.17.58.18 (version=SSLv3 cipher=OTHER); Thu, 23 Jun 2011 17:58:19 -0700 (PDT)
Message-ID: <4E03E12D.9040405@gmail.com>
Date: Thu, 23 Jun 2011 16:58:21 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im>
In-Reply-To: <4E03DDF8.1040806@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Fri, 24 Jun 2011 00:58:21 -0000

On 06/23/2011 04:44 PM, Peter Saint-Andre wrote:
 > [ ... ] but my reading was that a
 > few folks were in the rough (although quite vocal) and that there was
 > rough consensus to publish. I would not have ballotted "No Objection"
 > otherwise. However, I freely admit that I might be wrong.

I don't think anybody has a particularly rigorous working
definition of "rough consensus" and it leaves the door open
for this sort of disagreement.

I also think that institutional navel-gazing around this stuff has
repeatedly proven to be fruitless and that maybe people who are
calling consensus should probably talk amongst themselves about
what they mean by "consensus" and how it differs from voting.

Melinda

From paul.hoffman@vpnc.org  Thu Jun 23 18:15:17 2011
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 E2D7E11E8084; Thu, 23 Jun 2011 18:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level: 
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HBEsQmogvpMO; Thu, 23 Jun 2011 18:15:16 -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 B969811E807C; Thu, 23 Jun 2011 18:15:14 -0700 (PDT)
Received: from [10.20.30.101] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p5O1F7Lv030973 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 23 Jun 2011 18:15:08 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4E03DDF8.1040806@stpeter.im>
Date: Thu, 23 Jun 2011 18:15:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1084)
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: Fri, 24 Jun 2011 01:15:17 -0000

On Jun 23, 2011, at 5:44 PM, Peter Saint-Andre wrote:

> I can't speak for other IESG members, but I made a point of reading =
the
> full text of every IETF LC message about this I-D, and I disagree with
> the accuracy of your quick count. It's true that the Last Call did not
> achieve unanimity or even smooth consensus, but my reading was that a
> few folks were in the rough (although quite vocal) and that there was
> rough consensus to publish. I would not have ballotted "No Objection"
> otherwise. However, I freely admit that I might be wrong.

And this goes back to my question of how the IESG wants to deal with =
consensus calls on ietf@. You say "a few folks", but my count says that =
there were six people who actively said "do not publish", and a few more =
who hinted at it. On the positive side, there were about five from the =
WG who said "publish" and a couple who said "let's just move on".

I do not put the latter into the "positive" category, but you might. =
However, in general, I have heard ADs tell WG chairs *not* to consider =
"I'm tired of this, publish this and move on" as useful input to the WG =
consensus process. Is it more useful in the IETF consensus process? =
Given that a WG has already worked hard on a document, I can see where =
such sentiment on ietf@ would be considered positive, but it would be =
good to hear that explicitly.

Said a different way, what needs to happen in IETF Last Call to overcome =
"we already discussed this in the WG" (which was the majority of the =
positive comments in this case)? Does a non-WG member need to do more, =
and if so what?=20

--Paul Hoffman

P.S. As someone noted offline, I did not voice my opinion on this =
document in IETF Last Call. That's correct: I didn't (and don't) care =
that much about the outcome either way. I do care about knowing how IETF =
consensus is judged, however.


From brian.e.carpenter@gmail.com  Thu Jun 23 18:34:47 2011
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 17AA311E80D8; Thu, 23 Jun 2011 18:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.518
X-Spam-Level: 
X-Spam-Status: No, score=-103.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VppBHDBw2FK4; Thu, 23 Jun 2011 18:34:46 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 10C9211E8084; Thu, 23 Jun 2011 18:34:45 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1821839fxm.31 for <multiple recipients>; Thu, 23 Jun 2011 18:34:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Fldd+CoAwEmsa4z3Vip5fPGnmnrcX7Twh/lUItaJ+UA=; b=f5LW7IYN2GAJfVWttAlLV/uMXl0XCUw8KlbIu8HS+ZqvGA2lZ08TRCR0L1mLHmi4eq Srum/Ju6YuQv+gwiCnx4mihS16GMc/39DiaNn/1zhGbaXHzoEjyMQ7wHMfvOomXHZW2X 2W5ZEOe7Cq5Cg+RVBV+wMs/5A217GUKj3yvKc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=L33LXejofT+1cuzm3K2wCo2fYVHwlV4dZ2k1ha/zXpjNqmIYBSSMyDBdgTL37rAkCH FUuReiFn+xvGIxcn44deT5SKHZBdbi++CTdHUHZp7ZbzGuXs5NBMkkc0r+pcGkcQ90o+ 7pgP7XOgu1IzbZ9a0JW8CeOHq3fRiw7oVLOOs=
Received: by 10.223.73.133 with SMTP id q5mr3637348faj.127.1308879285110; Thu, 23 Jun 2011 18:34:45 -0700 (PDT)
Received: from [10.255.25.96] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id o23sm1331501faa.9.2011.06.23.18.34.42 (version=SSLv3 cipher=OTHER); Thu, 23 Jun 2011 18:34:44 -0700 (PDT)
Message-ID: <4E03E9A9.2000300@gmail.com>
Date: Fri, 24 Jun 2011 13:34:33 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im>
In-Reply-To: <4E03DDF8.1040806@stpeter.im>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Fri, 24 Jun 2011 01:34:47 -0000

On 2011-06-24 12:44, Peter Saint-Andre wrote:
> On 6/23/11 4:36 PM, Paul Hoffman wrote:
>> Greetings again. The subject line is an honest question, not a
>> gripe.
>>
>> For those on the ietf@ mailing list, please see
>> <https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ballot/>.
>> In short, the IESG just approved publication of
>> draft-ietf-v6ops-6to4-to-historic, even with what appears to be a
>> lack of consensus in the comments on the ietf@ mailing list. One AD
>> called it "pretty rough", but my quick count shows that it was not
>> rough at all: there were more people on the ietf@ against this than
>> in favor of it.
> 
> I can't speak for other IESG members, but I made a point of reading the
> full text of every IETF LC message about this I-D, and I disagree with
> the accuracy of your quick count. It's true that the Last Call did not
> achieve unanimity or even smooth consensus, but my reading was that a
> few folks were in the rough (although quite vocal) and that there was
> rough consensus to publish. I would not have ballotted "No Objection"
> otherwise. However, I freely admit that I might be wrong.

I think that's about right. There were several strong and very raional
opinions against this, including some who were not involved in the similarly
rough consensus in the WG discussion. But (speaking as a co-author of one of
the drafts being historicised) I'd say the balance of opinion was to publish.
However, it's a close call.

    Brian

From stpeter@stpeter.im  Thu Jun 23 18:38:10 2011
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 D0459228017; Thu, 23 Jun 2011 18:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level: 
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dzGPVJoddtF7; Thu, 23 Jun 2011 18:38:10 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 24FE4228015; Thu, 23 Jun 2011 18:38:10 -0700 (PDT)
Received: from squire.local (dsl-179-111.dynamic-dsl.frii.net [216.17.179.111]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 6D7A04032B; Thu, 23 Jun 2011 19:38:53 -0600 (MDT)
Message-ID: <4E03EA7F.206@stpeter.im>
Date: Thu, 23 Jun 2011 19:38:07 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E12D.9040405@gmail.com>
In-Reply-To: <4E03E12D.9040405@gmail.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Fri, 24 Jun 2011 01:38:11 -0000

On 6/23/11 6:58 PM, Melinda Shore wrote:
> On 06/23/2011 04:44 PM, Peter Saint-Andre wrote:
>> [ ... ] but my reading was that a
>> few folks were in the rough (although quite vocal) and that there was
>> rough consensus to publish. I would not have ballotted "No Objection"
>> otherwise. However, I freely admit that I might be wrong.
> 
> I don't think anybody has a particularly rigorous working
> definition of "rough consensus" and it leaves the door open
> for this sort of disagreement.
> 
> I also think that institutional navel-gazing around this stuff has
> repeatedly proven to be fruitless and that maybe people who are
> calling consensus should probably talk amongst themselves about
> what they mean by "consensus" and how it differs from voting.

Omphaloskepsis aside, I've been thinking about writing an I-D on the
meaning of consensus, although I somehow doubt we'd be able to get
consensus on the topic...

Peter

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



From jmh@joelhalpern.com  Thu Jun 23 19:54:08 2011
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 7903311E8097; Thu, 23 Jun 2011 19:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.454
X-Spam-Level: 
X-Spam-Status: No, score=-102.454 tagged_above=-999 required=5 tests=[AWL=-0.189, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZPoSzX+QHpLD; Thu, 23 Jun 2011 19:54:08 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 1845511E8071; Thu, 23 Jun 2011 19:54:08 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob.out.tigertech.net [74.114.88.71]) by morbo.tigertech.net (Postfix) with ESMTP id DF983A63D8; Thu, 23 Jun 2011 19:18:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 8B56532466D4; Thu, 23 Jun 2011 19:17:13 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.154.181.49] (unknown [129.192.185.163]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id A3FE0324662A; Thu, 23 Jun 2011 19:17:12 -0700 (PDT)
Message-ID: <4E03F3A5.40905@joelhalpern.com>
Date: Thu, 23 Jun 2011 22:17:09 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
Subject: [Gen-art] Review: draft-ietf-mpls-ldp-p2mp-14
References: <4E038C9B.3070206@nostrum.com>
In-Reply-To: <4E038C9B.3070206@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Adrian Farrel <adrian@olddog.co.uk>, 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, 24 Jun 2011 02:54:08 -0000

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

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

Document: draft-ietf-mpls-ldp-p2mp-14
    Label Distribution Protocol Extensions for Point-to-Multipoint and
              Multipoint-to-Multipoint Label Switched Paths
Reviewer: Joel M. Halpern
Review Date: 23-June-2011
IETF LC End Date: 4-July-2011
IESG Telechat date: N/A

Summary:  This document is close to ready for publication as a Proposed 
Standard RFC>  Certain questions should be answered, and some minor 
issues considered.

Major issues:
     As I read the document, status codes (and stauts TLVs) are for 
reporting on the status of LSPs.  They are not for negotiating 
behaviors.  Thus, I find it very strange that make-before-break behavior 
(section 8) is requested (by a downstream device sending a request to an 
upstream device) by including a specific status code in the request. 
Has this technique been used in MPLS LDP before?

Minor issues:
     The definition (section 1.2)  of MP2MP LSPs should indicate that 
even though all nodes are allowed to send on the LSP, there is still a 
distinguished root node.

     The LDP MP Opaque Value Element extended type (section 2.3, second 
definition) seems to be gratuitous complexity, adding extra matching 
cases in the LDP processing path for no stated value.  Is there really 
believed to be a need for more than 254 types of Opaque values?  If so, 
explain it in the document.

     Section 3.3.1.3 begins by describing two methods for installing the 
upstream path of a MP2MPLSP.  After carefully describing both, it says 
to only and always use the second method.  Would it not be better to 
describe the constraint (that the upstream path must be in place all the 
way to the root before it claims to be established), and then describe 
the one method that meets taht.  Just don't describe a method that is 
not to be used.

Nits/editorial comments:

From evnikita2@gmail.com  Thu Jun 23 20:49:20 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F3C611E81A4 for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 20:49:20 -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.168, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hRq1xWKfD4IH for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 20:49:18 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5CA8711E8071 for <ietf@ietf.org>; Thu, 23 Jun 2011 20:49:18 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1864247fxm.31 for <ietf@ietf.org>; Thu, 23 Jun 2011 20:49:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+Ix/OqS51TkbyuFLIcKXiBYpKWyEWZo0d9dCDxSKkQM=; b=Va5EgOCj8uAp7790z/0xAtrKoOYRUJoyLO1G28R8h7zQrPLLEDjVsoFitvcApf5fF0 I/xejAJ8JT04fy/Bhq/Vd+8NHE7WreVkRskwB9xNyxu5OfnAawX4u3VQs4oM3N0UlJG5 ep81jxVZ5NG1SP2Kt9T3GBrQPH6Q+qIh8m9Eo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Z0br22rgUrVyz3GBnSRi3z4rFMtMT8ZsxGA0cE/3zzHZj0BIXD4WN5g6QjX9BFAzCq BpcoP3R43hVUb++tmNLQLxvXup8vOjfn1Ca1qwSgMAkjQozmnt6dTbaVO17d7a7bguxD lnmbS7l6zpme4h7ZuLM6D/YDC6tC/4xnDwQwQ=
Received: by 10.223.71.201 with SMTP id i9mr1713186faj.97.1308887357461; Thu, 23 Jun 2011 20:49:17 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id q10sm1374197fan.8.2011.06.23.20.49.14 (version=SSLv3 cipher=OTHER); Thu, 23 Jun 2011 20:49:15 -0700 (PDT)
Message-ID: <4E040968.3050205@gmail.com>
Date: Fri, 24 Jun 2011 06:50:00 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
References: <0EC26EB10287E2A20769C9CC@PST.JCK.COM> <4E0171EB.4020109@gmail.com> <4E0320A2.6030000@lachy.id.au>
In-Reply-To: <4E0320A2.6030000@lachy.id.au>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-holsten-about-uri-scheme@tools.ietf.org, John C Klensin <klensin@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: Fri, 24 Jun 2011 03:49:20 -0000

Hello all,

23.06.2011 14:16, Lachlan Hunt wrote:
> On 2011-06-22 06:39, Mykyta Yevstifeyev wrote:
>>> (1) There seems to be consensus that registering this URI as a
>>> mechanism for accessing built-in functionality and configuration
>>> information such as application information, preferences, or
>>> settings. (Text derived from the Abstract with "configuration
>>> information", which may mean more to some readers, added and
>>> "easter eggs" dropped. Dropping "easter eggs" reflects other
>>> comments on the list and my opinion that it isn't worth the
>>> trouble to define.
>>
>> With regard to easter eggs I have no strong position. If it is
>> troubling, I don't object to remove any mention of them from the 
>> document.
>
> The easter eggs are mentioned only in non-normative parts of the 
> document, including the abstract and examples, and just reflect the 
> reality of what some implementations use about URLs for.  I do not 
> understand the objection.
As I've already mentioned, I have no any strong position regarding 
"easter eggs".  Yet, my opinion is that mentioning them clarifies the 
usage of about URIs a bit.
>
>>> (2) The document itself reflects an attempt to define the
>>> undefinable. There is no cross-implementation interoperability
>>> issue here; if anything, the document should me more clear that
>>> it would be stupid to assume it. The document, nonetheless,
>>> tries to define what is done with some specific URIs in some
>>> places and then has to turn around and indicate that they may be
>>> used in entirely different ways in other places and should not
>>> be relied upon. In the process, it skips back and forth between
>>> being descriptive and being normative, with some definitions
>>> becoming circular in the process. That just isn't a good
>>> combination and some of it actually looks pretty silly.
>
> This feedback is not helpful, as it just vague hand waving and 
> dismissive.
I wouldn't say so; this remark is quite reasonable.  In our section 
dedicated to categorization we try to normatively specify how about URIs 
are resolved due to the categories we try to create; ibidem we sometimes 
give no clear description of related issue.  Eg., suppose I write my 
browser, YevstifeyevBrowser, which uses the about URI about:bad-guy.  I 
then claim it as "reserved" and, according to our draft, any application 
which is compatible to it must resolve it to what I want.  Suppose 
another browser, FooBrowser, makes use if about:bad-guy as well, but for 
other purpose; but, being compatible with our spec. it can't.  The issue 
is impossibility to rule out which is a priori used internally only and 
is implementation-specific.  Another instance.  Some application may 
treat some about URIs as resolvable while other as unresolvable.  Eg., 
FooBrowser may resolve "unresolvable-as-per-HTML5" about:legacy-compat 
to the page saying it is unresolvable etc.
>
>> I may partly agree with you. Reading the document for a number of times
>> I've also noticed this. A logical conclusion of everything
>> aforementioned is below.
>>
>>> "about:blank" is particularly troubling in that regard because
>>> the text essentially says that it is reserved except where it
>>> isn't.
>
> Nonsense. "about:blank" is clearly defined as reserved, and nowhere 
> does it indicate otherwise.  Perhaps you are confused where it 
> excludes variations that include query strings?
"about:blank" is a special case which is one of the rare instances of 
what is acceptable by almost all browsers.  As for queries - I've 
checked several browsers for their behavior.  Firefox 5.0 - 
about:blank?aa is treated about:blank.  Chrome 12 - the same.  IE8 
treats about:blank?aa as invalid URI returning "going to web page 
canceled".  Opera 11 - as FF.  Finally, Safari 3.2.1 has the same 
behavior.  I see the majority of contemporary browsers treat about:blank 
with query component as if it isn't present.  I personally see no point 
in reserving the about URI with no query only.
>
>>> Option 2: Really try to make this normative wrt some subset of
>>> URI values. In this approach, stop the extremely confusing
>>> circling around.
>
> The circular definitions have been resolved in the editor's draft.
>
> https://github.com/josephholsten/about-uri-scheme/blob/master/draft-holsten-about-uri-scheme-07.txt 
>
I, as one of the editors, is a bit confused by this draft.  It 
incorporates none of changes I proposed and made after you made it 
available.  My editor's version is from June 14, not April 13, when this 
file was uploaded.
>
>>> Indicate explicitly that "about" URIs have been used enough and in
>>> enough different circumstances that no application should assume
>>> that an "about" URI, if encountered, is actually its own and that
>>> due caution needs to be taken about non-conforming implementations.
>
> That's the whole point of the unreserved category.
>
>>> Then explicitly reserve, not only"about:blank", but everything the
>>> authors think is worth listing in Examples _and_ create an IANA
>>> registry for more of them.
>
> No.  The registry is a completely unnecessary bureaucratic mess that 
> I'm strongly fighting against, and will most likely be removing from a 
> future draft.  Mykyta added mention of it to the draft* against my 
> wishes after I allowed him/her
I'm male, FYI.
> to become an editor even though (s)he has still not been able to 
> provide justification for why such a registry is necessary.  (However, 
> I allowed the draft to be publicised with it for public review and 
> comment.)
>
> * Note: That change hasn't been checked into github, and I don't know
>   if Mykyta has those changes somewhere public yet.
I have no access to Github but I've sent you the latest edited version 
of the draft in email on 14 June, if you remember.
>
> The purely informative value of a registry can and has already been 
> achieved by Wikipedia.  The three known reserved about URIs (blank, 
> legacy-compat and scrdoc) are already documented, as are many other 
> unreserved, but recognised application-specific URIs.
>
> Beyond that, the whole concept of reservation only exists to give 
> other specifications a clear way to define about URIs for their own 
> purposes and doesn't need any formal registration process. It doesn't 
> have any impact on any implementations that are not implementing the 
> given specification.
Considering the controversy of this question, I think we may put it 
aside for a time.  Anyway, when the document is published, we can add 
the registry if there is a necessity; please note that my justification 
for the registry was ongoing comments on its necessity during Last Call, 
so IMO, of course, "he has still not been able to provide justification 
for why such a registry is necessary" is probably untrue.

Actually, I have some concerns about section on resolving about URIs.  I 
understand what I propose below surely does not fit in what we have in 
the current draft and, mainly, its concepts.  However, were I to decide 
myself, I would fully rewrite the document is the following way.  First, 
the intended status would be Informational.  Syntax would be left in the 
current form.  More important the semantics probably are.  I'd mention 
that (1) 'about' URIs are used internally only, so any application is 
free to resolve it to any resource with any semantics, except the 
several instances, defined below as "special-purpose 'about' URIs", 
which are permanently reserved for use in a specific manner; (2) a 
special-purpose 'about' URI as an 'about' URI using a particular 
well-known segment and which is defined to be used for a specific 
purpose and MUST be used only and only as defined in a specification of 
such URI; (3) categorization into "resolvable/unresolvable" would be 
eliminated; (4) provisions regarding recognition of the URIs would be 
almost the same.  Encoding considerations would be that about URIs may 
contain characters from UCS first encoded with UTF-8; those UTF-8 
encoded characters which do not fit in the RFC 3986 definition for 
<segment> or <query> SHALL be percent-encoded within corresponding 
part.  Then a registry for special-purpose 'about' URIs would be 
created.  For a number of now-in-use, though not special-purpose, 
'about' URIs the reader would be pointed to 
http://en.wikipedia.org/wiki/About_URI_scheme

I'd like to seek the current editors' opinion on the proposed approach 
above.  IMO, such description is (a) clearer and (b) removes a number of 
controversial issues.
>
>>> the document should be really clear that all that the use of
>>> "about:" really tells someone is that it is application-specific
>>> and that a particular implementation of a particular application
>>> may do whatever it pleases with them.
>
> It still says that, though the way it is written is a quite ambiguous 
> and convoluted and I understand the confusion here.  I'll rephrase the 
> section on recognised URIs to address this.
See my proposal above.
>
>>> Smaller issues:
>>>
>>> (i) Section 6, Normalization, sadly really doesn't belong here
>>> unless the authors can show that everyone interprets "about:"
>>> according to those rules. Otherwise, it would be better to say
>>> that the URI is interpreted in an implementation-specific way
>>> and that implementations would be well-advised to conform to
>>> normal URI syntax rules unless there is a strong reason not
>
>> Agree here. This thread restarted with the response to Boris's comment
>> regarding Gecko's normalization rules. This was to claim that no unified
>> rules for the scheme which is a priori used by the applications on their
>> own. As I proposed below, if no document is to be written, the template
>> may contain such statement about implementation-specific normalization
>> rules.
>
> Yes, normalisation requirements will be removed.
Probably they aren't to be removed but rather mentioned as 
implementation-specific.
>
>>> (ii) IMO, Section 7, Security Considerations, should be modified
>>> to include an explicit statement that, since these things are
>>> intended for convenience use within an implementation of an
>>> application, passing them between systems (embedded in files or
>>> otherwise) is very risky behavior and should generally be
>>> discouraged except, possibly, in documentation contexts.
>> I agree here.
>> ...
>> Section 4 is what is also questionable. This issue was raised during
>> Last Call and I think can be resolved by saying that an about URIs may
>> contain UTF-8 encoded characters in the <segment>, as suggested by RFC
>> 3986 and that's all.
>
> Mykyta, feel free to revise sections 4 and 7 as you see fit.
>
All the best,
Mykyta Yevstifeyev


From narten@us.ibm.com  Thu Jun 23 21:53:17 2011
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 2544911E8105 for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 21:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.949
X-Spam-Level: 
X-Spam-Status: No, score=-105.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fAxigpdAHFqE for <ietf@ietfa.amsl.com>; Thu, 23 Jun 2011 21:53:16 -0700 (PDT)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by ietfa.amsl.com (Postfix) with ESMTP id 12DB011E80AF for <ietf@ietf.org>; Thu, 23 Jun 2011 21:53:16 -0700 (PDT)
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e33.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p5O4jbV5013478 for <ietf@ietf.org>; Thu, 23 Jun 2011 22:45:37 -0600
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id p5O4r4Xn165702 for <ietf@ietf.org>; Thu, 23 Jun 2011 22:53:04 -0600
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 p5NMr33m029765 for <ietf@ietf.org>; Thu, 23 Jun 2011 16:53:03 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.176.22]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p5NMr32N029754 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 23 Jun 2011 16:53:03 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p5O4r2Gt019808 for <ietf@ietf.org>; Fri, 24 Jun 2011 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p5O4r2fi019796 for ietf@ietf.org; Fri, 24 Jun 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201106240453.p5O4r2fi019796@rotala.raleigh.ibm.com>
Date: Fri, 24 Jun 2011 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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 04:53:17 -0000

Total of 155 messages in the last 7 days.
 
script run at: Fri Jun 24 00:53:02 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.10% |   11 |  4.90% |    47604 | johnl@iecc.com
  5.81% |    9 |  5.48% |    53245 | gwz@net-zen.net
  5.16% |    8 |  4.19% |    40724 | msk@cloudmark.com
  2.58% |    4 |  3.87% |    37643 | stpeter@stpeter.im
  3.23% |    5 |  3.03% |    29433 | dhc2@dcrocker.net
  3.23% |    5 |  2.55% |    24753 | moore@network-heretics.com
  2.58% |    4 |  3.00% |    29112 | ray.bellis@nominet.org.uk
  1.94% |    3 |  3.57% |    34676 | evnikita2@gmail.com
  2.58% |    4 |  2.83% |    27536 | joelja@bogus.com
  2.58% |    4 |  2.29% |    22247 | mstjohns@comcast.net
  2.58% |    4 |  2.16% |    20984 | ole@cisco.com
  2.58% |    4 |  1.80% |    17473 | simon.perreault@viagenie.ca
  1.94% |    3 |  2.18% |    21226 | bzbarsky@mit.edu
  1.94% |    3 |  2.01% |    19549 | randy@qualcomm.com
  1.94% |    3 |  1.97% |    19170 | barryleiba@computer.org
  1.94% |    3 |  1.88% |    18308 | krishnabirth@gmail.com
  1.94% |    3 |  1.71% |    16631 | ben@nostrum.com
  1.94% |    3 |  1.60% |    15517 | john-ietf@jck.com
  1.94% |    3 |  1.58% |    15320 | scott.brim@gmail.com
  1.94% |    3 |  1.56% |    15188 | julian.reschke@gmx.de
  1.29% |    2 |  2.08% |    20180 | mnot@mnot.net
  1.29% |    2 |  2.01% |    19506 | mary.ietf.barnes@gmail.com
  1.29% |    2 |  1.71% |    16632 | lachlan.hunt@lachy.id.au
  1.29% |    2 |  1.35% |    13122 | henk.uijterwaal@gmail.com
  1.29% |    2 |  1.33% |    12914 | rdroms.ietf@gmail.com
  1.29% |    2 |  1.21% |    11710 | tjc@ecs.soton.ac.uk
  1.29% |    2 |  1.19% |    11538 | mcr@sandelman.ca
  1.29% |    2 |  1.16% |    11261 | paul.hoffman@vpnc.org
  1.29% |    2 |  1.14% |    11093 | lear@cisco.com
  1.29% |    2 |  1.09% |    10591 | melinda.shore@gmail.com
  1.29% |    2 |  0.95% |     9225 | ajs@anvilwalrusden.com
  0.65% |    1 |  1.58% |    15307 | doug.mtview@gmail.com
  0.65% |    1 |  1.30% |    12593 | ietfdbh@comcast.net
  0.65% |    1 |  1.24% |    12000 | gregory.cauchie@orange-ftgroup.com
  0.65% |    1 |  1.15% |    11176 | paulej@packetizer.com
  0.65% |    1 |  0.95% |     9228 | dotis@mail-abuse.org
  0.65% |    1 |  0.90% |     8697 | adrian@olddog.co.uk
  0.65% |    1 |  0.87% |     8434 | klensin@jck.com
  0.65% |    1 |  0.85% |     8262 | narten@us.ibm.com
  0.65% |    1 |  0.85% |     8238 | fluffy@cisco.com
  0.65% |    1 |  0.81% |     7830 | lberger@labn.net
  0.65% |    1 |  0.76% |     7397 | hamza.gharsallah@gmail.com
  0.65% |    1 |  0.74% |     7187 | d3e3e3@gmail.com
  0.65% |    1 |  0.74% |     7145 | ot@cisco.com
  0.65% |    1 |  0.73% |     7094 | nurit.sprecher@nsn.com
  0.65% |    1 |  0.72% |     6960 | daedulus@btconnect.com
  0.65% |    1 |  0.71% |     6921 | jmpolk@cisco.com
  0.65% |    1 |  0.69% |     6665 | ietf@thomasclausen.org
  0.65% |    1 |  0.68% |     6568 | rbarnes@bbn.com
  0.65% |    1 |  0.68% |     6568 | bob.hinden@gmail.com
  0.65% |    1 |  0.65% |     6340 | rja.lists@gmail.com
  0.65% |    1 |  0.65% |     6336 | scott@kitterman.com
  0.65% |    1 |  0.65% |     6310 | marka@isc.org
  0.65% |    1 |  0.64% |     6248 | brian.e.carpenter@gmail.com
  0.65% |    1 |  0.64% |     6238 | stewe@stewe.org
  0.65% |    1 |  0.64% |     6175 | jmh@joelhalpern.com
  0.65% |    1 |  0.63% |     6164 | steve@shinkuro.com
  0.65% |    1 |  0.60% |     5809 | dworley@avaya.com
  0.65% |    1 |  0.60% |     5792 | tnadeau@lucidvision.com
  0.65% |    1 |  0.59% |     5740 | sob@harvard.edu
  0.65% |    1 |  0.57% |     5578 | jdrake@juniper.net
  0.65% |    1 |  0.57% |     5574 | klaas@wierenga.net
  0.65% |    1 |  0.57% |     5543 | hoene@uni-tuebingen.de
  0.65% |    1 |  0.57% |     5491 | julien.ietf@gmail.com
  0.65% |    1 |  0.53% |     5179 | aj@sneep.net
  0.65% |    1 |  0.50% |     4895 | cabo@tzi.org
  0.65% |    1 |  0.50% |     4851 | henk@uijterwaal.nl
  0.65% |    1 |  0.49% |     4760 | jari.arkko@piuha.net
  0.65% |    1 |  0.48% |     4663 | christer.holmberg@ericsson.com
  0.65% |    1 |  0.47% |     4577 | dave@cridland.net
  0.65% |    1 |  0.46% |     4474 | tytso@mit.edu
  0.65% |    1 |  0.46% |     4426 | ekr@rtfm.com
  0.65% |    1 |  0.45% |     4405 | michel@arneill-py.sacramento.ca.us
  0.65% |    1 |  0.42% |     4129 | mathieu.goessens@irisa.fr
  0.65% |    1 |  0.36% |     3482 | iad@ietf.org
--------+------+--------+----------+------------------------
100.00% |  155 |100.00% |   971560 | Total

From daedulus@btconnect.com  Fri Jun 24 02:38:13 2011
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 C68C321F853D; Fri, 24 Jun 2011 02:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.974
X-Spam-Level: 
X-Spam-Status: No, score=-0.974 tagged_above=-999 required=5 tests=[AWL=-0.975, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MOEo+tzlHKnC; Fri, 24 Jun 2011 02:38:12 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by ietfa.amsl.com (Postfix) with ESMTP id 5167E21F853C; Fri, 24 Jun 2011 02:38:11 -0700 (PDT)
Received: from host81-156-207-154.range81-156.btcentralplus.com (HELO pc6) ([81.156.207.154]) by c2beaomr06.btconnect.com with SMTP id DOF40071; Fri, 24 Jun 2011 10:38:07 +0100 (BST)
Message-ID: <002b01cc3249$b67abc00$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Paul Hoffman" <paul.hoffman@vpnc.org>, "The IESG" <iesg@ietf.org>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>
Subject: Re: Why ask for IETF Consensus on a WG document?
Date: Fri, 24 Jun 2011 10:35:41 +0200
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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0302.4E045AFE.0069, actions=TAG
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.6.24.85114:17:7.586, ip=81.156.207.154, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_PATH, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0209.4E045B00.006A,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
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 Jun 2011 09:38:13 -0000

----- Original Message -----
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "The IESG" <iesg@ietf.org>
Cc: "IETF-Discussion list" <ietf@ietf.org>
Sent: Friday, June 24, 2011 12:36 AM
> Greetings again. The subject line is an honest question, not a gripe.
>
> For those on the ietf@ mailing list, please see
<https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ballot/>. In
short, the IESG just approved publication of draft-ietf-v6ops-6to4-to-historic,
even with what appears to be a lack of consensus in the comments on the ietf@
mailing list. One AD called it "pretty rough", but my quick count shows that it
was not rough at all: there were more people on the ietf@ against this than in
favor of it. If the consensus in a WG for a document was the same as we saw on
ietf@ for this document, and the WG chair declared consensus anyway, there would
be some serious talks with that WG AD about the chairs.
>
> For a document such as this, why even ask for IETF consensus if the IETF
consensus doesn't matter? There was a lot of good discussion and a fair number
of varied objections to approval of the document. It sounds like the WG was
strongly in favor of the document, which may be sufficient motivation to publish
it, but the intermediate step of asking for IETF consensus and then not paying
attention to the result then seems wasteful of IETF time.
>
> If the IESG has a policy that "WG consensus trumps IETF consensus", that's
fine, but it should be a stated policy so we know where to spend our time.

I have always seen that as part of our procedures. The IETF Last Call is mostly
about objections, about problems missed, about unforeseen interactions with
other work.  Most of those who spoke up in support of a WG Last Call do not go
on to support the IETF Last Call, while those who object most strenuously in a
WG Last Call tend to repeat their objections at an IETF Last Call, so I have
always taken as axiomatic that the IESG would factor in all the support
expressed in a WG Last Call into the judgement of consensus on an IETF Last
Call, as opposed to a mere count of e-mails to the IETF list during the IETF
Last Call.

The I-D in question seems to fit this pattern perfectly.

Tom Petch


If this document is special for some reason (for example, because it was about
policy instead of being a protocol) and therefore the IESG measures consensus
differently, that too is fine if we all know that ahead of time. Even a policy
of "more than a dozen IETF regulars must object on ietf@ before we will consider
overturning a WG" is fine, as long as it is a stated policy. If the IESG has a
policy that says "the way we count in IETF Last Call is different than the way
we expect Working Group chairs to count in WG Last call", that's fine as well.
None of that is obvious from the ballot comments that are visible to the
community, however.
>
> Guidance from the IESG for our future participation in IETF Last Call
discussions would be greatly appreciated. We try to save you folks time and
effort; such guidance would return the favor to us.
>
> --Paul Hoffman
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From stephen.farrell@cs.tcd.ie  Fri Jun 24 02:40:26 2011
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 6F8D621F84E1; Fri, 24 Jun 2011 02:40:26 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zq4RXQEYP3k3; Fri, 24 Jun 2011 02:40:25 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id AABD621F8530; Fri, 24 Jun 2011 02:40:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 1691C171C1B; Fri, 24 Jun 2011 10:40:19 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1308908418; bh=v2qY4B+yYjsIbN 61xgmcEnWNMWPtYBaLnj+LZcAxSnk=; b=qzNYoHRDYJRr2HBndRliMMRnuRRgNk D9C403Q0v7+vcje3MtQOf1rbTRa+gPEXkuhb2pVFidw/9jVCZv+NCzhpTKI3soRk Dg+Ej5P5KdyZ00MT6XIkaeBunrM0uiNo+luyJiygZ5SQLT7oRSu5uUXwUvEnmR3X 0AVC/7MwzIebFw8gVkzkXaP/gQGS7kA7IUK/650XqCu3qPrZzMRm61xXxBbMvjyB tyyGNtqx+eanw+q0V5WbPmdUwbCc5k35GUAX0MLqBN2AnhpXEV9O3Euuiys3WM4J e00CLJesb3UECdpRMVi8BLqpxzMkqd3zm+NXEaRTRmSqTuf8d+NFeg2Q==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id zvhmqyeg4cse; Fri, 24 Jun 2011 10:40:18 +0100 (IST)
Received: from [134.226.36.137] (stephen-samy.dsg.cs.tcd.ie [134.226.36.137]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 39BF6171C19; Fri, 24 Jun 2011 10:40:16 +0100 (IST)
Message-ID: <4E045B80.7060800@cs.tcd.ie>
Date: Fri, 24 Jun 2011 10:40:16 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org>
In-Reply-To: <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Fri, 24 Jun 2011 09:40:26 -0000

Basically, I approached this the way Peter did. One further
point below though.

On 24/06/11 02:15, Paul Hoffman wrote:
> Said a different way, what needs to happen in IETF Last Call to overcome "we already discussed this in the WG" (which was the majority of the positive comments in this case)? Does a non-WG member need to do more, and if so what? 

In addition to the other factors already mentioned, I didn't
see what I thought were significant new facts or issues being
raised at the IETF LC. I think that such things are perhaps
more likely to cause the IETF rough consensus to differ from
that in the WG. In this case, it looked to me like people
were bringing concerns already expressed in the WG to the
attention of the wider community, which is a reasonable thing
to do in cases like this where the WG consensus was already
fairly rough.

It could well be that I know so little about 6to4 that I was
wrong in that conclusion of course, but then there's so much
about which I know so little that I've gotten used to living
with that risk;-)

S.

From moore@network-heretics.com  Fri Jun 24 04:35:39 2011
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 3F10121F845E; Fri, 24 Jun 2011 04:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.401
X-Spam-Level: 
X-Spam-Status: No, score=-3.401 tagged_above=-999 required=5 tests=[AWL=0.198,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6iMCaBkqIQ8f; Fri, 24 Jun 2011 04:35:38 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id A368021F8459; Fri, 24 Jun 2011 04:35:38 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 9F15421270; Fri, 24 Jun 2011 07:35:37 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Fri, 24 Jun 2011 07:35:37 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=8GExfl4kjfGKZB89EDi4Sf4alew=; b=oUGMQba+I/vJUY1NXn1aKldsz5iKXwyiaDEHA77oOkKmijolGNmjfCUUemNnflmW6VYGcswnroinDTUAP6Q6p5nBSLotJVmfxOM14rchsiMWtHv4zE22DKef2HOayP7xZzoWPBMLdj5Haa6RsMO7BailFqidMufzQ3QL7LebQw8=
X-Sasl-enc: yyHljwp6REhTrZr0II23pKKz+IkWZMYFGJqSxyT7BwQW 1308915337
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 8659B4068E7; Fri, 24 Jun 2011 07:35:36 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E03DDF8.1040806@stpeter.im>
Date: Fri, 24 Jun 2011 07:35:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1485FF3E-0A3E-40C0-A785-775C9BCE7B73@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1084)
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: Fri, 24 Jun 2011 11:35:39 -0000

On Jun 23, 2011, at 8:44 PM, Peter Saint-Andre wrote:

> On 6/23/11 4:36 PM, Paul Hoffman wrote:
>> Greetings again. The subject line is an honest question, not a
>> gripe.
>>=20
>> For those on the ietf@ mailing list, please see
>> =
<https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ballot=
/>.
>> In short, the IESG just approved publication of
>> draft-ietf-v6ops-6to4-to-historic, even with what appears to be a
>> lack of consensus in the comments on the ietf@ mailing list. One AD
>> called it "pretty rough", but my quick count shows that it was not
>> rough at all: there were more people on the ietf@ against this than
>> in favor of it.
>=20
> I can't speak for other IESG members, but I made a point of reading =
the
> full text of every IETF LC message about this I-D, and I disagree with
> the accuracy of your quick count. It's true that the Last Call did not
> achieve unanimity or even smooth consensus, but my reading was that a
> few folks were in the rough (although quite vocal) and that there was
> rough consensus to publish.=20

I often get the impression that dissenters are dismissed as "in the =
rough" and that their opinions, no matter how well expressed, are given =
less weight than those who are in favor.

It was clear to me that there was nowhere nearly consensus on this =
action, not even "rough consensus", and it was completely inappropriate =
of IESG to approve it. =20

Rough consensus does not mean you can disregard the opinions of those =
whom you disagree with.

Keith


From moore@network-heretics.com  Fri Jun 24 04:47:39 2011
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 E990221F84B5; Fri, 24 Jun 2011 04:47:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.105
X-Spam-Level: 
X-Spam-Status: No, score=-3.105 tagged_above=-999 required=5 tests=[AWL=-0.106, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhKzmGK88kvf; Fri, 24 Jun 2011 04:47:39 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 3AAE521F84B4; Fri, 24 Jun 2011 04:47:39 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id E1B7320EF4; Fri, 24 Jun 2011 07:47:38 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 24 Jun 2011 07:47:38 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=pDVeQWoBJitV9lsnjXI69Q1t7sc=; b=jNrsxODspoUaIQbPCzHQasqQ3TRtNbVb6U8/RtYgo0udmMcIn/XuW81O+vq4k9T8hif26NUws35IoF1CmzHNjB/DX5D/QHL+MFo+MeMrrgD36Eg03gMus6DxdIE/tn2Je8YtLFDsgr9pp4upkGHj3+ZIML5wYNRV9nVkeqJwm7g=
X-Sasl-enc: FcmpZ2o5rIE934OLivwKmFg0W2LL/LCFzPrdjO1x6skW 1308916058
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id ACBA3407328; Fri, 24 Jun 2011 07:47:37 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E045B80.7060800@cs.tcd.ie>
Date: Fri, 24 Jun 2011 07:47:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org> <4E045B80.7060800@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1084)
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: Fri, 24 Jun 2011 11:47:40 -0000

On Jun 24, 2011, at 5:40 AM, Stephen Farrell wrote:

>=20
> Basically, I approached this the way Peter did. One further
> point below though.
>=20
> On 24/06/11 02:15, Paul Hoffman wrote:
>> Said a different way, what needs to happen in IETF Last Call to =
overcome "we already discussed this in the WG" (which was the majority =
of the positive comments in this case)? Does a non-WG member need to do =
more, and if so what?=20
>=20
> In addition to the other factors already mentioned, I didn't
> see what I thought were significant new facts or issues being
> raised at the IETF LC. I think that such things are perhaps
> more likely to cause the IETF rough consensus to differ from
> that in the WG. In this case, it looked to me like people
> were bringing concerns already expressed in the WG to the
> attention of the wider community, which is a reasonable thing
> to do in cases like this where the WG consensus was already
> fairly rough.
>=20
> It could well be that I know so little about 6to4 that I was
> wrong in that conclusion of course, but then there's so much
> about which I know so little that I've gotten used to living
> with that risk;-)

It's problematic, and I believe inappropriate, to consider WG consensus =
as contributing to community consensus.  The two questions need to be =
considered separately, for two reasons:

1. Working groups often have strong biases and aren't representative of =
the whole community.  Put another way, a working group often represents =
only one side of a tussle, and working groups are often deliberately =
chartered in such a way as to minimize the potential for conflict within =
the group.   So when evaluating standards actions for the whole =
community, the consensus within a working group means little.   In this =
particular case, v6ops heavily represents the interests of operators =
(who are naturally interested in having IPv6 run smoothly in the long =
term) and works against the interests of applications developers (who =
are naturally interested in having transition mechanisms that allow them =
to ship code that uses IPv6 and an IPv6 programming model regardless of =
whether the underlying network supports it).

2. Working groups have spent a lot of time working on a document and =
will have several members actively participating.  By contrast, most of =
the wider community will not have these issues "on their radar" until =
they come up for IETF-wide Last Call.   Also, busy people need to find =
time to review a document before making comments, and this may require =
multiple readings.  So it's hardly surprising if the number of IETF-wide =
Last Call comments is smaller than the number of WG Last Call comments.  =
 Consensus needs to be evaluated separately in the WG and the IETF =
because the populations and sample sizes are different.

Keith


From ycsijes@gmail.com  Fri Jun 24 05:20:37 2011
Return-Path: <ycsijes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E189911E809B; Fri, 24 Jun 2011 05:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.816
X-Spam-Level: 
X-Spam-Status: No, score=-1.816 tagged_above=-999 required=5 tests=[AWL=0.583,  BAYES_00=-2.599, J_CHICKENPOX_23=0.6, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1K4d0nUf4t-v; Fri, 24 Jun 2011 05:20:37 -0700 (PDT)
Received: from mail-iy0-f194.google.com (mail-iy0-f194.google.com [209.85.210.194]) by ietfa.amsl.com (Postfix) with ESMTP id F369411E8081; Fri, 24 Jun 2011 05:20:36 -0700 (PDT)
Received: by iyj12 with SMTP id 12so697967iyj.1 for <multiple recipients>; Fri, 24 Jun 2011 05:20:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4LQHG8Lblr4sJRQ8eFpj2mWtqRDrV8vRZ37NY0AopEE=; b=HLZFm6TDtFeusUgZ0P5UV2C7+1LU/b2rHrKxsJplnbPbPJAoZvyiA36bj1SKglFDaO xaPXVFfAX3lJM+0MbBAcmVVFiwqLPEiqvk6gDa1YXoEqpv7Xi2ILEA73fXn5C+kakZl/ iagVm2swVTiiMyCuSm1VO5HdtnMrc4ZB3iLWE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=ez6sdoArXibsw5FyLar9gAlG4fyH0oJVZP3eyMz80HKWFuZak1WKaGXpuBSy9ZVpT7 jU6eOk1SaJzUVv5G3Rh/BkvFEo6DZncmnHAIsUuuTmDK7N/Ya+cL4+9sDnuLY4IS/y52 8MyRuNxaK7Cwls/mj86CqWPBOn2Hgj8OwL72U=
Received: by 10.231.24.143 with SMTP id v15mr2853937ibb.90.1308918036319; Fri, 24 Jun 2011 05:20:36 -0700 (PDT)
Received: from [121.49.101.224] ([125.71.231.216]) by mx.google.com with ESMTPS id f13sm1443417ibe.27.2011.06.24.05.20.24 (version=SSLv3 cipher=OTHER); Fri, 24 Jun 2011 05:20:35 -0700 (PDT)
Message-ID: <4E048061.6020900@gmail.com>
Date: Fri, 24 Jun 2011 20:17:37 +0800
From: Yang C Sijes <ycsijes@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>
In-Reply-To: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Fri, 24 Jun 2011 12:20:38 -0000

On 2011-6-24 6:36, Paul Hoffman wrote:
> Greetings again. The subject line is an honest question, not a gripe.
>
> For those on the ietf@ mailing list, please see<https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ballot/>. In short, the IESG just approved publication of draft-ietf-v6ops-6to4-to-historic, even with what appears to be a lack of consensus in the comments on the ietf@ mailing list. One AD called it "pretty rough", but my quick count shows that it was not rough at all: there were more people on the ietf@ against this than in favor of it. If the consensus in a WG for a document was the same as we saw on ietf@ for this document, and the WG chair declared consensus anyway, there would be some serious talks with that WG AD about the chairs.
>
> For a document such as this, why even ask for IETF consensus if the IETF consensus doesn't matter? There was a lot of good discussion and a fair number of varied objections to approval of the document. It sounds like the WG was strongly in favor of the document, which may be sufficient motivation to publish it, but the intermediate step of asking for IETF consensus and then not paying attention to the result then seems wasteful of IETF time.
>
> If the IESG has a policy that "WG consensus trumps IETF consensus", that's fine, but it should be a stated policy so we know where to spend our time. If this document is special for some reason (for example, because it was about policy instead of being a protocol) and therefore the IESG measures consensus differently, that too is fine if we all know that ahead of time. Even a policy of "more than a dozen IETF regulars must object on ietf@ before we will consider overturning a WG" is fine, as long as it is a stated policy. If the IESG has a policy that says "the way we count in IETF Last Call is different than the way we expect Working Group chairs to count in WG Last call", that's fine as well. None of that is obvious from the ballot comments that are visible to the community, however.
>
> Guidance from the IESG for our future participation in IETF Last Call discussions would be greatly appreciated. We try to save you folks time and effort; such guidance would return the favor to us.
>
> --Paul Hoffman
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
I maybe wrong but I mean no offensive.
IMO, the "consensus" is not only a matter of numbers.
For example, it's quite OK to move on if we got 6 against 4 by voting. But it's not good if we want
"consensus". Even there's only one individual who is against the draft, His(or her) opinion should
be considered carefully enough, as long as his(or her) suggestion matters.
But it's AD's job to decide whether the suggestion matters or not. If AD thinks that the problem does
not worth another discussion or the draft is OK with these flaws, then we move on. In this case, AD
do(and should) have this power.

--Yang C Sijes



From brian.e.carpenter@gmail.com  Fri Jun 24 05:34:31 2011
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 73B2E21F84C9; Fri, 24 Jun 2011 05:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.221
X-Spam-Level: 
X-Spam-Status: No, score=-103.221 tagged_above=-999 required=5 tests=[AWL=-0.222, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DAUkoYngpiwb; Fri, 24 Jun 2011 05:34:30 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 61A5D21F846E; Fri, 24 Jun 2011 05:34:30 -0700 (PDT)
Received: by bwz13 with SMTP id 13so2606175bwz.31 for <multiple recipients>; Fri, 24 Jun 2011 05:34:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=7Cl3PTCLMRfSPlU7yWmZM0Xm2SMYKiRU34pAoGf7F6Y=; b=HVB+Gj5QYka8C+b5HkDPWcIgk6Xw1IXcHHLpfuiTExpD47Zsis30JrhuHG2qVCDEEO 18Gx4d/GTATfsnSUavRrZeKdtfhXBECuApS0sqlrFijU0Vo+lxmq6QOZl5y7FiOVNIe6 saVV3d8l/HSiC0Z9xJdL6nrdcl+cnD+zdaVng=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=pF+QePy8d82QYhvi1MgAf8w8rIjPeIc5tvlXZ13h7i0vI1pKbp4GkWsmoyAkoVXbQU 92+9/fJf7MK80Zh2lj72guxZIOrHyfo0lnis0eF4M8Ay2ybpBGIXEz1v8XRZ2C2zFbcb aoMn7qKLRSEY/EGWKC9lxR/dxpoNj79WBdSgM=
Received: by 10.204.138.142 with SMTP id a14mr1870232bku.195.1308918869219; Fri, 24 Jun 2011 05:34:29 -0700 (PDT)
Received: from [10.255.25.96] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id m6sm262335fac.1.2011.06.24.05.34.25 (version=SSLv3 cipher=OTHER); Fri, 24 Jun 2011 05:34:28 -0700 (PDT)
Message-ID: <4E04844B.8030507@gmail.com>
Date: Sat, 25 Jun 2011 00:34:19 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im>	<FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org>	<4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com>
In-Reply-To: <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.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, 24 Jun 2011 12:34:31 -0000

Keith,

On 2011-06-24 23:47, Keith Moore wrote:
...
> 1. Working groups often have strong biases and aren't representative of the whole community.  Put another way, a working group often represents only one side of a tussle, and working groups are often deliberately chartered in such a way as to minimize the potential for conflict within the group.   So when evaluating standards actions for the whole community, the consensus within a working group means little.   In this particular case, v6ops heavily represents the interests of operators (who are naturally interested in having IPv6 run smoothly in the long term) and works against the interests of applications developers (who are naturally interested in having transition mechanisms that allow them to ship code that uses IPv6 and an IPv6 programming model regardless of whether the underlying network supports it).

I suspect that operators are *severely* under-represented on this
list (ietf@ietf.org) because it is very noisy and operators have other
priorities. Most of them are probably unaware of this discussion,
in fact.

   Brian

From scott@kitterman.com  Fri Jun 24 05:41:44 2011
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 6C94911E80C9 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 05:41: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cWKtVy-rG-yd for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 05:41:43 -0700 (PDT)
Received: from mailout00.controlledmail.com (mailout00.controlledmail.com [72.81.252.19]) by ietfa.amsl.com (Postfix) with ESMTP id C4C6D11E809B for <ietf@ietf.org>; Fri, 24 Jun 2011 05:41:43 -0700 (PDT)
Received: from mailout00.controlledmail.com (localhost [127.0.0.1]) by mailout00.controlledmail.com (Postfix) with ESMTP id C4F4138C115; Fri, 24 Jun 2011 08:41:42 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1308919302; bh=brDZv2QjPNNM1qME4mttzn9VGTyaKmMT0nEk1Z5WrT0=; h=From:To:Subject:Date:References:In-Reply-To:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=ZHzye8dGkTr5OytasMTVcpi5Q8WyxRwUAcCndd92tvA81rUjGdQNhc+g/FiiKhgzt 5xjy6v4KqLuVBdc8Y4HbmEkpj1JptuW4pR657gzKwZO5dpWoKCxyix+K/R+0IdajRH TrhyR2ag+u9D4Q1ranxtRo1K3DkFUAcN1mmdhn8E=
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Why ask for IETF Consensus on a WG document?
Date: Fri, 24 Jun 2011 08:41:41 -0400
User-Agent: KMail/1.13.6 (Linux/2.6.38-8-generic-pae; KDE/4.6.2; i686; ; )
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com>
In-Reply-To: <4E03E9A9.2000300@gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201106240841.41592.scott@kitterman.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: Fri, 24 Jun 2011 12:41:44 -0000

On Thursday, June 23, 2011 09:34:33 PM Brian E Carpenter wrote:
> On 2011-06-24 12:44, Peter Saint-Andre wrote:
> > On 6/23/11 4:36 PM, Paul Hoffman wrote:
> >> Greetings again. The subject line is an honest question, not a
> >> gripe.
> >> 
> >> For those on the ietf@ mailing list, please see
> >> <https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ball
> >> ot/>. In short, the IESG just approved publication of
> >> draft-ietf-v6ops-6to4-to-historic, even with what appears to be a
> >> lack of consensus in the comments on the ietf@ mailing list. One AD
> >> called it "pretty rough", but my quick count shows that it was not
> >> rough at all: there were more people on the ietf@ against this than
> >> in favor of it.
> > 
> > I can't speak for other IESG members, but I made a point of reading the
> > full text of every IETF LC message about this I-D, and I disagree with
> > the accuracy of your quick count. It's true that the Last Call did not
> > achieve unanimity or even smooth consensus, but my reading was that a
> > few folks were in the rough (although quite vocal) and that there was
> > rough consensus to publish. I would not have ballotted "No Objection"
> > otherwise. However, I freely admit that I might be wrong.
> 
> I think that's about right. There were several strong and very raional
> opinions against this, including some who were not involved in the
> similarly rough consensus in the WG discussion. But (speaking as a
> co-author of one of the drafts being historicised) I'd say the balance of
> opinion was to publish. However, it's a close call.

I'm relatively new to IETF procedure, so I may misunderstand, but that sounds 
a lot more like voting than any kind of consensus, rough or otherwise.

Scott K

From john@jlc.net  Fri Jun 24 05:55:24 2011
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 3FC8011E80E0 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 05:55:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.712
X-Spam-Level: 
X-Spam-Status: No, score=-105.712 tagged_above=-999 required=5 tests=[AWL=0.287, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id an6B-fl5GefL for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 05:55:23 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 7749311E80C7 for <ietf@ietf.org>; Fri, 24 Jun 2011 05:55:23 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id E023C33C24; Fri, 24 Jun 2011 08:55:22 -0400 (EDT)
Date: Fri, 24 Jun 2011 08:55:22 -0400
From: John Leslie <john@jlc.net>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
Message-ID: <20110624125522.GD76722@verdi>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org> <4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com>
User-Agent: Mutt/1.4.1i
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 Jun 2011 12:55:24 -0000

   (Wearing my Narrative-Scribe hat)

   First, note the Subject line: an IETF Last-Call on a Working Group
document _isn't_ asking for IETF Consensus: it's simply a last-call for
comments on an action proposed by a Working Group.

   Second, I think the Narrative Minutes will help considerably in
understanding this situation. They will likely be published July 5 or 6.

Keith Moore <moore@network-heretics.com> wrote:
> 
> It's problematic, and I believe inappropriate, to consider WG consensus
> as contributing to community consensus.

   I agree -- however, this was not a call for community consensus.

   (Possibly it should have been. At the same IESG telechat, there was
a Statement on moving an RFC to Historic Status, which perhaps should
cover cases like this.)

> The two questions need to be considered separately, for two reasons:
> 
> 1. Working groups often have strong biases and aren't representative
> of the whole community. Put another way, a working group often
> represents only one side of a tussle, and working groups are often
> deliberately chartered in such a way as to minimize the potential
> for conflict within the group.

   Nonetheless, WGs are open to all.

   When a WG document comes before the IESG, there are several Directorate
reviews and an IETF-wide Last-Call. These exist to give guidance to the
IESG on whether to send the document back to the WG with comments on
how to improve it. If it is sent back, the WG must deal with anyone who
may join that WG to express opinions on those comments.

   IESG members dislike sending documents back to the WG, because it is
perceived (by WG members) as "micro-management" or whatever nasty term
may come to mind. Generally, IESG members choose to avoid this when they
don't believe the WG consensus will change.

> So when evaluating standards actions for the whole community, the
> consensus within a working group means little.

   I don't agree. The WG is where concerns are supposed to be balanced.
The <ietf@ietf.org> list cannot handle the bandwidth of doing this.

> In this particular case, v6ops heavily represents the interests of
> operators (who are naturally interested in having IPv6 run smoothly
> in the long term) and works against the interests of applications
> developers (who are naturally interested in having transition
> mechanisms that allow them to ship code that uses IPv6 and an
> IPv6 programming model regardless of whether the underlying network
> supports it).

   True.

> 2. Working groups have spent a lot of time working on a document and
> will have several members actively participating. By contrast, most
> of the wider community will not have these issues "on their radar"
> until they come up for IETF-wide Last Call. Also, busy people need
> to find time to review a document before making comments, and this
> may require multiple readings.

   True.

> So it's hardly surprising if the number of IETF-wide Last Call
> comments is smaller than the number of WG Last Call comments.
> Consensus needs to be evaluated separately in the WG and the IETF
> because the populations and sample sizes are different.

   I'm not sure I agree that IETF-wide consensus needs to be evaluated
at all.

   The model of IETF is that work is normally done in WGs, and that
an IETF-wide review is done before publishing an RFC.

   In this particular case, we have an Informational-status RFC
intended to declare a Standards-Track RFC to no longer be an Internet
Standard in any sense. It is arguable that such an action _should_
require IETF-wide consensus; but at the moment there is no procedure
requiring it.

   So, Keith, you must first convince us that an action like this
_does_ require IETF-wide consensus.

--
John Leslie <john@jlc.net>

From moore@network-heretics.com  Fri Jun 24 06:42:06 2011
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 4098F1F0C3D; Fri, 24 Jun 2011 06:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.103
X-Spam-Level: 
X-Spam-Status: No, score=-3.103 tagged_above=-999 required=5 tests=[AWL=-0.104, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id meYCX+nyotLq; Fri, 24 Jun 2011 06:42:05 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 741C31F0C38; Fri, 24 Jun 2011 06:42:05 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 2A502209A3; Fri, 24 Jun 2011 09:42:05 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Fri, 24 Jun 2011 09:42:05 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=DnLh72T3lZTf7rwCPmMgMjfPCts=; b=AUJkTsKHxglDypb1R3y82x3mzou3OwE4EnSt0teeqvK27ATiAG5ZRRxpY6CUNlM6k6pJDmVHWiEOVV83a1SB0RMBebi2ASwcE3p9vhfe/xZzDgYfhzU1hcmNsl3lw48d2Zs7Xl31ex34iQc1KGIS+gYADd739MtIXdN/FLosGnc=
X-Sasl-enc: 3ip6TglQucbXRmmVLB0zTb5hDZvvJlffD/tyyTPyzQqI 1308922924
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 0BA7A406D6D; Fri, 24 Jun 2011 09:42:03 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E04844B.8030507@gmail.com>
Date: Fri, 24 Jun 2011 09:42:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1C4B003-C4BF-4864-B051-85EDFDD17E4B@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im>	<FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org>	<4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <4E04844B.8030507@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion list <ietf@ietf.org>, The IESG <iesg@ietf.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: Fri, 24 Jun 2011 13:42:06 -0000

On Jun 24, 2011, at 8:34 AM, Brian E Carpenter wrote:

> Keith,
>=20
> On 2011-06-24 23:47, Keith Moore wrote:
> ...
>> 1. Working groups often have strong biases and aren't representative =
of the whole community.  Put another way, a working group often =
represents only one side of a tussle, and working groups are often =
deliberately chartered in such a way as to minimize the potential for =
conflict within the group.   So when evaluating standards actions for =
the whole community, the consensus within a working group means little.  =
 In this particular case, v6ops heavily represents the interests of =
operators (who are naturally interested in having IPv6 run smoothly in =
the long term) and works against the interests of applications =
developers (who are naturally interested in having transition mechanisms =
that allow them to ship code that uses IPv6 and an IPv6 programming =
model regardless of whether the underlying network supports it).
>=20
> I suspect that operators are *severely* under-represented on this
> list (ietf@ietf.org) because it is very noisy and operators have other
> priorities. Most of them are probably unaware of this discussion,
> in fact.

You're probably right about the representation of operators on the ietf =
list.  But our process requires that we get consensus here in addition =
to in the working group.

Keith


From moore@network-heretics.com  Fri Jun 24 07:07:21 2011
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 1BB1611E8076 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 07:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.101
X-Spam-Level: 
X-Spam-Status: No, score=-3.101 tagged_above=-999 required=5 tests=[AWL=-0.102, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mSU-AXB2RSU3 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 07:07:20 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 2D21D228013 for <ietf@ietf.org>; Fri, 24 Jun 2011 07:07:20 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id DCBFB20690; Fri, 24 Jun 2011 10:07:19 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 24 Jun 2011 10:07:19 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=0MEj048eL35laTb/30zFKMKJJMs=; b=UKU2gizcUaePvifatgvXu3KTZUNKG3wYCXMZGJ7aYYLXcEwFaqd538zgu0OsVxryQJth9EbEvThlDluyAeFuAjKpO8IktbiGEVnrjDVZp4fK8nPrFPn1e8czM13s7FqYBMSh1LUKY7+23baC03z+iQlX6DKIFO09fzjYi6uSaE4=
X-Sasl-enc: OJvss5py/DSix1vUK8yIMTtFFnbtllznRmM5GPGh8A1i 1308924439
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id B325740701E; Fri, 24 Jun 2011 10:07:18 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110624125522.GD76722@verdi>
Date: Fri, 24 Jun 2011 10:07:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B6419E6-5277-4A48-A141-346A761ABC19@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org> <4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <20110624125522.GD76722@verdi>
To: John Leslie <john@jlc.net>
X-Mailer: Apple Mail (2.1084)
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 Jun 2011 14:07:21 -0000

On Jun 24, 2011, at 8:55 AM, John Leslie wrote:

>   (Wearing my Narrative-Scribe hat)
>=20
>   First, note the Subject line: an IETF Last-Call on a Working Group
> document _isn't_ asking for IETF Consensus: it's simply a last-call =
for
> comments on an action proposed by a Working Group.
>=20
>   Second, I think the Narrative Minutes will help considerably in
> understanding this situation. They will likely be published July 5 or =
6.
>=20
> Keith Moore <moore@network-heretics.com> wrote:
>>=20
>> It's problematic, and I believe inappropriate, to consider WG =
consensus
>> as contributing to community consensus.
>=20
>   I agree -- however, this was not a call for community consensus.
>=20
>   (Possibly it should have been. At the same IESG telechat, there was
> a Statement on moving an RFC to Historic Status, which perhaps should
> cover cases like this.)

Well, there was also a process issue because a standards action =
(changing 6to4 to historic) was advertised as a proposal to publish an =
informational document. =20

But I read 2026 as requiring broad community consensus for standards =
actions.

>> The two questions need to be considered separately, for two reasons:
>>=20
>> 1. Working groups often have strong biases and aren't representative
>> of the whole community. Put another way, a working group often
>> represents only one side of a tussle, and working groups are often
>> deliberately chartered in such a way as to minimize the potential
>> for conflict within the group.
>=20
>   Nonetheless, WGs are open to all.
>=20
>   When a WG document comes before the IESG, there are several =
Directorate
> reviews and an IETF-wide Last-Call. These exist to give guidance to =
the
> IESG on whether to send the document back to the WG with comments on
> how to improve it. If it is sent back, the WG must deal with anyone =
who
> may join that WG to express opinions on those comments.
>=20
>   IESG members dislike sending documents back to the WG, because it is
> perceived (by WG members) as "micro-management" or whatever nasty term
> may come to mind. Generally, IESG members choose to avoid this when =
they
> don't believe the WG consensus will change.

I served on IESG for four years, and understand all of that.  =
Nevertheless, even a strong consensus of a WG should never be taken as =
consensus of the IETF as a whole.    Working groups are almost =
inevitably narrowly focused, and in practice they rarely consider the =
wider effects of their actions.

And in this particular case, I don't think there was even rough =
consensus within the v6ops working group.

Moreover, while it is always necessary to get rough consensus from the =
broad community on any standards action, WG consensus is not a necessary =
condition.   Individual submissions for standards-track can be approved =
with a 4-week Last Call.   The value of a narrowly-focused working group =
is not so much to gain consensus of that group (though this can be =
useful), but to encourage an appropriate amount of attention on protocol =
design.  Clearly the broad community consensus is more important than =
the working group's consensus.   A working group should understand that =
its job is to put forth a proposal that will win consensus of the broad =
community.

>> So when evaluating standards actions for the whole community, the
>> consensus within a working group means little.
>=20
>   I don't agree. The WG is where concerns are supposed to be balanced.
> The <ietf@ietf.org> list cannot handle the bandwidth of doing this.

Working groups that are narrowly focused (which is to say the vast =
majority of them) cannot possibly balance the competing concerns of the =
broad community.    They are too subject to the dictates of a single =
"area".  And schedule conflicts at IETF meetings also discourage =
cross-area participation.

>   I'm not sure I agree that IETF-wide consensus needs to be evaluated
> at all.

RFC 2026 states over and over again, in several different ways, that the =
goal of the process is to achieve broad community consensus.

Keith



From paul.hoffman@vpnc.org  Fri Jun 24 07:18:38 2011
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 7766B21F8507; Fri, 24 Jun 2011 07:18:38 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f8FyOK+DIk00; Fri, 24 Jun 2011 07:18:37 -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 0F44021F850B; Fri, 24 Jun 2011 07:18:36 -0700 (PDT)
Received: from [10.20.30.104] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p5OEH5SZ066317 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 Jun 2011 07:17:06 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4E045B80.7060800@cs.tcd.ie>
Date: Fri, 24 Jun 2011 07:17:10 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <11E1860E-BCB6-48FF-AF2C-5A17F57151C5@vpnc.org>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org> <4E045B80.7060800@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1084)
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: Fri, 24 Jun 2011 14:18:38 -0000

On Jun 24, 2011, at 2:40 AM, Stephen Farrell wrote:

> In addition to the other factors already mentioned, I didn't
> see what I thought were significant new facts or issues being
> raised at the IETF LC. I think that such things are perhaps
> more likely to cause the IETF rough consensus to differ from
> that in the WG. In this case, it looked to me like people
> were bringing concerns already expressed in the WG to the
> attention of the wider community, which is a reasonable thing
> to do in cases like this where the WG consensus was already
> fairly rough.

My (possibly-flawed) reading of the responses was that none of the =
people objecting to the publication of this document during IETF LC were =
WG participants. So, while they might have brought up points already =
considered by the WG, they were not bringing up ones that they had =
already expressed.

Is it then your (individual) opinion that issues that were raised in a =
WG but determined to not be strong enough to affect WG rough consensus =
should be ignored when determining IETF rough consensus? That's a =
reasonable opinion, but not one I had heard before. At least, it helps =
answer the question of what a WG non-participant needs to do to cause a =
WG document to not pass IETF consensus.

--Paul Hoffman


From paul.hoffman@vpnc.org  Fri Jun 24 07:23:23 2011
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 31D07228013; Fri, 24 Jun 2011 07:23:23 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uGK6obN4I3vB; Fri, 24 Jun 2011 07:23:22 -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 7AA63228005; Fri, 24 Jun 2011 07:23:21 -0700 (PDT)
Received: from [10.20.30.104] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p5OENDT7066605 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 Jun 2011 07:23:13 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20110624125522.GD76722@verdi>
Date: Fri, 24 Jun 2011 07:23:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F965C40C-1B96-4590-A05E-7988EBAB51F6@vpnc.org>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org> <4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <20110624125522.GD76722@verdi>
To: John Leslie <john@jlc.net>
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion list <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: Fri, 24 Jun 2011 14:23:23 -0000

On Jun 24, 2011, at 5:55 AM, John Leslie wrote:

>   (Wearing my Narrative-Scribe hat)
>=20
>   First, note the Subject line: an IETF Last-Call on a Working Group
> document _isn't_ asking for IETF Consensus: it's simply a last-call =
for
> comments on an action proposed by a Working Group.

I'm quite confused by this opinion. *No* IETF Last Call announcements, =
even those for standards track documents, say that they are to determine =
IETF consensus, yet IETF consensus is required for many of these =
documents. In your view, how are we to know which IETF Last Call =
announcements are to determine IETF consensus and which are just to =
bring additional input to the IESG for a non-consensus decision? Or are =
you saying that the IESG determines IETF consensus using metrics other =
than the discussion on ietf@?

Again, the community knowing what type of response would be productive =
during IETF Last Call would help everyone set their priorities better.

--Paul Hoffman


From stephen.farrell@cs.tcd.ie  Fri Jun 24 07:44:26 2011
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 EAFD121F8564; Fri, 24 Jun 2011 07:44:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.399
X-Spam-Level: 
X-Spam-Status: No, score=-106.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cG95ddL8JSuy; Fri, 24 Jun 2011 07:44:26 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 280CB21F8561; Fri, 24 Jun 2011 07:44:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id EC35F171C1F; Fri, 24 Jun 2011 15:44:21 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1308926661; bh=Rqhth79vELefR/ rM5G5QQFBA5PkhJz2GKcYIAq347Ts=; b=bNG6PZn7h9eBZHr9EEHuxP4HF542VZ +DdT2ySu9ERgcxEueueg5IycTRhOxJIr70oJ9hJCeJgR0nSt06B/684HpGD26L8D CqNPg/Ek0D0UIfZtkz6nQTuUrJKVyEhRHBy4onwEh98PM18RrNspeaU9oh5IbWXY jylcmWq9DzYuMK0sn2LpmzR73m0QqvOEcyIllsIFSatidSMbqr2qDcoc1UI32hIU lezRUi0bd2+5mUdJo80IRssmANUtCQUK2RP1NbeRleYM/r+wjREU5sqPxtRKekaW FgqWtMNwjx6gMxhk2UUTlZ++5iXiWeJZIPvwLQs6uAxEY03V0R244G5A==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id bBPEbV90gwAd; Fri, 24 Jun 2011 15:44:21 +0100 (IST)
Received: from [134.226.36.137] (stephen-samy.dsg.cs.tcd.ie [134.226.36.137]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 94E6F171C1D; Fri, 24 Jun 2011 15:44:21 +0100 (IST)
Message-ID: <4E04A2C4.8090301@cs.tcd.ie>
Date: Fri, 24 Jun 2011 15:44:20 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im>	<FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org>	<4E045B80.7060800@cs.tcd.ie> <11E1860E-BCB6-48FF-AF2C-5A17F57151C5@vpnc.org>
In-Reply-To: <11E1860E-BCB6-48FF-AF2C-5A17F57151C5@vpnc.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Fri, 24 Jun 2011 14:44:27 -0000

On 24/06/11 15:17, Paul Hoffman wrote:
> On Jun 24, 2011, at 2:40 AM, Stephen Farrell wrote:
> 
>> In addition to the other factors already mentioned, I didn't
>> see what I thought were significant new facts or issues being
>> raised at the IETF LC. I think that such things are perhaps
>> more likely to cause the IETF rough consensus to differ from
>> that in the WG. In this case, it looked to me like people
>> were bringing concerns already expressed in the WG to the
>> attention of the wider community, which is a reasonable thing
>> to do in cases like this where the WG consensus was already
>> fairly rough.
> 
> My (possibly-flawed) reading of the responses was that none of the people objecting to the publication of this document during IETF LC were WG participants. 

I had the opposite impression. I thought that I saw people
say a few times, "when you brought this up in the WG" type
remark as well (but I've not looked back).

> So, while they might have brought up points already considered by the
WG, they were not bringing up ones that they had already expressed.
> 
> Is it then your (individual) opinion that issues that were raised in a WG but determined to not be strong enough to affect WG rough consensus should be ignored when determining IETF rough consensus? That's a reasonable opinion, but not one I had heard before. At least, it helps answer the question of what a WG non-participant needs to do to cause a WG document to not pass IETF consensus.

No. Not "ignored," but I do think that finding out new facts
and cross-cutting considerations are an important part of
IETF LC. (And recall that I started my mail by saying that
I was just adding an additional point.)

So I don't think I've answered your question, or at best,
only partly.

S.

(And of course I'm not talking for the IESG here, just
saying what I did/think - what hat is that anyway? :-)

> 
> --Paul Hoffman
> 

From d3e3e3@gmail.com  Fri Jun 24 07:46:32 2011
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 3210111E808C; Fri, 24 Jun 2011 07:46:32 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xHD-WQ6Mnizz; Fri, 24 Jun 2011 07:46:31 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 92C7C11E8076; Fri, 24 Jun 2011 07:46:31 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1717591gxk.31 for <multiple recipients>; Fri, 24 Jun 2011 07:46:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=KhExV3CgwJS2dJ7aZLR2erjgVYJnFVlSo0nSySJ/bFo=; b=eoLPe02mGLijKFr/CrrmyxI1702vH/ngnMYWGhtZqlbodZkOlFVNwGtzMPkWvux7QN irPt7xOyTiACHgWh+Q26IW78osrcKE07vhIPyRXYaufQ+rZVJs/mmlb96MebzDuPYcvQ WjY6ZgAQuGB9hrab3fKK6uNNbTsjrJlMY4QOk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=mOttg7e7LJT50Gms+60jtSph74XAJF06Md+fcEDd/yHceXbrwAJVyFOonNuKT622xQ KDQXa0OsT/JVBOQlW6ODh26OIsB7zalHF8ocRUN/3fH8Mz4MgcvLhdIN1AWlX6E1IoHH JT58ZCO7iLbPqZsltmCtD6ogZMtrUM88jSytg=
Received: by 10.150.193.13 with SMTP id q13mr3629876ybf.303.1308926791148; Fri, 24 Jun 2011 07:46:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.39.5 with HTTP; Fri, 24 Jun 2011 07:46:11 -0700 (PDT)
In-Reply-To: <F965C40C-1B96-4590-A05E-7988EBAB51F6@vpnc.org>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org> <4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <20110624125522.GD76722@verdi> <F965C40C-1B96-4590-A05E-7988EBAB51F6@vpnc.org>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 24 Jun 2011 10:46:11 -0400
Message-ID: <BANLkTim9ECfr5e43x22OwYHo9KS=G09LGA@mail.gmail.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
To: IETF-Discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: Fri, 24 Jun 2011 14:46:32 -0000

An IETF consensus call is judgement as to rough consensus. There is no
mechanical set of rules that can substitute for judgement.

WG Chairs judge the consensus of the Working Group. It is reasonable
for them to take into account discussions at WG meetings as well as WG
mailing list discussions.

The IESG judges the consensus of the IETF. It is reasonable for them
to take into account discussions on the WG mailing list and on any
area mailing list or the like, as well as on the IETF mailing list and
discussions at WG, area, and IETF plenary meetings.

If polls at area meetings with 100+ people at them at three successive
IETF meetings on different continents consistently show, say, a 3 to 1
preference for some proposal but the IETF Last call email has 6 people
speaking against and only 4 in favor, what do you think the right
judgement would be as to the consensus of the IETF community? Of
course, I'm not saying that's what happened hear. But a narrow rules
that the IESG is required to put on blinders and only consider the
IETF discussion list IETF Last Call email, ignoring previous
discussions on other relevant IETF mailing lists and ignoring WG,
area, and IETF plenary meeting discussions they have attended, is just
arbitrary nonsense.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street
=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

From petithug@acm.org  Fri Jun 24 08:08:17 2011
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 062C121F84DC for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 08:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.254
X-Spam-Level: 
X-Spam-Status: No, score=-102.254 tagged_above=-999 required=5 tests=[AWL=-0.254, BAYES_00=-2.599, J_CHICKENPOX_16=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QVovVrymbQa6 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 08:08:16 -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 2B8EC21F8443 for <ietf@ietf.org>; Fri, 24 Jun 2011 08:08:16 -0700 (PDT)
Received: from [IPv6:2001:55c:4c15:5f80:213:d4ff:fe04:3e08] (unknown [IPv6:2001:55c:4c15:5f80:213:d4ff:fe04:3e08]) by implementers.org (Postfix) with ESMTPS id 16E0A226E9 for <ietf@ietf.org>; Fri, 24 Jun 2011 17:08:01 +0200 (CEST)
Message-ID: <4E04A85B.9010603@acm.org>
Date: Fri, 24 Jun 2011 08:08:11 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110606 Iceowl/1.0b2 Icedove/3.1.10
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Agenda for IETF 81 not available
X-Enigmail-Version: 1.1.2
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: Fri, 24 Jun 2011 15:08:17 -0000

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

According to the IETF web site, the preliminary agenda for IETF 81 should have
been published yesterday, but is still not available.

Something similar happened for the previous IETF meeting, so I wrote a
Greasemonkey script that fixes the dates in the IETF web site so they match reality:


// ==UserScript==
// @name           fix-ietf
// @namespace      http://shalmaneser.org/fix-ietf
// @description    Align IETF meeting important dates with reality
// @include        http://www.ietf.org/meeting/cutoff-dates-*
// ==/UserScript==
var days = ["Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday",
"Saturday" ];
var e = document.getElementsByTagName('strong');
for (var i = e.length -1; i >= 0; i--) {
	if (e[i].nextSibling !== null &&
e[i].nextSibling.nodeValue.indexOf('Preliminary agenda') !== -1) {
		var d = new Date(e[i].childNodes[0].nodeValue.slice(0, 10));
		d.setTime(d.getTime() + 5 * 86400000);
		e[i].childNodes[0].nodeValue = d.getFullYear() + "-" + (d.getMonth() < 9 ? "0"
: "") + (d.getMonth() + 1) + "-" + d.getDate() + " (" + days[d.getDay()] + "):";
	}
}

- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk4EqFUACgkQ9RoMZyVa61d2zQCeITfOgnwB3GGRksdvp5LWU3ie
ffIAnjFBMAY/09WIb+fyxpxOcKflS1/v
=u6vZ
-----END PGP SIGNATURE-----

From Even.roni@huawei.com  Fri Jun 24 00:23:42 2011
Return-Path: <Even.roni@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 331BA11E816A; Fri, 24 Jun 2011 00:23:42 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 67sHek8Q+sps; Fri, 24 Jun 2011 00:23:41 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id E0BA011E80B7; Fri, 24 Jun 2011 00:23:40 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNA0021U9U0ZR@szxga04-in.huawei.com>; Fri, 24 Jun 2011 15:22:48 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LNA00EUE9U0E4@szxga04-in.huawei.com>; Fri, 24 Jun 2011 15:22:48 +0800 (CST)
Received: from windows8d787f9 ([109.67.30.132]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LNA00J3T9TQ8T@szxml12-in.huawei.com>; Fri, 24 Jun 2011 15:22:48 +0800 (CST)
Date: Fri, 24 Jun 2011 10:20:36 +0300
From: Roni Even <Even.roni@huawei.com>
Subject: Gen-ART LC review of draft-ietf-ftpext2-hosts-02
To: draft-ietf-ftpext2-hosts.all@tools.ietf.org
Message-id: <002e01cc323f$3d9e1340$b8da39c0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_Vzk+GHABmLcAda5ntdoGmA)"
Content-language: en-us
Thread-index: AcwyPzY4XJ2+70MeRCOBBRrApsM2qg==
X-Mailman-Approved-At: Fri, 24 Jun 2011 08:20:20 -0700
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, 24 Jun 2011 07:23:42 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_Vzk+GHABmLcAda5ntdoGmA)
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-ftpext2-hosts-02

Reviewer: Roni Even

Review Date:2011-6-21

IETF LC End Date: 2011-6-30

IESG Telechat date: 2011-6-30

 

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

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

 


--Boundary_(ID_Vzk+GHABmLcAda5ntdoGmA)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family: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;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="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]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at &lt;<a href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Please resolve these comments along with any other Last Call comments you may receive.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-ftpext2-hosts-02<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"
 Calibri"
Roni Even<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review Date:2011&#8211;6&#8211;21<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC End Date: 2011&#8211;6&#8211;30<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG Telechat date: 2011-6-30<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: This draft is ready for publication as a standard track</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>RFC.<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'
 ><o:p>&n
lass=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major issues:<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor issues:<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editorial comments:<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>

--Boundary_(ID_Vzk+GHABmLcAda5ntdoGmA)--

From scott.rose@nist.gov  Fri Jun 24 08:16:45 2011
Return-Path: <scott.rose@nist.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 150C722801C; Fri, 24 Jun 2011 08:16:45 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WG4BqBbAwLNU; Fri, 24 Jun 2011 08:16:44 -0700 (PDT)
Received: from smtp.nist.gov (rimp1.nist.gov [129.6.16.226]) by ietfa.amsl.com (Postfix) with ESMTP id 8A26F228006; Fri, 24 Jun 2011 08:16:43 -0700 (PDT)
Received: from 107-140.antd.nist.gov (107-140.antd.nist.gov [129.6.140.107]) by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id p5OFGU5T003194; Fri, 24 Jun 2011 11:16:32 -0400
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Scott Rose <scott.rose@nist.gov>
In-Reply-To: <42646542-15D4-4ABF-A65F-A0F3361D049A@nostrum.com>
Date: Fri, 24 Jun 2011 11:16:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <86B91666-359A-416F-8D22-A99F2A759BE9@nist.gov>
References: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com> <BANLkTin0xTnTpA79PL12UcBADQj-A8U_GQ@mail.gmail.com> <42646542-15D4-4ABF-A65F-A0F3361D049A@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1084)
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: scott.rose@nist.gov
X-Mailman-Approved-At: Fri, 24 Jun 2011 08:20:20 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The 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, 24 Jun 2011 15:16:45 -0000

FYI:
A new version (-23) of the dname-bis draft has been posted with the two =
sections re-added (resolver algorithm and examples of DNAME use). I =
haven't heard any comments from the DNSEXT WG on it, but it was only =
just posted.

Scott=20

On Jun 8, 2011, at 5:50 PM, Ben Campbell wrote:

> Thanks for the response! Comments below, eliding the bits I think need =
no further comment.
>=20
> On Jun 8, 2011, at 12:11 PM, Scott Rose wrote:
>=20
>> Perhaps the document should only update RFC 2672 instead of =
obsoleting it? =20
>=20
> That would resolve my concern, if it fits with the intent of the work =
group.
>=20
>=20
>>=20
>> As for the nits:
>>=20
>>=20
>> On Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <ben@nostrum.com> wrote: =
=20
>>=20
>=20
> [...]
>=20
>> Yes, will correct.
>> =20
>> -- ..., 7th paragraph: "...replaced with the word "DELETED"."
>>=20
>> Won't that just leave the word "deleted" hanging on page without =
explanation? Wouldn't it be better to just simply delete it?
>>=20
>>=20
>> Maybe, but I think the logic was that if there is some text there =
(just something), it can be cleanly referenced (i.e. "DELETED =
[RFCXXXX]")if someone is making a revised version of the RFC for some =
purpose.  Purely deleting it accomplishes the task, but this provides a =
good "hook" for a paper trail.
>>=20
>=20
> Okay. On reflection, it's not like we really render the updates the =
old RFC documents.
>=20
>=20
>> Scott
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Scott Rose
NIST
scott.rose@nist.gov
+1 301-975-8439
Google Voice: +1 571-249-3671
http://www.dnsops.gov/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


From rja.lists@gmail.com  Fri Jun 24 08:21:11 2011
Return-Path: <rja.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 1F00B9E8047 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 08:21:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.61
X-Spam-Level: 
X-Spam-Status: No, score=-3.61 tagged_above=-999 required=5 tests=[AWL=-0.011,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M77bdhhq+8EY for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 08:21:10 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 23D659E8005 for <ietf@ietf.org>; Fri, 24 Jun 2011 08:21:10 -0700 (PDT)
Received: by vxi40 with SMTP id 40so2972978vxi.31 for <ietf@ietf.org>; Fri, 24 Jun 2011 08:21:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=K2FmdQpYsHa3xbceP2YbkQOXSQMjTPPuH7ZNcAVa3E4=; b=XodzxxxWeYoUIDsfoCrrvARcIx3ULpeJ63iWlwIj/X89mEH6ODh+lkgIHSmoILG9P4 9cT+pUBtmmX3rIPMwXTj65xhI+UuE1EsM8C3RMWPY1upFigogDXySB1wpZJjAf8AcCs4 vKFKtfjZ79L3GIAq3CUpMqxDVYBtSP4R+HPqo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=sTX5EF4mqWxmwRfVYFAwGRG6PODWFVIhT62nfuXJ5xKEv7/Cto4/ADdCJ5mI1XLOE7 Xm1YutiU2XxneutcyPFdyU/nsJo5rTNEIqX967nwpRmygHhBTZ4HhWWJE+plVNii+Cv7 G8hl3dCIAtu9sHjncdJy1cKvKaQiokUJijmnc=
Received: by 10.52.93.67 with SMTP id cs3mr4690328vdb.4.1308928869547; Fri, 24 Jun 2011 08:21:09 -0700 (PDT)
Received: from [10.30.20.12] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id bh17sm788286vdc.27.2011.06.24.08.21.07 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 24 Jun 2011 08:21:08 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: Why ask for IETF Consensus on a WG document?  
Date: Fri, 24 Jun 2011 11:21:06 -0400
Message-Id: <6C4159EC-9C66-48B4-8856-AD772745A026@gmail.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 15:21:11 -0000

Earlier, Paul Hoffman wrote, in part:
> ...the IESG just approved publication of X, even with
> what appears to be a lack of consensus in the comments
> on the ietf@ mailing list.
> 
> (some other text elided here.)
> 
> For a document such as this, why even ask for IETF consensus 
> if the IETF consensus doesn't matter?
>  
> (remaining text elided here.) 


Next, as a reference, here is a boilerplate snippet from
a recent IETF Last Call:
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf at ietf.org mailing lists by 2011-07-21. Exceptionally, comments
> may be sent to iesg at ietf.org instead. In either case, please retain
> the beginning of the Subject line to allow automated sorting.


The "IETF Consensus" matters, and I believe the IESG 
did fully and properly consider that matter in the case
that appears to have driven your note.

There appears to be a confusion underlying your note.

Paul's assertion that public postings to the IETF Discussion 
list are the only metric for "IETF Consensus" is NOT correct 
-- and never has been in the past.  

"IETF Consensus" includes ALL of the inputs that the IESG
receives about a document or issue that is put to IETF
Last Call.   The Last Call announcement specifically says,
for example, that comments may be sent privately to the
IESG.

Consensus inputs are NOT limited to posted public comments,
BUT ALSO include formal liaisons, communications with various 
WG Chairs (not limited to the sponsoring WG), private email 
to the IESG, private email to an AD, and more.

Note also that this is THE SAME as how WG Chairs are supposed
to operate.  WG Chairs are supposed to consider ALL inputs,
NOT ONLY public postings to the WG list, BUT ALSO private
inputs from WG participants and other applicable folks,
and whatever other inputs arrive after a WG Last Call is
announced.

I hear that Paul H is unhappy with this particular outcome,
but there is no evidence of any kind of process problem
or process mistake here.

Yours,

Ran



From moore@network-heretics.com  Fri Jun 24 08:21:13 2011
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 545559E804D; Fri, 24 Jun 2011 08:21:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.396
X-Spam-Level: 
X-Spam-Status: No, score=-3.396 tagged_above=-999 required=5 tests=[AWL=0.202,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hDp6WEL2Rcuk; Fri, 24 Jun 2011 08:21:11 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 4902F9E8005; Fri, 24 Jun 2011 08:21:11 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 08FCC209B1; Fri, 24 Jun 2011 11:21:11 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 24 Jun 2011 11:21:11 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=vPXnDub15U2kAv6jydz1L4Cok80=; b=X5SaDFpCvKUtaHPIcf5LJBjLoTJ3UXoSIvInSCExMhCuFaXCpM4ReHCTvOPF6Zi0e5jrh91JiSkKa7hPljrIDLoT2/8nqe/5xKdzzq8hS2ztibt0F+ekK0td8SMK8ysYrIiSqxju+J+tEcNfDWMcjKyTOor0qn46ek4rdjFju1w=
X-Sasl-enc: o58bHY0p3WuMJkBtGL80FmFJWGvV+Ecw+R9FswJADs+n 1308928870
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 886974009B8; Fri, 24 Jun 2011 11:21:09 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-46--90815890
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E04A2C4.8090301@cs.tcd.ie>
Date: Fri, 24 Jun 2011 11:21:05 -0400
Message-Id: <DF9F5AAB-D3CF-426E-A60D-16AF8F1B851B@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im>	<FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org>	<4E045B80.7060800@cs.tcd.ie> <11E1860E-BCB6-48FF-AF2C-5A17F57151C5@vpnc.org> <4E04A2C4.8090301@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1084)
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: Fri, 24 Jun 2011 15:21:13 -0000

--Apple-Mail-46--90815890
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 24, 2011, at 10:44 AM, Stephen Farrell wrote:
>=20
> On 24/06/11 15:17, Paul Hoffman wrote:
>> On Jun 24, 2011, at 2:40 AM, Stephen Farrell wrote:
>>=20
>>> In addition to the other factors already mentioned, I didn't
>>> see what I thought were significant new facts or issues being
>>> raised at the IETF LC. I think that such things are perhaps
>>> more likely to cause the IETF rough consensus to differ from
>>> that in the WG. In this case, it looked to me like people
>>> were bringing concerns already expressed in the WG to the
>>> attention of the wider community, which is a reasonable thing
>>> to do in cases like this where the WG consensus was already
>>> fairly rough.
>>=20
>> My (possibly-flawed) reading of the responses was that none of the =
people objecting to the publication of this document during IETF LC were =
WG participants.=20
>=20
> I had the opposite impression. I thought that I saw people
> say a few times, "when you brought this up in the WG" type
> remark as well (but I've not looked back).

Looking over both WGLC and IETF LC responses just now and making a rough =
tally of opinions, I only saw one person who responded to both LC =
requests.  (But I was only counting the objections to the proposed =
action.)

>> So, while they might have brought up points already considered by the
> WG, they were not bringing up ones that they had already expressed.
>>=20
>> Is it then your (individual) opinion that issues that were raised in =
a WG but determined to not be strong enough to affect WG rough consensus =
should be ignored when determining IETF rough consensus? That's a =
reasonable opinion, but not one I had heard before. At least, it helps =
answer the question of what a WG non-participant needs to do to cause a =
WG document to not pass IETF consensus.
>=20
> No. Not "ignored," but I do think that finding out new facts
> and cross-cutting considerations are an important part of
> IETF LC. (And recall that I started my mail by saying that
> I was just adding an additional point.)

I don't think that people's concerns can be disregarded just because =
others raised similar concerns in WG discussion.  If anything, that =
should give more weight to those concerns.

Keith


--Apple-Mail-46--90815890
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 24, 2011, at 10:44 AM, Stephen Farrell =
wrote:</div><blockquote type=3D"cite"><div><font =
class=3D"Apple-style-span" color=3D"#000000"><br></font>On 24/06/11 =
15:17, Paul Hoffman wrote:<br><blockquote type=3D"cite">On Jun 24, 2011, =
at 2:40 AM, Stephen Farrell wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">In addition to the other factors already mentioned, I =
didn't<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">see what I thought were significant new facts or issues =
being<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">raised at the IETF LC. I think that such things are =
perhaps<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite">more likely to cause the IETF rough consensus to differ =
from<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">that in the WG. In this case, it looked to me like =
people<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">were bringing concerns already expressed in the WG to =
the<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">attention of the wider community, which is a reasonable =
thing<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">to do in cases like this where the WG consensus was =
already<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite">fairly rough.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">My =
(possibly-flawed) reading of the responses was that none of the people =
objecting to the publication of this document during IETF LC were WG =
participants. <br></blockquote><br>I had the opposite impression. I =
thought that I saw people<br>say a few times, "when you brought this up =
in the WG" type<br>remark as well (but I've not looked =
back).<br></div></blockquote><div><br></div>Looking over both WGLC and =
IETF LC responses just now and making a rough tally of opinions, I only =
saw one person who responded to both LC requests. &nbsp;(But I was only =
counting the objections to the proposed =
action.)</div><div><br><blockquote type=3D"cite"><div><blockquote =
type=3D"cite">So, while they might have brought up points already =
considered by the<br></blockquote>WG, they were not bringing up ones =
that they had already expressed.<br><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Is it then your =
(individual) opinion that issues that were raised in a WG but determined =
to not be strong enough to affect WG rough consensus should be ignored =
when determining IETF rough consensus? That's a reasonable opinion, but =
not one I had heard before. At least, it helps answer the question of =
what a WG non-participant needs to do to cause a WG document to not pass =
IETF consensus.<br></blockquote><br>No. Not "ignored," but I do think =
that finding out new facts<br>and cross-cutting considerations are an =
important part of<br>IETF LC. (And recall that I started my mail by =
saying that<br>I was just adding an additional =
point.)<br></div></blockquote></div><br><div>I don't think that people's =
concerns can be disregarded just because others raised similar concerns =
in WG discussion. &nbsp;If anything, that should give more weight to =
those =
concerns.</div><div><br></div><div>Keith</div><div><br></div></body></html=
>=

--Apple-Mail-46--90815890--

From moore@network-heretics.com  Fri Jun 24 08:39:50 2011
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 5016911E808D; Fri, 24 Jun 2011 08:39:50 -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=[AWL=0.199, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id be0UFDBZwTom; Fri, 24 Jun 2011 08:39:49 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 4897611E808C; Fri, 24 Jun 2011 08:39:49 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id BF78920737; Fri, 24 Jun 2011 11:39:48 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Fri, 24 Jun 2011 11:39:48 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=p/pCrEZIVKF57AVS4zrmYmFmZjk=; b=YUTVg+tnsVEM24YoFXsxwKn/jq2A4fvphvE8EopQhB5YH8kQC71NY8dr5GW6ZqwNyPrbgk8H0aiaGeQI60DlTWbdTBsUiNHA917H8QekdICy4bIbZT7G2LwekVXduVhUIcIyxGM7rvfavN8vaqmQwL/LuSi4hSST/BXF+IFqVQ8=
X-Sasl-enc: szqEl/SAbM/oeZqoH858tG0+wOhLkwS9dyth7IupQD0+ 1308929988
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 958854054C7; Fri, 24 Jun 2011 11:39:47 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <BANLkTim9ECfr5e43x22OwYHo9KS=G09LGA@mail.gmail.com>
Date: Fri, 24 Jun 2011 11:39:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EBE21D75-3828-45EB-9534-04F9AB63423A@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org> <4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <20110624125522.GD76722@verdi> <F965C40C-1B96-4590-A05E-7988EBAB51F6@vpnc.org> <BANLkTim9ECfr5e43x22OwYHo9KS=G09LGA@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion list <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: Fri, 24 Jun 2011 15:39:50 -0000

On Jun 24, 2011, at 10:46 AM, Donald Eastlake wrote:

> An IETF consensus call is judgement as to rough consensus. There is no
> mechanical set of rules that can substitute for judgement.
>=20
> WG Chairs judge the consensus of the Working Group. It is reasonable
> for them to take into account discussions at WG meetings as well as WG
> mailing list discussions.
>=20
> The IESG judges the consensus of the IETF. It is reasonable for them
> to take into account discussions on the WG mailing list and on any
> area mailing list or the like, as well as on the IETF mailing list and
> discussions at WG, area, and IETF plenary meetings.

I think I mostly disagree with this, for reasons stated earlier. =20

Now it might be that, for some specific issue or objection raised during =
IETF LC to some technical proposal, the IESG could look at the WG record =
and say "This issue was thoroughly considered by the WG.   There's =
really no way to solve this problem that will satisfy all concerns, and =
the WG did as good a job at making an appropriate compromise as could be =
expected."    That could be an appropriate way to respond to a dispute =
over a technical compromise design choice.  And in general, I think IESG =
should give preference to a WG's technical decisions if it's clear that =
the WG made an effort to understand all of the competing concerns and to =
strike an appropriate balance between them.

I don't think that rationale would apply in the case of 6to4-historic, =
as there's really no technical need to declare this historic.   And the =
6to4-advisory document does a much better job at both recommending =
remedies to the problems that people have (reasonably) complained about, =
and striking a balance between competing concerns.

> If polls at area meetings with 100+ people at them at three successive
> IETF meetings on different continents consistently show, say, a 3 to 1
> preference for some proposal but the IETF Last call email has 6 people
> speaking against and only 4 in favor, what do you think the right
> judgement would be as to the consensus of the IETF community? Of
> course, I'm not saying that's what happened hear. But a narrow rules
> that the IESG is required to put on blinders and only consider the
> IETF discussion list IETF Last Call email, ignoring previous
> discussions on other relevant IETF mailing lists and ignoring WG,
> area, and IETF plenary meeting discussions they have attended, is just
> arbitrary nonsense.

I wouldn't agree with that kind of narrow rule either.   But when =
evaluating IETF-wide consensus, it doesn't make sense to just add up all =
of the yeas and nays in both IETF and WG last call. =20

And in any case where there's not a clear consensus, part of the =
question should probably be "is there a compelling need for this =
document or action to move forward at this time?"  Sometimes I think =
people get the idea that they have to approve things "to get them off of =
their plates" so to speak, and to avoid having to iterate over the =
document several more times.  =20

Keith

p.s. My belief is that the 6to4-historic document wouldn't be nearly as =
divisive if either (a) it were deferred for a year or three or (b) the =
proponents had been willing to compromise on the status label.  When =
simple changes would suffice to build wide consensus, you have to wonder =
why there's been so much effort to push through a document for which =
consensus is dubious at best.



From paul.hoffman@vpnc.org  Fri Jun 24 08:50:48 2011
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 E140F21F8443; Fri, 24 Jun 2011 08:50:48 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0tSul-YnjjJ1; Fri, 24 Jun 2011 08:50:46 -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 E2E4521F8450; Fri, 24 Jun 2011 08:50:31 -0700 (PDT)
Received: from [10.20.30.104] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p5OFoMe1071026 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 Jun 2011 08:50:23 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Why ask for IETF Consensus on a WG document?  
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <6C4159EC-9C66-48B4-8856-AD772745A026@gmail.com>
Date: Fri, 24 Jun 2011 08:50:27 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <97F90077-97BA-470A-A4D0-7AD40402349E@vpnc.org>
References: <6C4159EC-9C66-48B4-8856-AD772745A026@gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion list <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: Fri, 24 Jun 2011 15:50:49 -0000

On Jun 24, 2011, at 8:21 AM, RJ Atkinson wrote:

> Paul's assertion that public postings to the IETF Discussion=20
> list are the only metric for "IETF Consensus" is NOT correct=20
> -- and never has been in the past.

Come on, Ran. I never said "only metric", did I? This whole thread is =
about asking the IESG how they determine IETF consensus, with this being =
an example.

The IETF Discussion list and the the IESG balloting history are the only =
observable metrics we have, thus my question on this thread.

> "IETF Consensus" includes ALL of the inputs that the IESG
> receives about a document or issue that is put to IETF
> Last Call.   The Last Call announcement specifically says,
> for example, that comments may be sent privately to the
> IESG.

Completely correct.

> Consensus inputs are NOT limited to posted public comments,
> BUT ALSO include formal liaisons, communications with various=20
> WG Chairs (not limited to the sponsoring WG), private email=20
> to the IESG, private email to an AD, and more.

Completely correct. You also left out the shepherd report, which also =
contains valuable information about the level of consensus in the WG.

And you have now listed so many variables, it begs the question: how =
does the IESG actually make the call when the observable comments on =
ietf@ make consensus seem questionable?

> Note also that this is THE SAME as how WG Chairs are supposed
> to operate.  WG Chairs are supposed to consider ALL inputs,
> NOT ONLY public postings to the WG list, BUT ALSO private
> inputs from WG participants and other applicable folks,
> and whatever other inputs arrive after a WG Last Call is
> announced.

We probably disagree here: I don't think that WG chairs should make =
consensus decisions based on private inputs that cannot be validated. =
Doing so is begging for WG chair over-reaching.

> I hear that Paul H is unhappy with this particular outcome,

...which means that you did not read the messages I sent. I explicitly =
said I didn't care about this one, which is why I didn't say anything =
during the Last Call.

> but there is no evidence of any kind of process problem
> or process mistake here.

Nor did I say that there was. I asked a question that this particular =
Draft helps illuminate, and I did so after talking to ADs who thought =
there were indeed interesting process problems. YMMV.

--Paul Hoffman


From moore@network-heretics.com  Fri Jun 24 08:54:08 2011
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 3B38921F844D for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 08:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.405
X-Spam-Level: 
X-Spam-Status: No, score=-3.405 tagged_above=-999 required=5 tests=[AWL=0.194,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JQLz626xY3I4 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 08:54:07 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 320F221F844B for <ietf@ietf.org>; Fri, 24 Jun 2011 08:54:07 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id DBC3820B21; Fri, 24 Jun 2011 11:54:06 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Fri, 24 Jun 2011 11:54:06 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=VUpw0vsEidyGlLYblW2e+ecLRdE=; b=pG4gicb3URM02uKQfgd+HS1lHp6lGcx4T8gT11LPHPaR7IIG+xBTrTx4FVfdHQrJnWRj3XtNMSEgSV/HnJdiiJPtscs+E3MkFXgJA9P8/5HH5d3QoW/rI1qBFt2Jhwt57JPGUqVJOKzPUNHTppM8Hv0dHVBdVtdObonvRxf9yKc=
X-Sasl-enc: a8DGqGCzkduUUsdq5g/E77DD66P1k6td3P8PyLZjUv8R 1308930846
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id CC28D40067C; Fri, 24 Jun 2011 11:54:05 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?  
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <6C4159EC-9C66-48B4-8856-AD772745A026@gmail.com>
Date: Fri, 24 Jun 2011 11:54:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EDB52C83-25F6-40C4-A5D1-9AFCEC13CB74@network-heretics.com>
References: <6C4159EC-9C66-48B4-8856-AD772745A026@gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 15:54:08 -0000

On Jun 24, 2011, at 11:21 AM, RJ Atkinson wrote:

> Earlier, Paul Hoffman wrote, in part:
>> ...the IESG just approved publication of X, even with
>> what appears to be a lack of consensus in the comments
>> on the ietf@ mailing list.
>>=20
>> (some other text elided here.)
>>=20
>> For a document such as this, why even ask for IETF consensus=20
>> if the IETF consensus doesn't matter?
>>=20
>> (remaining text elided here.)=20
>=20
>=20
> Next, as a reference, here is a boilerplate snippet from
> a recent IETF Last Call:
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf at ietf.org mailing lists by 2011-07-21. Exceptionally, comments
>> may be sent to iesg at ietf.org instead. In either case, please =
retain
>> the beginning of the Subject line to allow automated sorting.
>=20
>=20
> The "IETF Consensus" matters, and I believe the IESG=20
> did fully and properly consider that matter in the case
> that appears to have driven your note.
>=20
> There appears to be a confusion underlying your note.
>=20
> Paul's assertion that public postings to the IETF Discussion=20
> list are the only metric for "IETF Consensus" is NOT correct=20
> -- and never has been in the past. =20
>=20
> "IETF Consensus" includes ALL of the inputs that the IESG
> receives about a document or issue that is put to IETF
> Last Call.   The Last Call announcement specifically says,
> for example, that comments may be sent privately to the
> IESG.
>=20
> Consensus inputs are NOT limited to posted public comments,

I agree with this much:  IESG, at least, should be able to consider =
private comments about document and standards actions, as input to its =
determinations.=20

But one of the important attributes of consensus, one of the things that =
makes it so powerful, is that ideally, it's visible to everyone.  Take =
the example where a bunch of people in a room are asked a question and =
asked to raise hands to indicate yea or nay.   If only one or two people =
express a particular opinion, they can each see that for themselves, and =
that the "rough consensus" is clearly against them.   Likewise, the =
other participants will be able to see that the rough consensus is on =
their side of things.=20

On a mailing list, it's a bit harder.  But still, when the traffic is =
visible to all list participants, it isn't too hard to know whether your =
opinion is widely supported, or whether you're part of a small minority.

In my experience, private input to IESG is more valuable in helping the =
IESG deal with technical evaluation or other concerns, than with =
consensus determination.   At least when I was on IESG, the volume of =
private Last Call responses was fairly small and I don't recall a case =
when I thought it would affect a determination of community wide =
consensus.    But private input was occasionally quite valuable in other =
ways.

While I do think that IESG should be able to consider private input in =
consensus determination, from a process standpoint it's problematic.  If =
the IESG decision doesn't reflect the visible consensus or lack thereof, =
this quite properly raises a question as to whether IESG has properly =
evaluated consensus.  So in the event that there were a substantial =
amount of private input, IESG would do well to find a way to make it =
clear to the public that is conclusions were based on that input, in =
what way, and for what reasons.

In this particular case I don't see any reason to believe that IESG has =
received a substantial amount of private input.  e.g. I didn't see any =
mention of such input in the IESG writeup or the IESG members' comments.

Keith


From john-ietf@jck.com  Fri Jun 24 09:09:11 2011
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 B3DA411E80E9; Fri, 24 Jun 2011 09:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MBuU3T5hjfwH; Fri, 24 Jun 2011 09:09:10 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 879DC11E809B; Fri, 24 Jun 2011 09:09:10 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Qa8wC-0005Pm-7h; Fri, 24 Jun 2011 12:08:56 -0400
Date: Fri, 24 Jun 2011 12:08:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Why ask for IETF Consensus on a WG document?
Message-ID: <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]>
In-Reply-To: <4E03E9A9.2000300@gmail.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@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: The IESG <iesg@ietf.org>, IETF-Discussion list <ietf@ietf.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: Fri, 24 Jun 2011 16:09:11 -0000

--On Friday, 24 June, 2011 13:34 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>...
> I think that's about right. There were several strong and very
> raional opinions against this, including some who were not
> involved in the similarly rough consensus in the WG
> discussion. But (speaking as a co-author of one of the drafts
> being historicised) I'd say the balance of opinion was to
> publish. However, it's a close call.

Brian,

I see another problem here that, IMO, is complementary to the
issue that Paul raises and enough independent of that issue that
one could agree that the consensus determination was reasonable
but still wrong (I don't concede the first, but want to look at
the second).

I've never assumed that the LC process is a binary one, with the
only possible answers being "approve as written" or "complete
trash".  It is a call for comments, not an approval vote.   The
IESG clearly recognizes the distinction, although usually in
minor ways -- tuning of documents after IETF LC or IESG reviews
is almost certainly the norm rather than the exception and that
tuning is sometimes fairly significant.

In this case, it would not be hard to convince me that there was
pretty good IETF consensus that an unrestricted recommendation
for using 6to4 was appropriate.  Even most of 6to4's strongest
advocates seem to agree that using it in stupid and naive ways
leads to bad outcomes.  But consensus on that subject is not
consensus that moving the whole business to Historic is a good
idea.  To paraphrase at least one comment, there is danger of
throwing the baby (and perhaps some of the plumbing fixtures)
away with the bath water. 

What I saw was what appeared to me to be some fairly strong
arguments for looking at the problem in a different way -- a way
that I've seen no evidence the WG considered at all.   That
would be to explore alternatives to the rather blunt instrument
of making a protocol specification historic: explaining what
needs to be done to get it right (your document does a lot of
that) and then figuring out ways to warn against the uses and
configurations that we all (or mostly) agree are bad news.

I would like to see evidence (or even a strong assertion) that
the IESG considered options other than "adopt package and more
6to4 to Historic" and "don't".   I believe the LC discussions
call for that discussion, not boilerplate about rough consensus
around a narrow reading of the question that does not admit of
the possibility of other alternatives.

I'm not going to appeal this one, but I think that someone who
feels more strongly about it probably should.

     john




From rja.lists@gmail.com  Fri Jun 24 09:18:13 2011
Return-Path: <rja.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 8B39411E809B for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 09:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.61
X-Spam-Level: 
X-Spam-Status: No, score=-3.61 tagged_above=-999 required=5 tests=[AWL=-0.011,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ld1t9i+Kzr7j for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 09:18:13 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id D0ED011E8096 for <ietf@ietf.org>; Fri, 24 Jun 2011 09:18:12 -0700 (PDT)
Received: by vxi40 with SMTP id 40so3022713vxi.31 for <ietf@ietf.org>; Fri, 24 Jun 2011 09:18:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=U4/o8fYJtY1klF8Jx+rJEw5EI1N1PZFVZxqeoCgPubY=; b=DVVjI4Ph9iZT3LLuv9f8S+KJF5V6YQKumB90Sda9y7PzZGZq8AoHc2a022JqUAZ+im FzpyP94OoZi7QzQkPO22i68KO+72sDHpeVJFQayBaIoTpRc1uDiGwjWlc/BiD+5uH7e6 k/PIn5Vvmf9uOGN7k6AhH8DGlsyr2GOYQV84Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=eZFOkimJf5LH8nUsG4Lqc3KO36z4g6BiZAU5MJXVKxIY8PJ6p1E0KAs5s00ewH3Z+a IqrUNXjRo1qc8/zHwYoLE5x/oAJsFZKX+YxUKDSgDwvGlwsd8IsEnh2wd8VU3xaJe4Ug ekusgnbE+NvlVh6R8HbzaC4RnoKFc4aKKkaRQ=
Received: by 10.52.173.84 with SMTP id bi20mr4672303vdc.69.1308932292324; Fri, 24 Jun 2011 09:18:12 -0700 (PDT)
Received: from [10.30.20.12] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id q1sm805070vdt.23.2011.06.24.09.18.11 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 24 Jun 2011 09:18:11 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Why ask for IETF Consensus on a WG document?  
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <97F90077-97BA-470A-A4D0-7AD40402349E@vpnc.org>
Date: Fri, 24 Jun 2011 12:18:09 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <0A5F9E30-D93A-4D97-982B-6560DEBC6B94@gmail.com>
References: <6C4159EC-9C66-48B4-8856-AD772745A026@gmail.com> <97F90077-97BA-470A-A4D0-7AD40402349E@vpnc.org>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 16:18:13 -0000

On 24  Jun 2011, at 11:50 , Paul Hoffman wrote:
> And you have now listed so many variables, it begs the question:

Paul,

I disagree that it begs that question.  

The IETF processes have always been open to ALL inputs from whatever 
source, in all parts of its processes.  You write that text above as if 
listening to all inputs is news, and it just isn't.

> how does the IESG actually make the call when the observable
> comments on ietf@ make consensus seem questionable?

The make their best effort determination, just as they always do.
That is how things have ALWAYS worked.  It works well.

Consensus in the IETF has NEVER been a numbers game, 
counting merely the public postings.  The IETF doesn't vote.

Just counting the numbers of public postings would be voting,
and this organisation has made a quite explicit decision 
NOT to vote.  

I'm told IEEE 802 votes, and I'm told they are happy with the results.
That's great for them, if true, but it isn't sensible for IETF.

To repeat some of what Don Eastlake wrote (I read his note 
just after sending my earlier note):
> But a narrow rule that the IESG is required to put on blinders and 
> only consider the IETF discussion list IETF Last Call email, 
> ignoring previous discussions on other relevant IETF mailing lists 
> and ignoring WG, area, and IETF plenary meeting discussions they
> have attended, is just arbitrary nonsense.

I totally agree with Don's quoted text just above.  

There is not now, has never been, and could never be a crisp rule 
defining a formula or algorithm on how the IESG determines consensus 
(or on how a WG Chair determines consensus).

I know of a large number of cases where one or more people sent private 
inputs to WG Chair(s) or to IESG folks on some Last Call item -- simply 
to avoid IETF-related controversy.  

Cheers,

Ran Atkinson





From mrex@sap.com  Fri Jun 24 09:32:39 2011
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 4FA5711E8116 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 09:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.614
X-Spam-Level: 
X-Spam-Status: No, score=-9.614 tagged_above=-999 required=5 tests=[AWL=0.635,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id von9XIlD0s9h for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 09:32:37 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id D9C5C11E80F0 for <ietf@ietf.org>; Fri, 24 Jun 2011 09:32:32 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p5OGWULn025069 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 24 Jun 2011 18:32:30 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201106241632.p5OGWUGH020309@fs4113.wdf.sap.corp>
Subject: Re: Why ask for IETF Consensus on a WG document?
To: rja.lists@gmail.com (RJ Atkinson)
Date: Fri, 24 Jun 2011 18:32:30 +0200 (MEST)
In-Reply-To: <6C4159EC-9C66-48B4-8856-AD772745A026@gmail.com> from "RJ Atkinson" at Jun 24, 11 11:21:06 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: 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: Fri, 24 Jun 2011 16:32:39 -0000

RJ Atkinson wrote:
> 
> The "IETF Consensus" matters,

I believe it should, but I currently completely fail to see
that it did matter to the IESG.


>
> and I believe the IESG did fully and properly consider that matter
> in the case that appears to have driven your note.

I would be curious about the IETF Last Call writeup from the responsible
Area Director about the issue that were raised during IETF Last Call
and their resolution, rfc-4858 Section 3.2 (2.i) => (2.b)-(2.h)

  http://tools.ietf.org/html/rfc4858#page-10


I don't see that IETF LC Writeup in the Datatracker

  https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/writeup/


And I don't see the significant objection specifically on the
procedural issue that moving to historic is an abuse of the
IETF process in the comments of other ADs here:

  https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ballot/


So I agree to Pauls original request for clarification:
Has the IESG given itself entirely new procedures for protocol
actions, and when are those going to be published  (maybe using
the same bypass of the traditional IETF consensus
process that the above document seems to have used).


> 
> Paul's assertion that public postings to the IETF Discussion 
> list are the only metric for "IETF Consensus" is NOT correct 
> -- and never has been in the past.  

If you read rfc4858 section 3.2 above, there was supposed to be a collection,
determination and resolution process for issues raised in an IETF LC in
just the same fashion as for the WG LC, and an IETF writeup of
significant issues raised during IETF LC and their resolution
as a prerequisition for an IESG decision.

If the new IESG approach to faster publication of RFC is to
simply ignore issues raised during IETF LC and rely primarily
on WG Last Call, and to make this change to the IETF procedures
bypassing public discussion and IETF consensus, then it would
be helpful for the resource management of IETF participants
when determining where to spend their valuable time: on WG
discussions or IETF LCs.


> 
> "IETF Consensus" includes ALL of the inputs that the IESG
> receives about a document or issue that is put to IETF
> Last Call.

IETF Consensus precludes ignoring procedural issues and
in-scope technical issues.  Otherwise it is IESG consensus
at best.


Why was there no serious consideration to downgrade 6to4 to
experimental instead of moving it to historic?
Are there any serious procedural issues against "experimental"?


>
> The Last Call announcement specifically says,
> for example, that comments may be sent privately to the
> IESG.
> 
> Consensus inputs are NOT limited to posted public comments,
> BUT ALSO include formal liaisons, communications with various 
> WG Chairs (not limited to the sponsoring WG), private email 
> to the IESG, private email to an AD, and more.


The irritation is about consensus-precluding input that has been
openly discussed in a quite elaborate fashion and a complete
lack of writeup and resolution of the IETF LC issues on the part
of the responsible AD.

...which bears resemblance with what this words of rfc2418
specifically cautions against:

   http://tools.ietf.org/html/rfc2418#section-2.3

   Proposed working groups often comprise technically competent
   participants who are not familiar with the history of Internet
   architecture or IETF processes.  This can, unfortunately, lead to
   good working group consensus about a bad design.


The job of the IESG is _not_ to defend a WGs interests against the interests
of the IETF at large, but the other way round, to ensure that the
interests of the IETF at large are sufficiently addressed by the output 
of the WG (or the author of an independent submission) before a document
is published as RFC.


> 
> Note also that this is THE SAME as how WG Chairs are supposed
> to operate.  WG Chairs are supposed to consider ALL inputs,
> NOT ONLY public postings to the WG list, BUT ALSO private
> inputs from WG participants and other applicable folks,
> and whatever other inputs arrive after a WG Last Call is
> announced.

Yes, but in an open standardizations body, the WG Chairs need to
document "openly" whatever input (content, not necessary contributor)
that they based their decision on.

A WG Chair or AD writing "I've received important input from important
lobbies, but I am unwilling or unable to disclose any content,
so I declare consensus to be that certain way." would not be appropriate
for the original open standardization process of the IETF.

Neither the absence of a write-up or deliberate ignorance of
raised procedural and in-scope technical issues.  Also contentious
matters of taste should be documented in the write-up.


-Martin

From msk@cloudmark.com  Fri Jun 24 09:36:16 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 704E011E809B; Fri, 24 Jun 2011 09:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.589
X-Spam-Level: 
X-Spam-Status: No, score=-103.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tp-ptUQz+Vsn; Fri, 24 Jun 2011 09:36:15 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 2A2C511E80E7; Fri, 24 Jun 2011 09:36:15 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Fri, 24 Jun 2011 09:36:14 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF-Discussion list <ietf@ietf.org>
Date: Fri, 24 Jun 2011 09:36:13 -0700
Subject: RE: Why ask for IETF Consensus on a WG document?
Thread-Topic: Why ask for IETF Consensus on a WG document?
Thread-Index: AcwyZJBeQiGsacQ/THSK8BAws0ctbQAJ7phQ
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC49DD@EXCH-C2.corp.cloudmark.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org>	<4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com>
In-Reply-To: <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 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: Fri, 24 Jun 2011 16:36:16 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of K=
eith Moore
> Sent: Friday, June 24, 2011 4:48 AM
> To: Stephen Farrell
> Cc: IETF-Discussion list; Paul Hoffman; The IESG
> Subject: Re: Why ask for IETF Consensus on a WG document?
>=20
> It's problematic, and I believe inappropriate, to consider WG consensus
> as contributing to community consensus.  The two questions need to be
> considered separately, for two reasons:
>=20
> 1. Working groups often have strong biases and aren't representative of
> the whole community.  Put another way, a working group often represents
> only one side of a tussle, and working groups are often deliberately
> chartered in such a way as to minimize the potential for conflict
> within the group.

By contrast, working groups tend to contain more expertise than may be avai=
lable in an IETF LC; that's partly why they're formed.  I've never been an =
AD before, but I imagine I might consider the WG consensus to be at least a=
 little bit more weighty than IETF LC resistance.

For that matter, if you object vehemently to something a WG produces, then =
the work is of interest to you, and I have to wonder why you weren't at lea=
st silently tracking that working group in the first place.


From moore@network-heretics.com  Fri Jun 24 09:37:23 2011
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 CAFB211E8120 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 09:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.409
X-Spam-Level: 
X-Spam-Status: No, score=-3.409 tagged_above=-999 required=5 tests=[AWL=0.190,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hq1YX15M-TpK for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 09:37:23 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 783EE11E80E8 for <ietf@ietf.org>; Fri, 24 Jun 2011 09:37:22 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 95B4820A85; Fri, 24 Jun 2011 12:37:21 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 24 Jun 2011 12:37:21 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=zIFr+JkzmRRgKfoQ8b/3z30+z54=; b=GHo+RJICg+Vah02HsJv6JsJJJf9u4i7io6Zfv7Ut9AVUIQ5UJBKH+9hVdZI1iQ9ylDoEePnwQ9CSy78Q2ZQchJrUzmhqHCLkZvz0hAKt9pPyS11Vdr5INN7qB/RayRon7mbkF1WivPH0IrXHYfBzoWcuqbOIrMGOgk3fqElJPOU=
X-Sasl-enc: Anv1abaW9Hfvynw0Ppm+MHSRu+HOenMHdzj+eH6abwM3 1308933440
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 9D47E400FA0; Fri, 24 Jun 2011 12:37:20 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?  
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <0A5F9E30-D93A-4D97-982B-6560DEBC6B94@gmail.com>
Date: Fri, 24 Jun 2011 12:37:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA109EA7-998F-4FB0-AD03-2B847AD9ECEA@network-heretics.com>
References: <6C4159EC-9C66-48B4-8856-AD772745A026@gmail.com> <97F90077-97BA-470A-A4D0-7AD40402349E@vpnc.org> <0A5F9E30-D93A-4D97-982B-6560DEBC6B94@gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 16:37:23 -0000

On Jun 24, 2011, at 12:18 PM, RJ Atkinson wrote:

> Consensus in the IETF has NEVER been a numbers game,=20
> counting merely the public postings.  The IETF doesn't vote.
>=20
> Just counting the numbers of public postings would be voting,
> and this organisation has made a quite explicit decision=20
> NOT to vote. =20

It's true in many ways that IETF does not vote.   Last Call inputs are =
not limited to strictly yea or nay; and there are no well-defined =
criteria for when an action has sufficient support (or lack thereof) =
from participants.

At the same time, when evaluating consensus, it's often useful to do a =
count of the number of approvals vs. objections.   Anytime there is a =
significant number of objections, "rough consensus" is in doubt.=20

Sometimes when weeding through a long exchange of emails, it's hard to =
get a sense of just what the balance is without doing an actual count.  =
Actually counting names helps remove some kinds of bias, e.g. the =
tendency to count opinions with which one agrees, more than those with =
which one disagrees.    =20

But even counting is an approximate process.   Not all responses are =
entirely yea or nay, and sometimes peoples' opinions shift as the =
conversation progresses.  (which, IMO, is a good sign.)

Keith


From jnc@mercury.lcs.mit.edu  Fri Jun 24 09:41:33 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0DA711E80F3 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 09:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level: 
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXN6ILyYw9En for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 09:41:33 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 2930111E809B for <ietf@ietf.org>; Fri, 24 Jun 2011 09:41:33 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 22FF318C0C1; Fri, 24 Jun 2011 12:41:32 -0400 (EDT)
To: ietf@ietf.org
Subject: RE: one data point regarding native IPv6 support
Message-Id: <20110624164132.22FF318C0C1@mercury.lcs.mit.edu>
Date: Fri, 24 Jun 2011 12:41:32 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 16:41:33 -0000

    > From: Christian Huitema <huitema@microsoft.com>

    > From Noel analysis

A belated (sorry) note to clarify the record: all I did was repeat stuff
from other people's studies (principally the one by Geoff Huston); they
should get all the credit.


And while I'm here anyway...

    > it seems that a lot of the issues could be mitigated by simple
    > connectivity test.

Well, IPv6 Neighbour Discovery is just the thing. I gather it's turned off
on 6to4 links, which in retrospect was probably a mistake. I would
recommend that it be turned on, but apparently the WG decided against
making that recommendation in the '6to4 fixes' document?

Other work with similar 'automatic' (i.e. not manually configured) overlay
networks has shown that conditions in the Internet these days are such
that one simply cannot assume that just because one's next-hop packet
switch appears to have a routing table entry for some destination, that
that means that any traffic sent to it will get there. You simply _have_
to do liveness testing (and not just on the other node, but also on the
paths in both directions).

On overlay networks with large fanouts, this can present a rather tricky
problem - O(N) overhead - but there are a variety of tricks (e.g.
piggybacking liveness mechanisms on user traffic) one can use. That
shouldn't be a problem in this case, which is why I think just turning on
ND on 6to4 is the way to go.


    > It also does not solve the problem of routers advertising an IPv6
    > route to 2002::/16 and then failing to deliver the IPv4 packets.

Well, RFC-3068 does say:

  "Any 6to4 relay router corresponding to this specification must
   include a monitoring function, to check that the 6to4 relay function
   is operational.  The router must stop injecting the route leading to
   the 6to4 anycast prefix immediately if it detects that the relay
   function is not operational."

So boxes that do what you mention (advertising 2002::/16 and then failing
to deliver the packets to the matching IPv4 address) are _already_
violating the spec...

	NOel

From evnikita2@gmail.com  Fri Jun 24 09:51:51 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF05611E815B; Fri, 24 Jun 2011 09:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.463
X-Spam-Level: 
X-Spam-Status: No, score=-3.463 tagged_above=-999 required=5 tests=[AWL=0.136,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XQvUCpgLjGqT; Fri, 24 Jun 2011 09:51:50 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id EF9F311E815C; Fri, 24 Jun 2011 09:51:49 -0700 (PDT)
Received: by fxm15 with SMTP id 15so2264934fxm.31 for <multiple recipients>; Fri, 24 Jun 2011 09:51:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Gdd+/QUuFtrUd/7TZsPew9FPGxIA5LDiIlnEx8fa0ak=; b=RMgAU7jtYbrzD4bm1mLMgL1Yi9OZiudXSz+xvkaEMbuH9ilR+mJq1eSvorSf+2qXAf yYiIr5KgBjiHHq31AZG2+H2G00BzNEBO9S6ovUlOvpAeM2QlV3j22y7FRluRxYRUT+6Z fJW2ScBYzczT2PMxruTjf5CVJr0J+MYPQGtAQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=R4zjeuEt+WzzyRvAcHqGYKRRtoRNrvsgfnzX8BiK4Id1aGEyvkCTaip61qX//5/AoA q2eB/2hKx81aIB1TBCD9QQ4tzfn3VbKFfEnCvS3wQieRvNpifFAcp/1GHkr7AJ3wQ1zo XV3ygdcngrYVmuOoJe/Re04rXnC1XiSFqT7do=
Received: by 10.223.1.201 with SMTP id 9mr4697128fag.91.1308934306925; Fri, 24 Jun 2011 09:51:46 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id y14sm1758091fah.37.2011.06.24.09.51.44 (version=SSLv3 cipher=OTHER); Fri, 24 Jun 2011 09:51:45 -0700 (PDT)
Message-ID: <4E04C0CE.1030807@gmail.com>
Date: Fri, 24 Jun 2011 19:52:30 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org, ftpext@ietf.org
Subject: Re: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File	Transfer Protocol	HOST Command for Virtual Hosts) to Proposed	Standard
References: <20110616130503.4854.51928.idtracker@ietfa.amsl.com>
In-Reply-To: <20110616130503.4854.51928.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 16:51:51 -0000

Hello,

This document is well written; I'm strongly for its publication on 
Standards Track.  I have an only remark.  This document doesn't seem to 
mention what is the behavior of the server if HOST command is sent after 
one HOST has already been sent.  Eg.

C> HOST example.com
S> 220 Host OK
C> USER foo
S> 331 Specify password
C> PASS bar
S> 230 Logged in
C> HOST example.org
S> ????

I suppose the server may treat this as REIN and then switching to 
specified host, if the user is authenticated, and just switch to such 
host if the user isn't already logged in.  Another option is sending 503 
reply, as invalid sequence of commands.

Thanks,
Mykyta Yevstifeyev

16.06.2011 16:05, The IESG wrote:
> The IESG has received a request from the FTP Extensions, 2nd edition WG
> (ftpext2) to consider the following document:
> - 'File Transfer Protocol HOST Command for Virtual Hosts'
>    <draft-ietf-ftpext2-hosts-02.txt>  as a Proposed Standard
>
> [ . . . ]


From moore@network-heretics.com  Fri Jun 24 09:55:03 2011
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 495ED11E8173; Fri, 24 Jun 2011 09:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.112
X-Spam-Level: 
X-Spam-Status: No, score=-3.112 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6-hMcP5pvOLL; Fri, 24 Jun 2011 09:55:02 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 85C6711E816F; Fri, 24 Jun 2011 09:55:01 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 84E1820348; Fri, 24 Jun 2011 12:55:00 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 24 Jun 2011 12:55:00 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=/VPWsqolJWlghHOb0N1tfX0NTKc=; b=Fj/azV5ckXy6ypvCaJnGZhhy0Z6JnlJy9QCFp3fVT3qnWNKe7ZS5xPFFMy+rpaCAtMf69i3OyiheDR9DHdhxJVqq00iikphuZESgIxBHONpaLHH31Iy3X9xypp55i8tzZYh7gLSh4Bf0qGpuiwZh95kV1R/aHZAdef75QcSkFwg=
X-Sasl-enc: FypyGsAcnSLfHqkO5cpT+K47v1pDrweE8ZVD/23zG1K1 1308934499
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 5260D400984; Fri, 24 Jun 2011 12:54:59 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134EBC49DD@EXCH-C2.corp.cloudmark.com>
Date: Fri, 24 Jun 2011 12:54:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <54FD1997-70C6-49E4-A783-3EC2386D71B3@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org>	<4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <F5833273385BB34F99288B3648C4F06F134EBC49DD@EXCH-C2.corp.cloudmark.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion list <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: Fri, 24 Jun 2011 16:55:04 -0000

On Jun 24, 2011, at 12:36 PM, Murray S. Kucherawy wrote:

>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Keith Moore
>> Sent: Friday, June 24, 2011 4:48 AM
>> To: Stephen Farrell
>> Cc: IETF-Discussion list; Paul Hoffman; The IESG
>> Subject: Re: Why ask for IETF Consensus on a WG document?
>>=20
>> It's problematic, and I believe inappropriate, to consider WG =
consensus
>> as contributing to community consensus.  The two questions need to be
>> considered separately, for two reasons:
>>=20
>> 1. Working groups often have strong biases and aren't representative =
of
>> the whole community.  Put another way, a working group often =
represents
>> only one side of a tussle, and working groups are often deliberately
>> chartered in such a way as to minimize the potential for conflict
>> within the group.
>=20
> By contrast, working groups tend to contain more expertise than may be =
available in an IETF LC; that's partly why they're formed.  I've never =
been an AD before, but I imagine I might consider the WG consensus to be =
at least a little bit more weighty than IETF LC resistance.

WGs tend to contain a narrow range of expertise, even when their work =
affects a wide range of concerns.   Having a narrow range of expertise =
is good when the WG is tasked with doing a particular kind of protocol =
design.  But in general I don't think an "ops" group is in a good =
position to make recommendations on behalf of the whole IETF about =
things that aren't related to operations.  If they want to say "we want =
to call attention to these significant operational problems with =
protocol X" or " we recommend these particular operational practices to =
help protocol X work well" I think that's fine.   I don't think it's =
fine for them to be trying to harm things that other people are using, =
at least not without some broader community input. =20

> For that matter, if you object vehemently to something a WG produces, =
then the work is of interest to you, and I have to wonder why you =
weren't at least silently tracking that working group in the first =
place.

This one caught me completely by surprise.  I happened to notice, almost =
by accident, the discussion on the 6to4-advisory document, and was able =
to participate in some of that discussion.   The main result of my =
participation in that conversation, I think, was that I became convinced =
that disabling 6to4 by default really is the right thing to do... mostly =
because of the impending imposition of LSN.    But 6to4-historic goes =
way too far, and I wasn't aware of the 6to4-historic effort until IETF =
LC.

Following WG discussion requires a significant commitment.   I'm =
peripherally interested in v6ops, but until recently I had assumed that =
they were generally up to Good Stuff and didn't need my input for damage =
control purposes.  And the 6to4-advisory document is quite well written, =
and I came away from that discussion with the mistaken impression that =
the balance shown in that document was a reflection of the working group =
as a whole.  Also, I've had significant deadline pressures elsewhere, so =
haven't been able to check my v6ops mail folder as often as I'd like.

I don't think it's in IETF's interests to restrict input to only those =
who can make the significant commitment required to follow every IETF =
working group that might impact their work.  Frankly, with so many =
working groups, it's hard to even be aware of every working group that =
might impact one's work.

Keith


From ajs@anvilwalrusden.com  Fri Jun 24 10:05:23 2011
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 123FF11E80B2 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 10:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bbCTI3LReSke for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 10:05:22 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB9911E8122 for <ietf@ietf.org>; Fri, 24 Jun 2011 10:05:22 -0700 (PDT)
Received: from shinkuro.com (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 4C0F41ECB41D for <ietf@ietf.org>; Fri, 24 Jun 2011 17:05:20 +0000 (UTC)
Date: Fri, 24 Jun 2011 13:05:15 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Why ask for IETF Consensus on a WG document?
Message-ID: <20110624170515.GB97941@shinkuro.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org> <4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <F5833273385BB34F99288B3648C4F06F134EBC49DD@EXCH-C2.corp.cloudmark.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134EBC49DD@EXCH-C2.corp.cloudmark.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: Fri, 24 Jun 2011 17:05:23 -0000

On Fri, Jun 24, 2011 at 09:36:13AM -0700, Murray S. Kucherawy wrote:

> By contrast, working groups tend to contain more expertise than may
> be available in an IETF LC; that's partly why they're formed.  I've
> never been an AD before, but I imagine I might consider the WG
> consensus to be at least a little bit more weighty than IETF LC
> resistance.

I rather hope not.  As someone else has argued in this thread, WGs
tend to be narrowly focussed.  The IETF LC is at least partly, as I
understand it, to make sure that something which seems an obviously
good idea to the WG doesn't have all manner of implications that the
WG perhaps did not consider.

It seems to me that very strong reaction in the IETF generally to a
proposal demands convincing counter-arguments from those who support
the publication.  I refuse to have an opinion about the example under
discussion, but surely we don't want to build in some preference for
what the WG says.

Best,

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From dotis@mail-abuse.org  Fri Jun 24 10:33:23 2011
Return-Path: <dotis@mail-abuse.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 7B15A11E817D for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 10:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.719
X-Spam-Level: 
X-Spam-Status: No, score=-103.719 tagged_above=-999 required=5 tests=[AWL=-1.120, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tnGZmdLscBYF for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 10:33:22 -0700 (PDT)
Received: from SJDC-SDIRelay3.sdi.trendmicro.com (sjdc-sdirelay3.sdi.trendmicro.com [150.70.69.27]) by ietfa.amsl.com (Postfix) with ESMTP id 1296911E809F for <ietf@ietf.org>; Fri, 24 Jun 2011 10:33:16 -0700 (PDT)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by SJDC-SDIRelay3.sdi.trendmicro.com (Postfix) with ESMTP id 3824D6E004B; Fri, 24 Jun 2011 17:33:15 +0000 (UTC)
Received: from US-DOUGO-MAC.local (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id 7136FA9443C; Fri, 24 Jun 2011 17:34:06 +0000 (UTC)
Message-ID: <4E04CA58.8070201@mail-abuse.org>
Date: Fri, 24 Jun 2011 10:33:12 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys	Identified Mail (DKIM) Signatures) to Draft Standard
References: <20110623152458.19049.qmail@joyce.lan>
In-Reply-To: <20110623152458.19049.qmail@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf-dkim@mipassoc.org" <ietf-dkim@mipassoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 17:33:23 -0000

On 6/23/11 8:24 AM, John Levine wrote:
> In article<4E02EE24.2060708@gmail.com>  you write:
>> On 6/22/11 11:14 AM, Dave CROCKER wrote:
>>> Folks,
>>>
>>> The bottom line about Doug's note is that the working group extensively
>>> considered the basic issue of multiple From: header fields and Doug is
>>> raising nothing new about the topic.
> Dave is quite right.  Doug's purported attack just describes one of
> the endless ways that a string of bytes could be not quite a valid
> 5322 message, which might display in some mail programs in ways that
> some people might consider misleading.  If it's a problem at all, it's
> not a DKIM problem.
Perhaps you can explain why the motivation stated in RFC4686 includes 
anti-phishing as DKIM's goal?  Why of all the possible headers ONLY the 
 From header field MUST be signed?  Why RFC5617 describes the From 
header field as the Author Author address that is positively confirmed 
simply with a Valid DKIM signature result?  Both RFC4686 and RFC5617 
overlooked a rather obvious threat clearly demonstrated by Hector Santos 
on the DKIM mailing list:  Pre-pended singleton header fields.

Neither SMTP nor DKIM check for an invalid number of singleton header 
fields. These few header fields are limited to one because they are 
commonly displayed.  Multiple occurrence of any of these headers is 
likely deceptive, especially in DKIM's case.  DKIM always selects header 
fields from the bottom-up, but most sorting and displaying functions go 
top-down selection.

Complaints from John, Dave, and Barry and others is likely and 
understandably out of fatigue.  They just want the process to be over.  
We are now hearing there is a vital protocol layering principle at stake 
which even precludes DKIM from making these checks!  Really?

Although DKIM will be securely hashing the headers fields which MUST 
include the From header,  developers are being told they must ignore 
multiple singleton header fields discovered in the process.  It is not 
their burden!  As if securely hashing, fetching any number of public 
keys, and verifying any number of signatures isn't?

-Doug



From aiverson@spamresource.com  Fri Jun 24 10:47:12 2011
Return-Path: <aiverson@spamresource.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03A2E11E818B for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 10:47:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e-ZGLr4q4hSX for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 10:47:11 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2BE6911E809F for <ietf@ietf.org>; Fri, 24 Jun 2011 10:47:11 -0700 (PDT)
Received: by gwb20 with SMTP id 20so1776247gwb.31 for <ietf@ietf.org>; Fri, 24 Jun 2011 10:47:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.126.99 with SMTP id a63mr4994381yhi.311.1308937630259; Fri, 24 Jun 2011 10:47:10 -0700 (PDT)
Received: by 10.236.60.131 with HTTP; Fri, 24 Jun 2011 10:47:10 -0700 (PDT)
In-Reply-To: <4E04CA58.8070201@mail-abuse.org>
References: <20110623152458.19049.qmail@joyce.lan> <4E04CA58.8070201@mail-abuse.org>
Date: Fri, 24 Jun 2011 12:47:10 -0500
Message-ID: <BANLkTin8LmbdQ9HBjZhMf6j+o8WjMnssng@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified Mail (DKIM) Signatures) to Draft Standard
From: Al Iverson <aiverson@spamresource.com>
To: "ietf@ietf.org" <ietf@ietf.org>, "ietf-dkim@mipassoc.org" <ietf-dkim@mipassoc.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, 24 Jun 2011 17:47:12 -0000

On Fri, Jun 24, 2011 at 12:33 PM, Douglas Otis <dotis@mail-abuse.org> wrote=
:
> On 6/23/11 8:24 AM, John Levine wrote:
>>
>> In article<4E02EE24.2060708@gmail.com> =A0you write:
>>>
>>> On 6/22/11 11:14 AM, Dave CROCKER wrote:
>>>>
>>>> Folks,
>>>>
>>>> The bottom line about Doug's note is that the working group extensivel=
y
>>>> considered the basic issue of multiple From: header fields and Doug is
>>>> raising nothing new about the topic.
>>
>> Dave is quite right. =A0Doug's purported attack just describes one of
>> the endless ways that a string of bytes could be not quite a valid
>> 5322 message, which might display in some mail programs in ways that
>> some people might consider misleading. =A0If it's a problem at all, it's
>> not a DKIM problem.
>
> Perhaps you can explain why the motivation stated in RFC4686 includes
> anti-phishing as DKIM's goal? =A0Why of all the possible headers ONLY the=
 From
> header field MUST be signed? =A0Why RFC5617 describes the From header fie=
ld as
> the Author Author address that is positively confirmed simply with a Vali=
d
> DKIM signature result? =A0Both RFC4686 and RFC5617 overlooked a rather ob=
vious
> threat clearly demonstrated by Hector Santos on the DKIM mailing list:
> =A0Pre-pended singleton header fields.
>
> Neither SMTP nor DKIM check for an invalid number of singleton header
> fields. These few header fields are limited to one because they are commo=
nly
> displayed. =A0Multiple occurrence of any of these headers is likely decep=
tive,
> especially in DKIM's case. =A0DKIM always selects header fields from the
> bottom-up, but most sorting and displaying functions go top-down selectio=
n.
>
> Complaints from John, Dave, and Barry and others is likely and
> understandably out of fatigue. =A0They just want the process to be over. =
=A0We
> are now hearing there is a vital protocol layering principle at stake whi=
ch
> even precludes DKIM from making these checks! =A0Really?

I'm not suffering from fatigue, personally, and I agree with their
negative reaction toward your commentary. You're speaking as though
you expect DKIM to be the *only* type of message validation that's
going to happen to a message and thus it must account for and handle
message flaws far outside of scope.

This is like complaining that four wheels don't work as a car. True,
but you're missing the point. And you're doing it in a manner so laden
with hyperbole as to be offensive. It's really distressing and
disrespecting to the rest of us to have to read your same complaint
over and over and over. You've made your point. Few (none?) seem to
agree. Could you please move on?

Regards,
Al Iverson

From melinda.shore@gmail.com  Fri Jun 24 10:57:13 2011
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 C9A1411E818F for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 10:57:13 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oM8MobgWI+fV for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 10:57:13 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by ietfa.amsl.com (Postfix) with ESMTP id 21BB911E8114 for <ietf@ietf.org>; Fri, 24 Jun 2011 10:57:13 -0700 (PDT)
Received: by pvh18 with SMTP id 18so2003170pvh.31 for <ietf@ietf.org>; Fri, 24 Jun 2011 10:57:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JgIms8W+cP4JuPQbrV4o8kiyKmPRz8Jnku4B6t3+mvY=; b=wRKNhT/1wf3AozXGcS8G9c1a/fy4gp4GVmFrBZ+lH3byB92ErWmc/d1uklpirzVAjq j0g2kQ8fWjYngq/+g8DhXPNI080b1QCNYpCLiNC8v0CLx6zv0/+LR5jg3VHcQo8fqTPc VLlu35UQtLN+w/PTSTrfOI+dXNQubMSWRnL34=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=BwX+55kb8GXZu/L3QlMdBI29m0lc0LZTR4bhDM9SDxmAu19J3nD2wvohjyMrGDojLW Lpqb5qVSc/KTbeG2hlnIZhtefa9xBHB3RQCDnGH0EW2Q+KeQA1P9aDGnNJUkS316Sog5 RYQci3ITmboizyJp4q3cuYN3SSISBJzaoV2Pc=
Received: by 10.68.13.4 with SMTP id d4mr1929164pbc.64.1308938232791; Fri, 24 Jun 2011 10:57:12 -0700 (PDT)
Received: from [137.229.12.236] (drake.swits.alaska.edu [137.229.12.236]) by mx.google.com with ESMTPS id m7sm2215274pbk.26.2011.06.24.10.57.10 (version=SSLv3 cipher=OTHER); Fri, 24 Jun 2011 10:57:11 -0700 (PDT)
Message-ID: <4E04CFF9.40305@gmail.com>
Date: Fri, 24 Jun 2011 09:57:13 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im>	<FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org>	<4E045B80.7060800@cs.tcd.ie>	<AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com>	<20110624125522.GD76722@verdi>	<F965C40C-1B96-4590-A05E-7988EBAB51F6@vpnc.org> <BANLkTim9ECfr5e43x22OwYHo9KS=G09LGA@mail.gmail.com>
In-Reply-To: <BANLkTim9ECfr5e43x22OwYHo9KS=G09LGA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 17:57:13 -0000

On 06/24/2011 06:46 AM, Donald Eastlake wrote:
> If polls at area meetings with 100+ people at them at three successive
> IETF meetings on different continents consistently show, say, a 3 to 1
> preference for some proposal but the IETF Last call email has 6 people
> speaking against and only 4 in favor, what do you think the right
> judgement would be as to the consensus of the IETF community?

My understanding is that any decisions reached at meetings must
be ratified on mailing lists, which seems to me to suggest something
about order of precedence.

Melinda

From d3e3e3@gmail.com  Fri Jun 24 11:13:55 2011
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 7B2209E804F for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 11:13: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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bl5eoUW5qk0J for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 11:13:54 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id B0FF69E8042 for <ietf@ietf.org>; Fri, 24 Jun 2011 11:13:54 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1816291gxk.31 for <ietf@ietf.org>; Fri, 24 Jun 2011 11:13:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=H8Pfx11Mbt7czxLR5zW9GW3LW9/TY70ewjqB3ej2x8w=; b=MVb+Uy//EggVDNk5Ukq5fVHhurKaVWl10l6N+PXlJt0zpjmoc4k5EpyxvuhqcNfV47 x4qU/8dyzH1obLiitM0sGSKZ9cl3ZHHuDJDPCvH5iVxWBXHui+YSoZLQ9umrRccUpv73 INwCx+eh6uOcjbAqAC/uRrHlyKqMaFlMsMMCs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=LA6cp7F8D+GxGdkCJXh/Xq9WDvx84ik87jZASAGHQ3AzsErZ300LEJfCfbtGWPDfBm 0OlgEk+PhATtq8t5l5vg6C08Eoe1OIsEM92F6A+PIGuJ9u5hiiT10bfKTIhwcZQ6c2w+ 3Zd6Z+aKur3C0fU/5sjsVac3qfede4HPAjkas=
Received: by 10.151.5.5 with SMTP id h5mr4280996ybi.246.1308939234068; Fri, 24 Jun 2011 11:13:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.39.5 with HTTP; Fri, 24 Jun 2011 11:13:34 -0700 (PDT)
In-Reply-To: <4E04CFF9.40305@gmail.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org> <4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <20110624125522.GD76722@verdi> <F965C40C-1B96-4590-A05E-7988EBAB51F6@vpnc.org> <BANLkTim9ECfr5e43x22OwYHo9KS=G09LGA@mail.gmail.com> <4E04CFF9.40305@gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 24 Jun 2011 14:13:34 -0400
Message-ID: <BANLkTimbF2MR+kp=CpQMojBwE3A0yHObBQ@mail.gmail.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 18:13:55 -0000

Hi Melinda,

On Fri, Jun 24, 2011 at 1:57 PM, Melinda Shore <melinda.shore@gmail.com> wr=
ote:
> On 06/24/2011 06:46 AM, Donald Eastlake wrote:
>>
>> If polls at area meetings with 100+ people at them at three successive
>> IETF meetings on different continents consistently show, say, a 3 to 1
>> preference for some proposal but the IETF Last call email has 6 people
>> speaking against and only 4 in favor, what do you think the right
>> judgement would be as to the consensus of the IETF community?
>
> My understanding is that any decisions reached at meetings must
> be ratified on mailing lists, which seems to me to suggest something
> about order of precedence.

It depends on what you mean by "ratified". I suppose a WG meeting
could be said to have "reached a decision" but it isn't a decision of
the WG, just the meeting. It must be brought up on the WG mailing list
to provide broader opportunity for input, positive or negative. After
it has been brought up on the mailing list, then the WG Chair(s) judge
what the WG consensus is. It is certainly not required that, in making
that judgement, the WG Chairs can only look at WG mailing list
postings.

> Melinda

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street
=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

From suresh.krishnan@ericsson.com  Fri Jun 24 11:19:07 2011
Return-Path: <suresh.krishnan@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 69E6111E808F for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 11:19:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.52
X-Spam-Level: 
X-Spam-Status: No, score=-106.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O+pGrjWBXTxs for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 11:19:06 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 75F6A11E809E for <ietf@ietf.org>; Fri, 24 Jun 2011 11:19:06 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p5OIJ4gG019778 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Fri, 24 Jun 2011 13:19:05 -0500
Received: from [142.133.10.107] (147.117.20.214) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.3.137.0; Fri, 24 Jun 2011 14:19:04 -0400
Message-ID: <4E04D399.1080400@ericsson.com>
Date: Fri, 24 Jun 2011 14:12:41 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Nomcom 2011-2012: Second Call for Volunteers
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 Jun 2011 18:19:07 -0000

This is the Second call for Volunteers for the 2011-12 Nomcom.  We are
just about halfway through the volunteer period so if you are considering
volunteering, please do so very soon.

We have had a very good response to the initial call for volunteers and
I am pleased to report that we have 50 volunteers thus far whose
qualifications have been confirmed by the secretariat. I have notified
each of these volunteers by email.

However, we would like to have many more volunteers. The more volunteers,
the better chance we have of choosing a random yet representative cross
section of the IETF population. You have until 11:59 pm EDT July 10, 2011
to volunteer for Nomcom but it would be much better if you can volunteer
as early as possible.

If you volunteered before 21:00 EDT on June 21 to serve as a voting member
and have not received a confirmation email from me, please re-submit and
bring to my attention right away!

Details about the process for volunteering for the Nomcom and the list
of open positions for which the nominating committee is responsible are
summarized in the initial announcement:

https://datatracker.ietf.org/ann/nomcom/2938/

The 50 volunteers who have thus far been qualified by the secretariat
are:

Alia Atlas , Juniper Networks
Lixia Zhang , UCLA
Wassim Haddad  , Ericsson
Glen Zorn , Network Zen
Richard Barnes , BBN Technologies
Stephen Kent , BBN Technologies
Scott Mansfield , Ericsson
Tina TSOU , FutureWei Technologies
Fernando Gont , UTN/FRH
Karen Seo , BBN Technologies
Jie Dong , Huawei Technologies
Mach Chen , Huawei Technologies Co.
Sheng Jiang , Huawei Technologies Co. Ltd.
Dimitri Papadimitriou , Alcatel-Lucent
Thomas D. Nadeau , CA Technologies
David Meyer , Cisco Systems/University of Oregon
Wesley George , Time Warner Cable
Cullen Jennings , Cisco
Stephen Hanna , Juniper Networks
Stephan Wenger , Bidyo
Keyur Patel , Cisco Systems
Michael Hamilton , BreakingPoint Systems
Behcet Sarikaya , Huawei USA
Mark Townsley , Cisco Systems
Fred Baker , Cisco Systems
Brian Trammell , ETH Zurich
Sam Hartman , Painless Security
Chris Griffiths , Comcast
George Michaelson , APNIC
Jiankang Yao , CNNIC
Sohel Khan , Comcast
Dacheng Zhang , Huawei
Lianshu Zheng , Huawei Technologies
Hui Deng , China Mobile
Gang Chen , China Mobile
Mirja Kuhlewind , University of Stuttgart
John E Drake , Juniper Networks
Matt Lepinski , BBN Technologies
Subir Das , Telcordia Technologies Inc
Yi Zhao , Huawei
John Scudder , Juniper Networks
Christer Holmberg , LM Ericsson
Teemu Savolainen , Nokia
Samita Chakrabarti , Ericsson
Jaap Akkerhuis , NLnet labs
Jason Weil , Time Warner Cable
Randy Bush , Internet Initiative Japan
Christian Schmidt , Nokia Siemens Networks
Sean Shen , CNNIC
Lou Berger , LabN Consulting

The primary activity for this nomcom will begin during IETF-81 in
Quebec City and should be completed by January 2012. The nomcom will
be collecting requirements from the community, as well as talking to
candidates and to community members about candidates. There will be
regularly scheduled conference calls to ensure progress. Thus, being a
nomcom member does require some time commitment.

Please volunteer by sending an email to me before
11:59 pm EDT July 10, 2011 as follows:

To: suresh.krishnan@ericsson.com
Subject: Nomcom 2011-12 Volunteer

Please include the following information in the body of the mail:

Full Name:  // As you enter in the IETF Registration Form,
             // First/Given name followed by Last/Family Name

Current Primary Affiliation: // typically what goes in the Company
                              // field in the IETF Registration Form

Email Address(es): // all email addresses used to Register for the
                    // past 5 IETF meetings
		   // Please designate a Preferred email address for
                    // contact if there is more than one email address

Telephone number:  // With country code (for confirmation if selected)

Please expect an email response from me within 3 business days stating
whether or not you are qualified.  If you do not receive a response in
this timeframe, please re-send your email with the tag "RESEND:" added
to the subject line.

If you are not yet sure you would like to volunteer, please consider
that Nomcom members play a very important role in shaping the
leadership of the IETF.  Ensuring the leadership of the IETF is fair
and balanced and comprised of those who can lead the IETF in the right
direction is an important responsibility that rests on the IETF
participants at large. Volunteering for the Nomcom is a good way of
contributing in that direction.

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 few days.

Thank you in advance for your participation.

Suresh Krishnan
Nomcom Chair 2011-2012
Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From mrex@sap.com  Fri Jun 24 11:27:23 2011
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 6406611E8137; Fri, 24 Jun 2011 11:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.665
X-Spam-Level: 
X-Spam-Status: No, score=-9.665 tagged_above=-999 required=5 tests=[AWL=0.584,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tnGPiER1E54n; Fri, 24 Jun 2011 11:27:22 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 68FB811E8134; Fri, 24 Jun 2011 11:27:22 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p5OIRF5B013773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 24 Jun 2011 20:27:20 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201106241827.p5OIRE1X027017@fs4113.wdf.sap.corp>
Subject: Re: Why ask for IETF Consensus on a WG document?
To: d3e3e3@gmail.com (Donald Eastlake)
Date: Fri, 24 Jun 2011 20:27:14 +0200 (MEST)
In-Reply-To: <BANLkTim9ECfr5e43x22OwYHo9KS=G09LGA@mail.gmail.com> from "Donald Eastlake" at Jun 24, 11 10:46:11 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 18:27:23 -0000

Donald Eastlake wrote:
> 
> If polls at area meetings with 100+ people at them at three successive
> IETF meetings on different continents consistently show, say, a 3 to 1
> preference for some proposal but the IETF Last call email has 6 people
> speaking against and only 4 in favor, what do you think the right
> judgement would be as to the consensus of the IETF community?

That is completely missing the point of the IETF consensus process.

If there is just one single person that objects during LC, but
raises 10 different issues, then it is totally irrelavant how many
there are that are in favour.  Raised issues have to be processed with the
issue resolution process, i.e. drilldown (probably during discussion)
into pure matters of taste (where a significant majority decision is OK),
procedural issues (which strongly need to be resolved) and technical
issues that need to be either resolved or determined&declared to be
out-of-scope (or documented that no practical solution is known to
exists but the proposal/document is useful in spite of that).


>
> course, I'm not saying that's what happened hear. But a narrow rules
> that the IESG is required to put on blinders and only consider the
> IETF discussion list IETF Last Call email, ignoring previous
> discussions on other relevant IETF mailing lists and ignoring WG,
> area, and IETF plenary meeting discussions they have attended, is just
> arbitrary nonsense.

There is no problem with pointing to the resolution of previously
resolved issues in the WG issue tracker or WG / Document summary
for issued raised during IETF LC that aren't new -- provided that
the issue was actually resolved (rather than the objection withdrawn).


The number of documents produced in the IETF and looking for IESG
approval is huge, so we can only expect a small number of ADs to
have actually read the document and followed the discussion.

But in order to make the IESG decision process work _despite_ the
resource starvation, it is at least necessary for the responsible AD
to create a detailed IESG write-up of the Last Call listing all
issues that were raised including URLs or other suitable references
_to_the_original_messages_ that raised significant or controversial
issues and significant messages of the followup discussion,
for there to be a resource-conservative independent judgement
on the _original_ issues, the _original_ discussion and the proposed
resolution by the responsible AD, document sheperd and document
author/editor.

Yes, I know that this is currently not easy for the one doing
the write-up.  Maybe this could be simplified by the IETF Mailing
List exploder to _first_ put a message in the mailing list archive,
obtain a URL into the archive for it and then send out the message
_with_ that URL of the archived message out to the mailing list recipients.


-Martin

From julian.reschke@gmx.de  Fri Jun 24 11:34:32 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93B8C11E8084 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 11:34:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.377
X-Spam-Level: 
X-Spam-Status: No, score=-103.377 tagged_above=-999 required=5 tests=[AWL=-0.777, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eWupus0wQ3y5 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 11:34:32 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 8642911E813D for <ietf@ietf.org>; Fri, 24 Jun 2011 11:34:31 -0700 (PDT)
Received: (qmail invoked by alias); 24 Jun 2011 18:34:29 -0000
Received: from p508FCC29.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.204.41] by mail.gmx.net (mp045) with SMTP; 24 Jun 2011 20:34:29 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/3/1ox2Ev3r5t1vawKjIFqLYqjwo0BWiTu34y2CX G9id86osV7C1iZ
Message-ID: <4E04D8AC.6050503@gmx.de>
Date: Fri, 24 Jun 2011 20:34:20 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <201106241827.p5OIRE1X027017@fs4113.wdf.sap.corp>
In-Reply-To: <201106241827.p5OIRE1X027017@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 24 Jun 2011 18:34:32 -0000

On 2011-06-24 20:27, Martin Rex wrote:
> ...
> Yes, I know that this is currently not easy for the one doing
> the write-up.  Maybe this could be simplified by the IETF Mailing
> List exploder to _first_ put a message in the mailing list archive,
> obtain a URL into the archive for it and then send out the message
> _with_ that URL of the archived message out to the mailing list recipients.
> ...

X-Archived-At?

Best regards, Julian

From julian.reschke@gmx.de  Fri Jun 24 11:51:13 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 316B811E8193 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 11:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.339
X-Spam-Level: 
X-Spam-Status: No, score=-103.339 tagged_above=-999 required=5 tests=[AWL=-0.740, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RnWmybY6D8oa for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 11:51:12 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 3360911E818E for <ietf@ietf.org>; Fri, 24 Jun 2011 11:51:11 -0700 (PDT)
Received: (qmail invoked by alias); 24 Jun 2011 18:51:08 -0000
Received: from p508FCC29.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.204.41] by mail.gmx.net (mp023) with SMTP; 24 Jun 2011 20:51:08 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+iIh1/K7KiGi3OxzzY6ei05/XZNKjvqqTWINQxLh /7IV+IEU+BlmXA
Message-ID: <4E04DC96.2080306@gmx.de>
Date: Fri, 24 Jun 2011 20:51:02 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: RFC production center XML format usage, was: [IAOC] xml2rfc and legal	services RFPs
References: <E23665735D529B2C8CC3A393@PST.JCK.COM>, <54C48986-B211-462C-B942-247886122AF2@gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14DA@DC-US1MBEX4.global.avaya.com>, <69EC0EF3-E8CB-473C-9F43-B29CD1C5F800@vigilsec.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14DD@DC-US1MBEX4.global.avaya.com>	<708DE35B-FCE3-4D64-B780-48C8820D5360@vigilsec.com>	<4D63E136.5070805@dcrocker.net>	<95586EBA-DB21-4D1F-A271-776C6FE4D27B@vigilsec.com>	<4D64D78C.5080500@gmx.de> <4D64DCF2.3060004@gmx.de>
In-Reply-To: <4D64DCF2.3060004@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 18:51:13 -0000

On 2011-02-23 11:09, Julian Reschke wrote:
> ...
> I just realized that I have an archive of XML versions of RFCs in AUTH48
> state; so I *can* report the percentage of XML versions since ~RFC5000.
>
> Note that these may be inaccurate (for instance, not all RFC numbers get
> assigned, right?); it just observes how much XML files ended up in AUTH48.
>
> Here are the numbers:
>
> RFC5000 - RFC5099: 41
> RFC5100 - RFC5199: 44
> RFC5200 - RFC5299: 47
> RFC5300 - RFC5399: 48
> RFC5400 - RFC5499: 64
> RFC5500 - RFC5599: 59
> RFC5600 - RFC5699: 58
> RFC5700 - RFC5799: 64
> RFC5800 - RFC5899: 63
> RFC5900 - RFC5999: 68
> RFC6000 - RFC6099: 69
> ...

Updated stats, just in time before the next meeting:

RFC5000 - RFC5099: 41
RFC5100 - RFC5199: 44
RFC5200 - RFC5299: 47
RFC5300 - RFC5399: 48
RFC5400 - RFC5499: 64
RFC5500 - RFC5599: 59
RFC5600 - RFC5699: 58
RFC5700 - RFC5799: 64
RFC5800 - RFC5899: 63
RFC5900 - RFC5999: 68
RFC6000 - RFC6099: 70
RFC6100 - RFC6199: 56
RFC6200 - RFC6299: 77

...so a drop in 6100..6199 (I wonder why?) and a all-time high in 
6200..6299.

Best regards,

Julian

From jnc@mercury.lcs.mit.edu  Fri Jun 24 11:53:45 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 088C011E81B3; Fri, 24 Jun 2011 11:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.569
X-Spam-Level: 
X-Spam-Status: No, score=-6.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FkQ4b1dsnPoH; Fri, 24 Jun 2011 11:53:44 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 6FFB111E818E; Fri, 24 Jun 2011 11:53:41 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id A155518C116; Fri, 24 Jun 2011 14:53:40 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Why ask for IETF Consensus on a WG document?
Message-Id: <20110624185340.A155518C116@mercury.lcs.mit.edu>
Date: Fri, 24 Jun 2011 14:53:40 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: iesg@ietf.org, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 18:53:45 -0000

    > From: Brian E Carpenter <brian.e.carpenter@gmail.com>

    > I suspect that operators are *severely* under-represented on this
    > list (ietf@ietf.org) because it is very noisy and operators have
    > other priorities.

Ah, operators. This would be the same group of people of whom, if the
recent anecdotal reports are much to go on, many (most?) are not bothering
to deploy IPv6 at all?

(Something which would seem to be very common among smaller operators,
whom one assumes, in typical long-tail fashion, form the majority of the
group.)

But their views are paramount?

I see.

	Noel

From mrex@sap.com  Fri Jun 24 11:55:32 2011
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 806C011E818E for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 11:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.708
X-Spam-Level: 
X-Spam-Status: No, score=-9.708 tagged_above=-999 required=5 tests=[AWL=0.541,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BQ+qh3fdfnN3 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 11:55:32 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id A5AB611E80C6 for <ietf@ietf.org>; Fri, 24 Jun 2011 11:55:31 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p5OItTXg018165 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 24 Jun 2011 20:55:30 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201106241855.p5OItTku028631@fs4113.wdf.sap.corp>
Subject: Re: Why ask for IETF Consensus on a WG document?
To: julian.reschke@gmx.de (Julian Reschke)
Date: Fri, 24 Jun 2011 20:55:29 +0200 (MEST)
In-Reply-To: <4E04D8AC.6050503@gmx.de> from "Julian Reschke" at Jun 24, 11 08:34:20 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: 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: Fri, 24 Jun 2011 18:55:32 -0000

Julian Reschke wrote:
> 
> On 2011-06-24 20:27, Martin Rex wrote:
> > ...
> > Yes, I know that this is currently not easy for the one doing
> > the write-up.  Maybe this could be simplified by the IETF Mailing
> > List exploder to _first_ put a message in the mailing list archive,
> > obtain a URL into the archive for it and then send out the message
> > _with_ that URL of the archived message out to the mailing list recipients.
> > ...
> 
> X-Archived-At?

rather not there.

Considering the sheer number of header lines of the averager mailing
list email that hits my mailbox, and considering how difficult it is
to get that junkyard visualized in some MUAs, I personally would prefer
a modification of the automatically added message signature.

The IETF mailing list exploder already automatically tacks a signature to
every redistributed message with an indirect URL to the "haystack"
i.e. the URL for the mailing list subscription page that itself contains
an URL to the mailing list archive.

potential solutions:
  - add a 4th line identifying the needle in the haystack.

  (bandwith-conservative)
  - replace the current indirect URL to the haystack (3rd line) with the
    direct message URL (needle URL) and add a back-reference to the mailing
    list subscription page to the top of the message/needle
    visualization page.

-Martin

From julian.reschke@gmx.de  Fri Jun 24 12:01:02 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7AF411E81E7 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 12:01:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.306
X-Spam-Level: 
X-Spam-Status: No, score=-103.306 tagged_above=-999 required=5 tests=[AWL=-0.707, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tyire0HMe8hs for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 12:01:02 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 3AB8B11E8219 for <ietf@ietf.org>; Fri, 24 Jun 2011 12:00:22 -0700 (PDT)
Received: (qmail invoked by alias); 24 Jun 2011 19:00:18 -0000
Received: from p508FCC29.dip.t-dialin.net (EHLO [192.168.178.36]) [80.143.204.41] by mail.gmx.net (mp011) with SMTP; 24 Jun 2011 21:00:18 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/GgOJ/CR/GKA3JzDoMB7t7A6z8V2U8gwGyuOQqNx A2X0/JgWu5+xoR
Message-ID: <4E04DEB9.4050905@gmx.de>
Date: Fri, 24 Jun 2011 21:00:09 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <201106241855.p5OItTku028631@fs4113.wdf.sap.corp>
In-Reply-To: <201106241855.p5OItTku028631@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 24 Jun 2011 19:01:02 -0000

On 2011-06-24 20:55, Martin Rex wrote:
> Julian Reschke wrote:
>>
>> On 2011-06-24 20:27, Martin Rex wrote:
>>> ...
>>> Yes, I know that this is currently not easy for the one doing
>>> the write-up.  Maybe this could be simplified by the IETF Mailing
>>> List exploder to _first_ put a message in the mailing list archive,
>>> obtain a URL into the archive for it and then send out the message
>>> _with_ that URL of the archived message out to the mailing list recipients.
>>> ...
>>
>> X-Archived-At?
>
> rather not there.
>
> Considering the sheer number of header lines of the averager mailing
> list email that hits my mailbox, and considering how difficult it is
> to get that junkyard visualized in some MUAs, I personally would prefer
> a modification of the automatically added message signature.
>
> The IETF mailing list exploder already automatically tacks a signature to
> every redistributed message with an indirect URL to the "haystack"
> i.e. the URL for the mailing list subscription page that itself contains
> an URL to the mailing list archive.
>
> potential solutions:
>    - add a 4th line identifying the needle in the haystack.
>
>    (bandwith-conservative)
>    - replace the current indirect URL to the haystack (3rd line) with the
>      direct message URL (needle URL) and add a back-reference to the mailing
>      list subscription page to the top of the message/needle
>      visualization page.

WFM.

Or make the archive URI a predictable function of the message ID, just 
like the W3C mailing list servers do.

Best regards, Julian

From d3e3e3@gmail.com  Fri Jun 24 12:11:47 2011
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 CADE311E8116; Fri, 24 Jun 2011 12:11:47 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sxiK10fWGy+k; Fri, 24 Jun 2011 12:11:47 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8C08811E8088; Fri, 24 Jun 2011 12:11:46 -0700 (PDT)
Received: by yxp4 with SMTP id 4so1366372yxp.31 for <multiple recipients>; Fri, 24 Jun 2011 12:11:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=z9L5YsvnfArBfNitE7IXvDzvEN1HCKa5LGPisg7FilU=; b=C8Gln0K7GGs7/5Wweh86rIoml+Zg5fe0ruIwhBZAmr43W2z52xQbU8RR9aNM639T1F W6eSA7nvYFfPxDJHfjs12aAjhaJVjVpZl4rTiAEYqXQWgMGoWHdfyszJRjUqdxxi9VfQ nqXCBMdehDVKNFoGIuqRksemJEIO5JUd2gBSc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=VGNy8SxyMpiiDviX/dqy/Myrks3CLNbed7u9+vp8YkZ9QGYbkKx67ywxv6KUx/Uk+7 RN+2w8Xz5wzAEm72FWaoISvtk3zhPzQEZRqYUENtuMWZND+8P8y3NRqWiVhhA4W9TWDx GM2JouRCkU2ZTvgRl3QQNtj9iG0+0KeUDn4BY=
Received: by 10.151.5.5 with SMTP id h5mr4348284ybi.246.1308942706108; Fri, 24 Jun 2011 12:11:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.39.5 with HTTP; Fri, 24 Jun 2011 12:11:26 -0700 (PDT)
In-Reply-To: <201106241827.p5OIRE1X027017@fs4113.wdf.sap.corp>
References: <BANLkTim9ECfr5e43x22OwYHo9KS=G09LGA@mail.gmail.com> <201106241827.p5OIRE1X027017@fs4113.wdf.sap.corp>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 24 Jun 2011 15:11:26 -0400
Message-ID: <BANLkTinVp_C3VdjoiM4uJbKDjwzQhVze=A@mail.gmail.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
To: mrex@sap.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 19:11:48 -0000

Hi Martin,

On Fri, Jun 24, 2011 at 2:27 PM, Martin Rex <mrex@sap.com> wrote:
> Donald Eastlake wrote:
>>
>> If polls at area meetings with 100+ people at them at three successive
>> IETF meetings on different continents consistently show, say, a 3 to 1
>> preference for some proposal but the IETF Last call email has 6 people
>> speaking against and only 4 in favor, what do you think the right
>> judgement would be as to the consensus of the IETF community?
>
> That is completely missing the point of the IETF consensus process.

Sometimes it does and sometimes it doesn't. It depends, as you state
below, on the type of issue or issues that are being discussed. I
should have stated that it was something like deciding between two
methods of accomplishing the same technical goal where neutral
observers do not think there is a big difference in the technical
effectiveness of the methods, or something like.

> If there is just one single person that objects during LC, but
> raises 10 different issues, then it is totally irrelavant how many
> there are that are in favour.

But then you go on, below, to say that the number of supporters really
is the most relevant thing if it turns out to be issues of taste...

> Raised issues have to be processed with the
> issue resolution process, i.e. drilldown (probably during discussion)
> into pure matters of taste (where a significant majority decision is OK),
> procedural issues (which strongly need to be resolved) and technical
> issues that need to be either resolved or determined&declared to be
> out-of-scope (or documented that no practical solution is known to
> exists but the proposal/document is useful in spite of that).

So it really depends on the circumstances.

>...
>
> -Martin

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street
=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

From cb.list6@gmail.com  Fri Jun 24 12:15:43 2011
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 D9C7B22800E; Fri, 24 Jun 2011 12:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.462
X-Spam-Level: 
X-Spam-Status: No, score=-3.462 tagged_above=-999 required=5 tests=[AWL=0.137,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id azqjPKU-cNjp; Fri, 24 Jun 2011 12:15:42 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 74665228006; Fri, 24 Jun 2011 12:15:42 -0700 (PDT)
Received: by wwe5 with SMTP id 5so2133205wwe.13 for <multiple recipients>; Fri, 24 Jun 2011 12:15:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=r0Te2NWjyE/OcqQbxWy3eMIp5+5+E0sNkKTxVE+ITDg=; b=RwEPDI0Y9gUWgeKTsTMM13DpJC6A803DGaDt0xvPXxMCramA9R/z0tbpVlzg4FcQt+ dgnag+f7YQqAhTr9mWXgSXZ6rqfIbcwDtMlTS8929tQb9GY7C/lLxA4nWIEKlxuMqfFL 71vmLqFYooUIY6dlVIAWkEFWwxrYmo+jxHvEU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=n2PJbE+R0+0czFRktkdK5LtQaOaxSaiZ40xs3Bn8mwTBR4SIE9iU55pQEAH0jJCkEg /vSggwhtb1XFQolO3uyy2+GbZWInGpSXDjMJO1g0jb1gm1HLssVQhdMJPKjgowmunNRi tuYUU8YBcWC/IRkkIsRZFt/XJ2Mp9FCA7d1/A=
MIME-Version: 1.0
Received: by 10.216.68.140 with SMTP id l12mr3226502wed.79.1308942941455; Fri, 24 Jun 2011 12:15:41 -0700 (PDT)
Received: by 10.216.169.15 with HTTP; Fri, 24 Jun 2011 12:15:41 -0700 (PDT)
In-Reply-To: <20110624185340.A155518C116@mercury.lcs.mit.edu>
References: <20110624185340.A155518C116@mercury.lcs.mit.edu>
Date: Fri, 24 Jun 2011 12:15:41 -0700
Message-ID: <BANLkTimF2G-8KG+uptcEFxPQ-Brbr7siDdV_mAhOJROtrR_WFA@mail.gmail.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
From: Cameron Byrne <cb.list6@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 19:15:44 -0000

On Fri, Jun 24, 2011 at 11:53 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wr=
ote:
> =A0 =A0> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>
> =A0 =A0> I suspect that operators are *severely* under-represented on thi=
s
> =A0 =A0> list (ietf@ietf.org) because it is very noisy and operators have
> =A0 =A0> other priorities.
>

Yes, and this thread is noise.  In fact, Noel comments are
specifically off-topic and should be a new thread which can get added
the old thread about 6to4.

> Ah, operators. This would be the same group of people of whom, if the
> recent anecdotal reports are much to go on, many (most?) are not botherin=
g
> to deploy IPv6 at all?
>

Which operator is not actively working on IPv6 projects *right now*?
Seriously, that old statement does not hold water today.

> (Something which would seem to be very common among smaller operators,
> whom one assumes, in typical long-tail fashion, form the majority of the
> group.)
>
> But their views are paramount?
>
> I see.
>

Not taking the bait.  Let's move.

> =A0 =A0 =A0 =A0Noel
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From moore@network-heretics.com  Fri Jun 24 12:36:25 2011
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 43E1011E81A8; Fri, 24 Jun 2011 12:36:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.41
X-Spam-Level: 
X-Spam-Status: No, score=-3.41 tagged_above=-999 required=5 tests=[AWL=0.189,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z4YaOLNtbVbv; Fri, 24 Jun 2011 12:36:24 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 1FFCC11E8114; Fri, 24 Jun 2011 12:36:24 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id AEB7320544; Fri, 24 Jun 2011 15:36:23 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Fri, 24 Jun 2011 15:36:23 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=ImCGtx1Yt+Ok02liren2frxyI14=; b=mOINxDs4cQRzN9xjcUqEiTBpfUzf+Lgx3LvMfMbz28zPxTnS/9u7P+lvhjYAX/j7Kw6GPEu5qKVpDnphTnN/w+3NJRCVOmU9MXiHL2u45fd30tomKoOwF7yEhkRI8Fks/UEyxr9mwaaD1IhBJ5BCqtP32TymWdw6XSwuHQsNZaw=
X-Sasl-enc: YJ8xImcw62wdK1De69wcdKUjP1qKwZAYPYuTmwqD5MAV 1308944183
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id C1A28406C4A; Fri, 24 Jun 2011 15:36:22 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <BANLkTimF2G-8KG+uptcEFxPQ-Brbr7siDdV_mAhOJROtrR_WFA@mail.gmail.com>
Date: Fri, 24 Jun 2011 15:36:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F73DDC06-A6B7-4817-A77F-3F26808C9441@network-heretics.com>
References: <20110624185340.A155518C116@mercury.lcs.mit.edu> <BANLkTimF2G-8KG+uptcEFxPQ-Brbr7siDdV_mAhOJROtrR_WFA@mail.gmail.com>
To: Cameron Byrne <cb.list6@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: iesg@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2011 19:36:25 -0000

On Jun 24, 2011, at 3:15 PM, Cameron Byrne wrote:

> Which operator is not actively working on IPv6 projects *right now*?
> Seriously, that old statement does not hold water today.

Perhaps you missed the "one data point" thread from a few days ago.  It =
appears that a great many ISPs aren't working on supporting IPv6 yet.

Seriously, the idea that we can wait for ISPs to deploy IPv6 the way =
they like it, before anyone actually uses it to a significant degree, is =
what doesn't hold water.  That kind of attitude will keep widespread =
deployment of IPv6 perpetually 5-10 years away.

Keith


From dougb@dougbarton.us  Fri Jun 24 12:58:03 2011
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 2DB8711E8212 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 12:58:03 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z6vAd4R9+EMX for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 12:58:01 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 61FE111E81BE for <ietf@ietf.org>; Fri, 24 Jun 2011 12:58:01 -0700 (PDT)
Received: (qmail 3062 invoked by uid 399); 24 Jun 2011 19:57:53 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 24 Jun 2011 19:57:53 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E04EC3F.9080207@dougbarton.us>
Date: Fri, 24 Jun 2011 12:57:51 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110429 Thunderbird/3.1.10
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]>
In-Reply-To: <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, IETF-Discussion list <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: Fri, 24 Jun 2011 19:58:03 -0000

On 06/24/2011 09:08, John C Klensin wrote:
>
>
> --On Friday, 24 June, 2011 13:34 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com>  wrote:
>
>> ...
>> I think that's about right. There were several strong and very
>> raional opinions against this, including some who were not
>> involved in the similarly rough consensus in the WG
>> discussion. But (speaking as a co-author of one of the drafts
>> being historicised) I'd say the balance of opinion was to
>> publish. However, it's a close call.
>
> Brian,
>
> I see another problem here that, IMO, is complementary to the
> issue that Paul raises and enough independent of that issue that
> one could agree that the consensus determination was reasonable
> but still wrong (I don't concede the first, but want to look at
> the second).
>
> I've never assumed that the LC process is a binary one, with the
> only possible answers being "approve as written" or "complete
> trash".  It is a call for comments, not an approval vote.   The
> IESG clearly recognizes the distinction, although usually in
> minor ways -- tuning of documents after IETF LC or IESG reviews
> is almost certainly the norm rather than the exception and that
> tuning is sometimes fairly significant.
>
> In this case, it would not be hard to convince me that there was
> pretty good IETF consensus that an unrestricted recommendation
> for using 6to4 was appropriate.  Even most of 6to4's strongest
> advocates seem to agree that using it in stupid and naive ways
> leads to bad outcomes.  But consensus on that subject is not
> consensus that moving the whole business to Historic is a good
> idea.

I haven't seen those 2 ideas conflated anywhere, but it's not impossible 
that I've missed something.

> To paraphrase at least one comment, there is danger of
> throwing the baby (and perhaps some of the plumbing fixtures)
> away with the bath water.
>
> What I saw was what appeared to me to be some fairly strong
> arguments for looking at the problem in a different way -- a way
> that I've seen no evidence the WG considered at all.   That
> would be to explore alternatives to the rather blunt instrument
> of making a protocol specification historic: explaining what
> needs to be done to get it right (your document does a lot of
> that) and then figuring out ways to warn against the uses and
> configurations that we all (or mostly) agree are bad news.

By "your document" above are you referring to Brian's 
http://tools.ietf.org/html/draft-ietf-v6ops-6to4-advisory ? If so I 
would argue that the extensive WG discussion about both documents meets 
your criteria. Taken together the 2 documents represent a series of 
compromises between those of us whose opinion is "Kill 6to4 dead, 
yesterday" and those who would like to give it as graceful an exit as 
possible. The "historic" document points out the reasons that doing it 
at all is probably a bad idea, and asks that it be off by default; while 
the "advisory" document tells people that want to to do it anyway how to 
do it right. Personally I was very satisfied with both products of the 
WG and taken as a whole I think they describe a very rational approach.

I would also encourage anyone who has strong opinions about the topic to 
read the WG archives for discussion of both drafts. It was wide-ranging 
and, I believe, thorough. I briefly considered summarizing the high 
points in this message, but my fear is that it would simply re-open 
debate on topics already covered more adequately in the WG archives.


hth,

Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From dougb@dougbarton.us  Fri Jun 24 13:05:59 2011
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 3F38621F84A1 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 13:05:59 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ky8LEpL99UXq for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 13:05:58 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 4726521F849F for <ietf@ietf.org>; Fri, 24 Jun 2011 13:05:58 -0700 (PDT)
Received: (qmail 13974 invoked by uid 399); 24 Jun 2011 20:05:52 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 24 Jun 2011 20:05:52 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E04EE1E.9070907@dougbarton.us>
Date: Fri, 24 Jun 2011 13:05:50 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110429 Thunderbird/3.1.10
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im> <1485FF3E-0A3E-40C0-A785-775C9BCE7B73@network-heretics.com>
In-Reply-To: <1485FF3E-0A3E-40C0-A785-775C9BCE7B73@network-heretics.com>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg@ietf.org>, IETF-Discussion list <ietf@ietf.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: Fri, 24 Jun 2011 20:05:59 -0000

On 06/24/2011 04:35, Keith Moore wrote:
> I often get the impression that dissenters are dismissed as "in the rough" and that their opinions, no matter how well expressed, are given less weight than those who are in favor.

One could also consider the idea that due to the very human tendency 
towards confirmation bias that those who dissent often view that 
dissenting opinion as both more important and more popular than a more 
objective observer would.

One of the reasons that I believe this document actually does achieve at 
least rough consensus is that in the course of the WG discussion 
something was achieved that at least in my experience is quite rare in 
the IETF, some people actually changed their opinions as a result of the 
discussion. To me that indicates that the concepts discussed were 
carefully considered (the concerns raised in the IETF LC being a subset 
of those discussed in the WG) and ultimately the right decision was 
reached. Of course, it could also be argued that I'm suffering from 
confirmation bias since I agree with the decisions reached, as far as 
they go.


hth,

Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From moore@network-heretics.com  Fri Jun 24 13:11:43 2011
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 83B6C21F84FA; Fri, 24 Jun 2011 13:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.113
X-Spam-Level: 
X-Spam-Status: No, score=-3.113 tagged_above=-999 required=5 tests=[AWL=-0.115, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aMu7QgXxJhbC; Fri, 24 Jun 2011 13:11:37 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 672BF21F8500; Fri, 24 Jun 2011 13:11:37 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id CCFED2040F; Fri, 24 Jun 2011 16:11:36 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Fri, 24 Jun 2011 16:11:36 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=I0uOHzGN1eO5R85yi/C1OUE8jUc=; b=UYtQTEgXJ+wIp5Rs8BIipJ8yiw+KEfQLRi9vPog1/xLQPBUm/a47luleF2/Nrx9zmHkjL2lY1NgbNxX4SZu3ld4uil5NHV0E9S9DQkUON09WzBnY75LbTKxJktgfoQMeptdwsTyO59Pwy6mUCkCoggBr84qLJNh178I8W2zUXLc=
X-Sasl-enc: yYP7e4i7DGA4zbmWGjOXjxYV9C4XR5n1FqjkBrpOmi5c 1308946295
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 37173406B49; Fri, 24 Jun 2011 16:11:33 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-47--73392619
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E04EC3F.9080207@dougbarton.us>
Date: Fri, 24 Jun 2011 16:11:29 -0400
Message-Id: <FBA6D753-531D-4918-B5B1-FB63ED64E288@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]> <4E04EC3F.9080207@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1084)
Cc: John C Klensin <john-ietf@jck.com>, The IESG <iesg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.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, 24 Jun 2011 20:11:43 -0000

--Apple-Mail-47--73392619
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 24, 2011, at 3:57 PM, Doug Barton wrote:

> By "your document" above are you referring to Brian's =
http://tools.ietf.org/html/draft-ietf-v6ops-6to4-advisory ? If so I =
would argue that the extensive WG discussion about both documents meets =
your criteria. Taken together the 2 documents represent a series of =
compromises between those of us whose opinion is "Kill 6to4 dead, =
yesterday" and those who would like to give it as graceful an exit as =
possible.=20

Taken together, the message is confusing.=20

And for those of you whose opinion is "KIll 6to4 dead, yesterday" - =
that's way beyond the scope of what v6ops was chartered to do.

Keith


--Apple-Mail-47--73392619
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 24, 2011, at 3:57 PM, Doug Barton wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-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; ">By "your =
document" above are you referring to Brian's<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://tools.ietf.org/html/draft-ietf-v6ops-6to4-advisory">http://=
tools.ietf.org/html/draft-ietf-v6ops-6to4-advisory</a><span =
class=3D"Apple-converted-space">&nbsp;</span>? If so I would argue that =
the extensive WG discussion about both documents meets your criteria. =
Taken together the 2 documents represent a series of compromises between =
those of us whose opinion is "Kill 6to4 dead, yesterday" and those who =
would like to give it as graceful an exit as possible.<span =
class=3D"Apple-converted-space">&nbsp;</span></span></blockquote></div><br=
><div>Taken together, the message is =
confusing.&nbsp;</div><div><br></div><div>And for those of you whose =
opinion is "KIll 6to4 dead, yesterday" - that's way beyond the scope of =
what v6ops was chartered to =
do.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-47--73392619--

From moore@network-heretics.com  Fri Jun 24 13:14:16 2011
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 2297321F8525; Fri, 24 Jun 2011 13:14:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.111
X-Spam-Level: 
X-Spam-Status: No, score=-3.111 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fJaYqsFG3GHN; Fri, 24 Jun 2011 13:14:15 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 0AF3A21F8543; Fri, 24 Jun 2011 13:14:08 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id ACE7B20BA5; Fri, 24 Jun 2011 16:14:07 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Fri, 24 Jun 2011 16:14:07 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=ShJkJ+3Y2ODgzznJ2q/PsmKZGBE=; b=BDE8I8fRoZEFe+AF8fM/f/4Z1FVoAPpWFXzBRs8v7LMXjiFo8K5pKu3bEYUOtF2ZGAVS61ZUdI6+ub+IgF0Vb/qFPQgYTKKJYOdXlTk9mEroxPTjT37eIcFiDhjz/tL5H8CFwavHeBNsPQkXqGzN2ANYDAtU7/X+pgh+XxVrOgg=
X-Sasl-enc: 4u/4rIEJrMGumv4oLhHzppBgfZLgdnEV0/c2y7KijFqs 1308946446
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 69762405F4A; Fri, 24 Jun 2011 16:14:06 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-48--73238994
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E04EE1E.9070907@dougbarton.us>
Date: Fri, 24 Jun 2011 16:14:02 -0400
Message-Id: <FEA5B9A8-0B3C-46AC-9B44-F6EA014443D9@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im> <1485FF3E-0A3E-40C0-A785-775C9BCE7B73@network-heretics.com> <4E04EE1E.9070907@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1084)
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, 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: Fri, 24 Jun 2011 20:14:16 -0000

--Apple-Mail-48--73238994
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 24, 2011, at 4:05 PM, Doug Barton wrote:

> On 06/24/2011 04:35, Keith Moore wrote:
>> I often get the impression that dissenters are dismissed as "in the =
rough" and that their opinions, no matter how well expressed, are given =
less weight than those who are in favor.
>=20
> One could also consider the idea that due to the very human tendency =
towards confirmation bias that those who dissent often view that =
dissenting opinion as both more important and more popular than a more =
objective observer would.
>=20
> One of the reasons that I believe this document actually does achieve =
at least rough consensus is that in the course of the WG discussion =
something was achieved that at least in my experience is quite rare in =
the IETF, some people actually changed their opinions as a result of the =
discussion. To me that indicates that the concepts discussed were =
carefully considered (the concerns raised in the IETF LC being a subset =
of those discussed in the WG) and ultimately the right decision was =
reached. Of course, it could also be argued that I'm suffering from =
confirmation bias since I agree with the decisions reached, as far as =
they go.

I've been reviewing the WGLC comments.  I haven't finished doing so yet, =
but so far my impression is that the discussion was both thorough and =
well-organized.

Of course, consensus within v6ops is not the same thing as =
community-wide consensus, and the latter is what is required for a =
standards action.

Keith


--Apple-Mail-48--73238994
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Jun 24, 2011, at 4:05 PM, Doug Barton wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
06/24/2011 04:35, Keith Moore wrote:<br><blockquote type=3D"cite">I =
often get the impression that dissenters are dismissed as "in the rough" =
and that their opinions, no matter how well expressed, are given less =
weight than those who are in favor.<br></blockquote><br>One could also =
consider the idea that due to the very human tendency towards =
confirmation bias that those who dissent often view that dissenting =
opinion as both more important and more popular than a more objective =
observer would.<br><br>One of the reasons that I believe this document =
actually does achieve at least rough consensus is that in the course of =
the WG discussion something was achieved that at least in my experience =
is quite rare in the IETF, some people actually changed their opinions =
as a result of the discussion. To me that indicates that the concepts =
discussed were carefully considered (the concerns raised in the IETF LC =
being a subset of those discussed in the WG) and ultimately the right =
decision was reached. Of course, it could also be argued that I'm =
suffering from confirmation bias since I agree with the decisions =
reached, as far as they go.<font class=3D"Apple-style-span" =
color=3D"#000000"><font class=3D"Apple-style-span" =
color=3D"#144FAE"><br></font></font></div></blockquote><br></div><div>I've=
 been reviewing the WGLC comments. &nbsp;I haven't finished doing so =
yet, but so far my impression is that the discussion was both thorough =
and well-organized.</div><div><br></div><div>Of course, consensus within =
v6ops is not the same thing as community-wide consensus, and the latter =
is what is required for a standards =
action.</div><div><br></div><div>Keith</div><div><br></div></body></html>=

--Apple-Mail-48--73238994--

From john@jlc.net  Fri Jun 24 13:17:54 2011
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 A85EE21F85B3 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 13:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.125
X-Spam-Level: 
X-Spam-Status: No, score=-106.125 tagged_above=-999 required=5 tests=[AWL=0.474, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2gGvyEwhEdii for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 13:17:53 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id CD76221F85B2 for <ietf@ietf.org>; Fri, 24 Jun 2011 13:17:53 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 95FD733C22; Fri, 24 Jun 2011 16:17:53 -0400 (EDT)
Date: Fri, 24 Jun 2011 16:17:53 -0400
From: John Leslie <john@jlc.net>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Why ask for IETF Consensus on a WG document?
Message-ID: <20110624201753.GB56541@verdi>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org> <4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <20110624125522.GD76722@verdi> <F965C40C-1B96-4590-A05E-7988EBAB51F6@vpnc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F965C40C-1B96-4590-A05E-7988EBAB51F6@vpnc.org>
User-Agent: Mutt/1.4.1i
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 Jun 2011 20:17:54 -0000

Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> On Jun 24, 2011, at 5:55 AM, John Leslie wrote:
> 
>> First, note the Subject line: an IETF Last-Call on a Working Group
>> document _isn't_ asking for IETF Consensus: it's simply a last-call for
>> comments on an action proposed by a Working Group.
> 
> I'm quite confused by this opinion. *No* IETF Last Call announcements,
> even those for standards track documents, say that they are to determine
> IETF consensus, yet IETF consensus is required for many of these
> documents.

   I cannot speak with any authority on this, but I can quote RFC 2026:
] 
] 4.2.2  Informational
] 
]  An "Informational" specification is published for the general
]  information of the Internet community, and does not represent an
]  Internet community consensus or recommendation.

   This seems pretty plain to me.

   As for Standards-track and BCP, I read RFC 2026 to call for "consensus
building", not "IETF consensus". YMMV.

> In your view, how are we to know which IETF Last Call announcements
> are to determine IETF consensus

   IMHO, essentially none of them. To quote RFC 2026:
] 
] 14. DEFINITIONS OF TERMS
]  Last-Call - A public comment period used to gage the level of
]     consensus about the reasonableness of a proposed standards action.
]     (see section 6.1.2)

   Section 6.1.2 is pretty long; I'll quote only one paragraph:
] 
]  The IESG will send notice to the IETF of the pending IESG
]  consideration of the document(s) to permit a final review by the
]  general Internet community.  This "Last-Call" notification shall be
]  via electronic mail to the IETF Announce mailing list.  Comments on a
]  Last-Call shall be accepted from anyone, and should be sent as
]  directed in the Last-Call announcement.

   I don't read that as requiring "IETF Consensus" to be determined:
merely that the "level of consensus" be considered -- strongly suggesting
that the IESG may approve something where the "level of consensus" falls
below "rough". (I do not intend to express any opinion whether they ever
do so.)

> and which are just to bring additional input to the IESG for a
> non-consensus decision?

   Clearly, RFC 2026 does not require any kind of consensus for Informational
documents.

   Perhaps less clearly, but IMHO, RFC 2026 does not require the IESG
to "determine" "IETF consensus" on Standards-track documents.

> Or are you saying that the IESG determines IETF consensus using metrics
> other than the discussion on ietf@?

   I have not said that. IMHO, the IESG procedures don't even attempt to
"determine IETF consensus" on the vast majority of documents. They attempt
to determine instead whether the document should be sent back for rework.

--
John Leslie <john@jlc.net>

From moore@network-heretics.com  Fri Jun 24 13:44:45 2011
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 36F7411E81B3 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 13:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.11
X-Spam-Level: 
X-Spam-Status: No, score=-3.11 tagged_above=-999 required=5 tests=[AWL=-0.111,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IrBuEUb82Q-b for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 13:44:44 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 0EC8C11E8144 for <ietf@ietf.org>; Fri, 24 Jun 2011 13:44:44 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id A7A7C20A20; Fri, 24 Jun 2011 16:44:43 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 24 Jun 2011 16:44:43 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=WBpZrfixJ+7u3SptoXDK1V58AEg=; b=Bf/JTKdi/TqXznCXzTaSIyvQqtGwKUzlog+V6zEGrCG1M9EBAJ/kYn8gJFQRV4LZM3iCdK8mdWWHfWnAzQUtfIlOKWHRQ3+veBvrGtk/j0YmqTeFNVS67U7Mk0Ppjh1N57a/Xs4uPFYWipVB6G8md+YeufLcnN5Oly1UnTrQF48=
X-Sasl-enc: pQ+j1TrRNNHhK0K4hUkI7asCGb9Sj5wDPqqhqOsdcF9y 1308948282
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 6F425406169; Fri, 24 Jun 2011 16:44:42 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20110624201753.GB56541@verdi>
Date: Fri, 24 Jun 2011 16:44:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F3C3541-D4D6-448E-B421-E4FBD6F28C97@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org> <4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <20110624125522.GD76722@verdi> <F965C40C-1B96-4590-A05E-7988EBAB51F6@vpnc.org> <20110624201753.GB56541@verdi>
To: John Leslie <john@jlc.net>
X-Mailer: Apple Mail (2.1084)
Cc: Paul Hoffman <paul.hoffman@vpnc.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, 24 Jun 2011 20:44:45 -0000

On Jun 24, 2011, at 4:17 PM, John Leslie wrote:

> Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>> On Jun 24, 2011, at 5:55 AM, John Leslie wrote:
>>=20
>>> First, note the Subject line: an IETF Last-Call on a Working Group
>>> document _isn't_ asking for IETF Consensus: it's simply a last-call =
for
>>> comments on an action proposed by a Working Group.
>>=20
>> I'm quite confused by this opinion. *No* IETF Last Call =
announcements,
>> even those for standards track documents, say that they are to =
determine
>> IETF consensus, yet IETF consensus is required for many of these
>> documents.
>=20
>   I cannot speak with any authority on this, but I can quote RFC 2026:
> ]=20
> ] 4.2.2  Informational
> ]=20
> ]  An "Informational" specification is published for the general
> ]  information of the Internet community, and does not represent an
> ]  Internet community consensus or recommendation.
>=20

Even if the document was to be labeled as informational, this was =
clearly a standards action. =20

>   This seems pretty plain to me.
>=20
>   As for Standards-track and BCP, I read RFC 2026 to call for =
"consensus
> building", not "IETF consensus". YMMV.

Yes, but that consensus that is called for is IETF-wide consensus.   If =
WG consensus were all that were were required, there would be no need =
for an IETF-wide Last Call.  And I can't tell that there's been any =
attempt at all by the v6ops group or the document authors to build =
IETF-wide consensus on this.

>> In your view, how are we to know which IETF Last Call announcements
>> are to determine IETF consensus
>=20
>   IMHO, essentially none of them. To quote RFC 2026:
> ]=20
> ] 14. DEFINITIONS OF TERMS
> ]  Last-Call - A public comment period used to gage the level of
> ]     consensus about the reasonableness of a proposed standards =
action.
> ]     (see section 6.1.2)
>=20
>   Section 6.1.2 is pretty long; I'll quote only one paragraph:
> ]=20
> ]  The IESG will send notice to the IETF of the pending IESG
> ]  consideration of the document(s) to permit a final review by the
> ]  general Internet community.  This "Last-Call" notification shall be
> ]  via electronic mail to the IETF Announce mailing list.  Comments on =
a
> ]  Last-Call shall be accepted from anyone, and should be sent as
> ]  directed in the Last-Call announcement.
>=20
>   I don't read that as requiring "IETF Consensus" to be determined:
> merely that the "level of consensus" be considered -- strongly =
suggesting
> that the IESG may approve something where the "level of consensus" =
falls
> below "rough". (I do not intend to express any opinion whether they =
ever
> do so.)

The stated purpose of Last Call is to "gage [sic] the level of =
consensus".  Of course, IESG does have an additional role beyond =
determining consensus.  e.g. It may also make judgments about the =
document's technical quality, whether a document meets the 2026 criteria =
for a particular status (e.g. "no known technical omissions" for =
Proposed), whether appropriate processes were followed by a WG, etc. =20

RFC 2026 does not explicitly state that community-wide consensus is =
required for standards action.  However it makes abundantly clear that =
community-wide consensus is the goal of everything in the process.  It =
also implies that lack of consensus is justification for appeal, and =
that the goal of the appeals process is to achieve consensus.

>   I have not said that. IMHO, the IESG procedures don't even attempt =
to
> "determine IETF consensus" on the vast majority of documents.  They =
attempt
> to determine instead whether the document should be sent back for =
rework.


In my experience, this was also true.  Consensus was not an issue for =
most documents that I saw while on IESG; technical quality was.    But =
it's also clear that IESG is supposed to evaluate Last Call comments to =
"gage" consensus.

Keith


From dougb@dougbarton.us  Fri Jun 24 13:45:57 2011
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 E815111E8210 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 13:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kspx5MCJRHdi for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 13:45:56 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 72D6D11E8212 for <ietf@ietf.org>; Fri, 24 Jun 2011 13:45:38 -0700 (PDT)
Received: (qmail 28091 invoked by uid 399); 24 Jun 2011 20:45:33 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 24 Jun 2011 20:45:33 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E04F76B.5040807@dougbarton.us>
Date: Fri, 24 Jun 2011 13:45:31 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110429 Thunderbird/3.1.10
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]> <4E04EC3F.9080207@dougbarton.us> <FBA6D753-531D-4918-B5B1-FB63ED64E288@network-heretics.com>
In-Reply-To: <FBA6D753-531D-4918-B5B1-FB63ED64E288@network-heretics.com>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, The IESG <iesg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.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, 24 Jun 2011 20:45:57 -0000

On 06/24/2011 13:11, Keith Moore wrote:
> On Jun 24, 2011, at 3:57 PM, Doug Barton wrote:
>
>> By "your document" above are you referring to
>> Brian'shttp://tools.ietf.org/html/draft-ietf-v6ops-6to4-advisory? If
>> so I would argue that the extensive WG discussion about both documents
>> meets your criteria. Taken together the 2 documents represent a series
>> of compromises between those of us whose opinion is "Kill 6to4 dead,
>> yesterday" and those who would like to give it as graceful an exit as
>> possible.
>
> Taken together, the message is confusing.

I'm not sure why you would think that. It fits in with a grand IETF 
tradition. :)

> And for those of you whose opinion is "KIll 6to4 dead, yesterday" -
> that's way beyond the scope of what v6ops was chartered to do.

ENONSEQUITUR



-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From dougb@dougbarton.us  Fri Jun 24 13:46:47 2011
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 DACB511E8184 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 13:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iGBSAw8sQBYV for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 13:46:47 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 1287311E8178 for <ietf@ietf.org>; Fri, 24 Jun 2011 13:46:47 -0700 (PDT)
Received: (qmail 29055 invoked by uid 399); 24 Jun 2011 20:46:45 -0000
Received: from unknown (HELO 65-241-43-4.globalsuite.net) (dougb@dougbarton.us@65.241.43.4) by mail2.fluidhosting.com with ESMTPAM; 24 Jun 2011 20:46:45 -0000
X-Originating-IP: 65.241.43.4
X-Sender: dougb@dougbarton.us
Message-ID: <4E04F7B4.9000602@dougbarton.us>
Date: Fri, 24 Jun 2011 13:46:44 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110429 Thunderbird/3.1.10
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im> <1485FF3E-0A3E-40C0-A785-775C9BCE7B73@network-heretics.com> <4E04EE1E.9070907@dougbarton.us> <FEA5B9A8-0B3C-46AC-9B44-F6EA014443D9@network-heretics.com>
In-Reply-To: <FEA5B9A8-0B3C-46AC-9B44-F6EA014443D9@network-heretics.com>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, 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: Fri, 24 Jun 2011 20:46:48 -0000

On 06/24/2011 13:14, Keith Moore wrote:
> On Jun 24, 2011, at 4:05 PM, Doug Barton wrote:
>
>> On 06/24/2011 04:35, Keith Moore wrote:
>>> I often get the impression that dissenters are dismissed as "in the
>>> rough" and that their opinions, no matter how well expressed, are
>>> given less weight than those who are in favor.
>>
>> One could also consider the idea that due to the very human tendency
>> towards confirmation bias that those who dissent often view that
>> dissenting opinion as both more important and more popular than a more
>> objective observer would.
>>
>> One of the reasons that I believe this document actually does achieve
>> at least rough consensus is that in the course of the WG discussion
>> something was achieved that at least in my experience is quite rare in
>> the IETF, some people actually changed their opinions as a result of
>> the discussion. To me that indicates that the concepts discussed were
>> carefully considered (the concerns raised in the IETF LC being a
>> subset of those discussed in the WG) and ultimately the right decision
>> was reached. Of course, it could also be argued that I'm suffering
>> from confirmation bias since I agree with the decisions reached, as
>> far as they go.
>
> I've been reviewing the WGLC comments. I haven't finished doing so yet,
> but so far my impression is that the discussion was both thorough and
> well-organized.

You might want to go further back in the archives than just the LC. 
There was quite a bit of discussion on both drafts.

> Of course, consensus within v6ops is not the same thing as
> community-wide consensus, and the latter is what is required for a
> standards action.

I'll leave that discussion to the process experts.


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From moore@network-heretics.com  Fri Jun 24 13:54:40 2011
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 3D54B11E820E; Fri, 24 Jun 2011 13:54:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[AWL=0.191,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id roT4-YOHhzWx; Fri, 24 Jun 2011 13:54:36 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 199FD11E8192; Fri, 24 Jun 2011 13:54:35 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8055B20C82; Fri, 24 Jun 2011 16:54:34 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 24 Jun 2011 16:54:34 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=xtBL+Bm6Zx+/0R4W9F3vUE+qvZM=; b=u0AdftvbG/YrwKcGuWaBW9VcyD6TaEsTBG3SStz/I313BxzCO5fGhKQVzYtHyOhpRimBpVZBJMYOTD+fokVzCbHVUmNBNQvPFW8z+rSYRdRFbHh901yZypYNU+2bZC4ODDzol4YX508qqyxgo2e06ExLDr+8WZxQAWw13aPJWAg=
X-Sasl-enc: j8R/9Uh/ZVlQlkRYCkgkIaJAKpGqMXn1/Cn9AF/lFBp9 1308948874
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 817394004E4; Fri, 24 Jun 2011 16:54:33 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E04F7B4.9000602@dougbarton.us>
Date: Fri, 24 Jun 2011 16:54:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA4216AA-8A32-4239-9A18-D840DF06F48F@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im> <1485FF3E-0A3E-40C0-A785-775C9BCE7B73@network-heretics.com> <4E04EE1E.9070907@dougbarton.us> <FEA5B9A8-0B3C-46AC-9B44-F6EA014443D9@network-heretics.com> <4E04F7B4.9000602@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1084)
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, 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: Fri, 24 Jun 2011 20:54:40 -0000

On Jun 24, 2011, at 4:46 PM, Doug Barton wrote:

>> I've been reviewing the WGLC comments. I haven't finished doing so =
yet,
>> but so far my impression is that the discussion was both thorough and
>> well-organized.
>=20
> You might want to go further back in the archives than just the LC. =
There was quite a bit of discussion on both drafts.

I've read some of it, and participated in some of the discussion for =
-advisory.    Though my immediate question has been whether the WG =
really had rough consensus, and I don't think the other WG discussion =
matters too much in gauging that.=20

Keith


From john-ietf@jck.com  Fri Jun 24 14:40:48 2011
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 B79B711E8111 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 14:40: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uIN9Tdyk-j1m for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 14:40:47 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 6180111E809E for <ietf@ietf.org>; Fri, 24 Jun 2011 14:40:47 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QaE7J-000AhB-Gv; Fri, 24 Jun 2011 17:40:45 -0400
Date: Fri, 24 Jun 2011 17:40:44 -0400
From: John C Klensin <john-ietf@jck.com>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: Why ask for IETF Consensus on a WG document?
Message-ID: <0243D1465C09BA6604141E22@[172.16.1.94]>
In-Reply-To: <4E04EC3F.9080207@dougbarton.us>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]> <4E04EC3F.9080207@dougbarton.us>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF-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 Jun 2011 21:40:48 -0000

--On Friday, 24 June, 2011 12:57 -0700 Doug Barton
<dougb@dougbarton.us> wrote:

>> What I saw was what appeared to me to be some fairly strong
>> arguments for looking at the problem in a different way -- a
>> way that I've seen no evidence the WG considered at all.
>> That would be to explore alternatives to the rather blunt
>> instrument of making a protocol specification historic:
>> explaining what needs to be done to get it right (your
>> document does a lot of that) and then figuring out ways to
>> warn against the uses and configurations that we all (or
>> mostly) agree are bad news.

> By "your document" above are you referring to Brian's
> http://tools.ietf.org/html/draft-ietf-v6ops-6to4-advisory ?

yes

> If
> so I would argue that the extensive WG discussion about both
> documents meets your criteria. Taken together the 2 documents
> represent a series of compromises between those of us whose
> opinion is "Kill 6to4 dead, yesterday" and those who would
> like to give it as graceful an exit as possible.

Doug,  you have just returned to the main point of Paul's
question.  Let me state it in a different way.  WGs who produce
drafts on a given issue tend to be made of folks who are heavily
concerned with that issue and who share similar perspectives on
it (that doesn't mean they agree on the answers, but they often
agree on the problem to be solved).   To even a much greater
degree than a decade or two ago, they also tend to be pretty
homogeneous (again, that doesn't mean they necessarily agree).
The reason we do IETF Last Calls is in order to bring community
perspective to bear, to consider things both cross-area and
cross-perspective and, if a WG has gotten over-focused on one
set of issues and ignored others, to create an opportunity to
bring the others out.

Now, the IESG gets to listen to all of those opinions, both WG
and non-WG, and say (in an extreme case) "the WG has engaged on
all the issues and has it right and the rest of the community,
no matter how numerous, doesn't have adequate understanding and
should be ignored".   This is supposed to be a process that
brings different technical perspectives out if they exist, not a
popularity contest.  I don't have any problem with that; I'm not
even clear that Paul does.

_However_ if something causes as much controversy as this did, I
think it is desirable for the IESG to be cautious in at least
two ways.   One is to examine whether it is worth sending the
draft back to the WG, saying "please review these points once
again and make sure you don't want to modify your
recommendation".   As far as I know, they did that... or
consulted with the WG leadership and concluded that the WG
position was sufficiently hardened that no amount of re-review
would make an difference.  Second, I think the IESG has some
implicit obligation to really document such a decision and the
reasons for it, not [just] to issue a Protocol Action notice
that can be easily construed the way several people on this list
have construed it, i.e., as "well the WG and the community input
disagreed, so screw the community".  

Personally, I don't believe that was the basis on which the IESG
made the decisions they made but, as is often the case in this
community, a little more explicitness and transparency about how
and why controversial decisions were made can head off a lot of
problems.

FWIW, if people actually believe that the IESG has gotten too
high-handed or dismissive of community input, I note that the
Nomcom Chair is looking for volunteers and will soon be looking
for input.

> The
> "historic" document points out the reasons that doing it at
> all is probably a bad idea, and asks that it be off by
> default; while the "advisory" document tells people that want
> to to do it anyway how to do it right. Personally I was very
> satisfied with both products of the WG and taken as a whole I
> think they describe a very rational approach.

And, if you will go back and read my comments on the subject,
you will find that I, personally, largely agree.  I just don't
think that adding "historic" to those pieces of advice will be
influential in accomplishing the goals, that it is a too-blunt
instrument, and its application in this sort of situation is
more likely to bring discredit on the IETF than to accomplish
the purpose for which its advocates are encouraging it.   I
believe I'm probably in the minority on that position and
recognize that I'm not likely to persuade anyone who isn't
persuaded already.  It certainly isn't the first time that has
happened and I have no particular problem with it.

But I do think that this is a situation in which a more nuanced
approach is appropriate (which is what my earlier note said) and
for more explanation from the IESG about the reasoning behind
their conclusion (which this one addresses).

I will now go back to lurking.

    john


From john-ietf@jck.com  Fri Jun 24 14:48:55 2011
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 52F0F21F84CC for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 14:48:55 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wRzyataWucM1 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 14:48:54 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id A75B721F84CB for <ietf@ietf.org>; Fri, 24 Jun 2011 14:48:54 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QaEF5-000AjX-LT; Fri, 24 Jun 2011 17:48:47 -0400
Date: Fri, 24 Jun 2011 17:48:46 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Leslie <john@jlc.net>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Why ask for IETF Consensus on a WG document?
Message-ID: <39EFBE60BFD088044F2DE951@[172.16.1.94]>
In-Reply-To: <20110624201753.GB56541@verdi>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org> <4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <20110624125522.GD76722@verdi> <F965C40C-1B96-4590-A05E-7988EBAB51F6@vpnc.org> <20110624201753.GB56541@verdi>
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, 24 Jun 2011 21:48:55 -0000

--On Friday, 24 June, 2011 16:17 -0400 John Leslie
<john@jlc.net> wrote:

>> and which are just to bring additional input to the IESG for a
>> non-consensus decision?
> 
>    Clearly, RFC 2026 does not require any kind of consensus
> for Informational documents.
>...

John,

A small nit...  While in this area as in many others, we've
never actually / formally updated 2026, things have evolved a
bit.  We've modified the RFC Editor model to include explicit
and separate streams, have added headers to indicate the stream
in which something is published, and have made provisions for
explicit statements about the level of consensus achieved.  IMO,
that is completely reasonable -- it is less important, IMO,
whether the IESG requires community consensus about a particular
document (regardless of whether it is Information, Full
Standard, or somewhere in between) than that they not
misrepresent the situation.

I don't quite see how that is relevant to this particular case,
either.

     john


From dhc2@dcrocker.net  Fri Jun 24 15:59:34 2011
Return-Path: <dhc2@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 9CF5411E810A for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 15:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rc90SWW8xDQn for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 15:59:33 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 72EFC11E80E1 for <ietf@ietf.org>; Fri, 24 Jun 2011 15:59:33 -0700 (PDT)
Received: from [192.168.1.42] (ppp-68-120-198-5.dsl.pltn13.pacbell.net [68.120.198.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p5OMxQGt010046 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Fri, 24 Jun 2011 15:59:32 -0700
Message-ID: <4E0516C8.7030404@dcrocker.net>
Date: Fri, 24 Jun 2011 15:59:20 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt>	(DomainKeys	Identified Mail (DKIM) Signatures) to Draft Standard
References: <20110623152458.19049.qmail@joyce.lan> <4E04CA58.8070201@mail-abuse.org>
In-Reply-To: <4E04CA58.8070201@mail-abuse.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.17]); Fri, 24 Jun 2011 15:59:32 -0700 (PDT)
Cc: DKIM IETF WG <ietf-dkim@mipassoc.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, 24 Jun 2011 22:59:34 -0000

On 6/24/2011 10:33 AM, Douglas Otis wrote:
> Complaints from John, Dave, and Barry and others is likely and understandably
> out of fatigue. They just want the process to be over. We are now hearing there
> is a vital protocol layering principle at stake which even precludes DKIM from
> making these checks! Really?


For those who weren't paying attention, I thought it worth noting that Doug has 
now devolved into an ad hominem line of attack, complete with proffered insight 
into the personal motivations driving 3 of us, absent any external signs to 
support that insight.

My own, actual, view is that a number of us have been considerably more than 
thorough in responding to Doug's entirely misguided campaign, within the DKIM 
working group, here on the IETF list, at the TrendLabs blog, at Circleid, and at 
the MAAWG Technical committee mailing list.

The decision to stop responding to the substance of his postings is merely 
because there is no new substance.  Absent any indication of his view gaining 
support, there's very obviously no benefit to be had in responding further.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From jhw@apple.com  Fri Jun 24 16:10:44 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F09321F84D9; Fri, 24 Jun 2011 16:10:19 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66uwRYdtgSvL; Fri, 24 Jun 2011 16:10:17 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 8379A21F84D7; Fri, 24 Jun 2011 16:10:17 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay11.apple.com ([17.128.113.48]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LNB00285HN00C12@mail-out.apple.com>; Fri, 24 Jun 2011 16:10:16 -0700 (PDT)
X-AuditID: 11807130-b7c45ae000001381-ff-4e05194a97de
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay11.apple.com (Apple SCV relay) with SMTP id 8C.D7.04993.A49150E4; Fri, 24 Jun 2011 16:10:02 -0700 (PDT)
Received: from [17.193.13.64] (unknown [17.193.13.64]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LNB00DX0HP3ZR90@cardamom.apple.com>; Fri, 24 Jun 2011 16:10:16 -0700 (PDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
From: james woodyatt <jhw@apple.com>
In-reply-to: <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]>
Date: Fri, 24 Jun 2011 16:10:15 -0700
Message-id: <A56C5B21-0BB4-4A96-AA21-905C03CB2F92@apple.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1244.3)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrJLMWRmVeSWpSXmKPExsUiON1OVddLktXPYP0fNYsZfyYyWzzbOJ/F gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZ/7/8YCyYK16xdP9u5gbGh0JdjJwcEgImEl+fHWeB sMUkLtxbz9bFyMUhJNDKJPFh4j4mkASvgKDEj8n3gIo4OJgF5CUOnpcFCTMLaEl8f9TKAlHf ziRxft9fdpCEsIClxK1XD5lBbDYBFYlvl+8ygfRyCphKrDgoBRJmEVCV+LTqLTvEHCeJ9187 2UFKeAVsJD6f9YYYuZhRYufNtWBjRATUJObtmcMKcae8xOKWz4wTGAVmIbluFsJ1s5Bct4CR eRWjYFFqTmKloaFeYkFBTqpecn7uJkZQADYUGuxgXPuT/xCjAAejEg9v524WPyHWxLLiytxD jBIczEoivEkbgUK8KYmVValF+fFFpTmpxYcYpTlYlMR5r6355CskkJ5YkpqdmlqQWgSTZeLg lGpgDKuZ/a5Tf7KXcPSKwJ1zAmM/9tWnrHT0dSntFskN37RRSUIo8s3kmMqmkpq81WbeFpd+ 6px/nDx3VXWf7WyXX0t1Ff5o73HZ2qG7zrJk8fL0pwYcBuYXry5Zfi70h3RU7jURA3n7q1te J+y+ZrPuSY6eOp8Nw43V/zp2LJ7kNdGMscv0Xu1uJZbijERDLeai4kQAhfs3aDwCAAA=
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: Fri, 24 Jun 2011 23:10:44 -0000

On Jun 24, 2011, at 09:08 , John C Klensin wrote:
> 
> What I saw was what appeared to me to be some fairly strong
> arguments for looking at the problem in a different way -- a way
> that I've seen no evidence the WG considered at all.   That
> would be to explore alternatives to the rather blunt instrument
> of making a protocol specification historic: explaining what
> needs to be done to get it right (your document does a lot of
> that) and then figuring out ways to warn against the uses and
> configurations that we all (or mostly) agree are bad news.

That's not how it appeared to me when I was participating the WG discussions and WG last call.  What I remember was that we had two drafts, the first, 6to4-advisory, aimed to do exactly what Mr. Klensin describes, and the second, 6to4-to-history, aimed at giving operators an excuse not to read the advisory, because hey-- 6to4 is history now.  The working group considered the option of publishing one and not the other.  That evaluation seemed to me to come to an end when the author of 6to4-advisory came out in support of publishing both documents.

In the WG discussions leading to the adoption of both drafts as work items, I supported 6to4-advisory and strenuously argued against taking up 6to4-to-historic.  When it became clear that I was on the losing side of that argument, and that WG consensus for publishing *both* would be achieved during LC, I analyzed my own reasons for opposing the 6to4-to-historic draft and concluded that I didn't really care that much if 6to4-to-historic were published, because the draft is clearly written to specify something other than what its authors and most of the WG were intending.

The WG consensus is to throw 6to4 into the historic trash bin.  The draft, however, doesn't do that.  It just tells the IETF to stop worrying and learn to love the bomb, while all the vendors of 6to4-capable equipment keep on keeping on with exactly what they're doing today.  I could live with that, and I said so.  Nobody seemed to care about it, but the observation *was* on the table.

I see that some of those in the opposition to 6to4-to-historic do not agree with me that the draft is utterly harmless and will be roundly ignored by industry.  To the extent that I can see how 6to4-to-historic may divert its intended audience from reading the much more important 6to4-advisory draft, I sympathize, but I don't see that argument moving too many minds.  I had kinda hoped that IESG would put a stop to this nonsense and kick the draft back to the WG with instructions to develop a phase-out plan for 6to4.  Alas, that didn't happen.  Oh well.

I do, however, wonder if we can finally remove 2002::/16 from the default policy table in the next revision of RFC 3484 on the grounds that 6to4 is Historic now, just like 3ffe::/16 is... that would be *excellent*.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From moore@network-heretics.com  Fri Jun 24 16:40:56 2011
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 A90989E8005; Fri, 24 Jun 2011 16:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.111
X-Spam-Level: 
X-Spam-Status: No, score=-3.111 tagged_above=-999 required=5 tests=[AWL=-0.112, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A1WdmRwZeeiw; Fri, 24 Jun 2011 16:40:55 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 71CB39E803F; Fri, 24 Jun 2011 16:40:55 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 1112D205FA; Fri, 24 Jun 2011 19:40:55 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Fri, 24 Jun 2011 19:40:55 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=UymWfhy18qshqiUA0ze4nqRpivU=; b=JTd/WC3jdO/vp4O/lJ8Z1EpiHWYzDVFqJWTBY7QcoOmRt7tIW22k677n/a1l7KXe1/dele0P2heI3FmsXcUlX3lN+maGA0n3lqus9qpewQf6Mglo5krXdx/bgO/PfDBZNXsU/qj71piPnQRTHdfrkCrt+9YPBdozbZyrbvdAv7c=
X-Sasl-enc: Y348PjAerB/V66HlFe7HtcUc0UCwGyMrfMoPUw1y9Biq 1308958854
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id EC84E405A92; Fri, 24 Jun 2011 19:40:53 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <A56C5B21-0BB4-4A96-AA21-905C03CB2F92@apple.com>
Date: Fri, 24 Jun 2011 19:40:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <178F55FB-B369-4AE7-AC0E-A1AF98616866@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]> <A56C5B21-0BB4-4A96-AA21-905C03CB2F92@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1084)
Cc: John C Klensin <john-ietf@jck.com>, 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: Fri, 24 Jun 2011 23:40:56 -0000

On Jun 24, 2011, at 7:10 PM, james woodyatt wrote:

> I see that some of those in the opposition to 6to4-to-historic do not =
agree with me that the draft is utterly harmless and will be roundly =
ignored by industry.=20

I think the effect of declaring something Historic is difficult to =
predict, and I doubt that all of "industry" will react in a uniform =
fashion.

We're a long way away from having universal v6; so far away that it's =
still not clear that it will ever happen.  We're not going to get there =
unless application vendors can ship code that makes good use of IPv6 =
(meaning the addressing and the programming model) and expect it to be =
able to run on customers' systems.  And we're not going to get that =
without a transition mechanism that's better than anything we currently =
have. =20

The 6to4-advisory document lists many ways in which 6to4 falls short of =
being suitable for this.  So, I believe, does Teredo, for different =
reasons.   But in order to get something better we need to be able to =
use some of the techniques of both.  If v6ops is allowed to declare 6to4 =
as Historic, that can be used as a bat to quash any further development =
in this space.  And I find that completely unacceptable.

Keith


From joelja@bogus.com  Fri Jun 24 17:10:50 2011
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 7820811E80C7; Fri, 24 Jun 2011 17:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.221
X-Spam-Level: 
X-Spam-Status: No, score=-102.221 tagged_above=-999 required=5 tests=[AWL=-0.222, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cjayt4VgfSxo; Fri, 24 Jun 2011 17:10:48 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A80AF11E80D2; Fri, 24 Jun 2011 17:10:47 -0700 (PDT)
Received: from [172.16.24.51] ([12.184.108.202]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5P0AerN005372 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 25 Jun 2011 00:10:42 GMT (envelope-from joelja@bogus.com)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <178F55FB-B369-4AE7-AC0E-A1AF98616866@network-heretics.com>
Date: Fri, 24 Jun 2011 17:10:34 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <567816BB-6747-402F-9D5C-A99F558A2FB4@bogus.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]> <A56C5B21-0BB4-4A96-AA21-905C03CB2F92@apple.com> <178F55FB-B369-4AE7-AC0E-A1AF98616866@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sat, 25 Jun 2011 00:10:42 +0000 (UTC)
Cc: John C Klensin <john-ietf@jck.com>, IETF-Discussion list <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: Sat, 25 Jun 2011 00:10:50 -0000

On Jun 24, 2011, at 4:40 PM, Keith Moore wrote:

> On Jun 24, 2011, at 7:10 PM, james woodyatt wrote:
>=20
>> I see that some of those in the opposition to 6to4-to-historic do not =
agree with me that the draft is utterly harmless and will be roundly =
ignored by industry.=20

Were it completely harmless I think it wouldn't meet the needs of the =
authors or supporters either. Clearly they would prefer that it be off =
as a result, or that the usage be limited to people who've deliberately =
turned it on and therefore can be expected to tolerate the limitations.

> I think the effect of declaring something Historic is difficult to =
predict, and I doubt that all of "industry" will react in a uniform =
fashion.
>=20
> We're a long way away from having universal v6; so far away that it's =
still not clear that it will ever happen.  We're not going to get there =
unless application vendors can ship code that makes good use of IPv6 =
(meaning the addressing and the programming model) and expect it to be =
able to run on customers' systems.  And we're not going to get that =
without a transition mechanism that's better than anything we currently =
have. =20
>=20
> The 6to4-advisory document lists many ways in which 6to4 falls short =
of being suitable for this.  So, I believe, does Teredo, for different =
reasons.   But in order to get something better we need to be able to =
use some of the techniques of both.  If v6ops is allowed to declare 6to4 =
as Historic, that can be used as a bat to quash any further development =
in this space.  And I find that completely unacceptable.
>=20
> Keith
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From jhw@apple.com  Fri Jun 24 18:25:49 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E442F11E80A5; Fri, 24 Jun 2011 18:25: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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JKnzhn8+dd1a; Fri, 24 Jun 2011 18:25:48 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 8A8FF11E8078; Fri, 24 Jun 2011 18:25:44 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LNB002P6NCO0CN2@mail-out.apple.com>; Fri, 24 Jun 2011 18:22:44 -0700 (PDT)
X-AuditID: 11807134-b7c71ae0000014d0-6e-4e0538337897
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay14.apple.com (Apple SCV relay) with SMTP id 6A.5B.05328.338350E4; Fri, 24 Jun 2011 18:21:55 -0700 (PDT)
Received: from [17.193.13.64] (unknown [17.193.13.64]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LNB00958NTVQ930@koseret.apple.com>; Fri, 24 Jun 2011 18:22:44 -0700 (PDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
From: james woodyatt <jhw@apple.com>
In-reply-to: <567816BB-6747-402F-9D5C-A99F558A2FB4@bogus.com>
Date: Fri, 24 Jun 2011 18:22:43 -0700
Message-id: <EE0BFEFD-DD51-4A87-9E31-9984279BED23@apple.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]> <A56C5B21-0BB4-4A96-AA21-905C03CB2F92@apple.com> <178F55FB-B369-4AE7-AC0E-A1AF98616866@network-heretics.com> <567816BB-6747-402F-9D5C-A99F558A2FB4@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1244.3)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrJLMWRmVeSWpSXmKPExsUiON1OXdfYgtXPYOMtG4sZfyYyWzzbOJ/F gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZbXNPMRZc4K84+3EZWwPjY54uRk4OCQETidYFrcwQ tpjEhXvr2UBsIYFOJom2md4gNq+AoMSPyfdYuhg5OJgF5CUOnpcFCTMLaEl8f9QKFOYCKm9l kvjRtRlsjrCApcStVw/BbDYBFYlvl+8ygdicArYSFx7uAZvDIqAq0bqGE2KOk8T7r53sEKts JFrb5zBBzDzOJLFvaxdYr4iAssSpJfNZIe6Ul1jc8plxAqPALCTnzUI4bxaS8xYwMq9iFCxK zUmsNDTRSywoyEnVS87P3cQICsCGQpMdjAd/8h9iFOBgVOLh7dzN4ifEmlhWXJl7iFGCg1lJ hDdpI1CINyWxsiq1KD++qDQntfgQozQHi5I47/U1n3yFBNITS1KzU1MLUotgskwcnFINjGuW vD1l6bF+lorpq6kbmNate7CKd8muaROPqt5UDtinHWkjuv/osttx5UfT89r2q0oEp1/ydjc6 eU6YfX1iyc9VVs5nJM+EvHj47Mzpya/s5RPezLDMnhV3XnZb6kXXGVWHXTo23hGrn1bWK/r2 9uRNy3jNivjnd6k+77X7mXX8unm74pLrXO1KLMUZiYZazEXFiQDK8ff6PAIAAA==
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: Sat, 25 Jun 2011 01:25:50 -0000

On Jun 24, 2011, at 17:10 , Joel Jaeggli wrote:
> 
> Were it completely harmless I think it wouldn't meet the needs of the authors or supporters either. Clearly they would prefer that it be off as a result, or that the usage be limited to people who've deliberately turned it on and therefore can be expected to tolerate the limitations.

Which the 6to4-advisory draft also says quite clearly.

I pointed this out in the WG discussion.  Everybody understands that 6to4-advisory is sufficient to send that message.  No, the WG supporters of this draft are firmly convinced that 6to4-to-historic is also necessary because they mistakenly believe it does something else that 6to4-advisory does not say.

The common thread tying together the sentiment expressed by practically all the supporters of 6to4-to-historic is that they want 6to4 not merely turned off by default in subscriber equipment, they also want IETF blessing for operators to ignore the recommendations in 6to4-advisory aimed at IPv6 content and network service providers for properly handling the presence of intentional 6to4 users.  In shorter terms, they want to kill 6to4 dead dead dead starting yesterday.

This, as others have observed, is a rather confusing message, but it's the one with rough consensus behind it.  As I said before, I had hoped that IESG would take the opportunity to clarify this muddle and demand a phase-out plan for 6to4 before declaring it a historic curiosity.  But no, it looks like 6to4 tunnel-router mode will be going into the same bucket as wired equivalent privacy (WEP), i.e. a technology that everyone knows is obsolete, and would like to see go away forever, but nobody wants to buy the phase-out plan for it, and so it will continue to be ubiquitous and kept in support forever.  Because it works for some people with legacy gear and they don't want to change.

Thanks ever so much, IESG!


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From jnc@mercury.lcs.mit.edu  Fri Jun 24 18:38:12 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E0FB11E80A5; Fri, 24 Jun 2011 18:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.572
X-Spam-Level: 
X-Spam-Status: No, score=-6.572 tagged_above=-999 required=5 tests=[AWL=0.027,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5DoSnaZmnL77; Fri, 24 Jun 2011 18:38:11 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 2044C11E809C; Fri, 24 Jun 2011 18:38:11 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id E4B8618C0D0; Fri, 24 Jun 2011 21:38:09 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Why ask for IETF Consensus on a WG document?
Message-Id: <20110625013809.E4B8618C0D0@mercury.lcs.mit.edu>
Date: Fri, 24 Jun 2011 21:38:09 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: iesg@ietf.org, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 01:38:12 -0000

    > From: james woodyatt <jhw@apple.com>

    > I supported 6to4-advisory and strenuously argued against taking up
    > 6to4-to-historic.
    > ...
    > I can see how 6to4-to-historic may divert its intended audience from
    > reading the much more important 6to4-advisory draft

I must admit, it does seem a little odd to issue two documents, one fixing a
protocol that you're about to declare obsolete with the other...

    > the [6to4-to-historic] draft is clearly written to specify something
    > other than what its authors and most of the WG were intending.

I'm afraid that was a little too Delphic for me. I can understand if you'd
said something like 'its authors clearly wrote it to specify something other
than what most of the WG were intending' - but how can a document have an
intent that its authors know nothing of (which is how I read the above)?

    > I do, however, wonder if we can finally remove 2002::/16 from the
    > default policy table in the next revision of RFC 3484 on the grounds
    > that 6to4 is Historic now, just like 3ffe::/16 is... that would be
    > *excellent*.

Umm, is this a serious suggestion, or are you just having a little fun in a
second-cousin-to-trolling way?

I mean, this is _exactly_ the sort of consequence of moving 6to4 to
'historic' that I think a lot of the people who oppose that move are worried
about: that although they are still using it (because it works in their
circumstances, and provides capabilities that other things such as 6rd do
not), people will use the existence of 6to4-to-historic to move on and do
things which negatively impact the users' ability to move packets around.

You weren't by any chance trying to show an example of the downsides of
that decision, were you?

	Noel

From mohta@necom830.hpcl.titech.ac.jp  Fri Jun 24 19:27:40 2011
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 3D43B11E8088 for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 19:27:40 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9r2jsSQgx8ZU for <ietf@ietfa.amsl.com>; Fri, 24 Jun 2011 19:27:39 -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 C5B1111E807E for <ietf@ietf.org>; Fri, 24 Jun 2011 19:27:38 -0700 (PDT)
Received: (qmail 68991 invoked from network); 25 Jun 2011 02:38:17 -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; 25 Jun 2011 02:38:17 -0000
Message-ID: <4E054735.8030201@necom830.hpcl.titech.ac.jp>
Date: Sat, 25 Jun 2011 11:25:57 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com>	<E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]>	<A56C5B21-0BB4-4A96-AA21-905C03CB2F92@apple.com>	<178F55FB-B369-4AE7-AC0E-A1AF98616866@network-heretics.com>	<567816BB-6747-402F-9D5C-A99F558A2FB4@bogus.com> <EE0BFEFD-DD51-4A87-9E31-9984279BED23@apple.com>
In-Reply-To: <EE0BFEFD-DD51-4A87-9E31-9984279BED23@apple.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, 25 Jun 2011 02:27:40 -0000

james woodyatt wrote:

> No, the WG supporters of this draft are firmly convinced that
> 6to4-to-historic is also necessary because they mistakenly
> believe it does something else that 6to4-advisory does not say.

That IETF declare 6to4 historic means that IETF, naturally,
won't produce any new document on 6to4.

							Masataka Ohta

From fluffy@cisco.com  Fri Jun 24 19:50:37 2011
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 0FBB011E807D; Fri, 24 Jun 2011 19:50:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.552
X-Spam-Level: 
X-Spam-Status: No, score=-110.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IdXb+blFIzn0; Fri, 24 Jun 2011 19:50:36 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfa.amsl.com (Postfix) with ESMTP id 58A3411E8072; Fri, 24 Jun 2011 19:50:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=4191; q=dns/txt; s=iport; t=1308970236; x=1310179836; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=ZCBD2TSYtEQD7shFuQ9PqCBw+TH2vquNi9ZeJvATRpo=; b=M0Sxpa0IH0ZLGsq4rEkBUapnwnH17IrGGvJXwhZPcukWlWR77QEdvmOW /bRPAhcwnHaI05iRGBFqi6u0N0qQO1G+AiNlbQkx2nSfrlr09JFT2ITyH JP0Jt4S4zbqojM0AwZo5MK6nPdyM2zPVhEz/nooP/+ciQl2a0o9QfTC+y g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAMpLBU6rRDoJ/2dsb2JhbABSp0J3iHOjY514hjAEhyyKVIRoi0k
X-IronPort-AV: E=Sophos;i="4.65,422,1304294400"; d="scan'208";a="386010918"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-2.cisco.com with ESMTP; 25 Jun 2011 02:50:36 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p5P2oYA4000845; Sat, 25 Jun 2011 02:50:35 GMT
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>
Date: Fri, 24 Jun 2011 20:50:34 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <EEF90F5C-B8DE-410E-B702-2AB69266EB4E@cisco.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1084)
Cc: The IESG <iesg@ietf.org>, Lisa Dusseault <lisa.dusseault@gmail.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: Sat, 25 Jun 2011 02:50:37 -0000

This thread brought up many good points but I would like to add one more =
that Lisa Dusseault made very clearly years ago. That is consensus is =
measured at a point of time. Many ideas start with people hating them =
and as people learn more, they may come to like them even thought the =
idea did not change. Or perhaps the deployment environment changed. The =
important point is that the results of consensus calls made in the past =
may or may not have much bearing on the current IETF consensus. I see =
IETF LC as a clear point where consensus can be measures before the IESG =
makes a decision. Most documents have very clear consensus by the time =
they reach IETF LC. For the ones that are not, every WG member is =
welcome to send comments to IETF LC, if they care - some times they do, =
mostly they do not.=20

It's very hard to define consensus and I actually think it is better if =
we don't strive for a formal definition of it. As with many of the best =
things in life, most of us know it when we see it. The words rough =
consensus certainly mean to me a lot more than half of the of the =
informed people. I do not believe that silence can be read as consensus =
support for a position - it is simply silence - it is not in favor or =
again. However each chair or AD judging rough consensus chooses to =
define it for themselves, I hope the definition results in an =
environment where a document can be progresses by a small group of the =
willing and only stopped by the outrage of the masses. WIthout that, the =
willing will simply find a better place to work. And with that, I'm off =
to read the WHATWG list.=20

Cullen

On Jun 23, 2011, at 4:36 PM, Paul Hoffman wrote:

> Greetings again. The subject line is an honest question, not a gripe.
>=20
> For those on the ietf@ mailing list, please see =
<https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ballot=
/>. In short, the IESG just approved publication of =
draft-ietf-v6ops-6to4-to-historic, even with what appears to be a lack =
of consensus in the comments on the ietf@ mailing list. One AD called it =
"pretty rough", but my quick count shows that it was not rough at all: =
there were more people on the ietf@ against this than in favor of it. If =
the consensus in a WG for a document was the same as we saw on ietf@ for =
this document, and the WG chair declared consensus anyway, there would =
be some serious talks with that WG AD about the chairs.
>=20
> For a document such as this, why even ask for IETF consensus if the =
IETF consensus doesn't matter? There was a lot of good discussion and a =
fair number of varied objections to approval of the document. It sounds =
like the WG was strongly in favor of the document, which may be =
sufficient motivation to publish it, but the intermediate step of asking =
for IETF consensus and then not paying attention to the result then =
seems wasteful of IETF time.
>=20
> If the IESG has a policy that "WG consensus trumps IETF consensus", =
that's fine, but it should be a stated policy so we know where to spend =
our time. If this document is special for some reason (for example, =
because it was about policy instead of being a protocol) and therefore =
the IESG measures consensus differently, that too is fine if we all know =
that ahead of time. Even a policy of "more than a dozen IETF regulars =
must object on ietf@ before we will consider overturning a WG" is fine, =
as long as it is a stated policy. If the IESG has a policy that says =
"the way we count in IETF Last Call is different than the way we expect =
Working Group chairs to count in WG Last call", that's fine as well. =
None of that is obvious from the ballot comments that are visible to the =
community, however.
>=20
> Guidance from the IESG for our future participation in IETF Last Call =
discussions would be greatly appreciated. We try to save you folks time =
and effort; such guidance would return the favor to us.
>=20
> --Paul Hoffman
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From huitema@microsoft.com  Fri Jun 24 21:18:07 2011
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8975C11E807D; Fri, 24 Jun 2011 21:18:07 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hiRwAijJ7+iy; Fri, 24 Jun 2011 21:18:06 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id B467F11E807A; Fri, 24 Jun 2011 21:18:06 -0700 (PDT)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 24 Jun 2011 21:18:06 -0700
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.1.289.8; Fri, 24 Jun 2011 21:18:05 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.58]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi id 14.01.0289.008; Fri, 24 Jun 2011 21:18:05 -0700
From: Christian Huitema <huitema@microsoft.com>
To: james woodyatt <jhw@apple.com>, Joel Jaeggli <joelja@bogus.com>
Subject: RE: Why ask for IETF Consensus on a WG document?
Thread-Topic: Why ask for IETF Consensus on a WG document?
Thread-Index: AQHMMfaJqr2Xrs3jt0OPorlcrmpBkpTMITgAgAAN8ICAAPRMgIAAdbiAgAAIiwCAAAhPAIAAFCmA//+zloA=
Date: Sat, 25 Jun 2011 04:18:04 +0000
Message-ID: <22F6318E46E26B498ABC828879B08D4F17B56C@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]> <A56C5B21-0BB4-4A96-AA21-905C03CB2F92@apple.com> <178F55FB-B369-4AE7-AC0E-A1AF98616866@network-heretics.com> <567816BB-6747-402F-9D5C-A99F558A2FB4@bogus.com> <EE0BFEFD-DD51-4A87-9E31-9984279BED23@apple.com>
In-Reply-To: <EE0BFEFD-DD51-4A87-9E31-9984279BED23@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.43]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Sat, 25 Jun 2011 04:18:07 -0000

It seems that we have wide consensus to publish the advisory document, not =
so much for the "6to4 historic" part. Can we just publish the advisory and =
be done with this thread?

-- Christian Huitema



From evnikita2@gmail.com  Fri Jun 24 21:31:54 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B811121F84F8; Fri, 24 Jun 2011 21:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.47
X-Spam-Level: 
X-Spam-Status: No, score=-3.47 tagged_above=-999 required=5 tests=[AWL=0.129,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDa11LNb0elr; Fri, 24 Jun 2011 21:31:54 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 780EE21F84F7; Fri, 24 Jun 2011 21:31:53 -0700 (PDT)
Received: by fxe6 with SMTP id 6so200502fxe.31 for <multiple recipients>; Fri, 24 Jun 2011 21:31:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=GF1rzVnsRBczTDx6kW8TaPZOfwy7Yi9gn0dMt4AdoMQ=; b=TaaEWxHBNi64psZ6g9H5CTx6FvPqropt9J22QBf3mb/X8SElIwEIXSZaqjO6+D2AIJ /NDnexpq/H6sAF99a5BTtA4UbKJHvdkRoGDx+ahwhBQdboCX9EkE9Xky8w6aaTkVH5qm GsAg2Fia78XnfIEHd+0Oq/vb6T3Q/KWG4l8tA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=gmqVZvIbj4tn27vQgA8e5duDEnotcAArMBJZBoY7iaKsIM6vcwfqd0tbqPlGXntOT8 z6bl8fc6zMGihBgPcpW0F3ra3HRV0ldwWRJKwwG1VKN+317iGLHEQmIo9j9bD5c8OaNR t3Te7/8+s770/dVdzFJ1xyN1as97FnKXv3/CQ=
Received: by 10.223.2.205 with SMTP id 13mr5423912fak.138.1308976312554; Fri, 24 Jun 2011 21:31:52 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id m26sm2031357fab.34.2011.06.24.21.31.50 (version=SSLv3 cipher=OTHER); Fri, 24 Jun 2011 21:31:51 -0700 (PDT)
Message-ID: <4E0564E4.9010200@gmail.com>
Date: Sat, 25 Jun 2011 07:32:36 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Robert McMurray <robmcm@microsoft.com>
Subject: Re: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File	Transfer Protocol	HOST Command for Virtual Hosts) to Proposed	Standard
References: <20110616130503.4854.51928.idtracker@ietfa.amsl.com> <4E04C0CE.1030807@gmail.com> <01AA9EC92749BF4894AC2B3039EA4A2C1949D19E@CH1PRD0302MB131.namprd03.prod.outlook.com>
In-Reply-To: <01AA9EC92749BF4894AC2B3039EA4A2C1949D19E@CH1PRD0302MB131.namprd03.prod.outlook.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ftpext@ietf.org" <ftpext@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: Sat, 25 Jun 2011 04:31:54 -0000

24.06.2011 22:08, Robert McMurray wrote:
> Thanks, Mykyta.
>
> Section 3.3 already addresses that scenario in the second paragraph - and the server behaviors are exactly what you were suggesting:
>
>     As discussed in section 3 of this document, if a HOST command is sent
>     after a user has been authenticated the server SHOULD do one of the
>     following:
>
>     a.  Send a 503 reply for an invalid sequence of commands.
>
>     b.  Treat the HOST command as though a REIN command was sent and
>         reset the user-PI to the state that existed after the previous
>         HOST command was sent and before the user had been authenticated,
>         and then return the appropriate reply for the HOST command.
OK, and if HOST is sent for the second time when the user hasn't got 
authenticated, eg.

S> 220 Server ready
C> HOST example.com
S> 220 HOST OK
C> HOST example.org
S> ???

I suppose it may be 503 reply or switching to the identified host with 
220 reply.  This situation isn't mentioned in your document.

Mykyta Yevstifeyev
> Thanks again!
>
> Robert McMurray
>
> -----Original Message-----
> From: Mykyta Yevstifeyev [mailto:evnikita2@gmail.com]
> Sent: Friday, June 24, 2011 9:53 AM
> To: ietf@ietf.org; ftpext@ietf.org
> Subject: Re: [ftpext] Last Call:<draft-ietf-ftpext2-hosts-02.txt>  (File Transfer Protocol HOST Command for Virtual Hosts) to Proposed Standard
>
> Hello,
>
> This document is well written; I'm strongly for its publication on Standards Track.  I have an only remark.  This document doesn't seem to mention what is the behavior of the server if HOST command is sent after one HOST has already been sent.  Eg.
>
> C>  HOST example.com
> S>  220 Host OK
> C>  USER foo
> S>  331 Specify password
> C>  PASS bar
> S>  230 Logged in
> C>  HOST example.org
> S>  ????
>
> I suppose the server may treat this as REIN and then switching to specified host, if the user is authenticated, and just switch to such host if the user isn't already logged in.  Another option is sending 503 reply, as invalid sequence of commands.
>
> Thanks,
> Mykyta Yevstifeyev
>
>
>


From moore@network-heretics.com  Fri Jun 24 22:24:40 2011
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 C8B9411E8076; Fri, 24 Jun 2011 22:24:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.409
X-Spam-Level: 
X-Spam-Status: No, score=-3.409 tagged_above=-999 required=5 tests=[AWL=0.190,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SoEuSK7RpELY; Fri, 24 Jun 2011 22:24:40 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 14D6111E8073; Fri, 24 Jun 2011 22:24:39 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id BC9A7207E3; Sat, 25 Jun 2011 01:24:38 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Sat, 25 Jun 2011 01:24:38 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=3cE9iI3MZcfzrJR7vTGPJhcP8MY=; b=bzLfv2XuNRVGoWbt0Nffzq4bHqfbXNjTXVtl+AxxM0sHIF/5Db9WdYhkMp8Ob8wu+UpYf9ETtpJ7llqSbvEoLjZXYlI9b7Vi2+CV10dQpz8qwFe8/FO3lYzTFr1voUU5nYLR6giailLqWqDa0EPkTNUjwmprJKwpQ1W2CXFrk1I=
X-Sasl-enc: /83VqtXmg17APM0EYS2x3PPMD+5SeDcgy8TrupBV+ws9 1308979478
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 87CFB403FD1; Sat, 25 Jun 2011 01:24:37 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <567816BB-6747-402F-9D5C-A99F558A2FB4@bogus.com>
Date: Sat, 25 Jun 2011 01:24:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <665B7796-66BF-4CDA-B876-DFFDEE63DB8F@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]> <A56C5B21-0BB4-4A96-AA21-905C03CB2F92@apple.com> <178F55FB-B369-4AE7-AC0E-A1AF98616866@network-heretics.com> <567816BB-6747-402F-9D5C-A99F558A2FB4@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1084)
Cc: John C Klensin <john-ietf@jck.com>, IETF-Discussion list <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: Sat, 25 Jun 2011 05:24:40 -0000

On Jun 24, 2011, at 8:10 PM, Joel Jaeggli wrote:

> On Jun 24, 2011, at 4:40 PM, Keith Moore wrote:
>=20
>> On Jun 24, 2011, at 7:10 PM, james woodyatt wrote:
>>=20
>>> I see that some of those in the opposition to 6to4-to-historic do =
not agree with me that the draft is utterly harmless and will be roundly =
ignored by industry.=20
>=20
> Were it completely harmless I think it wouldn't meet the needs of the =
authors or supporters either. Clearly they would prefer that it be off =
as a result, or that the usage be limited to people who've deliberately =
turned it on and therefore can be expected to tolerate the limitations.

But there is general agreement to turn 6to4 off by default.   It's the =
labeling of 6to4 as historic that is the divisive point.

Keith


From tjc@ecs.soton.ac.uk  Sat Jun 25 02:45:32 2011
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 3008711E8077; Sat, 25 Jun 2011 02:45:32 -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=[AWL=0.000,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o3YEl3vlEyPL; Sat, 25 Jun 2011 02:45:31 -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 22DFB11E807E; Sat, 25 Jun 2011 02:45:28 -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 p5P9jH3N005068;  Sat, 25 Jun 2011 10:45:17 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p5P9jH3N005068
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1308995117; bh=Ghj62gWCdufgfg/mwTTYQI7ye1Y=; h=References:In-Reply-To:Mime-Version:Cc:From:Subject:Date:To; b=ISluLy0oZHAVpXmmE+j6ixHua+Bfb31cI5eQF/cKP0CI2UdcA4ijVnNkXcT9cJlS0 qDqz/NrO/JIodJN1S9CNG94JuOXI+jr5TCJpap+i/Ak+GAi935qVmcyMIbwF/jCUOg ABbXSsxAhoqibCju59uOnVDuVjBOizi/GlibpvnY=
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 id n5OAjH0366150211kn ret-id none; Sat, 25 Jun 2011 10:45:17 +0100
Received: from [172.20.10.2] ([82.132.139.12]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p5P9j2XF011403 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 25 Jun 2011 10:45:07 +0100
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]> <A56C5B21-0BB4-4A96-AA21-905C03CB2F92@apple.com> <178F55FB-B369-4AE7-AC0E-A1AF98616866@network-heretics.com> <567816BB-6747-402F-9D5C-A99F558A2FB4@bogus.com> <EE0BFEFD-DD51-4A87-9E31-9984279BED23@apple.com> <22F6318E46E26B498ABC828879B08D4F17B56C@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <753410D7-DAA6-4610-9E7C-F718C0491AD3@ecs.soton.ac.uk>
In-Reply-To: <22F6318E46E26B498ABC828879B08D4F17B56C@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0 (iPad Mail 8J2)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-ID: <EMEW3|ceabbc55c7a520c4c5f96f5bcaf97d92n5OAjH03tjc|ecs.soton.ac.uk|753410D7-DAA6-4610-9E7C-F718C0491AD3@ecs.soton.ac.uk>
X-Mailer: iPad Mail (8J2)
From: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: Why ask for IETF Consensus on a WG document?
Date: Sat, 25 Jun 2011 10:44:55 +0100
To: Christian Huitema <huitema@microsoft.com>
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n5OAjH036615021100; tid=n5OAjH0366150211kn; client=relay,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p5P9jH3N005068
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: IETF-Discussion list <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: Sat, 25 Jun 2011 09:45:32 -0000

On 25 Jun 2011, at 05:18, Christian Huitema <huitema@microsoft.com> wrote:

> It seems that we have wide consensus to publish the advisory document, not=
 so much for the "6to4 historic" part. Can we just publish the advisory and b=
e done with this thread?

I'm a little confused by this discussion.

I had thought the call here was to solicit 'substantial' comments about -adv=
isory and -historic.  Thus I assume people who, like me, are in favour of bo=
th drafts progressing are not going to respond to the list at all, which mea=
ns the list isn't a reflection of consensus - it's not a vote.

I do agree with the comment that the call should be identifying new issues, a=
nd even if just one person raises several such (valid) issues, they should b=
e considered as part of the process.=20

While I'm now here, my personal view is that -advisory must be progressed an=
d -historic should be progressed.

Tim=

From sm@resistor.net  Sat Jun 25 04:07:01 2011
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 5684A21F84BB for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 04: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZ2Ony2JOII1 for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 04:06: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 7927E21F84B9 for <ietf@ietf.org>; Sat, 25 Jun 2011 04:06:54 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p5PB6iv8003851;  Sat, 25 Jun 2011 04:06:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1309000011; bh=oI/Brm0rL7Su8oGaV3Q2oC7RHc300YALP0hPuXSRk0w=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=0E8y5x3f+D9ty7rQJHURo1GpU7DNhiF7ZC73pUJooHgi9BsHHyxTDVkpLhv2WmKgE S3y81LwIpmjctfn9KUuuaFsFBzXi99Mv+Lfcd58r+Oqc1F9G1RM6J2bsSPxgFgJiMg uZxYZ/iWP8HIGE/cMBAyHT8OdBwc3DHFxG4iSfhE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1309000011; bh=oI/Brm0rL7Su8oGaV3Q2oC7RHc300YALP0hPuXSRk0w=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=frKeXiv2wcikavEu8awEDvPqpEgTq40Z0g/O918teJWprzm41LX+hJnJcM9ZSMZAT n5F4kU8a+tvoHG2UKxiaPugFkhFbGuuguqQQY5K8vVEjDlpn9zTk++EiSPtoF+rBly MVrDvB+oKPf1+tKeSMQnEm8XZsQx2Ulu0qNXG634=
Message-Id: <6.2.5.6.2.20110625013139.051be2e8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 25 Jun 2011 02:30:31 -0700
To: Paul Hoffman <paul.hoffman@vpnc.org>
From: SM <sm@resistor.net>
Subject: Re: Why ask for IETF Consensus on a WG document?
In-Reply-To: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 25 Jun 2011 11:07:01 -0000

Hi Paul,
At 15:36 23-06-2011, Paul Hoffman wrote:
>For those on the ietf@ mailing list, please see 
><https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/ballot/>. 
>In short, the IESG just approved publication of 
>draft-ietf-v6ops-6to4-to-historic, even with what appears to be a 
>lack of consensus in the comments on the ietf@ mailing list. One AD 
>called it "pretty rough", but my quick count shows that it was not 
>rough at all: there were more people on the ietf@ against this than 
>in favor of it. If the consensus in a WG for a document was the same 
>as we saw on ietf@ for this document, and the WG chair declared 
>consensus anyway, there would be some serious talks with that WG AD 
>about the chairs.

Assuming that there was rough consensus (I agree with you that it was 
not rough at all), the document would still not satisfy the following 
statement:

   "It represents the consensus of the IETF community.  It has
    received public review and has been approved for publication by
    the Internet Engineering Steering Group (IESG)."

The IETF Last Call is to get cross-area review and, as others have 
pointed out, to provide an opportunity for people who have not read 
the WG document previously to comment.  Sometimes there is a rehash 
of the WG discussions.  Although that might be viewed by some 
participants as "wasting IETF time", it is part of the cost of the process.

If an objection was raised, the IESG might have to argue that the 
document represents the consensus of the IETF community.  That is 
generally based on the IETF Last Call comments and not discussions 
within the WG Cloud.

If a WG chair declared consensus on an issue like this, the 
responsible AD would hear about it.  If the IESG declared consensus 
on an issue like this, complain to NomCom about it.

Regards,
-sm 


From sm@resistor.net  Sat Jun 25 04:39:35 2011
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 D3BC511E8084 for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 04:39:35 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1--58pW1-lXQ for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 04:39: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 E073511E8070 for <ietf@ietf.org>; Sat, 25 Jun 2011 04:39:33 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p5PBdMSR006743 for <ietf@ietf.org>; Sat, 25 Jun 2011 04:39:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1309001969; bh=dcGbVhNPZQ/+wEbKOy5zlJZt5Ua85RwaMwBxvbZZf0c=; h=Message-Id:X-Mailer:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type; b=Zb2X6GeesacRcmEQdJVqvZQnqZv7bILOSuoZYRLEJzSflag6SSTBgZNw5uHnLAIZI 4DLYBIeOFcMw/q7QoqV379TlIy1BDCKwCRagVkaC4yizB8II6UkwlCpwiWrDrRrxif WLwkVlX0aP5p48WKNJmJDhjgwAXegp+ra+6qP0Bc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1309001969; bh=dcGbVhNPZQ/+wEbKOy5zlJZt5Ua85RwaMwBxvbZZf0c=; h=Message-Id:X-Mailer:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type; b=2+nfb+CtknnHLDKm2R7XgWNcD37tbSfM9ZFcO3NzIfLRUFyXuZkjzIVYqln0vyYuQ yGQEPJ0Ym7a6J43mPcgb5vhMzKkXvt8p4tZQD9YZtq5gJ055yo4tI7QjqiKy37zSMw aircVHzQOsaVtlpKMqKCpPT+UOcmzKVstxNvfjtU=
Message-Id: <6.2.5.6.2.20110625032041.03c8b498@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 25 Jun 2011 04:39:14 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified Mail (DKIM) Signatures) to Draft Standard
In-Reply-To: <20110615213858.9853.22165.idtracker@ietfa.amsl.com>
References: <20110615213858.9853.22165.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: Sat, 25 Jun 2011 11:39:35 -0000

At 14:38 15-06-2011, The IESG wrote:
>The IESG has received a request from the Domain Keys Identified Mail WG
>(dkim) to consider the following document:
>- 'DomainKeys Identified Mail (DKIM) Signatures'
>   <draft-ietf-dkim-rfc4871bis-12.txt> as a Draft 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 2011-06-29. Exceptionally, comments may be

This document obsoletes RFC 4871 for which there is an IPR disclosure 
( http://datatracker.ietf.org/ipr/1547/ ).  As this is a move from 
Proposed to Draft, is a new IPR disclosure required?

In Appendix B.1.4, news@news-site.com could be changed to 
news@news-site.example (RFC 2606).

In Section C.1:

   "This differs from the usage in the original DKIM specification,
    where a null "g=" value is not valid for any address."

I suggest a minor change, "previous DKIM specification [RFC4871]", for clarity.

Regards,
-sm 


From brian.e.carpenter@gmail.com  Sat Jun 25 05:11:17 2011
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 BF2D221F8528; Sat, 25 Jun 2011 05:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.356
X-Spam-Level: 
X-Spam-Status: No, score=-103.356 tagged_above=-999 required=5 tests=[AWL=-0.072, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ij666nfFQNMf; Sat, 25 Jun 2011 05:11:17 -0700 (PDT)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by ietfa.amsl.com (Postfix) with ESMTP id B21ED21F8527; Sat, 25 Jun 2011 05:11:16 -0700 (PDT)
Received: by fxe4 with SMTP id 4so944012fxe.27 for <multiple recipients>; Sat, 25 Jun 2011 05:11:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=FokTECIXqomyIbZT5dqGGA4pZRnhofrGJ2RDyNUWdR0=; b=oawYAAaqQz7w00uIe8VSo3g7CweRGmV197g4KtfB6r4//UdI+U5borV+LBE4ptPLEt wVVwm3VXMmQVJDbzHf4jSGl+p6V5KqlR0Gddn7NmYemlq25UPwiFqivnMGefHGXXStjX p1u70tWUWcFuE4i0B46X1hezhlSt6fW9BCIFU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=cGR0PA1g2ofbS8S+z7tFC0GhwH+VdXvl7jvv1+jLHeSO3Z2/ppKMmoDD26udHnlXhj v6oEWaLi8rvVGZkQ9B+xdP+G4I6bh5xbXm9z/EnjD8+ctZSPznatx39AX1fw7jGRy6ty kPcG9jakeCqVblwUR3b3vdGBle1kl4d6HStD0=
Received: by 10.223.156.9 with SMTP id u9mr6087625faw.70.1309003875780; Sat, 25 Jun 2011 05:11:15 -0700 (PDT)
Received: from [10.255.25.96] (74-95-74-1-Indianapolis.hfc.comcastbusiness.net [74.95.74.1]) by mx.google.com with ESMTPS id r10sm2233669fah.2.2011.06.25.05.11.13 (version=SSLv3 cipher=OTHER); Sat, 25 Jun 2011 05:11:15 -0700 (PDT)
Message-ID: <4E05D05B.7030000@gmail.com>
Date: Sun, 26 Jun 2011 00:11:07 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <20110625013809.E4B8618C0D0@mercury.lcs.mit.edu>
In-Reply-To: <20110625013809.E4B8618C0D0@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 12:11:17 -0000

On 2011-06-25 13:38, Noel Chiappa wrote:
>     > From: james woodyatt <jhw@apple.com>
> 
>     > I supported 6to4-advisory and strenuously argued against taking up
>     > 6to4-to-historic.
>     > ...
>     > I can see how 6to4-to-historic may divert its intended audience from
>     > reading the much more important 6to4-advisory draft
> 
> I must admit, it does seem a little odd to issue two documents, one fixing a
> protocol that you're about to declare obsolete with the other...

Not so odd. There are hundreds of millions of hosts out there that attempt
to use 6to4 by default, and (probably) thousands of relay routers that
attempt to support such users. Those boxes will be around for years, and are
the target for the -advisory draft, regardless of the deprecation.

   Brian

From john@jlc.net  Sat Jun 25 06:16:28 2011
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 9FE9421F8494 for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 06:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.858
X-Spam-Level: 
X-Spam-Status: No, score=-105.858 tagged_above=-999 required=5 tests=[AWL=0.141, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A3GcGqo58c9v for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 06:16:27 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 7429421F8498 for <ietf@ietf.org>; Sat, 25 Jun 2011 06:16:27 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id E80AA33C22; Sat, 25 Jun 2011 09:16:26 -0400 (EDT)
Date: Sat, 25 Jun 2011 09:16:26 -0400
From: John Leslie <john@jlc.net>
To: SM <sm@resistor.net>
Subject: Re: Why ask for IETF Consensus on a WG document?
Message-ID: <20110625131626.GC56541@verdi>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <6.2.5.6.2.20110625013139.051be2e8@resistor.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20110625013139.051be2e8@resistor.net>
User-Agent: Mutt/1.4.1i
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, 25 Jun 2011 13:16:28 -0000

SM <sm@resistor.net> wrote:
> 
> Assuming that there was rough consensus (I agree with you that it was 
> not rough at all), the document would still not satisfy the following 
> statement:
> 
>   "It represents the consensus of the IETF community.  It has
>    received public review and has been approved for publication by
>    the Internet Engineering Steering Group (IESG)."

   I actually don't know whether the intent is to attach that boilerplate:
it certainly isn't present in the I-D.

   I quite agree that -6to4-to-historic doesn't satisfy such a statement;
and I don't believe the IESG process for Informational track documents
gives any assurance of "consensus of the IETF community".

   In the interests of truth in advertising, perhaps we should be
looking towards boilerplate more like:
" 
" This document represents the consensus of the V6OPS WG...

   (Disclaimer: I date from when RFCs didn't claim any sort of consensus;
and I'd be happier if we simply avoided such claims on Informational
track RFCs.)

--
John Leslie <john@jlc.net>

From john-ietf@jck.com  Sat Jun 25 07:09:15 2011
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 9F3FE21F8554; Sat, 25 Jun 2011 07:09:15 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sgfr7hzKRS0v; Sat, 25 Jun 2011 07:09:14 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id C51A821F8553; Sat, 25 Jun 2011 07:09:12 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QaTXr-000OfT-TH; Sat, 25 Jun 2011 10:09:12 -0400
Date: Sat, 25 Jun 2011 10:09:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: james woodyatt <jhw@apple.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
Message-ID: <C6C4295177A399D74887A882@JCK-EEE10>
In-Reply-To: <A56C5B21-0BB4-4A96-AA21-905C03CB2F92@apple.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]> <A56C5B21-0BB4-4A96-AA21-905C03CB2F92@apple.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: 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: Sat, 25 Jun 2011 14:09:15 -0000

--On Friday, 24 June, 2011 16:10 -0700 james woodyatt
<jhw@apple.com> wrote:

> On Jun 24, 2011, at 09:08 , John C Klensin wrote:
>> 
>> What I saw was what appeared to me to be some fairly strong
>> arguments for looking at the problem in a different way -- a
>> way that I've seen no evidence the WG considered at all.
>> That would be to explore alternatives to the rather blunt
>...
> That's not how it appeared to me when I was participating the
> WG discussions and WG last call.  What I remember was that we
> had two drafts, the first, 6to4-advisory, aimed to do exactly
> what Mr. Klensin describes, and the second, 6to4-to-history,
> aimed at giving operators an excuse not to read the advisory,
> because hey-- 6to4 is history now.  The working group
> considered the option of publishing one and not the other.
> That evaluation seemed to me to come to an end when the author
> of 6to4-advisory came out in support of publishing both
> documents.

First. as I've told that author at more length privately, I
disagree with that decision as, apparently, do many others.  As
others have pointed out, it sends a very confusing message to
someone who doesn't know the WG history, is reading the RFCs in
isolation, and isn't doing so carefully.   Fortunately or
unfortunately, that is a pretty good description of the typical
reader of RFCs, as least in my experience/observation.  

As I told Brian, if the intent is to deliver a clear "we think
you REALLY REALLY SHOULD NOT (a term that is not quite in 2119)
use this, but, if you do anyway, take this advice", then you do
that in one document that explains both.   When you publish the
advice document and simultaneously publish a document that can
be read as saying "never mind, this, including the advice, is
all ancient history and you should pay no attention to it", you
are just being confusing.   IMO, that is largely independent of
whether you also move everything to Historic except that the
formal Historic classification just adds to the confusion.

Now that opinion obviously disagrees with that of the WG.  My
hypothesis is that the WG just got too close to the problem to
see the issue from the casual reader of RFCs who doesn't have a
long history with debates about the issue.  And, as others have
said, I believe that IETF LC is designed to identify exactly
that problem.  In matters of technical expertise, I believe the
IESG should balance WG opinion and IETF opinion very carefully,
giving great (but certainly not absolute) weight to issues that
the WG considered carefully and reached a conclusion about.
But when the evaluation is about whether the document is clear
to an expert who did not participate in the WG or whether it
sends a clear message, then I believe the opinions of those
outside the WG, without the history and shared understanding,
should absolutely predominate.  And I hope that, if you think
about it for a while, that reasoning will be clear.

> In the WG discussions leading to the adoption of both drafts
> as work items, I supported 6to4-advisory and strenuously
> argued against taking up 6to4-to-historic.  When it became
> clear that I was on the losing side of that argument, and that
> WG consensus for publishing *both* would be achieved during
> LC, I analyzed my own reasons for opposing the
> 6to4-to-historic draft and concluded that I didn't really care
> that much if 6to4-to-historic were published, because the
> draft is clearly written to specify something other than what
> its authors and most of the WG were intending.

And, if IETF Last Call had pointed out, really clearly, that the
intent of "...historic" was different from what the WG intended,
would you expect the IESG to follow the WG's intent or the text
of the document?  That is actually a serious question.  If I
were IESG, I'd argue strongly for punting both documents back to
the WG at that point and say "figure out what you really want
and mean and express it clearly and consistently in one
document".   But I'm no on the IESG and know that I'm taking
advantage of not having to deal with possible consequences and
side-effects of such a move.

> The WG consensus is to throw 6to4 into the historic trash bin.
> The draft, however, doesn't do that.  It just tells the IETF
> to stop worrying and learn to love the bomb, while all the
> vendors of 6to4-capable equipment keep on keeping on with
> exactly what they're doing today.  I could live with that, and
> I said so.  Nobody seemed to care about it, but the
> observation *was* on the table.

Yes.  And???  (see above)

> I see that some of those in the opposition to 6to4-to-historic
> do not agree with me that the draft is utterly harmless and
> will be roundly ignored by industry.  To the extent that I can
> see how 6to4-to-historic may divert its intended audience from
> reading the much more important 6to4-advisory draft, I
> sympathize, but I don't see that argument moving too many
> minds.  I had kinda hoped that IESG would put a stop to this
> nonsense and kick the draft back to the WG with instructions
> to develop a phase-out plan for 6to4.  Alas, that didn't
> happen.  Oh well.

With one major exception, I think that puts us pretty much on
the same page, including with some small disappointment at the
IESG for not telling the WG to do its job.   The exception is
that I believe  that every authoritative-sounding document that
is published in the IETF Stream and then ignored by industry
strikes a blow against IETF's overall credibility and that those
blows, however small, are cumulatively damaging.
>...

And, from your later note but very much to the same point...

> But no, it looks like 6to4 tunnel-router mode will be going
> into the same bucket as wired equivalent privacy (WEP), i.e. a
> technology that everyone knows is obsolete, and would like to
> see go away forever, but nobody wants to buy the phase-out
> plan for it, and so it will continue to be ubiquitous and kept
> in support forever.  

In addition, WEP, and the process that created it, are routinely
held up outside that group as the product of a clueless
standards body that probably understood radios but that
exhibited a complete lack of clue where encryption was
concerned.  That may be an unfair rap, or may not be, but, as
far as good reputations are concerned, it is bad news...

    john


From jnc@mercury.lcs.mit.edu  Sat Jun 25 07:36:22 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EAE421F8505 for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 07:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.574
X-Spam-Level: 
X-Spam-Status: No, score=-6.574 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EaQpRmDxrh9o for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 07:36:21 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id B53E521F8503 for <ietf@ietf.org>; Sat, 25 Jun 2011 07:36:21 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id C892118C10C; Sat, 25 Jun 2011 10:36:15 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Why ask for IETF Consensus on a WG document?
Message-Id: <20110625143615.C892118C10C@mercury.lcs.mit.edu>
Date: Sat, 25 Jun 2011 10:36:15 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 14:36:22 -0000

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

    > I just don't think that adding "historic" to those pieces of advice
    > will be influential in accomplishing the goals, that it is a too-blunt
    > instrument, and its application in this sort of situation is more
    > likely to bring discredit on the IETF than to accomplish the purpose
    > for which its advocates are encouraging it. I believe I'm probably in
    > the minority on that position

The fact that you're in a minority shouldn't matter.

Dave Clark's phrase "rough consensus" gets tossed around a lot, but we seem to
be missing the clear point of what it says. People seem to be focusing on the
'rough' part, and not on the 'consensus': "consensus" is the noun, and "rough"
is just a modifier. In other words, we should focus on basically having
consensus; if we have lots of people - and especially people with significant
technical weight - disagreeing with a position, we don't 'basically have
consensus'.

If Dave had meant to say 'significant majority', he could have said that
instead. He didn't. But that is effectively the standard people are now
applying - not 'basically consensus'.


I believe that he picked "rough consensus" instead for a very good reason
(below) - but even if this reason was not in his mind, it still seems to me
the best argument why "rough consensus" is the right standard to apply instead
of 'significant majority', in what is basically a 'herding cats'
organization. When you have a _significant_ minority which is really unhappy
with a decision, it's going to have poisonous effects which are going to
hamper the promulgation/adoption of that design/decision/etc. And this is in
fact what have seen happen, when we crossed this line before.

Not that I really expect anything to happen here as a result of this. The IETF
has ignored this principle before (to its grave cost), and I expect it will
again here, with the exact result which you forsee ("bring discredit on the
IETF"). Where an accumulation of these will bring us to eventually is anyone's
guess.

	Noel

From sm@resistor.net  Sat Jun 25 11:11:07 2011
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 9C24C21F844A for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 11:11:07 -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_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kugnSQwVah+8 for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 11:11:06 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 489FD21F8449 for <ietf@ietf.org>; Sat, 25 Jun 2011 11:11:06 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p5PIAqqx029698;  Sat, 25 Jun 2011 11:10:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1309025463; bh=NGcTgNCXmi1EGG96wklcYZcEvXTPFnoftRpwP7fW4Jg=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=ng93shU2TEriSbjkBH24NMif6HlM1+nxHfSr2tpda/TQ+wEAu31rI5OP9zTT+DQLh npRP4PzosfBPeSIESjpQB2LKr8B9ixOTVwORdgnWgBpaj6T8EBiaEqrOVBS77rplB5 UBzNBZpSDrfqSJ+D27qwb3gXKxRyN1XnJPry4Wyc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1309025463; bh=NGcTgNCXmi1EGG96wklcYZcEvXTPFnoftRpwP7fW4Jg=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=h2nHvkpLrnTcTMOttaP1PJXWYITmo/fP84yJLMfs2lUgn+2qAG1lKnzEbDYwgdd5V HB+gGGgpmhaT6p4vT0+7YBW9XKDDOCKJ3A0ne9l4WWD4UXzvThleK9L7HXwROE1TLn drephx5mh8jmZOExSFres19Ma7c1++PZsXGcbFcU=
Message-Id: <6.2.5.6.2.20110625100001.037a1e28@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 25 Jun 2011 11:01:08 -0700
To: IETF-Discussion list <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: Why ask for IETF Consensus on a WG document?
In-Reply-To: <20110625131626.GC56541@verdi>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <6.2.5.6.2.20110625013139.051be2e8@resistor.net> <20110625131626.GC56541@verdi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: John Leslie <john@jlc.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: Sat, 25 Jun 2011 18:11:07 -0000

At 06:16 25-06-2011, John Leslie wrote:
>    I quite agree that -6to4-to-historic doesn't satisfy such a statement;
>and I don't believe the IESG process for Informational track documents
>gives any assurance of "consensus of the IETF community".

It doesn't.

The IANA Considerations section raises an interesting question about 
whether it is appropriate to have such action in an Informational RFC.

>    In the interests of truth in advertising, perhaps we should be
>looking towards boilerplate more like:
>"
>" This document represents the consensus of the V6OPS WG...

That document would then have to be published as a WG Snapshot.  That 
label does not exist yet.

>    (Disclaimer: I date from when RFCs didn't claim any sort of consensus;
>and I'd be happier if we simply avoided such claims on Informational
>track RFCs.)

The objective was to document the level of consensus.  It is 
sometimes overlooked as the I-D does not contain the final 
boilerplate text.  I would be happy if such claims were avoided in 
Informational RFCs as it makes the line between Standards-Track and 
Informational fuzzy.

At 02:44 25-06-2011, Tim Chown wrote:
>I had thought the call here was to solicit 'substantial' comments 
>about -advisory and -historic.  Thus I assume people who, like me, 
>are in favour of both drafts progressing are not going to respond to 
>the list at all, which means the list isn't a reflection of 
>consensus - it's not a vote.

The wording in the Last Call announcement says "substantive 
comments".  The use of the word "substantive" is intentional (see 
comment from "the Last Defender of Camelot" [1]).  A response is 
optional if there are already arguments in the I-D to counter the 
"substantive comments".  If there are strong objections, it is left 
to the working group or author to see whether it is worthwhile to 
address the objections.

A long time ago, there was an RFC [2], from which I'll quote:

   "This group of people struggled with a broad range of issues in host
    implementations of the Internet protocols, attempting to reconcile
    theoretical and architectural concerns with the sometimes conflicting
    imperatives of the real world.  The present RFC recaps the results of
    this struggle, with the issues that were settled and those that
    remain for future work."

   'However, not all issues were so easy; the working group struggled
    with a number of deep and controversial technical issues.  Where the
    result was a reasonable consensus, then definite, firm
    recommendations and requirements resulted.  We list these settled
    issues in Section 2.  Section 2 also lists a number of areas where
    the HR RFCs fill gaping holes in the current specifications by giving
    extended discussions of particular issues.

    However, in some other cases the working group was unable to reach a
    crisp decision or even a reasonable consensus; we list these open
    issues in Section 3.  Future discussion is needed to ascertain which
    of these issues really do have "right answers", and which can
    reasonably be left as implementation choices.'

At 07:09 25-06-2011, John C Klensin wrote:
>that problem.  In matters of technical expertise, I believe the
>IESG should balance WG opinion and IETF opinion very carefully,
>giving great (but certainly not absolute) weight to issues that
>the WG considered carefully and reached a conclusion about.

It's better when there is consensus on a reclassification to Historic.

>With one major exception, I think that puts us pretty much on
>the same page, including with some small disappointment at the
>IESG for not telling the WG to do its job.   The exception is
>that I believe  that every authoritative-sounding document that
>is published in the IETF Stream and then ignored by industry
>strikes a blow against IETF's overall credibility and that those
>blows, however small, are cumulatively damaging.

Agreed.

At 07:36 25-06-2011, Noel Chiappa wrote:
>organization. When you have a _significant_ minority which is really unhappy
>with a decision, it's going to have poisonous effects which are going to
>hamper the promulgation/adoption of that design/decision/etc. And this is in
>fact what have seen happen, when we crossed this line before.

Agreed.

1. http://www.ietf.org/mail-archive/web/apps-discuss/current/msg02651.html
2. http://www.rfc-editor.org/rfc/rfc1127.txt 


From joelja@bogus.com  Sat Jun 25 12:04:55 2011
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 8CE8711E8102; Sat, 25 Jun 2011 12:04:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level: 
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=-0.308, BAYES_00=-2.599, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xJ2iqXwJXINW; Sat, 25 Jun 2011 12:04:55 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id F3D6111E80CB; Sat, 25 Jun 2011 12:04:54 -0700 (PDT)
Received: from [192.168.0.139] (adsl-99-191-195-38.dsl.pltn13.sbcglobal.net [99.191.195.38]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5PJ4JAg024913 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 25 Jun 2011 19:04:50 GMT (envelope-from joelja@bogus.com)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4E05D05B.7030000@gmail.com>
Date: Sat, 25 Jun 2011 12:04:14 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B91BB6CD-656F-4935-B513-A6225C8F3973@bogus.com>
References: <20110625013809.E4B8618C0D0@mercury.lcs.mit.edu> <4E05D05B.7030000@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sat, 25 Jun 2011 19:04:50 +0000 (UTC)
Cc: iesg@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 19:04:55 -0000

On Jun 25, 2011, at 5:11 AM, Brian E Carpenter wrote:

> On 2011-06-25 13:38, Noel Chiappa wrote:
>>> From: james woodyatt <jhw@apple.com>
>>=20
>>> I supported 6to4-advisory and strenuously argued against taking up
>>> 6to4-to-historic.
>>> ...
>>> I can see how 6to4-to-historic may divert its intended audience from
>>> reading the much more important 6to4-advisory draft
>>=20
>> I must admit, it does seem a little odd to issue two documents, one =
fixing a
>> protocol that you're about to declare obsolete with the other...
>=20
> Not so odd. There are hundreds of millions of hosts out there that =
attempt
> to use 6to4 by default, and (probably) thousands of relay routers that
> attempt to support such users. Those boxes will be around for years, =
and are
> the target for the -advisory draft, regardless of the deprecation.

the very fact that the devices are largely unmanaged, means that if you =
don't want to break them worse then they already are that you have =
continue to support them until they age out of the network.

>   Brian
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From joelja@bogus.com  Sat Jun 25 12:18:45 2011
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 A55F311E80F9; Sat, 25 Jun 2011 12:18:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.647
X-Spam-Level: 
X-Spam-Status: No, score=-102.647 tagged_above=-999 required=5 tests=[AWL=-0.048, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D08D-WZ1OVbn; Sat, 25 Jun 2011 12:18:45 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id CAC7311E80EE; Sat, 25 Jun 2011 12:18:44 -0700 (PDT)
Received: from [192.168.0.139] (adsl-99-191-195-38.dsl.pltn13.sbcglobal.net [99.191.195.38]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5PJIAXQ025169 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 25 Jun 2011 19:18:41 GMT (envelope-from joelja@bogus.com)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <CA4216AA-8A32-4239-9A18-D840DF06F48F@network-heretics.com>
Date: Sat, 25 Jun 2011 12:18:05 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <059D9573-C0F3-4391-8FC6-A93B224D5C66@bogus.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<4E03DDF8.1040806@stpeter.im> <1485FF3E-0A3E-40C0-A785-775C9BCE7B73@network-heretics.com> <4E04EE1E.9070907@dougbarton.us> <FEA5B9A8-0B3C-46AC-9B44-F6EA014443D9@network-heretics.com> <4E04F7B4.9000602@dougbarton.us> <CA4216AA-8A32-4239-9A18-D840DF06F48F@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sat, 25 Jun 2011 19:18:41 +0000 (UTC)
Cc: The IESG <iesg@ietf.org>, IETF-Discussion list <ietf@ietf.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: Sat, 25 Jun 2011 19:18:45 -0000

On Jun 24, 2011, at 1:54 PM, Keith Moore wrote:

> On Jun 24, 2011, at 4:46 PM, Doug Barton wrote:
>=20
>>> I've been reviewing the WGLC comments. I haven't finished doing so =
yet,
>>> but so far my impression is that the discussion was both thorough =
and
>>> well-organized.
>>=20
>> You might want to go further back in the archives than just the LC. =
There was quite a bit of discussion on both drafts.
>=20
> I've read some of it, and participated in some of the discussion for =
-advisory.    Though my immediate question has been whether the WG =
really had rough consensus, and I don't think the other WG discussion =
matters too much in gauging that.=20

The  question of what the wg thought at the time of the wg last call is =
supposed to be captured in the document shepherd writeup.

=
https://datatracker.ietf.org/doc/draft-ietf-v6ops-6to4-to-historic/history=
/

I belive that in the case of this documents the unresolvable but =
understood objections present in the wg process around this document are =
specifically called out.

> Keith
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From sm@resistor.net  Sat Jun 25 13:01:27 2011
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 9D83A11E811B for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 13:01:27 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CaZBkIvRvT8t for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 13:01: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 CC5E211E811C for <ietf@ietf.org>; Sat, 25 Jun 2011 13:01:24 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p5PK1JQK016002 for <ietf@ietf.org>; Sat, 25 Jun 2011 13:01:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1309032083; bh=Ry+2TndQBgGJazAO2j2TF4m740iexeymkQStqKx2yuQ=; h=Message-Id:X-Mailer:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type; b=4yA5WfYhcHv6OsW3bUZh2C0CYwNylP2sSEXl4KpxW57dcdB9icBkE79f+9say6+Fb mY9EtSnCHLA/UoGTN4x5Djn5TynY2nNz1Jw4NFKTH0i1W2pjLy81zoAYXbCm1didoG SA7PHNHlWndd5MNtNMvKtOJv+rUy1b72udejC0Jc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1309032083; bh=Ry+2TndQBgGJazAO2j2TF4m740iexeymkQStqKx2yuQ=; h=Message-Id:X-Mailer:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type; b=ak8fiGyC05f1MuhJXPyQlGAN0uuDsi1FSRQ3emoyfMTvNzmsInomiQfbLLNeBLxeA SUm+wlR6lhNf/axjJeYmMjnihCenVoPeLTk4xFVQ5iEcyH6Ru7b8Iy94BKlxaEs0Uc 3+ykMOv0OZO2UI/U6SSJGE7YwpQh4H7/vTLOss60=
Message-Id: <6.2.5.6.2.20110625111608.037bfe18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 25 Jun 2011 12:27:06 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-appsawg-rfc3536bis-02.txt> (Terminology Used in Internationalization in the IETF) to BCP
In-Reply-To: <20110616130400.4851.68985.idtracker@ietfa.amsl.com>
References: <20110616130400.4851.68985.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: Sat, 25 Jun 2011 20:01:27 -0000

At 06:04 16-06-2011, The IESG wrote:
>The IESG has received a request from the Applications Area Working Group
>WG (appsawg) to consider the following document:
>- 'Terminology Used in Internationalization in the IETF'
>   <draft-ietf-appsawg-rfc3536bis-02.txt> as a BCP
>
>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 2011-06-30. Exceptionally, comments may be

This document uses an unusual format to show the source of a 
definition (Section 1.2).  It's clearer (to me) if the document used 
the regular format for references.

The anchor9 comment in Section 3.2, minus the last sentence, could be 
folded in as part of the I-D.  Pointing out that the definition is 
not precisely correct is correct in itself.

In Section 4:

   "Code Point order is usually not how any human educated by a local
    school system expects to see strings ordered; if one orders to the
    expectations of a human, one has a language-specific sort."

This is generally referred to as natural language sort.

There is a view within the IETF that a BCP comes with the obligatory 
RFC 2119 key words.  This old school "BCP" was a pleasant read.

Regards,
-sm 


From sm@resistor.net  Sat Jun 25 13:01:31 2011
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 F29B011E8125; Sat, 25 Jun 2011 13:01:30 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j43b3PHiZJQl; Sat, 25 Jun 2011 13:01: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 30AF011E811B; Sat, 25 Jun 2011 13:01:29 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p5PK1JQM016002;  Sat, 25 Jun 2011 13:01:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1309032087; bh=4GcySkDCMyAafKlBTMWlkYu4bZeG/AdX6ChDqKDjFXU=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=PJ7FCAUs+95L+lu3mtMiNUWPWRMwUjoVIX0q4pQtbA0I+UANdIC4WeHoBlDkvvfjx T5q8SWV+0bzOqH9KGzmaYkpezV7eat2MAWSVK0K8DyO4/2kQjp0YzhWsKp9Gc3IMgW BfNZ1WkSr9bsa8vnbafeLGv9A87Mo/sJ85ZCqEn0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1309032087; bh=4GcySkDCMyAafKlBTMWlkYu4bZeG/AdX6ChDqKDjFXU=; h=Message-Id:X-Mailer:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=NVUxG11ljvBsdSoqJFik0GmtT/0bv05bTAr6NqpeUEg8GoksGE4uEjsuDPsG7Kinf 6CwbXVo1dFh8jKoIg70dO5FAxNVahNBux0UJ45001sk7NUWwZmN6BJrrryfDiE8/Rv lni7OkKDL2r0L7aoruSdowITlsHVBu6dC67IdYds=
Message-Id: <6.2.5.6.2.20110625123633.02e3ddb8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 25 Jun 2011 13:01:09 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-dnsext-rfc2672bis-dname-22.txt> (Update to DNAME Redirection in the DNS) to Proposed Standard
In-Reply-To: <20110526205629.21816.5196.idtracker@ietfa.amsl.com>
References: <20110526205629.21816.5196.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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: Sat, 25 Jun 2011 20:01:31 -0000

At 13:56 26-05-2011, The IESG wrote:
>The IESG has received a request from the DNS Extensions WG (dnsext) to
>consider the following document:
>- 'Update to DNAME Redirection in the DNS'
>   <draft-ietf-dnsext-rfc2672bis-dname-22.txt> as a 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 2011-06-09. Exceptionally, comments may be

I apologize for sending these comments after the end of the Last Call.

Quoting Section 4:

   'Based on the experience gained in the meantime, [RFC3363] is revised,
    dropping all constraints on having DNAME RRs in these zones.  This
    would greatly improve the manageability of the IPv6 reverse tree.
    These changes are made explicit below.


    In [RFC3363], the paragraph

      "The issues for DNAME in the reverse mapping tree appears to be
      closely tied to the need to use fragmented A6 in the main tree: if
      one is necessary, so is the other, and if one isn't necessary, the
      other isn't either.  Therefore, in moving RFC 2874 to experimental,
      the intent of this document is that use of DNAME RRs in the reverse
      tree be deprecated."

   is to be replaced with the word "DELETED".'

Is the intent to allow the use of DNAME RRs in the reverse tree?  if 
so, replacing the paragraph with the word "DELETED" does not make that clear.

Regards,
-sm 


From presnick@qualcomm.com  Sat Jun 25 14:15:14 2011
Return-Path: <presnick@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 29D4E11E80AC for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 14:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.496
X-Spam-Level: 
X-Spam-Status: No, score=-106.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzluybJViEkQ for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 14:15:13 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 6976411E807F for <ietf@ietf.org>; Sat, 25 Jun 2011 14:15:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1309036513; x=1340572513; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4E064FD6.7060508@qualcomm.com>|Date:=20Sa t,=2025=20Jun=202011=2016:15:02=20-0500|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20John=20Leslie=20<john@jlc.net> |CC:=20SM=20<sm@resistor.net>,=20IETF-Discussion=20list =20<ietf@ietf.org>|Subject:=20Re:=20Why=20ask=20for=20IET F=20Consensus=20on=20a=20WG=20document?|References:=20<19 BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>=09<6.2.5.6.2 .20110625013139.051be2e8@resistor.net>=20<20110625131626. GC56541@verdi>|In-Reply-To:=20<20110625131626.GC56541@ver di>|Content-Type:=20text/plain=3B=20charset=3D"ISO-8859-1 "=3B=20format=3Dflowed|Content-Transfer-Encoding:=207bit |X-Originating-IP:=20[172.30.39.5]; bh=sU+8Ltoo7xz3RnVpXgGdQo6tdvjpor7IjbGjcOrD6S4=; b=hPK7oOqtovSDeTBLEd7tbMU/Dz5a4OdldtrNhAD8F1Ivb79dZg3MPCcb PNthPIFy81KJ9ogpMQ4poKysTmVnNpG32uqxAoRYlMDm7S3lXZ4FjfwYJ OdgthDMpysOi8RFW7rnYsRTa189AOL71KCfWyoZ4oTlIYwINFcY67wnUe s=;
X-IronPort-AV: E=McAfee;i="5400,1158,6388"; a="99890220"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine02.qualcomm.com with ESMTP; 25 Jun 2011 14:15:12 -0700
X-IronPort-AV: E=Sophos;i="4.65,424,1304319600"; d="scan'208";a="77543568"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 25 Jun 2011 14:15:12 -0700
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.270.1; Sat, 25 Jun 2011 14:15:12 -0700
Message-ID: <4E064FD6.7060508@qualcomm.com>
Date: Sat, 25 Jun 2011 16:15:02 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<6.2.5.6.2.20110625013139.051be2e8@resistor.net> <20110625131626.GC56541@verdi>
In-Reply-To: <20110625131626.GC56541@verdi>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: SM <sm@resistor.net>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 21:15:14 -0000

On 6/25/11 8:16 AM, John Leslie wrote:
>     I quite agree that -6to4-to-historic doesn't satisfy such a statement;
> and I don't believe the IESG process for Informational track documents
> gives any assurance of "consensus of the IETF community".
>    

I believe the IESG concluded that, although the document itself is 
Informational, it is moving two RFCs to Historic status, which is a 
Standards Action, and that we would use whatever procedures are 
appropriate to a Standards Action to act on the document. This was the 
third point of my DISCUSS comment and I believe the rest of the IESG 
agreed with me on this point.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From joelja@bogus.com  Sat Jun 25 16:48:14 2011
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 A5EB311E8080 for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 16:48:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.322
X-Spam-Level: 
X-Spam-Status: No, score=-102.322 tagged_above=-999 required=5 tests=[AWL=0.278, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CJBTqjyjMjAK for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 16:48:14 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id CD9A111E808F for <ietf@ietf.org>; Sat, 25 Jun 2011 16:48:13 -0700 (PDT)
Received: from zorch.lan (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5PNm8Xg030192 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 25 Jun 2011 23:48:10 GMT (envelope-from joelja@bogus.com)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4E064FD6.7060508@qualcomm.com>
Date: Sat, 25 Jun 2011 16:48:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D25573C7-7D1A-48C9-B7D8-4CFA81D4434F@bogus.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<6.2.5.6.2.20110625013139.051be2e8@resistor.net> <20110625131626.GC56541@verdi> <4E064FD6.7060508@qualcomm.com>
To: Pete Resnick <presnick@qualcomm.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sat, 25 Jun 2011 23:48:12 +0000 (UTC)
Cc: SM <sm@resistor.net>, John Leslie <john@jlc.net>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2011 23:48:14 -0000

On Jun 25, 2011, at 2:15 PM, Pete Resnick wrote:

> On 6/25/11 8:16 AM, John Leslie wrote:
>>    I quite agree that -6to4-to-historic doesn't satisfy such a =
statement;
>> and I don't believe the IESG process for Informational track =
documents
>> gives any assurance of "consensus of the IETF community".
>>  =20
>=20
> I believe the IESG concluded that, although the document itself is =
Informational, it is moving two RFCs to Historic status, which is a =
Standards Action, and that we would use whatever procedures are =
appropriate to a Standards Action to act on the document. This was the =
third point of my DISCUSS comment and I believe the rest of the IESG =
agreed with me on this point.

Draft 4 which went through wgcl and was  submitted to the iesg had an =
intended status of standards track, at the request of the iesg the =
reguested status was changed to informational. The document is a =
standards action and thus must meet the higher standard to pass iesg =
review regardless of it's intended status... This is entirely consistent =
with historical precident as far as I can tell.=20

> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: =
(858)651-1102
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From barryleiba.mailing.lists@gmail.com  Sat Jun 25 18:56:31 2011
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 CA52211E80F7 for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 18:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qkVxC0vdpM+Y for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 18:56:31 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3CE3911E8099 for <ietf@ietf.org>; Sat, 25 Jun 2011 18:56:31 -0700 (PDT)
Received: by gwb20 with SMTP id 20so2266108gwb.31 for <ietf@ietf.org>; Sat, 25 Jun 2011 18:56:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ywBbncHEGyxefIptykxQ1/GkXY5tKeVAqn3jLsNrETk=; b=sz0ScsgZ38bcPRVBf9CG59SL+yebikEQTOnJY+LxE5NFxOAnXZ3Do9ynytc816uIM8 3KEQO0O0vRC2YTUCwhkha2mCJV6iFIoKVTNs8xDGXKqv3iRv8S+lkLSaIUL/9Rf/Xthi gxDIo0ZzzRuoUnM69RstPPzQ+gmasrpUkb07w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=KtBYitTxOk6792s5BoqUzW4la5OhbFiQzQbpt5/sKgXOsIXfFHZIPDqvmQ4IpevQAE PMLkdEDZU6/YHcO+PTWAoRkjef1nXDWXdPZTgw7wIhQzyRWtCMVnH4rZEiqDJ9wrZvBM bEzfRh0Ltx4Gv/TMcbiUx1TY05D/Q6iGqpHkA=
MIME-Version: 1.0
Received: by 10.236.170.227 with SMTP id p63mr168835yhl.184.1309053389104; Sat, 25 Jun 2011 18:56:29 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.170.15 with HTTP; Sat, 25 Jun 2011 18:56:29 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20110625032041.03c8b498@resistor.net>
References: <20110615213858.9853.22165.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110625032041.03c8b498@resistor.net>
Date: Sat, 25 Jun 2011 21:56:29 -0400
X-Google-Sender-Auth: yDpzCNlspV70lASv93EmPxTj8Mw
Message-ID: <BANLkTikbYYXK2aUJydUffWPb0ibiBH9CYg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified Mail (DKIM) Signatures) to Draft Standard
From: Barry Leiba <barryleiba@computer.org>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jun 2011 01:56:31 -0000

> This document obsoletes RFC 4871 for which there is an IPR disclosure (
> http://datatracker.ietf.org/ipr/1547/ ). =A0As this is a move from Propos=
ed to
> Draft, is a new IPR disclosure required?

The disclosure you cite *is* the new one, which applies to the 4871bis
draft (disclosure 1547 updates disclosure 920, which applied to RFC
4871 only).  Yahoo! will update the disclosure again when 4871bis gets
its own RFC number.

Barry, DKIM working group chair

From barryleiba.mailing.lists@gmail.com  Sat Jun 25 19:07:50 2011
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 4EDCD11E8099 for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 19:07:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.988
X-Spam-Level: 
X-Spam-Status: No, score=-102.988 tagged_above=-999 required=5 tests=[AWL=-0.011, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPswiJm2UXYT for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 19:07:49 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 72A6D11E8096 for <ietf@ietf.org>; Sat, 25 Jun 2011 19:07:48 -0700 (PDT)
Received: by ywp31 with SMTP id 31so2278741ywp.31 for <ietf@ietf.org>; Sat, 25 Jun 2011 19:07:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=yHfQbeKtA96CPEz+V8TvwUbfiGV2ypiV1iV7/CQrukk=; b=wCnreWPBBanumwNiVKEQL3DJGLeTZHfBd1EiYlYGP75jnR8eWtNMNl2H3xXNz9S4Qi m01lvbMAwRjBKR0RadR0jj+QBNBeNYXfAfwE6ZvI4e48+lnNWfaQ6jkJLdwN/m5Yi1sC oT8IWUluUj/FQEIbD+NenuWJHgUxocpKh5feU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=c3uog3Ilo/Jj7sT+ba8dXmntcFiAKaql2jETZhHPRIc0nHm9X4K2zPIcsQNbYMcq+R v3P7pQyFeILrdJ7TKtUOXL8JJRdQj0IWkjxdSRevuAPz97Bmm00GdLM0G6wLi035KAN+ 0ri0gceZcR4cN2ZfK/ybcQtQ0NrNTYlU5Rb78=
MIME-Version: 1.0
Received: by 10.236.80.69 with SMTP id j45mr7910529yhe.50.1309054067869; Sat, 25 Jun 2011 19:07:47 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.170.15 with HTTP; Sat, 25 Jun 2011 19:07:47 -0700 (PDT)
In-Reply-To: <4E04CA58.8070201@mail-abuse.org>
References: <20110623152458.19049.qmail@joyce.lan> <4E04CA58.8070201@mail-abuse.org>
Date: Sat, 25 Jun 2011 22:07:47 -0400
X-Google-Sender-Auth: IMOSCDdOBUXC0pbYIQAGWeX2YWU
Message-ID: <BANLkTiky_8jW65COxswQWsOY+MmYUU7Kvg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified Mail (DKIM) Signatures) to Draft Standard
From: Barry Leiba <barryleiba@computer.org>
To: "ietf@ietf.org" <ietf@ietf.org>, "ietf-dkim@mipassoc.org" <ietf-dkim@mipassoc.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: Sun, 26 Jun 2011 02:07:50 -0000

One final response from me to this, because it is relevant to the IETF
last call:

On Fri, Jun 24, 2011 at 1:33 PM, Douglas Otis <dotis@mail-abuse.org> wrote:
> Complaints from John, Dave, and Barry and others is likely and
> understandably out of fatigue. =A0They just want the process to be over.

No.  We want to get the spec right, and to make sure it specifies the
right normative things.

> Although DKIM will be securely hashing the headers fields which MUST incl=
ude
> the From header, =A0developers are being told they must ignore multiple
> singleton header fields discovered in the process.

No one is saying that anyone "must ignore" anything.  If you think we
are, cite the words in the spec that say that.

What we are saying, and have said repeatedly in many places, is that
it is not the job of the DKIM specification to define the handling of
this normatively.  Developers may certainly handle the presence of
multiple instances of header fields that are not allowed to have
multiple instances... in any manner they like, and we even suggest
(non-normatively) what they might do -- and ignoring the situation
isn't among our suggestions.

But it's not a normative part of the DKIM protocol, and it shouldn't be.

Now I'm done responding to this topic.  The points have all been made,
on both sides.

Barry, DKIM chair

From msk@cloudmark.com  Sat Jun 25 21:42:10 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82C5B11E8086 for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 21:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.604
X-Spam-Level: 
X-Spam-Status: No, score=-103.604 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t0I4PPG7ihEi for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 21:42:09 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 7324811E807C for <ietf@ietf.org>; Sat, 25 Jun 2011 21:42:09 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Sat, 25 Jun 2011 21:42:08 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Sat, 25 Jun 2011 21:42:08 -0700
Subject: RE: Why ask for IETF Consensus on a WG document?
Thread-Topic: Why ask for IETF Consensus on a WG document?
Thread-Index: AcwykPymzaCIxZ4FRdCmPbJ4Dd7FlwBKCGOg
Message-ID: <F5833273385BB34F99288B3648C4F06F134EBC4A0C@EXCH-C2.corp.cloudmark.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org>	<4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <F5833273385BB34F99288B3648C4F06F134EBC49DD@EXCH-C2.corp.cloudmark.com> <20110624170515.GB97941@shinkuro.com>
In-Reply-To: <20110624170515.GB97941@shinkuro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jun 2011 04:42:10 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of A=
ndrew Sullivan
> Sent: Friday, June 24, 2011 10:05 AM
> To: ietf@ietf.org
> Subject: Re: Why ask for IETF Consensus on a WG document?
>=20
> On Fri, Jun 24, 2011 at 09:36:13AM -0700, Murray S. Kucherawy wrote:
>=20
> > By contrast, working groups tend to contain more expertise than may
> > be available in an IETF LC; that's partly why they're formed.  I've
> > never been an AD before, but I imagine I might consider the WG
> > consensus to be at least a little bit more weighty than IETF LC
> > resistance.
>=20
> I rather hope not.  As someone else has argued in this thread, WGs
> tend to be narrowly focussed.  The IETF LC is at least partly, as I
> understand it, to make sure that something which seems an obviously
> good idea to the WG doesn't have all manner of implications that the
> WG perhaps did not consider.

Maybe I'm taking your words too extremely, but if WGs tend to be narrowly f=
ocused, then how can they be reasonably assured of the success of anything =
they produce?  I'm imagining a model here wherein a WG produces documents s=
uffering from a focus that is too narrow, those documents go to IETF LC or =
the IESG, and are invariably shot down because they failed to account for t=
his or that outside of that focus.  It would take a huge number of iteratio=
ns to get anything done.

Rather, I would hope they would have or seek to have enough people in them =
to bring breadth as well as depth, specifically so that they aren't produci=
ng things prone to raise objections.  Perhaps we see this as the role of th=
e AD that is overseeing that particular WG, but that seems a huge burden to=
 put on one person.

For the working groups and documents into which I've put work, I've made a =
point of seeking the breadth so that the reviews of the various directorate=
s, whose comments are influential with the IESG, don't end up stalling publ=
ication.  I would hope this is common practice.

> It seems to me that very strong reaction in the IETF generally to a
> proposal demands convincing counter-arguments from those who support
> the publication.  I refuse to have an opinion about the example under
> discussion, but surely we don't want to build in some preference for
> what the WG says.

I suspect the documents from a WG should carry within them enough instructi=
ve text to include those arguments up-front, so if there's any objection vo=
iced at IETF LC, it's bound to be new material.  The re-hashing of the same=
 arguments made in the WG during IETF LC seems like a waste of time to me u=
nless there are new details available.

-MSK

From evnikita2@gmail.com  Sat Jun 25 21:46:13 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E26F411E8072 for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 21:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.475
X-Spam-Level: 
X-Spam-Status: No, score=-3.475 tagged_above=-999 required=5 tests=[AWL=0.123,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YSEywFgAxXWD for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 21:46:12 -0700 (PDT)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by ietfa.amsl.com (Postfix) with ESMTP id 73E8521F846C for <ietf@ietf.org>; Sat, 25 Jun 2011 21:46:12 -0700 (PDT)
Received: by fxe4 with SMTP id 4so1340553fxe.27 for <ietf@ietf.org>; Sat, 25 Jun 2011 21:46:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=AUMz8ga/vY7xSmy4yV46OOxaGZ4QLmPmuNS6ljOnxKw=; b=fuimU6n8Zd0K8D1msZrAv++6lE2kadk1wHiHjKXcIoqJIBkS1UmHLM6wDfh2utZidH SFTXCoY5l75NnAG4VOqzwGTUmoXD2WANWqbkEuThjikmlR1jLg0fB+Mrwb5+5Z6ucQ+k RtpP3Q9Y5UZflNjVPwk19hiUpUuP2ZVzAsFKs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; b=mkc1TD6uNKhKPPkRj9kW+QDODNKX1fkZLA6pYm4/8q+ExulsbAH+sNQOW9jvNLyxUi 5pZ6pMU6cAYMka+hrCmoPzRkdgtsE3B/w8MOsBSUzy94Fsr45dhGZ51w69jR04M7BTep 2mAEr1VTWY8+GF79Fe0wfePJREcmX6s/SS1xA=
Received: by 10.223.92.146 with SMTP id r18mr6810768fam.135.1309063571271; Sat, 25 Jun 2011 21:46:11 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id b3sm1165563fao.44.2011.06.25.21.46.09 (version=SSLv3 cipher=OTHER); Sat, 25 Jun 2011 21:46:10 -0700 (PDT)
Message-ID: <4E06B9BF.3000200@gmail.com>
Date: Sun, 26 Jun 2011 07:46:55 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-appsawg-rfc3536bis-02.txt>	(Terminology Used in Internationalization in the IETF) to BCP
References: <20110616130400.4851.68985.idtracker@ietfa.amsl.com> <6.2.5.6.2.20110625111608.037bfe18@resistor.net>
In-Reply-To: <6.2.5.6.2.20110625111608.037bfe18@resistor.net>
Content-Type: multipart/alternative; boundary="------------000507090106010407020500"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 04:46:14 -0000

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

25.06.2011 22:27, SM wrote:
> At 06:04 16-06-2011, The IESG wrote:
>> The IESG has received a request from the Applications Area Working Group
>> WG (appsawg) to consider the following document:
>> - 'Terminology Used in Internationalization in the IETF'
>> <draft-ietf-appsawg-rfc3536bis-02.txt> as a BCP
>>
>> 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 2011-06-30. Exceptionally, comments 
>> may be
>
> This document uses an unusual format to show the source of a 
> definition (Section 1.2).  It's clearer (to me) if the document used 
> the regular format for references.
RFC 3536 itself, which this document tries to follow, was Independent 
stream document, whereas we have a number of evidences of unusual 
formatting within such documents.  My personal opinion is that your 
comment is quite reasonable, and this should be fixed. <NONE>s should be 
removed then.
>
> The anchor9 comment in Section 3.2, minus the last sentence, could be 
> folded in as part of the I-D.  Pointing out that the definition is not 
> precisely correct is correct in itself.
Another comment to Section 3.2:

     "and defined in The Unicode Standard
       (Sections 3.9 
<http://tools.ietf.org/html/draft-ietf-appsawg-rfc3536bis-02#section-3.9> and 
16.8 
<http://tools.ietf.org/html/draft-ietf-appsawg-rfc3536bis-02#section-16.8> 
of Version 5.2)"

Such instances of text should be reverified to suit Unicode 6.0 and 
ISO/IEC 10646:2011.

I also don't think definition of BMP should not go in Section 3.2, but 
somewhere else.

As for SM's comment, I'd recommend the draft's 1st paragraph of Section 
3.2 with anchor9 were rewritten to suit the new editions of Standards 
and, as a result, didn't mention transformation formats but rather 
encoding forms.  This is also as ISO/IEC 10646:2011 does.
>
> In Section 4:
>
>   "Code Point order is usually not how any human educated by a local
>    school system expects to see strings ordered; if one orders to the
>    expectations of a human, one has a language-specific sort."
>
> This is generally referred to as natural language sort.
>
> There is a view within the IETF that a BCP comes with the obligatory 
> RFC 2119 key words.  This old school "BCP" was a pleasant read.
My personal opinion is that use of RFC 2119 in glossaries isn't 
appropriate.  As they give definitions, I don't think requirement levels 
are fine here.

An additional comment to Section 8 I didn't expressed before.

     "private use

      ISO/IEC 10646 code points from U+E000 to U+F8FF, U+F0000 to"

I'd better use "private use character" or "private use codepoint" as a 
name of term.

Please also verify many of your Informative references to see whether 
they didn't get obsoleted by other document.  Eg. ISO/IEC TR 
11017:1997(E) has :2003 edition now, etc.

Thanks,
Mykyta Yevstifeyev

>
> Regards,
> -sm
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


--------------000507090106010407020500
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <title></title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    25.06.2011 22:27, SM wrote:
    <blockquote
      cite="mid:6.2.5.6.2.20110625111608.037bfe18@resistor.net"
      type="cite">At 06:04 16-06-2011, The IESG wrote:
      <br>
      <blockquote type="cite">The IESG has received a request from the
        Applications Area Working Group
        <br>
        WG (appsawg) to consider the following document:
        <br>
        - 'Terminology Used in Internationalization in the IETF'
        <br>
        &nbsp; &lt;draft-ietf-appsawg-rfc3536bis-02.txt&gt; as a BCP
        <br>
        <br>
        The IESG plans to make a decision in the next few weeks, and
        solicits
        <br>
        final comments on this action. Please send substantive comments
        to the
        <br>
        <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2011-06-30. Exceptionally,
        comments may be
        <br>
      </blockquote>
      <br>
      This document uses an unusual format to show the source of a
      definition (Section 1.2).&nbsp; It's clearer (to me) if the document
      used the regular format for references.
      <br>
    </blockquote>
    RFC 3536 itself, which this document tries to follow, was
    Independent stream document, whereas we have a number of evidences
    of unusual formatting within such documents.&nbsp; My personal opinion is
    that your comment is quite reasonable, and this should be fixed.&nbsp;
    &lt;NONE&gt;s should be removed then.<br>
    <blockquote
      cite="mid:6.2.5.6.2.20110625111608.037bfe18@resistor.net"
      type="cite">
      <br>
      The anchor9 comment in Section 3.2, minus the last sentence, could
      be folded in as part of the I-D.&nbsp; Pointing out that the definition
      is not precisely correct is correct in itself.
      <br>
    </blockquote>
    Another comment to Section 3.2:<br>
    <br>
    &nbsp; &nbsp; "and defined in The Unicode Standard<br>
    &nbsp;&nbsp;&nbsp; &nbsp; (Sections <a
href="http://tools.ietf.org/html/draft-ietf-appsawg-rfc3536bis-02#section-3.9">3.9</a>
    and <a
href="http://tools.ietf.org/html/draft-ietf-appsawg-rfc3536bis-02#section-16.8">16.8</a>
    of Version 5.2)"<br>
    <br>
    Such instances of text should be reverified to suit Unicode 6.0 and
    ISO/IEC 10646:2011.&nbsp; <br>
    <br>
    I also don't think definition of BMP should not go in Section 3.2,
    but somewhere else.<br>
    <br>
    As for SM's comment, I'd recommend the draft's 1st paragraph of
    Section 3.2 with anchor9 were rewritten to suit the new editions of
    Standards and, as a result, didn't mention transformation formats
    but rather encoding forms.&nbsp; This is also as ISO/IEC 10646:2011 does.<br>
    <blockquote
      cite="mid:6.2.5.6.2.20110625111608.037bfe18@resistor.net"
      type="cite">
      <br>
      In Section 4:
      <br>
      <br>
      &nbsp; "Code Point order is usually not how any human educated by a
      local
      <br>
      &nbsp;&nbsp; school system expects to see strings ordered; if one orders to
      the
      <br>
      &nbsp;&nbsp; expectations of a human, one has a language-specific sort."
      <br>
      <br>
      This is generally referred to as natural language sort.
      <br>
      <br>
      There is a view within the IETF that a BCP comes with the
      obligatory RFC 2119 key words.&nbsp; This old school "BCP" was a
      pleasant read.
      <br>
    </blockquote>
    My personal opinion is that use of RFC 2119 in glossaries isn't
    appropriate.&nbsp; As they give definitions, I don't think requirement
    levels are fine here.<br>
    <br>
    An additional comment to Section 8 I didn't expressed before.<br>
    <br>
    &nbsp;&nbsp;&nbsp; "private use<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp; ISO/IEC 10646 code points from U+E000 to U+F8FF, U+F0000 to"<br>
    <br>
    I'd better use "private use character" or "private use codepoint" as
    a name of term.<br>
    <br>
    Please also verify many of your Informative references to see
    whether they didn't get obsoleted by other document.&nbsp; Eg. ISO/IEC TR
    11017:1997(E) has :2003 edition now, etc.<br>
    <br>
    Thanks,<br>
    Mykyta Yevstifeyev<br>
    <br>
    <blockquote
      cite="mid:6.2.5.6.2.20110625111608.037bfe18@resistor.net"
      type="cite">
      <br>
      Regards,
      <br>
      -sm <br>
      _______________________________________________
      <br>
      Ietf mailing list
      <br>
      <a class="moz-txt-link-abbreviated" href="mailto:Ietf@ietf.org">Ietf@ietf.org</a>
      <br>
      <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a>
      <br>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------000507090106010407020500--

From evnikita2@gmail.com  Sat Jun 25 21:52:32 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 086A821F8476 for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 21:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.478
X-Spam-Level: 
X-Spam-Status: No, score=-3.478 tagged_above=-999 required=5 tests=[AWL=0.121,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fqPuVeaR9+Fi for <ietf@ietfa.amsl.com>; Sat, 25 Jun 2011 21:52:31 -0700 (PDT)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by ietfa.amsl.com (Postfix) with ESMTP id D56DF21F8471 for <ietf@ietf.org>; Sat, 25 Jun 2011 21:52:30 -0700 (PDT)
Received: by fxe4 with SMTP id 4so1342194fxe.27 for <ietf@ietf.org>; Sat, 25 Jun 2011 21:52:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vcg+UuDJcn7zebSwOXguV7cO60Po/Rz2ZwWPwyvYgn4=; b=RTtfh162XUAc7Fore3ZemnyfOraT7AZCgyMsnpT6Weds8q3cHTpPYzBV5fmaZ4cc1R 8FZvOR8tu1vLySXDBy3Pi3Ju0qLIsJTz7WdPUt2tHrHUo1Nc0ReAR5eJXfECVzTJMze9 UAFDqnXom+aIq3R04AF9SN6let1SDRzN1Xtas=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=aFtDRWe3rTHDU3pGhKj8dV6CwLl0m3CduKbZf87guEcO/Pg3heW9PpGA4x4GT8DEZQ wnFYpW0NRnp5vzrlh6H3lytuDnLB2VuHmw+N9AycJf+uuDzmeK05bA/2XzmsTPj0tjBm XmIxSuGE8tvAWNtwa1qYBnWJfb71HUwwTJc7I=
Received: by 10.223.17.141 with SMTP id s13mr6982880faa.23.1309063950078; Sat, 25 Jun 2011 21:52:30 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id w15sm2654940faj.23.2011.06.25.21.52.28 (version=SSLv3 cipher=OTHER); Sat, 25 Jun 2011 21:52:29 -0700 (PDT)
Message-ID: <4E06BB3B.8010005@gmail.com>
Date: Sun, 26 Jun 2011 07:53:15 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Why ask for IETF Consensus on a WG document?
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org>	<6.2.5.6.2.20110625013139.051be2e8@resistor.net>	<20110625131626.GC56541@verdi> <4E064FD6.7060508@qualcomm.com>
In-Reply-To: <4E064FD6.7060508@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jun 2011 04:52:32 -0000

26.06.2011 0:15, Pete Resnick wrote:
> On 6/25/11 8:16 AM, John Leslie wrote:
>>     I quite agree that -6to4-to-historic doesn't satisfy such a 
>> statement;
>> and I don't believe the IESG process for Informational track documents
>> gives any assurance of "consensus of the IETF community".
 From RFC 5741, Section 3.2.2, for Informational documents which were 
Last Called and approved on IETF Stream:

          "It represents the consensus of the IETF community.  It has
          received public review and has been approved for publication by
          the Internet Engineering Steering Group (IESG)."

Note the first sentence.  By approving the Informational RFC which Last 
Call was issued for, IESG claims that IETF consensus exists.  Thia 
assumes Last Call which actually resulted in IETF consensus.  However, 
if Last Call doesn't represent such sort of agreement, IESG just 
shouldn't approve the document.

Mykyta Yevstifeyev
>
> I believe the IESG concluded that, although the document itself is 
> Informational, it is moving two RFCs to Historic status, which is a 
> Standards Action, and that we would use whatever procedures are 
> appropriate to a Standards Action to act on the document. This was the 
> third point of my DISCUSS comment and I believe the rest of the IESG 
> agreed with me on this point.
>
> pr
>


From moore@network-heretics.com  Sun Jun 26 06:10:29 2011
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 BD20C21F8446 for <ietf@ietfa.amsl.com>; Sun, 26 Jun 2011 06:10: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n-VHHqgbCxEc for <ietf@ietfa.amsl.com>; Sun, 26 Jun 2011 06:10:28 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 9168621F843F for <ietf@ietf.org>; Sun, 26 Jun 2011 06:10:28 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 509A5210F2; Sun, 26 Jun 2011 09:10:13 -0400 (EDT)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 26 Jun 2011 09:10:13 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=Q4a1VvGIY6S1XnTMtfyaRtgvo00=; b=Pk12aAg6+5gYKnkOYGG1NTlbs6LFIg6pQFlciT1D23hwu0gxkujecrdIInl6OLRM2BWdJ3No5++hXqLimqKog9SkJciitQ6B0imYhXSD6hmPigexjYfdMnTH3t54QqO5EQOMV2kev3C32cL5KzrwwAJWk/Q/0ZAqjpLLaxRZkTk=
X-Sasl-enc: 5/jrWf8hZX2+59OgbW+nUlTbBEDJgB1EE/JVl+ktbPxJ 1309093812
Received: from [10.59.1.13] (static-71-166-174-114.washdc.east.verizon.net [71.166.174.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 15311443559; Sun, 26 Jun 2011 09:10:10 -0400 (EDT)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F134EBC4A0C@EXCH-C2.corp.cloudmark.com>
Date: Sun, 26 Jun 2011 09:09:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4341E9D2-8452-416F-B010-5370D786DF1D@network-heretics.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <FD6E82FD-2FF9-4B4F-BC94-73E9507F2BAD@vpnc.org>	<4E045B80.7060800@cs.tcd.ie> <AC9A650F-1B8E-44F0-9660-12DEC4D31F27@network-heretics.com> <F5833273385BB34F99288B3648C4F06F134EBC49DD@EXCH-C2.corp.cloudmark.com> <20110624170515.GB97941@shinkuro.com> <F5833273385BB34F99288B3648C4F06F134EBC4A0C@EXCH-C2.corp.cloudmark.com>
To: Murray S. Kucherawy <msk@cloudmark.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jun 2011 13:10:30 -0000

On Jun 26, 2011, at 12:42 AM, Murray S. Kucherawy wrote:

>> I rather hope not.  As someone else has argued in this thread, WGs
>> tend to be narrowly focussed.  The IETF LC is at least partly, as I
>> understand it, to make sure that something which seems an obviously
>> good idea to the WG doesn't have all manner of implications that the
>> WG perhaps did not consider.
>=20
> Maybe I'm taking your words too extremely, but if WGs tend to be =
narrowly focused, then how can they be reasonably assured of the success =
of anything they produce?  I'm imagining a model here wherein a WG =
produces documents suffering from a focus that is too narrow, those =
documents go to IETF LC or the IESG, and are invariably shot down =
because they failed to account for this or that outside of that focus.  =
It would take a huge number of iterations to get anything done.

Quite often it really doesn't matter that a WG is narrowly focused.  =
Consider IP-over-foo documents, for example.  Most of the rest of the =
community doesn't care, or need to care, how a particular IP-over-foo =
mechanism is defined.  IP has been around so long that people generally =
understand what any given IP-over-foo mechanism needs to accomplish.   =
Even where some difficult compromise is needed, the community can =
generally trust the Internet area to make reasonable decisions.=20

But cross-area concerns in IETF have often been handled poorly.   The =
way IETF is structured, it takes careful crafting of a charter and close =
management by a politically skilled and conscientious AD, to get a =
working group whose output is going to affect a wide range of concerns, =
to produce documents that really earn community-wide consensus.   This =
has to be balanced against a very real concern that trying to put too =
many different kinds of people in the same room, so to speak, might =
result in a group that can't agree on anything.  (When I was an AD my =
goal was always to get a broad spectrum of interests in the room, but I =
remember one occasion where the group failed miserably because the =
various factions were completely unwilling to compromise on how to solve =
a problem....in this case because two out of the three factions saw an =
opportunity for a land grab and weren't about to give it up that =
easily.)=20

Without pointing fingers, I think it's fair to say that the results of =
WGs producing documents that really had broad consensus of the =
community, have been mixed.   Some WGs and ADs have done better jobs =
than others.  =20

Note that these are effects of scale.  I remember it being easier to =
look for, and to get consensus on, such issues when active participation =
in IETF was only a few hundred people.  It was certainly easier to track =
what was going on in IETF when there were fewer working groups.

Also, in the distant past there were plenary meetings where each area =
would give a summary of activity in that area for the benefit of all of =
the participants.   Those meetings tended to drag a bit, and take time =
away from WG sessions, so I don't think they were missed very much.  But =
it might be that a stripped down version of such meetings - focusing on =
issues that might affect multiple areas of concern - would benefit the =
community, and be more important than WG sessions.  (I tend to think =
that IETF has too many WGs these days, but of course that just reflects =
the incredible breadth of the Internet today.)

> Rather, I would hope they would have or seek to have enough people in =
them to bring breadth as well as depth, specifically so that they aren't =
producing things prone to raise objections.  Perhaps we see this as the =
role of the AD that is overseeing that particular WG, but that seems a =
huge burden to put on one person.

It is.

> For the working groups and documents into which I've put work, I've =
made a point of seeking the breadth so that the reviews of the various =
directorates, whose comments are influential with the IESG, don't end up =
stalling publication.  I would hope this is common practice.

It's a good idea, and I suspect it's often sufficient, but not always. =20=


>> It seems to me that very strong reaction in the IETF generally to a
>> proposal demands convincing counter-arguments from those who support
>> the publication.  I refuse to have an opinion about the example under
>> discussion, but surely we don't want to build in some preference for
>> what the WG says.
>=20
> I suspect the documents from a WG should carry within them enough =
instructive text to include those arguments up-front, so if there's any =
objection voiced at IETF LC, it's bound to be new material.  The =
re-hashing of the same arguments made in the WG during IETF LC seems =
like a waste of time to me unless there are new details available.

Sometimes it does help if the WG explains why it made particular =
decisions; that can help to reduce re-hashing of those same issues =
during IETF LC.  That doesn't by itself counter the effect of WG bias in =
favor of some concerns and against others, though it might make such =
biases more obvious both to the WG and to the community at large.

In general, I think WGs need to be more aware that their job is to =
produce a document that will earn consensus of the whole community.

Keith


From sm@resistor.net  Sun Jun 26 10:51:35 2011
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 56E7C1F0C48 for <ietf@ietfa.amsl.com>; Sun, 26 Jun 2011 10:51: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18mUjKv+EJYZ for <ietf@ietfa.amsl.com>; Sun, 26 Jun 2011 10:51: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 91C271F0C3B for <ietf@ietf.org>; Sun, 26 Jun 2011 10:51:33 -0700 (PDT)
Received: from subman.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5.Beta0) with ESMTP id p5QHpKWJ007407 for <ietf@ietf.org>; Sun, 26 Jun 2011 10:51:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1309110691; bh=2MW8iJoi6McEijmeVw4gX7PjCu5HS2nz73/ZRU2Ejpw=; h=Message-Id:X-Mailer:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type; b=FT47WuKQRSW3cowUvzhnsHfii9zceNmVabG4dui2QHL/U37XrpztQC6O00mrTzyKy DeirTOrUaPhe27bUo542dgewwv2Dhdy/QvIr2G26wga1za0eUZivdhEqUVC7UU8WSb LCmY09oTN8u9Wch5g+MB9YuO0ZSPkeR9BucbN2IQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1309110691; bh=2MW8iJoi6McEijmeVw4gX7PjCu5HS2nz73/ZRU2Ejpw=; h=Message-Id:X-Mailer:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type; b=qKZETJONCzs+R6jCa0koHMUxFD4n9krIg43ThzzFFJlobJxGx2M1ehOhRGNycCaTu FTFdFieCf8KcOvaDinGSAZwrw6L23xwT8FB5/vORJ2qvQQ21n5OF4IrpK3uQaNOET9 Jl0fZjOs1lnNTU+TjG3Vf31CcOxW98Xc4e4CBDtg=
Message-Id: <6.2.5.6.2.20110626093734.03ab1810@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 26 Jun 2011 10:49:09 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: draft-ietf-v6ops-6to4-to-historic-05 (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
In-Reply-To: <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.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: Sun, 26 Jun 2011 17:51:35 -0000

Hello,

The IANA IPv4/IPv6 Address Space registries currently have the 
following status: RESERVED, LEGACY, ALLOCATED and UNALLOCATED.  Is 
IANA marking the 192.88.99.0/24 prefix and 2002::/16 prefix as 
"deprecated" or is it using an existing status?

BCP 153 lists 192.88.99.0/24 as allocated.  The IANA registry lists 
it as "reserved".

According to the Writeup:

  "This draft represents the intersection of those views -
   rough consensus in the best possible meaning of the phrase."

Will the IESG be using the following text:

   "It has been approved for publication by the Internet
    Engineering Steering Group (IESG)."

for the second paragraph of the "Status of This Memo"?

Regards,
-sm


From joelja@bogus.com  Sun Jun 26 10:56:59 2011
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 A2D8E1F0C48 for <ietf@ietfa.amsl.com>; Sun, 26 Jun 2011 10:56:59 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zZBixL2fy9Va for <ietf@ietfa.amsl.com>; Sun, 26 Jun 2011 10:56:59 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1042E1F0C3B for <ietf@ietf.org>; Sun, 26 Jun 2011 10:56:58 -0700 (PDT)
Received: from zorch.lan (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5QHuu7d049510 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 26 Jun 2011 17:56:57 GMT (envelope-from joelja@bogus.com)
Subject: Re: draft-ietf-v6ops-6to4-to-historic-05 (Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <6.2.5.6.2.20110626093734.03ab1810@resistor.net>
Date: Sun, 26 Jun 2011 10:56:56 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B23FC47-7565-49D0-BED9-D0B2B614AE7A@bogus.com>
References: <20110606162326.26262.53944.idtracker@ietfa.amsl.com> <B2BD84CF-06B2-43C6-9DAC-F51D37F48219@network-heretics.com> <6.2.5.6.2.20110626093734.03ab1810@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 26 Jun 2011 17:56:57 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jun 2011 17:56:59 -0000

On Jun 26, 2011, at 10:49 AM, SM wrote:

> Hello,
>=20
> The IANA IPv4/IPv6 Address Space registries currently have the =
following status: RESERVED, LEGACY, ALLOCATED and UNALLOCATED.  Is IANA =
marking the 192.88.99.0/24 prefix and 2002::/16 prefix as "deprecated" =
or is it using an existing status?
>=20
> BCP 153 lists 192.88.99.0/24 as allocated.  The IANA registry lists it =
as "reserved".

The assumption (vis--a-vis the discussion in the wg on a or lack of =
sunset period (and there's a longish port of the thread on this)) is =
that the prefixs would remain in use for the for the forseeable future. =
there would therefore be no change required to the status of the  =
prefixes.

> According to the Writeup:
>=20
> "This draft represents the intersection of those views -
>  rough consensus in the best possible meaning of the phrase."
>=20
> Will the IESG be using the following text:
>=20
>  "It has been approved for publication by the Internet
>   Engineering Steering Group (IESG)."
>=20
> for the second paragraph of the "Status of This Memo"?
>=20
> Regards,
> -sm
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From marka@isc.org  Sun Jun 26 16:10:40 2011
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 3586B21F852A; Sun, 26 Jun 2011 16:10:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.284
X-Spam-Level: 
X-Spam-Status: No, score=-2.284 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mD7WuqRiEvsv; Sun, 26 Jun 2011 16:10: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 74E4921F852B; Sun, 26 Jun 2011 16:10:36 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id B5AE45F98F6; Sun, 26 Jun 2011 23:10:01 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 26C09216C80; Sun, 26 Jun 2011 23:09:59 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id C8DE41136E12; Mon, 27 Jun 2011 09:09:55 +1000 (EST)
To: Joel Jaeggli <joelja@bogus.com>
From: Mark Andrews <marka@isc.org>
References: <20110625013809.E4B8618C0D0@mercury.lcs.mit.edu> <4E05D05B.7030000@gmail.com> <B91BB6CD-656F-4935-B513-A6225C8F3973@bogus.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
In-reply-to: Your message of "Sat, 25 Jun 2011 12:04:14 MST." <B91BB6CD-656F-4935-B513-A6225C8F3973@bogus.com>
Date: Mon, 27 Jun 2011 09:09:55 +1000
Message-Id: <20110626230955.C8DE41136E12@drugs.dv.isc.org>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jun 2011 23:10:40 -0000

In message <B91BB6CD-656F-4935-B513-A6225C8F3973@bogus.com>, Joel Jaeggli writ
es:
> 
> On Jun 25, 2011, at 5:11 AM, Brian E Carpenter wrote:
> 
> > On 2011-06-25 13:38, Noel Chiappa wrote:
> >>> From: james woodyatt <jhw@apple.com>
> >> 
> >>> I supported 6to4-advisory and strenuously argued against taking up
> >>> 6to4-to-historic.
> >>> ...
> >>> I can see how 6to4-to-historic may divert its intended audience from
> >>> reading the much more important 6to4-advisory draft
> >> 
> >> I must admit, it does seem a little odd to issue two documents, one fixin
> g a
> >> protocol that you're about to declare obsolete with the other...
> > 
> > Not so odd. There are hundreds of millions of hosts out there that attempt
> > to use 6to4 by default, and (probably) thousands of relay routers that
> > attempt to support such users. Those boxes will be around for years, and a
> re
> > the target for the -advisory draft, regardless of the deprecation.
> 
> the very fact that the devices are largely unmanaged, means that if you don'
> t want to break them worse then they already are that you have continue to s
> upport them until they age out of the network.

And historic just told CISCO and Juniper to stop supporting 6to4 in their
big iron.  The very boxes that need to remain to the end supporting 6to4
because they are managed boxes.

> 
> >   Brian
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> > 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From warren@kumari.net  Sun Jun 26 19:36:29 2011
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 EA10911E8095; Sun, 26 Jun 2011 19:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.392
X-Spam-Level: 
X-Spam-Status: No, score=-101.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wkk37XxxuGNm; Sun, 26 Jun 2011 19:36:29 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 5965211E808B; Sun, 26 Jun 2011 19:36:26 -0700 (PDT)
Received: from [10.91.2.134] (unknown [203.176.188.50]) by vimes.kumari.net (Postfix) with ESMTPSA id 8DEA41B4014B; Sun, 26 Jun 2011 22:36:21 -0400 (EDT)
From: Warren Kumari <warren@kumari.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Operations Directorate Review of draft-ietf-soc-overload-design 
Date: Mon, 27 Jun 2011 10:36:05 +0800
Message-Id: <19D94B7B-4D67-4D2C-9517-412ABC6A94F1@kumari.net>
To: ops-dir@ietf.org, ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: draft-ietf-soc-overload-design@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, 27 Jun 2011 02:36:30 -0000

I reviewed the document draft-ietf-soc-overload-design in general
and for its operational impact.
=20
Do not be alarmed -- Operations directorate reviews are solicited =
primarily to help=20
the Area Directors improve their efficiency, particularly when preparing =
for IESG
telechats, and allowing them to focus on documents requiring their =
attention
and spend less time on the trouble-free ones.

Improving the documents is important, but clearly a secondary purpose.
A third purpose is to broaden the OpsDir reviewers' exposure to work =
going
on in other parts of the IETF.
=20
Reviews from OpsDir members do not in and of themselves cause the IESG =
to
raise issue with a document. The reviews may, however, convince =
individual
IESG members to raise concern over a particular document requiring =
further
discussion. The reviews, particularly those conducted in last call and
earlier, may also help the document editors improve their documents.
=20
--
=20
Review Summary:=20
Intended status: Informational

This document discusses models and design considerations for a SIP =
overload control mechanism.
As such it doesn't document in much detail exactly how the mechanisms =
will be implemented, and so many of the standard Ops Directorate =
questions are not hugely relevant.
=20
Is the document readable?

Yes.

Is the document class appropriate?=20

Yes.

Is the problem well stated?=20

Yes.


Are there nits?

No:
No issues found here.

     Summary: 0 errors (**), 0 warnings (=3D=3D), 1 comment (--).
(comment is because of date!)

Is the problem really a problem?=20

Yes. (Taken as a given that devices can become overloaded, solving this =
is necessary).

Does the document consider existing solutions?

Yes (I am not a SIP geek and there may be other solutions that were not =
discussed).

Does the solution break existing technology?

No -- well, not to the best of my knowledge.
SIP is Dark Magic to me, and I don't know many of the existing =
technologies, but it all sounds benign!

Does the solution preclude future activity?

No.=20
=20
Is the solution sufficiently configurable?

Yes.=20

Can performance be measured? How?
Yes -- integral to the design of the system is monitoring for overload. =
The document could possibly have better explained that this information =
should be exposed for monitoring purposes, but the other docs are =
probably a better place for this.

Does the solution scale well?

Dealing with overload is very much required for scaling (basically the =
point of the doc!).

Is Security Management discussed?=20

Yes, very well -- the Security Considerations is long, clear and well =
thought out
By dealing with / responding to overload, DoS situation can be avoided.
More specific information will be discussed in documents specific to the =
overload feedback mechanisms.

--=

From ichiroumakino@gmail.com  Mon Jun 27 01:35:32 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62D8311E807A for <ietf@ietfa.amsl.com>; Mon, 27 Jun 2011 01:35:32 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uCfn1K8V-UL8 for <ietf@ietfa.amsl.com>; Mon, 27 Jun 2011 01:35:32 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id A32D011E8094 for <ietf@ietf.org>; Mon, 27 Jun 2011 01:35:31 -0700 (PDT)
Received: by wwe5 with SMTP id 5so2992757wwe.13 for <ietf@ietf.org>; Mon, 27 Jun 2011 01:35:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=z+t57qFe5xu6O1mq/SXG464MBXHSeo6e2Q74iP8RLl0=; b=c9hgF8qjL7GAk8pzAc865b9j+bB/si7T8Dv4Zuso3KZV5+i7MHykichLkYVvZsFeqg Qq3r9ZKDfCw9ARuBsVIZbjDKjzx1geoEGf6Oms7U3l7fjp4Of8Mn8PfQXnNXST1FshfO FJlPO3J251oNtXLv/X33wOolM9ddJLN0d31qE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=hnJg/YCYujmdO3cx34IcLb85bLPJPrUFumShJ9bUnAJAd8lXVYqV30eMhm+IdW32tJ tQxcv9ItJfl0XPuWWU5z7RJkSTn2RFOaUzI510kRb1qfO7o8+rP15Zj/Rf/rytT0HV0l ZMD082+4Tsb1D3MO5OcLGMn32Q8VOsgiDht0c=
Received: by 10.227.28.161 with SMTP id m33mr5219648wbc.107.1309163730612; Mon, 27 Jun 2011 01:35:30 -0700 (PDT)
Received: from dhcp-10-61-101-219.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id o19sm3907231wbh.38.2011.06.27.01.35.27 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 27 Jun 2011 01:35:29 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: one data point regarding native IPv6 support
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <20110624164132.22FF318C0C1@mercury.lcs.mit.edu>
Date: Mon, 27 Jun 2011 10:35:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <10A40227-EB65-4E4B-A0FC-E4B0B0CCC116@employees.org>
References: <20110624164132.22FF318C0C1@mercury.lcs.mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 08:35:32 -0000

Noel,

>> it seems that a lot of the issues could be mitigated by simple
>> connectivity test.
>=20
> Well, IPv6 Neighbour Discovery is just the thing. I gather it's turned =
off
> on 6to4 links, which in retrospect was probably a mistake. I would
> recommend that it be turned on, but apparently the WG decided against
> making that recommendation in the '6to4 fixes' document?

IPv6 Neighbour Discovery requires a multicast capable link and support =
for link-local addresses. a 6to4 link doesn't support either.
NUD could be made to work, but I don't think NUD is any better than any =
other connectivity test. e.g. a "BFD echo" style one as specified for =
6rd.

cheers,
Ole=

From ron.even.tlv@gmail.com  Mon Jun 27 02:06:29 2011
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 9057D21F864F; Mon, 27 Jun 2011 02:06:29 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VKi2Qhk1PIxP; Mon, 27 Jun 2011 02:06:28 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2928721F863F; Mon, 27 Jun 2011 02:06:27 -0700 (PDT)
Received: by wyj26 with SMTP id 26so3451560wyj.31 for <multiple recipients>; Mon, 27 Jun 2011 02:06:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=BTQPDYnwyM0NrMmiL0kWtbdoD2z3A1Zf7U+Lb+xVpkE=; b=jHEem9vd+0gz0ggja1FSwKh8kW/mfENTWysWs8oiFe+E5+JlgZq5CrIs8QhBW97EIF x1Sk+NwSaM3UQ78speHXzsf3o+R9jMItA9r4XQ1CI3xOLqfwxwO/mx3XvWN0DGqzDF0e V0ZsTHWtdn6YX7JmN37hz78XAaLxllutcKFsk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; b=vVLIEkvp2aWnnrIQ1aKewqOaAPcD967+X4AnvViW4LLWsTR2j+Adr6jug+Q/PT8M2r XDuNgxHs78/IbBrVDlTCXrlSb49Z1ndOPQWDBBsGzcA9Pggc3b1YHmS1D87W6FHb3CP+ XpNTDminmdRiKKzvopb9mIg8vB1m+Oj1ScnXM=
Received: by 10.227.165.202 with SMTP id j10mr5345408wby.18.1309165586884; Mon, 27 Jun 2011 02:06:26 -0700 (PDT)
Received: from windows8d787f9 ([109.64.7.173]) by mx.google.com with ESMTPS id gg16sm556906wbb.17.2011.06.27.02.06.23 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 27 Jun 2011 02:06:25 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-roll-of0.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-roll-of0-14
Date: Mon, 27 Jun 2011 12:04:20 +0300
Message-ID: <4e084811.90d1e30a.3d19.222f@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000F_01CC34C2.5BAF80F0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acw0qTMmkmCJF09OQ7OyctDJhB8Jjw==
Content-Language: en-us
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: Mon, 27 Jun 2011 09:06:29 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_000F_01CC34C2.5BAF80F0
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-roll-of0-14

Reviewer: Roni Even

Review Date:2011-6-27

IETF LC End Date: 2011-7-4

IESG Telechat date: 

 

Summary: This draft is ready for publication as a standard track RFC.
Please note the Nits.

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

1.       The "requirement language" is usually in the terminology section
and not with the abstract.

2.       In section 7.2 first paragraph replace "tthat" with "that"

3.       In section 7.2 third paragraph replace "he current Version Number"
with "the ."

 


------=_NextPart_000_000F_01CC34C2.5BAF80F0
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 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family: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;}
@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:1157764602;
	mso-list-type:hybrid;
	mso-list-template-ids:1213479206 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-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
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>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
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=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-=
roll-of0-14<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:2011&#8211;6&#8211;27<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: 2011&#8211;7&#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 ready for publication as a standard track</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>RFC.&nbsp; =
Please note the Nits.<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"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:<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 =
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"'>The =
&#8220;requirement language&quot; is usually in the terminology section =
and not with the abstract.<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'>2.<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"'>In section =
7.2 first paragraph replace &#8220;tthat&#8221; with =
&#8220;that&#8221;<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'>3.<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"'>In section =
7.2 third paragraph replace &#8220;he </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>current =
Version Number&#8221; with &#8220;the &#8230;&#8221;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_000F_01CC34C2.5BAF80F0--


From robmcm@microsoft.com  Fri Jun 24 12:08:24 2011
Return-Path: <robmcm@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2845011E80FB; Fri, 24 Jun 2011 12:08:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.984
X-Spam-Level: 
X-Spam-Status: No, score=-6.984 tagged_above=-999 required=5 tests=[AWL=0.483,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8NHpbMcXK8ze; Fri, 24 Jun 2011 12:08:23 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id 5DB4711E80F1; Fri, 24 Jun 2011 12:08:23 -0700 (PDT)
Received: from TK5EX14HUBC105.redmond.corp.microsoft.com (157.54.80.48) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 24 Jun 2011 12:08:23 -0700
Received: from AM1EHSOBE006.bigfish.com (157.54.51.112) by mail.microsoft.com (157.54.80.48) with Microsoft SMTP Server (TLS) id 14.1.289.8; Fri, 24 Jun 2011 12:08:22 -0700
Received: from mail93-am1-R.bigfish.com (10.3.201.246) by AM1EHSOBE006.bigfish.com (10.3.204.26) with Microsoft SMTP Server id 14.1.225.22; Fri, 24 Jun 2011 19:08:20 +0000
Received: from mail93-am1 (localhost.localdomain [127.0.0.1])	by mail93-am1-R.bigfish.com (Postfix) with ESMTP id 4CE7B17980DB; Fri, 24 Jun 2011 19:08:20 +0000 (UTC)
X-SpamScore: -35
X-BigFish: PS-35(zz9371M111aL4015L542Mzz1202h1082kzz1033IL8275bh8275dhz31h2a8h668h839h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: CIP:157.55.61.146; KIP:(null); UIP:(null); IPV:SKI; H:CH1PRD0302HT006.namprd03.prod.outlook.com; R:internal; EFV:INT
Received-SPF: softfail (mail93-am1: transitioning domain of microsoft.com does not designate 157.55.61.146 as permitted sender) client-ip=157.55.61.146; envelope-from=robmcm@microsoft.com; helo=CH1PRD0302HT006.namprd03.prod.outlook.com ; .outlook.com ; 
Received: from mail93-am1 (localhost.localdomain [127.0.0.1]) by mail93-am1 (MessageSwitch) id 130894250069656_30765; Fri, 24 Jun 2011 19:08:20 +0000 (UTC)
Received: from AM1EHSMHS018.bigfish.com (unknown [10.3.201.253])	by mail93-am1.bigfish.com (Postfix) with ESMTP id 02A40F8804B; Fri, 24 Jun 2011 19:08:20 +0000 (UTC)
Received: from CH1PRD0302HT006.namprd03.prod.outlook.com (157.55.61.146) by AM1EHSMHS018.bigfish.com (10.3.206.21) with Microsoft SMTP Server (TLS) id 14.1.225.22; Fri, 24 Jun 2011 19:08:20 +0000
Received: from CH1PRD0302MB131.namprd03.prod.outlook.com ([169.254.11.234]) by CH1PRD0302HT006.namprd03.prod.outlook.com ([10.28.29.125]) with mapi id 14.01.0225.056; Fri, 24 Jun 2011 19:08:18 +0000
From: Robert McMurray <robmcm@microsoft.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>,  "ftpext@ietf.org" <ftpext@ietf.org>
Subject: RE: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File Transfer Protocol	HOST Command for Virtual Hosts) to Proposed	Standard
Thread-Topic: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File Transfer Protocol	HOST Command for Virtual Hosts) to Proposed	Standard
Thread-Index: AQHMMqEmcdEZfuFND0GouWGSZJApmpTM3a+w
Date: Fri, 24 Jun 2011 19:08:18 +0000
Message-ID: <01AA9EC92749BF4894AC2B3039EA4A2C1949D19E@CH1PRD0302MB131.namprd03.prod.outlook.com>
References: <20110616130503.4854.51928.idtracker@ietfa.amsl.com> <4E04C0CE.1030807@gmail.com>
In-Reply-To: <4E04C0CE.1030807@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.28.29.74]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: CH1PRD0302HT006.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GMAIL.COM$RO%2$TLS%6$FQDN%131.107.125.5$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%131.107.125.5$TlsDn%
X-OriginatorOrg: microsoft.com
X-CrossPremisesHeadersPromoted: TK5EX14HUBC105.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC105.redmond.corp.microsoft.com
X-Mailman-Approved-At: Mon, 27 Jun 2011 08:04:10 -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 Jun 2011 19:08:24 -0000

Thanks, Mykyta.

Section 3.3 already addresses that scenario in the second paragraph - and t=
he server behaviors are exactly what you were suggesting:

   As discussed in section 3 of this document, if a HOST command is sent
   after a user has been authenticated the server SHOULD do one of the
   following:

   a.  Send a 503 reply for an invalid sequence of commands.

   b.  Treat the HOST command as though a REIN command was sent and
       reset the user-PI to the state that existed after the previous
       HOST command was sent and before the user had been authenticated,
       and then return the appropriate reply for the HOST command.

Thanks again!

Robert McMurray

-----Original Message-----
From: Mykyta Yevstifeyev [mailto:evnikita2@gmail.com]=20
Sent: Friday, June 24, 2011 9:53 AM
To: ietf@ietf.org; ftpext@ietf.org
Subject: Re: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File Tr=
ansfer Protocol HOST Command for Virtual Hosts) to Proposed Standard

Hello,

This document is well written; I'm strongly for its publication on Standard=
s Track.  I have an only remark.  This document doesn't seem to mention wha=
t is the behavior of the server if HOST command is sent after one HOST has =
already been sent.  Eg.

C> HOST example.com
S> 220 Host OK
C> USER foo
S> 331 Specify password
C> PASS bar
S> 230 Logged in
C> HOST example.org
S> ????

I suppose the server may treat this as REIN and then switching to specified=
 host, if the user is authenticated, and just switch to such host if the us=
er isn't already logged in.  Another option is sending 503 reply, as invali=
d sequence of commands.

Thanks,
Mykyta Yevstifeyev



From ben@nostrum.com  Fri Jun 24 15:20:17 2011
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 D7E4711E80ED; Fri, 24 Jun 2011 15:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.471
X-Spam-Level: 
X-Spam-Status: No, score=-102.471 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LwUOLsttYiwh; Fri, 24 Jun 2011 15:20:12 -0700 (PDT)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by ietfa.amsl.com (Postfix) with ESMTP id 6454211E80E7; Fri, 24 Jun 2011 15:20:12 -0700 (PDT)
Received: from dn3-227.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p5OMItYG061207 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 Jun 2011 17:18:56 -0500 (CDT) (envelope-from ben@nostrum.com)
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <86B91666-359A-416F-8D22-A99F2A759BE9@nist.gov>
Date: Fri, 24 Jun 2011 17:18:55 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <16FAD31E-CC87-4110-A43F-4DFBD46536A5@nostrum.com>
References: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com> <BANLkTin0xTnTpA79PL12UcBADQj-A8U_GQ@mail.gmail.com> <42646542-15D4-4ABF-A65F-A0F3361D049A@nostrum.com> <86B91666-359A-416F-8D22-A99F2A759BE9@nist.gov>
To: Scott Rose <scott.rose@nist.gov>
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Mon, 27 Jun 2011 08:04:10 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The 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, 24 Jun 2011 22:20:17 -0000

Thanks!

This version resolves all of my comments, with the exception that while =
the text now says the draft updates DNAME, the header still says it =
obsoletes RFC 2672. Is that the intent?

Thanks!

Ben.

On Jun 24, 2011, at 10:16 AM, Scott Rose wrote:

> FYI:
> A new version (-23) of the dname-bis draft has been posted with the =
two sections re-added (resolver algorithm and examples of DNAME use). I =
haven't heard any comments from the DNSEXT WG on it, but it was only =
just posted.
>=20
> Scott=20
>=20
> On Jun 8, 2011, at 5:50 PM, Ben Campbell wrote:
>=20
>> Thanks for the response! Comments below, eliding the bits I think =
need no further comment.
>>=20
>> On Jun 8, 2011, at 12:11 PM, Scott Rose wrote:
>>=20
>>> Perhaps the document should only update RFC 2672 instead of =
obsoleting it? =20
>>=20
>> That would resolve my concern, if it fits with the intent of the work =
group.
>>=20
>>=20
>>>=20
>>> As for the nits:
>>>=20
>>>=20
>>> On Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <ben@nostrum.com> =
wrote: =20
>>>=20
>>=20
>> [...]
>>=20
>>> Yes, will correct.
>>>=20
>>> -- ..., 7th paragraph: "...replaced with the word "DELETED"."
>>>=20
>>> Won't that just leave the word "deleted" hanging on page without =
explanation? Wouldn't it be better to just simply delete it?
>>>=20
>>>=20
>>> Maybe, but I think the logic was that if there is some text there =
(just something), it can be cleanly referenced (i.e. "DELETED =
[RFCXXXX]")if someone is making a revised version of the RFC for some =
purpose.  Purely deleting it accomplishes the task, but this provides a =
good "hook" for a paper trail.
>>>=20
>>=20
>> Okay. On reflection, it's not like we really render the updates the =
old RFC documents.
>>=20
>>=20
>>> Scott
>>> _______________________________________________
>>> Gen-art mailing list
>>> Gen-art@ietf.org
>>> https://www.ietf.org/mailman/listinfo/gen-art
>>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Scott Rose
> NIST
> scott.rose@nist.gov
> +1 301-975-8439
> Google Voice: +1 571-249-3671
> http://www.dnsops.gov/
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20


From john@jck.com  Sat Jun 25 07:06:38 2011
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1BEE21F8554; Sat, 25 Jun 2011 07:06: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sz-sR9qreW9x; Sat, 25 Jun 2011 07:06:38 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by ietfa.amsl.com (Postfix) with ESMTP id 1A65A21F8553; Sat, 25 Jun 2011 07:06:38 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1QaTVF-000OcF-Ry; Sat, 25 Jun 2011 10:06:29 -0400
Date: Sat, 25 Jun 2011 10:06:29 -0400
From: John C Klensin <john@jck.com>
To: Christian Huitema <huitema@microsoft.com>, james woodyatt <jhw@apple.com>,  Joel Jaeggli <joelja@bogus.com>
Subject: RE: Why ask for IETF Consensus on a WG document?
Message-ID: <82B5D703819AADB07BC928C3@JCK-EEE10>
In-Reply-To: <22F6318E46E26B498ABC828879B08D4F17B56C@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <19BA5B79-DC0B-4409-91A2-12FA94AE9523@vpnc.org> <4E03DDF8.1040806@stpeter.im> <4E03E9A9.2000300@gmail.com> <E1E0A4DF2DA94C08DB4F75B6@[192.168.1.3]> <A56C5B21-0BB4-4A96-AA21-905C03CB2F92@apple.com> <178F55FB-B369-4AE7-AC0E-A1AF98616866@network-heretics.com> <567816BB-6747-402F-9D5C-A99F558A2FB4@bogus.com> <EE0BFEFD-DD51-4A87-9E31-9984279BED23@apple.com> <22F6318E46E26B498ABC828879B08D4F17B56C@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.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-Mailman-Approved-At: Mon, 27 Jun 2011 08:04:10 -0700
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: Sat, 25 Jun 2011 14:06:38 -0000

+1


--On Saturday, 25 June, 2011 04:18 +0000 Christian Huitema
<huitema@microsoft.com> wrote:

> It seems that we have wide consensus to publish the advisory
> document, not so much for the "6to4 historic" part. Can we
> just publish the advisory and be done with this thread?





From kathleen.moriarty@emc.com  Mon Jun 27 06:50:52 2011
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 EB28421F85F9; Mon, 27 Jun 2011 06:50:51 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bmrd7l6Uu06T; Mon, 27 Jun 2011 06:50:50 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 7D2F821F86D3; Mon, 27 Jun 2011 06:12:13 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p5RD9MZW006068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jun 2011 09:09:23 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 27 Jun 2011 09:09:08 -0400
Received: from mxhub07.corp.emc.com (mxhub07.corp.emc.com [128.221.46.115]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p5RD8kaG032761; Mon, 27 Jun 2011 09:08:46 -0400
Received: from mx06a.corp.emc.com ([169.254.1.199]) by mxhub07.corp.emc.com ([128.221.46.115]) with mapi; Mon, 27 Jun 2011 09:08:46 -0400
From: <kathleen.moriarty@emc.com>
To: <gen-art@ietf.org>, <draft-li-pwe3-ms-pw-pon.all@tools.ietf.org>, <ietf@ietf.org>
Date: Mon, 27 Jun 2011 09:08:45 -0400
Subject: GEN-ART review for draft-li-pwe3-ms-pw-pon-03 
Thread-Topic: GEN-ART review for draft-li-pwe3-ms-pw-pon-03 
Thread-Index: Acw0y1h5B+aMJLm8RXy6PuQpHJ/2KA==
Message-ID: <AE31510960917D478171C79369B660FA0E0325329B@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Mon, 27 Jun 2011 08:04:10 -0700
Cc: lihy@huawei.com, robin@huawei.com, adrian.farrel@huawei.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, 27 Jun 2011 13:50: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-li-pwe3-ms-pw-pon-03
Reviewer:  Kathleen Moriarty
Review Date: June 27, 2011
IETF LC End Date:
IESG Telechat date: June 28, 2011

Summary:  This document is ready with nits.

Major issues:

Minor issues:

Nits/editorial comments:

The acronym PW is used in the abstract and is not defined until the introdu=
ction.  Please fix.

Paragraph 7 of the introduction, last sentence:
Change from "Besides coding and
   maintenance of these new protocols, a much powerful CPU and more
   memory are also necessary for them to run smoothly."
To: "Besides coding and
   maintenance of these new protocols, a much more powerful CPU and more
   memory are also necessary for them to run smoothly."
If you do not want to repeat the word more, consider the word additional to=
 replace the second instance of more.

Last paragraph of Section 4:
Consider changing from: "OMCI supports the configuration of a number of PW =
types including
   TDM, ATM, and Ethernet, and the protocol can also be used to allow
   the ONU to notify the OLT of the status of the AC."
To: "OMCI supports the configuration of a number of PW types including
   TDM, ATM, and Ethernet.  The protocol can also be used to allow
   the ONU to notify the OLT of the status of the AC."






From scott.rose@nist.gov  Mon Jun 27 07:16:04 2011
Return-Path: <scott.rose@nist.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 594A721F8590 for <ietf@ietfa.amsl.com>; Mon, 27 Jun 2011 07:16: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cgKZWEVOQWSG for <ietf@ietfa.amsl.com>; Mon, 27 Jun 2011 07:16:00 -0700 (PDT)
Received: from smtp.nist.gov (rimp1.nist.gov [129.6.16.226]) by ietfa.amsl.com (Postfix) with ESMTP id 2833121F855B for <ietf@ietf.org>; Mon, 27 Jun 2011 07:15:59 -0700 (PDT)
Received: from 107-140.antd.nist.gov (107-140.antd.nist.gov [129.6.140.107]) by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id p5REFlid028080; Mon, 27 Jun 2011 10:15:49 -0400
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-dnsext-rfc2672bis-dname-22
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Scott Rose <scott.rose@nist.gov>
In-Reply-To: <16FAD31E-CC87-4110-A43F-4DFBD46536A5@nostrum.com>
Date: Mon, 27 Jun 2011 10:15:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE447DE4-CD85-4386-9C97-2008524D2402@nist.gov>
References: <4E75C85C-5086-4951-867D-618C6CE13EDC@nostrum.com> <BANLkTin0xTnTpA79PL12UcBADQj-A8U_GQ@mail.gmail.com> <42646542-15D4-4ABF-A65F-A0F3361D049A@nostrum.com> <86B91666-359A-416F-8D22-A99F2A759BE9@nist.gov> <16FAD31E-CC87-4110-A43F-4DFBD46536A5@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1084)
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: scott.rose@nist.gov
X-Mailman-Approved-At: Mon, 27 Jun 2011 08:04:10 -0700
Cc: The 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 Jun 2011 14:16:04 -0000

Ben,
Are you referring to the title ("Update to the DNAME...")?  Then yes, =
that could be confusing - that was missed in the revision.

Would trimming the title to the shorter "DNAME Redirection in the DNS" =
fix that?  It's the simplest fix.

Scott

On Jun 24, 2011, at 6:18 PM, Ben Campbell wrote:

> Thanks!
>=20
> This version resolves all of my comments, with the exception that =
while the text now says the draft updates DNAME, the header still says =
it obsoletes RFC 2672. Is that the intent?
>=20
> Thanks!
>=20
> Ben.
>=20
> On Jun 24, 2011, at 10:16 AM, Scott Rose wrote:
>=20
>> FYI:
>> A new version (-23) of the dname-bis draft has been posted with the =
two sections re-added (resolver algorithm and examples of DNAME use). I =
haven't heard any comments from the DNSEXT WG on it, but it was only =
just posted.
>>=20
>> Scott=20
>>=20
>> On Jun 8, 2011, at 5:50 PM, Ben Campbell wrote:
>>=20
>>> Thanks for the response! Comments below, eliding the bits I think =
need no further comment.
>>>=20
>>> On Jun 8, 2011, at 12:11 PM, Scott Rose wrote:
>>>=20
>>>> Perhaps the document should only update RFC 2672 instead of =
obsoleting it? =20
>>>=20
>>> That would resolve my concern, if it fits with the intent of the =
work group.
>>>=20
>>>=20
>>>>=20
>>>> As for the nits:
>>>>=20
>>>>=20
>>>> On Tue, Jun 7, 2011 at 6:35 PM, Ben Campbell <ben@nostrum.com> =
wrote: =20
>>>>=20
>>>=20
>>> [...]
>>>=20
>>>> Yes, will correct.
>>>>=20
>>>> -- ..., 7th paragraph: "...replaced with the word "DELETED"."
>>>>=20
>>>> Won't that just leave the word "deleted" hanging on page without =
explanation? Wouldn't it be better to just simply delete it?
>>>>=20
>>>>=20
>>>> Maybe, but I think the logic was that if there is some text there =
(just something), it can be cleanly referenced (i.e. "DELETED =
[RFCXXXX]")if someone is making a revised version of the RFC for some =
purpose.  Purely deleting it accomplishes the task, but this provides a =
good "hook" for a paper trail.
>>>>=20
>>>=20
>>> Okay. On reflection, it's not like we really render the updates the =
old RFC documents.
>>>=20
>>>=20
>>>> Scott
>>>> _______________________________________________
>>>> Gen-art mailing list
>>>> Gen-art@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/gen-art
>>>=20
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Scott Rose
>> NIST
>> scott.rose@nist.gov
>> +1 301-975-8439
>> Google Voice: +1 571-249-3671
>> http://www.dnsops.gov/
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>=20
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Scott Rose
NIST
scott.rose@nist.gov
+1 301-975-8439
Google Voice: +1 571-249-3671
http://www.dnsops.gov/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


From joelja@bogus.com  Mon Jun 27 10:26:03 2011
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 EFB3011E8117; Mon, 27 Jun 2011 10:26:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.284
X-Spam-Level: 
X-Spam-Status: No, score=-102.284 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8XK4owSAlb2; Mon, 27 Jun 2011 10:26:03 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 609BF11E810B; Mon, 27 Jun 2011 10:26:03 -0700 (PDT)
Received: from [172.16.24.51] ([12.184.108.202]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p5RHPtDt075472 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 27 Jun 2011 17:25:57 GMT (envelope-from joelja@bogus.com)
Subject: Re: Why ask for IETF Consensus on a WG document?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <20110626230955.C8DE41136E12@drugs.dv.isc.org>
Date: Mon, 27 Jun 2011 10:25:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D67BAD3-45C1-47AC-BF42-9CEFA7C4A6FC@bogus.com>
References: <20110625013809.E4B8618C0D0@mercury.lcs.mit.edu> <4E05D05B.7030000@gmail.com> <B91BB6CD-656F-4935-B513-A6225C8F3973@bogus.com> <20110626230955.C8DE41136E12@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 27 Jun 2011 17:25:59 +0000 (UTC)
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2011 17:26:04 -0000

On Jun 26, 2011, at 4:09 PM, Mark Andrews wrote:
> In message <B91BB6CD-656F-4935-B513-A6225C8F3973@bogus.com>, Joel =
Jaeggli writ
> es:
>>=20
>> On Jun 25, 2011, at 5:11 AM, Brian E Carpenter wrote:
>>>=20
>>> Not so odd. There are hundreds of millions of hosts out there that =
attempt
>>> to use 6to4 by default, and (probably) thousands of relay routers =
that
>>> attempt to support such users. Those boxes will be around for years, =
and a
>> re
>>> the target for the -advisory draft, regardless of the deprecation.
>>=20
>> the very fact that the devices are largely unmanaged, means that if =
you don'
>> t want to break them worse then they already are that you have =
continue to s
>> upport them until they age out of the network.
>=20
> And historic just told CISCO and Juniper to stop supporting 6to4 in =
their
> big iron.  The very boxes that need to remain to the end supporting =
6to4
> because they are managed boxes.

I think this argument is somewhat orthogonal to the problem of =
supporting end-systems... However if your want to explore it, think the =
author is probably in a position to interpret the draft on behalf of his =
company. Juniper doesn't support 6to4 on the big iron.

>>=20
>>>  Brian
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>=20


From randy@qualcomm.com  Mon Jun 27 12:26:50 2011
Return-Path: <randy@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 6B79111E8141 for <ietf@ietfa.amsl.com>; Mon, 27 Jun 2011 12:26:50 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id soaI0nIf05vB for <ietf@ietfa.amsl.com>; Mon, 27 Jun 2011 12:26:49 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id AA1A811E8140 for <ietf@ietf.org>; Mon, 27 Jun 2011 12:26:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1309202809; x=1340738809; h=message-id:x-mailer:date:to:from:subject:mime-version: content-type:x-random-sig-tag:x-originating-ip; z=Message-ID:=20<p0624060cca2e8707f11a@[172.10.100.118]> |X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date:=20Mon,=202 7=20Jun=202011=2012:19:30=20-0700|To:=20<ietf@ietf.org> |From:=20Randall=20Gellens=20<randy@qualcomm.com> |Subject:=20Anyone=20need=20a=20room=20at=20the=20Hilton? |MIME-Version:=201.0|Content-Type:=20text/plain=3B=20char set=3D"us-ascii"=3B=20format=3Dflowed|X-Random-Sig-Tag: =201.0b28|X-Originating-IP:=20[172.30.48.1]; bh=m1aHhHgsPyNDbc5LT1yz3nQhsvrwBVqcBeSekyVVm8Y=; b=uMX0HGNCVCaNRPfGA3+/YWAtj741tdjXxNKP8seuYvqirr8MrFvufRKc zukfZkYD6+OL7PQh/AiliR1SL8Us4IsWlryY6TZmQbzVliS2phMHL2Tvq fwn4FR05NZUhdhgNys+oystXEqaZURlQ2XhOekh8c/EKNmVDiH+kdioc1 I=;
X-IronPort-AV: E=McAfee;i="5400,1158,6390"; a="100375482"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine01.qualcomm.com with ESMTP; 27 Jun 2011 12:26:48 -0700
X-IronPort-AV: E=Sophos;i="4.65,432,1304319600"; d="scan'208";a="82045463"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 27 Jun 2011 12:26:48 -0700
Received: from [172.10.100.118] (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 27 Jun 2011 12:23:36 -0700
Message-ID: <p0624060cca2e8707f11a@[172.10.100.118]>
X-Mailer: Eudora for Mac OS X
Date: Mon, 27 Jun 2011 12:19:30 -0700
To: <ietf@ietf.org>
From: Randall Gellens <randy@qualcomm.com>
Subject: Anyone need a room at the Hilton?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 19:26:50 -0000

Would anyone like a room at the Hilton for CAD$229/night?  I seem to 
have a spare.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
The early bird catches the worm, but what does the early worm get?
                                                 --Randall Gellens

From jnc@mercury.lcs.mit.edu  Mon Jun 27 13:41:09 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34CCC11E8184 for <ietf@ietfa.amsl.com>; Mon, 27 Jun 2011 13:41: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vF3itAFESsS9 for <ietf@ietfa.amsl.com>; Mon, 27 Jun 2011 13:41:08 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 3803311E8183 for <ietf@ietf.org>; Mon, 27 Jun 2011 13:41:08 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id EE3FF18C127; Mon, 27 Jun 2011 16:41:06 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: one data point regarding native IPv6 support
Message-Id: <20110627204106.EE3FF18C127@mercury.lcs.mit.edu>
Date: Mon, 27 Jun 2011 16:41:06 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2011 20:41:09 -0000

    > From: Ole Troan <otroan@employees.org>

    >> IPv6 Neighbour Discovery is just the thing. I gather it's turned
    >> off on 6to4 links

    > IPv6 Neighbour Discovery requires a multicast capable link and
    > support for link-local addresses.

Well, RFC-4861 does say:

  Unless specified otherwise ... this document applies to all link types.
  ... it is possible that on some link types (e.g., Non-Broadcast
  Multi-Access (NBMA) links), alternative protocols or mechanisms to
  implement those services will be specified ... services described in
  this document that are not directly dependent on multicast, such as
  Redirects, Next-hop determination, Neighbor Unreachability Detection,
  etc., are expected to be provided as specified in this document. 

6to4 (especially anycast 6to4) should/would be considered an NBMA link,
and the spec does say (for such links):

  Redirect, Neighbor Unreachability Detection and next-hop determination
  should be implemented as described in this document.

So I don't see that it's wildly inappropriate.


    > NUD could be made to work, but I don't think NUD is any better than
    > any other connectivity test. e.g. a "BFD echo" style one as

I only suggested doing reachability detection by turning on ND as an simple,
easy way to do it - one would avoid having to write a bunch of code (which one
would have to, in order to use, say, an ICMPv6 ping based mechaniam).

But this isn't the right place for a detailed discussion - which is probably
OBE anyway - so I will leave it there.

	Noel

From marka@isc.org  Mon Jun 27 17:28:24 2011
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 767E711E8071; Mon, 27 Jun 2011 17:28:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.284
X-Spam-Level: 
X-Spam-Status: No, score=-2.284 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63RBj2SkZlsa; Mon, 27 Jun 2011 17:28:24 -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 977AC9E8009; Mon, 27 Jun 2011 17:28:23 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 9FC0E5F98EC; Tue, 28 Jun 2011 00:28:04 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 55189216C80; Tue, 28 Jun 2011 00:28:02 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 453B4113B898; Tue, 28 Jun 2011 10:28:00 +1000 (EST)
To: Joel Jaeggli <joelja@bogus.com>
From: Mark Andrews <marka@isc.org>
References: <20110625013809.E4B8618C0D0@mercury.lcs.mit.edu> <4E05D05B.7030000@gmail.com> <B91BB6CD-656F-4935-B513-A6225C8F3973@bogus.com> <20110626230955.C8DE41136E12@drugs.dv.isc.org> <3D67BAD3-45C1-47AC-BF42-9CEFA7C4A6FC@bogus.com>
Subject: Re: Why ask for IETF Consensus on a WG document?
In-reply-to: Your message of "Mon, 27 Jun 2011 10:25:50 MST." <3D67BAD3-45C1-47AC-BF42-9CEFA7C4A6FC@bogus.com>
Date: Tue, 28 Jun 2011 10:28:00 +1000
Message-Id: <20110628002800.453B4113B898@drugs.dv.isc.org>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jun 2011 00:28:24 -0000

In message <3D67BAD3-45C1-47AC-BF42-9CEFA7C4A6FC@bogus.com>, Joel Jaeggli write
s:
> 
> On Jun 26, 2011, at 4:09 PM, Mark Andrews wrote:
> > In message <B91BB6CD-656F-4935-B513-A6225C8F3973@bogus.com>, Joel =
> Jaeggli writ
> > es:
> >> 
> >> On Jun 25, 2011, at 5:11 AM, Brian E Carpenter wrote:
> >>> 
> >>> Not so odd. There are hundreds of millions of hosts out there that =
> attempt
> >>> to use 6to4 by default, and (probably) thousands of relay routers =
> that
> >>> attempt to support such users. Those boxes will be around for years, =
> and a
> >> re
> >>> the target for the -advisory draft, regardless of the deprecation.
> >> 
> >> the very fact that the devices are largely unmanaged, means that if =
> you don'
> >> t want to break them worse then they already are that you have =
> continue to s
> >> upport them until they age out of the network.
> > 
> > And historic just told CISCO and Juniper to stop supporting 6to4 in =
> their
> > big iron.  The very boxes that need to remain to the end supporting =
> 6to4
> > because they are managed boxes.
> 
> I think this argument is somewhat orthogonal to the problem of =
> supporting end-systems... However if your want to explore it, think the =
> author is probably in a position to interpret the draft on behalf of his =
> company. Juniper doesn't support 6to4 on the big iron.

CPE devices need to talk to something.  If you take that something
away you make the problem worse not better and don't say historic
is not going to result in product support going away as no one
believes that.

The boxes on the carrier end of the 6to4 tunnels will need to be
upgraded to deal with other issues and historic is likely to leave
the operators in the unenviable position of having to run relays
with known security flaws or kill the service.

> >>>  Brian
> >>> _______________________________________________
> >>> Ietf mailing list
> >>> Ietf@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/ietf
> >>> 
> >> 
> >> _______________________________________________
> >> Ietf mailing list
> >> Ietf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf
> > -- 
> > 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 R.E.Sonneveld@sonnection.nl  Tue Jun 28 06:04:45 2011
Return-Path: <R.E.Sonneveld@sonnection.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 6B5D021F86BC; Tue, 28 Jun 2011 06:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NtZkaiHDegtE; Tue, 28 Jun 2011 06:04:44 -0700 (PDT)
Received: from mx20.mailtransaction.com (mx20.mailtransaction.com [78.46.16.213]) by ietfa.amsl.com (Postfix) with ESMTP id C1DB721F86BB; Tue, 28 Jun 2011 06:04:42 -0700 (PDT)
Received: from process-dkim-sign-daemon.helium.mailtransaction.com by helium.mailtransaction.com (Oracle Communications Messaging Exchange Server 7u4-18.01 64bit (built Jul 15 2010)) id <0LNI008004BTQG00@helium.mailtransaction.com>; Tue, 28 Jun 2011 15:04:41 +0200 (CEST)
Received: from lion.sonnection.nl (lion.sonnection.nl [80.127.135.138]) by helium.mailtransaction.com (Oracle Communications Messaging Exchange Server 7u4-18.01 64bit (built Jul 15 2010)) with ESMTP id <0LNI00AM24BSFF00@helium.mailtransaction.com>; Tue, 28 Jun 2011 15:04:41 +0200 (CEST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from a80-127-135-139.adsl.xs4all.nl (a80-127-135-139.adsl.xs4all.nl [80.127.135.139]) by lion.sonnection.nl (Sun Java(tm) System Messaging Server 7.3-11.01 32bit (built Sep 1 2009)) with ESMTPA id <0LNI009364BRMS00@lion.sonnection.nl>; Tue, 28 Jun 2011 15:04:40 +0200 (CEST)
Message-id: <4E09D207.90900@sonnection.nl>
Date: Tue, 28 Jun 2011 15:07:19 +0200
From: "Rolf E. Sonneveld" <R.E.Sonneveld@sonnection.nl>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-dkim-rfc4871bis-12.txt> (DomainKeys Identified Mail (DKIM) Signatures) to Draft Standard
References: <20110623152458.19049.qmail@joyce.lan> <4E04CA58.8070201@mail-abuse.org> <BANLkTiky_8jW65COxswQWsOY+MmYUU7Kvg@mail.gmail.com>
In-reply-to: <BANLkTiky_8jW65COxswQWsOY+MmYUU7Kvg@mail.gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sonnection.nl; s=2009;  t=1309266281; bh=96Zoh4jMkNOJoO7vsR8JP43O9oDMJAuc+ygsFgECArw=;  h=MIME-version:Content-transfer-encoding:Content-type:Message-id: Date:From:To:Cc:Subject:References:In-reply-to; b=BIdS5o4K67mAaN0qQ+pAKWUweLqqheAwn92KmWwY4K+ZI6DMb8r9q8CZUVJI8BUNl IiNZdMQolo4mpezcRYlKfkqHjSGq30hdT/NCnrHRdAhb7L0T+EZW0bh6BkSDQJlKRi SK3K+0O96bjDMvnVglWEgIL2X3OMq/Vncqa9L4zY=
X-DKIM: OpenDKIM Filter v2.1.3 helium.mailtransaction.com 0LNI008004BTQG00
Cc: iesg@ietf.org, Charles Lindsey <chl@clerew.man.ac.uk>, Barry Leiba <barryleiba@computer.org>, "ietf-dkim@mipassoc.org" <ietf-dkim@mipassoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 13:04:45 -0000

One final note from me, as I want to state my current position regarding 
4871bis, with respect to Last Call.

As the receiving verifier has all the information to _reliably_ [0] 
determine which combination(s) [1] of From [2] and DKIM-Signature 
verifies correctly, it has the means to provide any consuming 
application with the right information. The mechanism(s) by which the 
verification results can be communicated to a consumer (as per par. 6.2 
of 4871bis) can be chosen by the verifier and does not restrict the 
results to only TEMPFAIL, PERMFAIL and SUCCESS [3].

Second, today there is hardly any installed base of MUA's that present 
any form of DKIM results to the end user, so most of this technology 
still needs to be written and 4871bis contains sufficient warnings about 
duplicate From and other fields; so in my view the argument of DKIM not 
being 'compatible' with the currently installed base of MUA's does not 
apply.

Third, DKIM is only one of multiple technologies that can and will be 
deployed by both senders and receivers. This means that any policy 
published by a sender regarding the use of DKIM does not have to provide 
a sharp 'black' or 'white', 'keep' or 'discard' result. Senders that 
wish to publish a policy need to take into account that the world is not 
perfect and that there always will be lousy implementations of protocols 
(be it RFC5321, RFC5322, RFC4871 or RFC4871bis). [4] It's better to 
acknowledge this, than to rely on the 'MUST's in this particular DKIM 
RFC. Policies that do not take this into account, can/may have dramatic 
results.

Hence, I no longer see a problem in 4871bis not mandating the duplicate 
header check.

/rolf

[0] irrespective of whether a From field has been prepended or appended 
or no such thing at all
[1] (s) plural form, if there are multiple DKIM-Signatures and multiple 
 From fields.
[2] From is mentioned here only:
- because it is the only mandatory header field to be used to generate 
the signature and
- for the case that there's a consuming application that would display 
the From header, which in your view is the attack vector
Apart from that, there is no special reason to focus here on From
[3] although TEMPFAIL and PERMFAIL are mentioned in 4871, there is no 
equivalent identifier for a positive result, is there? I suggest to make 
the success status explicit in 4871bis
[4] The fact that a sender doesn't know in advance how well the receiver 
implements the DKIM verification process will need to be taken into 
account for any policy protocol that will be built on top of DKIM.

From robmcm@microsoft.com  Mon Jun 27 10:25:07 2011
Return-Path: <robmcm@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23DE811E8117; Mon, 27 Jun 2011 10:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.467
X-Spam-Level: 
X-Spam-Status: No, score=-7.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cV5km3SKYjCa; Mon, 27 Jun 2011 10:25:06 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE0B11E810B; Mon, 27 Jun 2011 10:25:03 -0700 (PDT)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 27 Jun 2011 10:25:03 -0700
Received: from CH1EHSOBE012.bigfish.com (157.54.51.113) by mail.microsoft.com (157.54.7.154) with Microsoft SMTP Server (TLS) id 14.1.289.8; Mon, 27 Jun 2011 10:25:00 -0700
Received: from mail107-ch1-R.bigfish.com (216.32.181.171) by CH1EHSOBE012.bigfish.com (10.43.70.62) with Microsoft SMTP Server id 14.1.225.22; Mon, 27 Jun 2011 17:24:59 +0000
Received: from mail107-ch1 (localhost.localdomain [127.0.0.1])	by mail107-ch1-R.bigfish.com (Postfix) with ESMTP id 0F57CFE0133; Mon, 27 Jun 2011 17:25:00 +0000 (UTC)
X-SpamScore: -31
X-BigFish: PS-31(zz9371M111aL542Mzz1202h1082kzz1033IL8275bh8275dhz31h2a8h668h839h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: CIP:157.55.61.146; KIP:(null); UIP:(null); IPV:SKI; H:CH1PRD0302HT002.namprd03.prod.outlook.com; R:internal; EFV:INT
Received-SPF: softfail (mail107-ch1: transitioning domain of microsoft.com does not designate 157.55.61.146 as permitted sender) client-ip=157.55.61.146; envelope-from=robmcm@microsoft.com; helo=CH1PRD0302HT002.namprd03.prod.outlook.com ; .outlook.com ; 
Received: from mail107-ch1 (localhost.localdomain [127.0.0.1]) by mail107-ch1 (MessageSwitch) id 1309195499926219_17229; Mon, 27 Jun 2011 17:24:59 +0000 (UTC)
Received: from CH1EHSMHS025.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.244])	by mail107-ch1.bigfish.com (Postfix) with ESMTP id D1CB1136004F;	Mon, 27 Jun 2011 17:24:59 +0000 (UTC)
Received: from CH1PRD0302HT002.namprd03.prod.outlook.com (157.55.61.146) by CH1EHSMHS025.bigfish.com (10.43.70.25) with Microsoft SMTP Server (TLS) id 14.1.225.22; Mon, 27 Jun 2011 17:24:55 +0000
Received: from CH1PRD0302MB131.namprd03.prod.outlook.com ([169.254.11.234]) by CH1PRD0302HT002.namprd03.prod.outlook.com ([10.28.28.64]) with mapi id 14.01.0225.056; Mon, 27 Jun 2011 17:24:54 +0000
From: Robert McMurray <robmcm@microsoft.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: RE: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File Transfer Protocol	HOST Command for Virtual Hosts) to Proposed	Standard
Thread-Topic: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File Transfer Protocol	HOST Command for Virtual Hosts) to Proposed	Standard
Thread-Index: AQHMMqEmcdEZfuFND0GouWGSZJApmpTM3a+wgACe3wCAA/wiIA==
Date: Mon, 27 Jun 2011 17:24:53 +0000
Message-ID: <01AA9EC92749BF4894AC2B3039EA4A2C1949EC06@CH1PRD0302MB131.namprd03.prod.outlook.com>
References: <20110616130503.4854.51928.idtracker@ietfa.amsl.com> <4E04C0CE.1030807@gmail.com> <01AA9EC92749BF4894AC2B3039EA4A2C1949D19E@CH1PRD0302MB131.namprd03.prod.outlook.com> <4E0564E4.9010200@gmail.com>
In-Reply-To: <4E0564E4.9010200@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.28.29.69]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: CH1PRD0302HT002.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GMAIL.COM$RO%2$TLS%6$FQDN%131.107.125.5$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%131.107.125.5$TlsDn%
X-OriginatorOrg: microsoft.com
X-CrossPremisesHeadersPromoted: TK5EX14HUBC102.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC102.redmond.corp.microsoft.com
X-Mailman-Approved-At: Tue, 28 Jun 2011 08:18:37 -0700
Cc: "ftpext@ietf.org" <ftpext@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, 27 Jun 2011 17:25:07 -0000

Thanks Mykyta,

Ah, now I see your point - that's a great catch, and I will add a section t=
o a new version of the draft that I am working on for other IETF comments.

Thanks again!

-----Original Message-----
From: Mykyta Yevstifeyev [mailto:evnikita2@gmail.com]=20
Sent: Friday, June 24, 2011 9:33 PM
To: Robert McMurray
Cc: ietf@ietf.org; ftpext@ietf.org
Subject: Re: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File Tr=
ansfer Protocol HOST Command for Virtual Hosts) to Proposed Standard

OK, and if HOST is sent for the second time when the user hasn't got=20
authenticated, eg.

S> 220 Server ready
C> HOST example.com
S> 220 HOST OK
C> HOST example.org
S> ???

I suppose it may be 503 reply or switching to the identified host with=20
220 reply.  This situation isn't mentioned in your document.

Mykyta Yevstifeyev



From ice@cisco.com  Mon Jun 27 12:20:57 2011
Return-Path: <ice@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 14AE811E812A; Mon, 27 Jun 2011 12:20: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dRtu85dtbiEh; Mon, 27 Jun 2011 12:20: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 133E711E80F8; Mon, 27 Jun 2011 12:20: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 p5RJKrH4013381; Mon, 27 Jun 2011 21:20:53 +0200 (CEST)
Received: from [10.155.35.20] ([10.155.35.20]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p5RJKo4Q027276; Mon, 27 Jun 2011 21:20:51 +0200 (CEST)
Subject: Re: [Gen-art] Review: draft-ietf-mpls-ldp-p2mp-14
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: IJsbrand Wijnands <ice@cisco.com>
In-Reply-To: <4E03F3A5.40905@joelhalpern.com>
Date: Mon, 27 Jun 2011 21:20:50 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC16901C-F0F3-43D2-8D5B-67FFAAB9DC0E@cisco.com>
References: <4E038C9B.3070206@nostrum.com> <4E03F3A5.40905@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1081)
X-Mailman-Approved-At: Tue, 28 Jun 2011 08:18:36 -0700
Cc: Adrian Farrel <adrian@olddog.co.uk>, 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: Mon, 27 Jun 2011 19:20:57 -0000

Hi Joel,

Thanks for the comments.

> Major issues:
>    As I read the document, status codes (and stauts TLVs) are for =
reporting on the status of LSPs.  They are not for negotiating =
behaviors.  Thus, I find it very strange that make-before-break behavior =
(section 8) is requested (by a downstream device sending a request to an =
upstream device) by including a specific status code in the request. Has =
this technique been used in MPLS LDP before?

Well, the status codes and TLVs are not restricted by RFC 5036 for any =
particular purpose. The MBB procedures requires to signal information =
about the LSP which is not part of the FEC. The status TLV seems a good =
way to do that. Also, the status of the LSP can be viewed as 'waiting on =
upstream LDP neighbor to respond for MBB purpose'. So I think its ok.

>=20
> Minor issues:
>    The definition (section 1.2)  of MP2MP LSPs should indicate that =
even though all nodes are allowed to send on the LSP, there is still a =
distinguished root node.

Ok, I will add that.

>=20
>    The LDP MP Opaque Value Element extended type (section 2.3, second =
definition) seems to be gratuitous complexity, adding extra matching =
cases in the LDP processing path for no stated value.  Is there really =
believed to be a need for more than 254 types of Opaque values?  If so, =
explain it in the document.

The opaque type was defined as a non-extensible one-octet field. This =
may be enough for the future, but you never know. I guess there are many =
examples in the IETF where fields seemed to be large enough but proved =
to be too small over time. So why not just document it now.

>=20
>    Section 3.3.1.3 begins by describing two methods for installing the =
upstream path of a MP2MPLSP.  After carefully describing both, it says =
to only and always use the second method.  Would it not be better to =
describe the constraint (that the upstream path must be in place all the =
way to the root before it claims to be established), and then describe =
the one method that meets taht.  Just don't describe a method that is =
not to be used.

That is a good comment, let me think about this for a bit.

Thx,

Ice.


>=20
> Nits/editorial comments:
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From paulfordh@uk.ibm.com  Mon Jun 27 13:39:08 2011
Return-Path: <paulfordh@uk.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 C891611E817D; Mon, 27 Jun 2011 13:39:08 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Te0Z71JTLQrX; Mon, 27 Jun 2011 13:39:07 -0700 (PDT)
Received: from mtagate1.uk.ibm.com (mtagate1.uk.ibm.com [194.196.100.161]) by ietfa.amsl.com (Postfix) with ESMTP id CBB6211E80D5; Mon, 27 Jun 2011 13:39:06 -0700 (PDT)
Received: from d06nrmr1707.portsmouth.uk.ibm.com (d06nrmr1707.portsmouth.uk.ibm.com [9.149.39.225]) by mtagate1.uk.ibm.com (8.13.1/8.13.1) with ESMTP id p5RKd4HB025532; Mon, 27 Jun 2011 20:39:04 GMT
Received: from d06av09.portsmouth.uk.ibm.com (d06av09.portsmouth.uk.ibm.com [9.149.37.250]) by d06nrmr1707.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p5RKcvw31912958; Mon, 27 Jun 2011 21:39:04 +0100
Received: from d06av09.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av09.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p5RKcvdr030572; Mon, 27 Jun 2011 14:38:57 -0600
Received: from d06ml069.portsmouth.uk.ibm.com (d06ml069.portsmouth.uk.ibm.com [9.149.38.218]) by d06av09.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p5RKcvHR030569; Mon, 27 Jun 2011 14:38:57 -0600
In-Reply-To: <20110616130503.4854.51928.idtracker@ietfa.amsl.com>
References: <20110616130503.4854.51928.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
MIME-Version: 1.0
Subject: Re: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File	Transfer Protocol	HOST Command for Virtual Hosts) to Proposed	Standard
X-KeepSent: A9997572:88B3CCF9-802578BC:006F9F84; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2FP1 SHF149 July 17, 2009
From: Paul Ford-Hutchinson <paulfordh@uk.ibm.com>
Message-ID: <OFA9997572.88B3CCF9-ON802578BC.006F9F84-802578BC.00716B95@uk.ibm.com>
Date: Mon, 27 Jun 2011 21:38:54 +0100
X-MIMETrack: Serialize by Router on D06ML069/06/M/IBM(Release 8.0.2FP6|July 15, 2010) at 27/06/2011 21:38:56, Serialize complete at 27/06/2011 21:38:56
Content-Type: multipart/alternative; boundary="=_alternative 00716646802578BC_="
X-Mailman-Approved-At: Tue, 28 Jun 2011 08:18:37 -0700
Cc: ftpext@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 20:39:08 -0000

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

Folks, some comments on the FTP HOST draft....

Section 3:

> Server-FTP processes SHOULD treat a situation where the HOST command
> is issued after the user has been authenticated using one of the
> following two behaviors:
>
>  a.  Treat the late HOST command as an erroneous sequence of commands
>       and return a 503 reply.
>
>  b.  Treat the late HOST command as though a REIN command was sent
>      before the HOST command and reset the user-PI to the state that
>      existed after the TCP connection was first established and before
>      the initial user authentication and then return the appropriate
>      reply for the HOST command.

Surely the first SHOULD has to be a MUST.  Otherwise we have a situation 
where, upon receipt of a valid HOST, some server implementations will 
implicitly REIN and clear AUTH/USER/ACCT and some will not.  That would be 
an interoperability nightmare.


Section 3.2:

> The "220" reply code for the HOST command is the same as the code
> that is used in the initial "welcome" message that is sent after the
> connection is established.  This reply code is used deliberately in
> order to allow the implementation of a front-end FTP server as a
> wrapper, which simply waits for the HOST command, and then invokes a
> server that is compliant with [RFC0959] in the appropriate
> environment for the particular hostname received.

I'm a little concerned that this presents the "wrapper" to be a lot more 
lightweight than it actually will need to be.  Such a wrapper will need to 
stay in the session in order to monitor for future HOST commands (which 
presumably will not be understood by the [RFC0959] compliant servers) and 
implicitly close and reopen a new session (or issue a REIN).  If the 
session between the client and real FTP server is AUTH protected then this 
may be impossible.

If we really do allow for such a lightweight wrapper, then this draft 
needs to mention that there is a perfectly expected mode of operation for 
a client where a FEAT command may initially return HOST and an initial 
HOST may indeed work - but after that - all bets are off.

I suggest that either the "wrapper" concept is dropped from the document 
altogether, or a fuller description of what a wrapper might be expected to 
do (and - more importantly, how a client may need to be written to allow 
for one to be there) is included.


Section 3.2.2:

> This is also true when the HOST command is used with the AUTH and
> ADAT commands that are discussed in [RFC2228] and [RFC4217].  In this
> scenario, the user-PI sends a HOST command which the server-PI uses
> to route activity to the correct virtual host, then the user-PI uses
> the AUTH and ADAT commands to negotiate the security mechanism and
> certificate with the server-PI ...

"to negotiate the security mechanism and certificate"

should be 

"to negotiate the security mechanism and relevant authentication token(s)" 
(RFC2228 is not dependent on 'certificates')

Section 4:

> Some organizations may 
> use private hostnames, and that information SHOULD be protected when
> transmitted between the client and server by using a strong method of
> encryption.

The "strong method of encryption" is a bit vague.  Are we suggesting 
something like TLS?  In which case it won't work - as the HOST precedes 
the AUTH.  Or are we suggesting some mutually shared secret between the 
client and the server for the parameter to the HOST command - somehow 
bootstrapped by some unspecified mechanism?  (or are we simply assuming 
such environments would be expected to be running over a VPN anyway?)

I don't think we can publish this paragraph without being more explicit 
about what this really means.

 
> Server implementations SHOULD reset the security environment when a
> HOST command is sent after a user has logged in.

I repeat my initial point - this has to be a MUST - otherwise the client 
has no idea what the state of a session is after the HOST is processed.

In the case of RFC4217, this is crucial - because a REIN closes the TLS 
session.  A client has to know if that is expected or not, this cannot be 
left to a server implementation decision. 

I believe that there's a good argument for stating that a HOST following a 
successful initial HOST MUST be preceded by an explicit REIN, but if we 
are going to let that slide, then we must be clear that a HOST always 
implies an implicit REIN.  (Note that RFC4217 has some words about the 
REIN response being transmitted on the protected channel prior to the 
dropping of the TLS session, it is precisely due to nuances like this, 
that I fee the REIN should be explicit - otherwise a similar statement 
would need to be made about the response to the HOST)

Finally, I would like some mention of the linkage (or more importantly, 
lack of mandated linkage) between the identity returned in an X.509 
certificate (in the case of RFC4217) and the parameter to the HOST command 
at the protocol specification level.  A pointer to the first paragraph of 
section 15.1.1 of [RFC4217] would be fine....

>Although it is entirely an implementation decision, it is
>recommended that certificates used for server authentication of the
>TLS session contain the server identification information in a
>similar manner to those used for http servers (see [RFC-2818])
 

Paul.

-- 

Paul Ford-Hutchinson CISSP - Tivoli Security Consultant
IBM UK Ltd. - NHBR - 1PH - North Harbour - Portsmouth - PO6 3AU
IBM Certified Deployment Professional - Tivoli Compliance Insight Manager 
V8.5

Tel +44 (0)7500 078379  (internal: 37269105)



From:
The IESG <iesg-secretary@ietf.org>
To:
IETF-Announce <ietf-announce@ietf.org>
Cc:
ftpext@ietf.org
Date:
16/06/2011 14:06
Subject:
[ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File     Transfer 
Protocol        HOST Command for Virtual Hosts) to Proposed     Standard
Sent by:
ftpext-bounces@ietf.org




The IESG has received a request from the FTP Extensions, 2nd edition WG
(ftpext2) to consider the following document:
- 'File Transfer Protocol HOST Command for Virtual Hosts'
  <draft-ietf-ftpext2-hosts-02.txt> as a 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 2011-06-30. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


The File Transfer Protocol, as defined in RFC 959 [RFC0959], does not
   provide a way for FTP clients and servers to differentiate between
   multiple DNS names that are registered for a single IP address.  This
   document defines a new FTP command that provides a mechanism for FTP
   clients and servers to identify individual virtual hosts on an FTP
   server.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-ftpext2-hosts/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-ftpext2-hosts/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
ftpext mailing list
ftpext@ietf.org
https://www.ietf.org/mailman/listinfo/ftpext



--=_alternative 00716646802578BC_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Folks, some comments on the FTP HOST
draft....</font>
<br>
<br><font size=2 face="sans-serif">Section 3:</font>
<br>
<br><font size=2 face="sans-serif">&gt; Server-FTP processes SHOULD treat
a situation where the HOST command</font>
<br><font size=2 face="sans-serif">&gt; is issued after the user has been
authenticated using one of the</font>
<br><font size=2 face="sans-serif">&gt; following two behaviors:</font>
<br><font size=2 face="sans-serif">&gt;</font>
<br><font size=2 face="sans-serif">&gt; &nbsp;a. &nbsp;Treat the late HOST
command as an erroneous sequence of commands</font>
<br><font size=2 face="sans-serif">&gt; &nbsp; &nbsp; &nbsp; and return
a 503 reply.</font>
<br><font size=2 face="sans-serif">&gt;</font>
<br><font size=2 face="sans-serif">&gt; &nbsp;b. &nbsp;Treat the late HOST
command as though a REIN command was sent</font>
<br><font size=2 face="sans-serif">&gt; &nbsp; &nbsp; &nbsp;before the
HOST command and reset the user-PI to the state that</font>
<br><font size=2 face="sans-serif">&gt; &nbsp; &nbsp; &nbsp;existed after
the TCP connection was first established and before</font>
<br><font size=2 face="sans-serif">&gt; &nbsp; &nbsp; &nbsp;the initial
user authentication and then return the appropriate</font>
<br><font size=2 face="sans-serif">&gt; &nbsp; &nbsp; &nbsp;reply for the
HOST command.</font>
<br>
<br><font size=2 face="sans-serif">Surely the first SHOULD has to be a
MUST. &nbsp;Otherwise we have a situation where, upon receipt of a valid
HOST, some server implementations will implicitly REIN and clear AUTH/USER/ACCT
and some will not. &nbsp;That would be an interoperability nightmare.</font>
<br>
<br>
<br><font size=2 face="sans-serif">Section 3.2:</font>
<br>
<br><font size=2 face="sans-serif">&gt; The &quot;220&quot; reply code
for the HOST command is the same as the code</font>
<br><font size=2 face="sans-serif">&gt; that is used in the initial &quot;welcome&quot;
message that is sent after the</font>
<br><font size=2 face="sans-serif">&gt; connection is established. &nbsp;This
reply code is used deliberately in</font>
<br><font size=2 face="sans-serif">&gt; order to allow the implementation
of a front-end FTP server as a</font>
<br><font size=2 face="sans-serif">&gt; wrapper, which simply waits for
the HOST command, and then invokes a</font>
<br><font size=2 face="sans-serif">&gt; server that is compliant with [RFC0959]
in the appropriate</font>
<br><font size=2 face="sans-serif">&gt; environment for the particular
hostname received.</font>
<br>
<br><font size=2 face="sans-serif">I'm a little concerned that this presents
the &quot;wrapper&quot; to be a lot more lightweight than it actually will
need to be. &nbsp;Such a wrapper will need to stay in the session in order
to monitor for future HOST commands (which presumably will not be understood
by the [RFC0959] compliant servers) and implicitly close and reopen a new
session (or issue a REIN). &nbsp;If the session between the client and
real FTP server is AUTH protected then this may be impossible.</font>
<br>
<br><font size=2 face="sans-serif">If we really do allow for such a lightweight
wrapper, then this draft needs to mention that there is a perfectly expected
mode of operation for a client where a FEAT command may initially return
HOST and an initial HOST may indeed work - but after that - all bets are
off.</font>
<br>
<br><font size=2 face="sans-serif">I suggest that either the &quot;wrapper&quot;
concept is dropped from the document altogether, or a fuller description
of what a wrapper might be expected to do (and - more importantly, how
a client may need to be written to allow for one to be there) is included.</font>
<br>
<br>
<br><font size=2 face="sans-serif">Section 3.2.2:</font>
<br>
<br><font size=2 face="sans-serif">&gt; This is also true when the HOST
command is used with the AUTH and</font>
<br><font size=2 face="sans-serif">&gt; ADAT commands that are discussed
in [RFC2228] and [RFC4217]. &nbsp;In this</font>
<br><font size=2 face="sans-serif">&gt; scenario, the user-PI sends a HOST
command which the server-PI uses</font>
<br><font size=2 face="sans-serif">&gt; to route activity to the correct
virtual host, then the user-PI uses</font>
<br><font size=2 face="sans-serif">&gt; the AUTH and ADAT commands to negotiate
the security mechanism and</font>
<br><font size=2 face="sans-serif">&gt; certificate with the server-PI
...</font>
<br>
<br><font size=2 face="sans-serif">&quot;to negotiate the security mechanism
and certificate&quot;</font>
<br>
<br><font size=2 face="sans-serif">should be </font>
<br>
<br><font size=2 face="sans-serif">&quot;to negotiate the security mechanism
and relevant authentication token(s)&quot; (RFC2228 is not dependent on
'certificates')</font>
<br>
<br><font size=2 face="sans-serif">Section 4:</font>
<br>
<br><font size=2 face="sans-serif">&gt; Some organizations may </font>
<br><font size=2 face="sans-serif">&gt; use private hostnames, and that
information SHOULD be protected when</font>
<br><font size=2 face="sans-serif">&gt; transmitted between the client
and server by using a strong method of</font>
<br><font size=2 face="sans-serif">&gt; encryption.</font>
<br>
<br><font size=2 face="sans-serif">The &quot;strong method of encryption&quot;
is a bit vague. &nbsp;Are we suggesting something like TLS? &nbsp;In which
case it won't work - as the HOST precedes the AUTH. &nbsp;Or are we suggesting
some mutually shared secret between the client and the server for the parameter
to the HOST command - somehow bootstrapped by some unspecified mechanism?
&nbsp;(or are we simply assuming such environments would be expected to
be running over a VPN anyway?)</font>
<br>
<br><font size=2 face="sans-serif">I don't think we can publish this paragraph
without being more explicit about what this really means.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;</font>
<br><font size=2 face="sans-serif">&gt; Server implementations SHOULD reset
the security environment when a</font>
<br><font size=2 face="sans-serif">&gt; HOST command is sent after a user
has logged in.</font>
<br>
<br><font size=2 face="sans-serif">I repeat my initial point - this has
to be a MUST - otherwise the client has no idea what the state of a session
is after the HOST is processed.</font>
<br>
<br><font size=2 face="sans-serif">In the case of RFC4217, this is crucial
- because a REIN closes the TLS session. &nbsp;A client has to know if
that is expected or not, this cannot be left to a server implementation
decision. </font>
<br>
<br><font size=2 face="sans-serif">I believe that there's a good argument
for stating that a HOST following a successful initial HOST MUST be preceded
by an explicit REIN, but if we are going to let that slide, then we must
be clear that a HOST always implies an implicit REIN. &nbsp;(Note that
RFC4217 has some words about the REIN response being transmitted on the
protected channel prior to the dropping of the TLS session, it is precisely
due to nuances like this, that I fee the REIN should be explicit - otherwise
a similar statement would need to be made about the response to the HOST)</font>
<br>
<br><font size=2 face="sans-serif">Finally, I would like some mention of
the linkage (or more importantly, lack of mandated linkage) between the
identity returned in an X.509 certificate (in the case of RFC4217) and
the parameter to the HOST command at the protocol specification level.
&nbsp;A pointer to the first paragraph of section 15.1.1 of [RFC4217] would
be fine....</font>
<br>
<br><font size=2 face="sans-serif">&gt;Although it is entirely an implementation
decision, it is</font>
<br><font size=2 face="sans-serif">&gt;recommended that certificates used
for server authentication of the</font>
<br><font size=2 face="sans-serif">&gt;TLS session contain the server identification
information in a</font>
<br><font size=2 face="sans-serif">&gt;similar manner to those used for
http servers (see [RFC-2818])</font>
<br><font size=2 face="sans-serif">&nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Paul.</font>
<br>
<br><font size=2 face="sans-serif">-- <br>
<br>
Paul Ford-Hutchinson CISSP - Tivoli Security Consultant<br>
IBM UK Ltd. - NHBR - 1PH - North Harbour - Portsmouth - PO6 3AU<br>
IBM Certified Deployment Professional - Tivoli Compliance Insight Manager
V8.5<br>
<br>
Tel +44 (0)7500 078379 &nbsp;(internal: 37269105)</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">The IESG &lt;iesg-secretary@ietf.org&gt;</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">IETF-Announce &lt;ietf-announce@ietf.org&gt;</font>
<tr>
<td valign=top><font size=1 color=#5f5f5f face="sans-serif">Cc:</font>
<td><font size=1 face="sans-serif">ftpext@ietf.org</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">16/06/2011 14:06</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">[ftpext] Last Call: &lt;draft-ietf-ftpext2-hosts-02.txt&gt;
(File &nbsp; &nbsp; &nbsp; &nbsp;Transfer Protocol &nbsp; &nbsp;
&nbsp; &nbsp;HOST Command for Virtual Hosts) to Proposed &nbsp;
&nbsp; &nbsp; &nbsp;Standard</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Sent by:</font>
<td><font size=1 face="sans-serif">ftpext-bounces@ietf.org</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2><br>
The IESG has received a request from the FTP Extensions, 2nd edition WG<br>
(ftpext2) to consider the following document:<br>
- 'File Transfer Protocol HOST Command for Virtual Hosts'<br>
 &nbsp;&lt;draft-ietf-ftpext2-hosts-02.txt&gt; as a Proposed Standard<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
ietf@ietf.org mailing lists by 2011-06-30. Exceptionally, comments may
be<br>
sent to iesg@ietf.org instead. In either case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
The File Transfer Protocol, as defined in RFC 959 [RFC0959], does not<br>
 &nbsp; provide a way for FTP clients and servers to differentiate between<br>
 &nbsp; multiple DNS names that are registered for a single IP address.
&nbsp;This<br>
 &nbsp; document defines a new FTP command that provides a mechanism for
FTP<br>
 &nbsp; clients and servers to identify individual virtual hosts on an
FTP<br>
 &nbsp; server.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
</font></tt><a href="http://datatracker.ietf.org/doc/draft-ietf-ftpext2-hosts/"><tt><font size=2>http://datatracker.ietf.org/doc/draft-ietf-ftpext2-hosts/</font></tt></a><tt><font size=2><br>
<br>
IESG discussion can be tracked via<br>
</font></tt><a href="http://datatracker.ietf.org/doc/draft-ietf-ftpext2-hosts/"><tt><font size=2>http://datatracker.ietf.org/doc/draft-ietf-ftpext2-hosts/</font></tt></a><tt><font size=2><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
_______________________________________________<br>
ftpext mailing list<br>
ftpext@ietf.org<br>
</font></tt><a href=https://www.ietf.org/mailman/listinfo/ftpext><tt><font size=2>https://www.ietf.org/mailman/listinfo/ftpext</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br>
--=_alternative 00716646802578BC_=--

From jari.arkko@piuha.net  Wed Jun 29 01:47:30 2011
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 EF36811E80A1; Wed, 29 Jun 2011 01:47:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.048
X-Spam-Level: 
X-Spam-Status: No, score=-102.048 tagged_above=-999 required=5 tests=[AWL=-0.049, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e409bcx4Xdab; Wed, 29 Jun 2011 01:47:29 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 03C2C21F86A1; Wed, 29 Jun 2011 01:47:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 22C512CC3B; Wed, 29 Jun 2011 11:47:26 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4NEFIdMMzeAl; Wed, 29 Jun 2011 11:47:20 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 080C02CC39; Wed, 29 Jun 2011 11:47:18 +0300 (EEST)
Message-ID: <4E0AE696.4020603@piuha.net>
Date: Wed, 29 Jun 2011 10:47:18 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: "homegate@ietf.org" <homegate@ietf.org>, IETF Discussion <ietf@ietf.org>
Subject: HOMENET working group proposal
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "W. Mark Townsley" <townsley@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: Wed, 29 Jun 2011 08:47:30 -0000

I would like to announce a new effort around home networking and solicit 
some feedback.

HOMENET is a new working group proposal, a variation of the 
HOMEGATE/HOMENET theme that we discussed last year, but this time 
looking at it from a different angle. The old effort was mostly focused 
about what home gateways should do: forwarding, transport, and DNS 
proxying issues. The new effort is about home networks themselves, in 
particular what kind of network architecture and configuration is 
necessary to support IPv6-based home networks. We view IPv4-based home 
networks as "done" at this time (or perhaps as "cannot be changed anyway").

I have been discussing this effort in the background for the last couple 
of month with Mark Townsley and others, and more publicly since early 
June. The proposal has been brought to the IESG, IAB and some 
directorates for discussion, and we've been going back and forth whether 
this is ready to become a working group or needs to be run as a BOF in 
Quebec City. The current plan is that the working group proposal goes to 
IETF-wide review this week, and if the feedback from the community, IAB, 
and the IESG is positive, we will create the working group just in time 
for the IETF. Otherwise, the slot reserved in the agenda for the meeting 
will be used to run the proposal as a BOF.

In any case, I would like to solicit discussion on this topic, and 
perhaps some early drafts as well. Please comment on the charter at 
least. Go here to subscribe https://www.ietf.org/mailman/listinfo/fun 
and below you can find the most recent charter proposal. Please join the 
list and the discussion.

Note that the new proposal was called FUN at the time that we created 
the list. It has now been renamed back to HOMENET to be more 
descriptive. The list will be renamed soon as well (current subscribers 
will stay). Note also that I'm sending this to the old homegate list, to 
inform people who were interested in that. I'd like the discussion to 
happen on the fun@ietf.org list, however.

Jari

Home Networks (homenet)
-----------------------------------

Current Status: Proposed
Last Edit: Wednesday, June 29th, 2011

Chairs:
TBD

Internet Area Directors:
Ralph Droms <rdroms.ietf@gmail.com>
Jari Arkko <jari.arkko@piuha.net>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>

Routing Area Technical Advisor:
TBD

Security Area Technical Advisor:
TBD

Mailing Lists:
General Discussion: fun@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/fun
Archive: http://www.ietf.org/mail-archive/web/fun

Description of Working Group:

This working group focuses on the evolving networking technology
within and among relatively small “residential home” networks. For
example, an obvious trend in home networking is the proliferation of
networking technology in an increasingly broad range and number of
devices. This evolution in scale and diversity sets some requirements
on IETF protocols. Some of the relevant trends include:

o Multiple segments: While less complex L3-toplogies involving as few
subnets as possible are preferred in home networks for a variety of
reasons including simpler management and service discovery, the
introduction of more than one subnet into a home network is enough
to add complexity that needs to be addressed, and multiple
dedicated segments are necessary for some cases. For instance, a
common feature in modern home routers in the ability to support
both guest and private network segments. Also, link layer
networking technology is poised to become more heterogeneous, as
networks begin to employ both traditional Ethernet technology and
link layers designed for low-powered sensor networks. Finally,
similar needs for segmentation may occur in other cases, such as
separating building control or corporate extensions from the
Internet access network. Different segments may be associated with
subnets that have different routing and security policies.

o Service providers are deploying IPv6, and support for IPv6 is
increasingly available in home gateway devices. While IPv6 resembles
IPv4 in many ways, it changes address allocation principles and allows
direct IP addressability and routing to devices in the home from the
Internet. This is a promising area in IPv6 that has proved challenging
in IPv4 with the proliferation of NAT.

o End-to-end communication is both an opportunity and a concern as it
enables new applications but also exposes nodes in the internal
networks to receipt of unwanted traffic from the Internet. Firewalls
that restrict incoming connections may be used to prevent exposure,
however, this reduces the efficacy of end-to-end connectivity that
IPv6 has the potential to restore.

Home networks need to provide the tools to handle these situations in
a manner accessible to all users of home networks. Manual
configuration is rarely, if at all, possible. The purpose of this
working group is to focus on this evolution, in particular as it
addresses the introduction of IPv6, by developing an architecture
addressing this full scope of requirements:

o prefix configuration for routers
o managing routing
o name resolution
o service discovery
o network security

The task of the group is to produce an architecture document that
outlines how to construct home networks involving multiple routers and
subnets. This document is expected to apply the IPv6 addressing
architecture, prefix delegation, global and ULA addresses, source
address selection rules and other existing components of the IPv6
architecture. The architecture document should drive what protocols
changes, if any, are necessary. Specific protocol work described below
is expected to be within the scope of the working group one the
architecture work is complete. However, the group is required to
review its charter and milestones with the IESG and IETF community
before submitting documents that make protocol changes. It is expected
that the group has to discuss some of the below solutions, however, in
order to complete the architecture work.

The group will apply existing protocols to handle the five
requirements above. For prefix configuration, existing protocols are
likely sufficient, and at worst may need some small enhancements, such
as new options. For automatic routing, it is expected that existing
routing protocols can be used as is, however, a new mechanism may be
needed in order to turn a selected protocol on by default. For name
resolution and service discovery, extensions to existing
multicast-based name resolution protocols are needed to enable them to
work across subnets.

For network security, the group shall document the concept of
"advanced security" as a further development of "simple security" from
RFC 6092. The main goal of this work is to enable a security policy
that adapts to IPv6 threats as they emerge, taking into account not
only traffic from the Internet at large, but within and leaving the
home network itself.

It is expected that the working group will define a set of protocol
specifications to accomplish the five requirements from
above. However, it is not in the scope of the working group to define
entirely new routing protocols or address allocation protocols. As
noted, additional options or other small extensions may be necessary
to use the existing protocols in these new configuration tasks. The
working group shall also not make any changes to IPv6 protocols or
addressing architecture. Prefix configuration, routing, and security
related work shall not cause any changes that are not backwards
compatible to existing IPv6 hosts. There may be host visible changes
in the work on naming and discovery protocols, however. In its design,
the working group shall also consider security aspects and the impact
on manageability. The main focus of the working group is home
networks, but the group's results may also find applications in other
small networks.

The working group will liaise with the relevant IETF working
groups. In particular, the group should work closely with the V6OPS
working group, review any use or extension of DHCP with the DHC
working group, and work with additional DNS requirements with the
DNSEXT and DNSOP working groups. If it turns out that additional
options are needed for a routing protocol, they will be developed in
the appropriate Routing Area working group, with the HOMENET working
group providing the architecture and requirements for such
enhancements. The working group will also liase with external
standards bodies where it is expected that there are normative
dependencies between the specifications of the two bodies.
It is expected that in the architecture definition stage liaising
with the Broadband Forum, DLNA, and UPnP Forum is necessary.

Milestones:

Jul 2011 Formation of the working group
Sep 2011 First WG draft on the architecture
Dec 2011 Submission of the architecture draft to the IESG as 
Informational RFC
Dec 2011 Charter re-evaluation based on the architecture work
Dec 2011 First WG draft on prefix configuration
Dec 2011 First WG draft on routing
Jan 2012 First WG draft on name resolution
Feb 2012 First WG draft on service discovery
Feb 2012 First WG draft on perimeter security
Feb 2012 Start of routing related work in the relevant routing area 
working group, if needed
Mar 2012 Submission of the prefix configuration draft to the IESG as 
Standards Track RFC
Apr 2012 Submission of the routing draft to the IESG as Informational RFC
Sep 2012 Submission of the name resolution draft to the IESG as 
Standards Track RFC
Nov 2012 Submission of the service discovery draft to the IESG as 
Standards Track RFC
Dec 2012 Submission of the perimeter security draft to the IESG as 
Informational RFC


From robmcm@microsoft.com  Tue Jun 28 19:20:50 2011
Return-Path: <robmcm@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1D599E8019; Tue, 28 Jun 2011 19:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.517
X-Spam-Level: 
X-Spam-Status: No, score=-6.517 tagged_above=-999 required=5 tests=[AWL=0.350,  BAYES_00=-2.599, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_HI=-8, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YR7dA7jFdrou; Tue, 28 Jun 2011 19:20:47 -0700 (PDT)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id EF1DA9E8004; Tue, 28 Jun 2011 19:20:46 -0700 (PDT)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 28 Jun 2011 19:20:46 -0700
Received: from VA3EHSOBE005.bigfish.com (157.54.51.81) by mail.microsoft.com (157.54.7.153) with Microsoft SMTP Server (TLS) id 14.1.289.8; Tue, 28 Jun 2011 19:20:45 -0700
Received: from mail112-va3-R.bigfish.com (10.7.14.241) by VA3EHSOBE005.bigfish.com (10.7.40.25) with Microsoft SMTP Server id 14.1.225.22; Wed, 29 Jun 2011 02:05:27 +0000
Received: from mail112-va3 (localhost.localdomain [127.0.0.1])	by mail112-va3-R.bigfish.com (Postfix) with ESMTP id 9C0811398121; Wed, 29 Jun 2011 02:05:27 +0000 (UTC)
X-SpamScore: -4
X-BigFish: PS-4(zz4015L103dKzz1202h1082kzzz31h793h2a8h668h839h34h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: CIP:157.55.61.146; KIP:(null); UIP:(null); IPV:SKI; H:CH1PRD0302HT002.namprd03.prod.outlook.com; R:internal; EFV:INT
Received-SPF: softfail (mail112-va3: transitioning domain of microsoft.com does not designate 157.55.61.146 as permitted sender) client-ip=157.55.61.146; envelope-from=robmcm@microsoft.com; helo=CH1PRD0302HT002.namprd03.prod.outlook.com ; .outlook.com ; 
Received: from mail112-va3 (localhost.localdomain [127.0.0.1]) by mail112-va3 (MessageSwitch) id 1309313111999234_13394; Wed, 29 Jun 2011 02:05:11 +0000 (UTC)
Received: from VA3EHSMHS004.bigfish.com (unknown [10.7.14.242])	by mail112-va3.bigfish.com (Postfix) with ESMTP id BB295580125; Wed, 29 Jun 2011 02:04:23 +0000 (UTC)
Received: from CH1PRD0302HT002.namprd03.prod.outlook.com (157.55.61.146) by VA3EHSMHS004.bigfish.com (10.7.99.14) with Microsoft SMTP Server (TLS) id 14.1.225.22; Wed, 29 Jun 2011 02:04:20 +0000
Received: from CH1PRD0302MB131.namprd03.prod.outlook.com ([169.254.11.234]) by CH1PRD0302HT002.namprd03.prod.outlook.com ([10.28.28.64]) with mapi id 14.01.0225.056; Wed, 29 Jun 2011 02:04:19 +0000
From: Robert McMurray <robmcm@microsoft.com>
To: Paul Ford-Hutchinson <paulfordh@uk.ibm.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File Transfer Protocol	HOST Command for Virtual Hosts) to Proposed	Standard
Thread-Topic: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File Transfer Protocol	HOST Command for Virtual Hosts) to Proposed	Standard
Thread-Index: AQHMNcZDcdEZfuFND0GouWGSZJApmpTTjkbg
Date: Wed, 29 Jun 2011 02:04:16 +0000
Message-ID: <01AA9EC92749BF4894AC2B3039EA4A2C194A07E2@CH1PRD0302MB131.namprd03.prod.outlook.com>
References: <20110616130503.4854.51928.idtracker@ietfa.amsl.com> <OFA9997572.88B3CCF9-ON802578BC.006F9F84-802578BC.00716B95@uk.ibm.com>
In-Reply-To: <OFA9997572.88B3CCF9-ON802578BC.006F9F84-802578BC.00716B95@uk.ibm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.28.29.114]
Content-Type: multipart/mixed; boundary="_004_01AA9EC92749BF4894AC2B3039EA4A2C194A07E2CH1PRD0302MB131_"
MIME-Version: 1.0
X-OrganizationHeadersPreserved: CH1PRD0302HT002.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%UK.IBM.COM$RO%2$TLS%6$FQDN%131.107.125.5$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%131.107.125.5$TlsDn%
X-OriginatorOrg: microsoft.com
X-CrossPremisesHeadersPromoted: TK5EX14HUBC101.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC101.redmond.corp.microsoft.com
X-Mailman-Approved-At: Wed, 29 Jun 2011 09:32:53 -0700
Cc: "ftpext@ietf.org" <ftpext@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 02:20:50 -0000

--_004_01AA9EC92749BF4894AC2B3039EA4A2C194A07E2CH1PRD0302MB131_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks, Paul.

I believe that I have addressed all of your comments with the following act=
ions:

--------------------
Section 3:
--------------------

> Surely the first SHOULD has to be a MUST.
> Otherwise we have a situation where, upon
> receipt of a valid HOST, some server
> implementations will implicitly REIN and
> clear AUTH/USER/ACCT and some will not.

Agreed - I changed that verbiage.

--------------------
Section 3.2:
--------------------

> I suggest that either the "wrapper" concept is
> dropped from the document altogether...

I removed that verbiage. (That was detail for a possible server implementat=
ion anyway.)

--------------------
Section 3.2.2:
--------------------

> should be "to negotiate the security mechanism
> and relevant authentication token(s)"

I changed that as well.

--------------------
Section 4
--------------------

> The "strong method of encryption" is a bit
> vague. I don't think we can publish this
> paragraph without being more explicit about
> what this really means.=20

I removed that paragraph. By way of explanation, this was in reference a se=
rver implementation detail that in hindsight probably shouldn't be in this =
document. More specifically, some FTP servers and clients support Implicit =
FTPS, but that is not defined by RFC and lately considered deprecated, so i=
t's best to just remove that information.

> I repeat my initial point - this has to be a MUST.

Agreed - I changed that verbiage.

> I would like some mention of the linkage
> between the identity returned in an X.509
> certificate and the parameter to the HOST
> command at the protocol specification level.

I have attached a new version of the draft that contains suggested wording =
for this request, with all of the other changes that I have addressed as we=
ll.


Thanks!

Robert

--_004_01AA9EC92749BF4894AC2B3039EA4A2C194A07E2CH1PRD0302MB131_
Content-Type: application/pdf; name="draft-ietf-ftpext2-hosts-04.pdf"
Content-Description: draft-ietf-ftpext2-hosts-04.pdf
Content-Disposition: attachment; filename="draft-ietf-ftpext2-hosts-04.pdf";
	size=34609; creation-date="Wed, 29 Jun 2011 01:37:15 GMT";
	modification-date="Wed, 29 Jun 2011 01:37:15 GMT"
Content-Transfer-Encoding: base64

JVBERi0xLjQKJcfsj6IKNSAwIG9iago8PC9MZW5ndGggNiAwIFIvRmlsdGVyIC9GbGF0ZURlY29k
ZT4+CnN0cmVhbQp4nI1W21IbORB991d05WFjqvCVZAl5C7eELch68eylKs6DPNNjK4ykiaQB/Pd7
pJENxqQAF+XxjLp1+pzTrflJw/6IhuGTvnPVGVwf0sJ1hvQZ/4vOz84oLqD0lSs6zrDoA43GlJWd
Nm5E4wM6fI87qtM9zyZn/2Vj+tfYG6kX9NmapqbX/k369IX9Uhm9l/3ojA4ou+x0L7Rnq9n3Tq0o
/atzrTPRsTV+ydbtve10/64L4dl9pKP3RzTrypJEXVtzy8Vs7xUpr/t0lV811opVyBaQ6YILcl74
BlmnXuhC2MJRZkV+80yGK5lb4wzqODG2NlZ4iWKR6+y+ljYgO+Wc1ZwtHYz2aTwcjV5E9UejmcZH
7WrkOjiKvG2en8uKAyDtSqSdgA6Tm4q+/DnNgEIpYKbSWPpHWt8IPDDOB7YS/89vWgQxepJ92St9
zfd+3FuGuN7wHULHv8fQT3PnQYQPBSImW/IvwOyTcFRwKTXYlJquz0+iRN9wMcTF930qDDvSxm8B
C9rJgknQnVjFImBAyivJ2jsKhTm2txCfvKFCltgTTyQ8QHP2d8w6QVNN5WUNaKdfp6SFwl5+KTwJ
y2R5IR08yC1NghycjaUXExJFAdFcP9QmXcpVmLxR2CYVBByk+a5FluiOuRP48FxxvhRaOrWuIaX6
RSWIQhXlClQVEjmCardJvagCwfdCP0rUBvcfpJlGy5IpgUU6umJlNirh95Omwx3XzJX0vtWnbKoK
xWigRT050530S2TiXXUcDB73OT6Z0OGHWEq8PHqEBou3d3SR+bs0RdaMJry8WUxnegGK2WLV1taZ
cDd0biygzboXZ9n5bA8ifTUQPnIfRwItwnRypOAdUbngEPhVzhvPiYtdAOIpN634TBViA7wc4yGI
v1mVUqWywCS2X3pffxwMMIxEaJAbSBNaqW/sYhA7yw1SnsHLLMWARxBvRSXXVlXiXqpGBWBO3hPm
oV9u93bQIxAwZ2ridCz24fi6Enm4QhIzd6biIPx8lXh7RAdaRK9SiV4qBhsX0S9Sx9Fa29htMG3j
eBe+w16xKfM15QrLEVOFrRGVyygZq7Q11NMh7E2QJlgReyxiD77ZIuo5F99JuJbjoA0NsjNpA9Xd
E1OvrFwsfXCL3MB6uD3r5jgs4mQOxsIwa5yntquZarRoMHxqUQnahNvpjM2IEI1fGhs89AnY4gaB
ktiuRX+3ok1g25E/OPeBpUe9Fdtjg+uto0teiGpr98lDX15zhSMIDkeSGHW6ljbVPesmr/qQjvnB
pxXI0Y57ElMAhEAKxnwFHlAbQAQvwXcpT93MERCPu83QWReD6icVCxdG7a3EqEQ4fhRPoOQwexg8
q/1E6QoT1uVoWKaVaeyavsACKEQn5z4WGYcT7tS8OYpQ7lMIJwYHCc7D2uhobZxp4ewKU98atb0c
54Vbp5I6rxqETqWqq1bx4+kpXbb0kEee9nRrocb5OeUIjd71E0Xh9QnirN9Zftu8Z7SnbXo7ePHl
4NtELJhG35HxLOv8hc//RAEGjWVuZHN0cmVhbQplbmRvYmoKNiAwIG9iagoxMTQ4CmVuZG9iagox
MiAwIG9iago8PC9MZW5ndGggMTMgMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJyd
lttS2zAQhu/9FHtVYKaksQ0kXDoHCh0OaWLai04vhLw2KrEUJDmBt+9KOZAAM4ljT0YZjfX539Wv
XT9DsxFC092LkZfBt2ELChM04Tv9iuA5CP0DsBh4CZ2UHmpDGEGaB/N1IUQxtFptSMvg8Epa1BLt
cU+z3IK7LtIBXN6NUuiqsmQyg1xp+CW0rdgYLpWxBlbXj0oiRM0wPEr/BfE5pNfBIU3bR4RUV8bC
NRa0aqDVVBihpAEHZBph4qYyzGAm7KOqLMyY1kzaV2Dm6CAI4yUrQ8O1eKAnhfTgkSgnY5ELmumM
enAtOEqDDVq0EJCyhzGCyikAik5ax4vOlrywAUBRa5VV3JIkaNS+Id5QGNFMT/GqpHe5d05p9LHW
JB76lEYNp7DDjOCQqiesxfGskzWW0zZCPUUNQ6S0YT3aihXT/5SS743BF8aoqet0pSv2MY5epWUv
bqNsXfIGy8W4sdogDVbw3WKF9oo1pzltw/7V7R68Dyyn7d6gPh5cQWVY4X3pxW5nnb9juT0YWWYR
eoIVmpW772XYXMtX/D5fqLXSZruiBau1xjoh1kU/SUGjmZDn0VeLnfcyXObrxPuUV1pQBaAzZKg2
aDY/RrvqWrJO3QlPbpM9OZ61zP2Z8wLmqFHymmfnA8vRnLdulS5J0hTrkzdYka9k+b60aOmJZDJB
mYkXSJxZ5UzpJ19Bk7HrDZ69jRi9+SvxMd5RxRkrlglZ+NPd/d1bGWIbK1xjRZ+wkm5310qxwYo/
Yd2P+sNdWdEay/mV7MXHldmnh0Tx+9x3CJjwJ6lmY8wKdL1kR8e+sSrqpNocQJJldBzNHn71rKg9
b5aXaB9LCu4L3PCbirrz67wW9V8mgvjQQ47lA3WWOPzqPwJg8/ozcPUu+kvIfhr8pPs/aTXy+GVu
ZHN0cmVhbQplbmRvYmoKMTMgMCBvYmoKNjg1CmVuZG9iagoxNyAwIG9iago8PC9MZW5ndGggMTgg
MCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJxtVtly2zgQfNdXTOlhN6lSHFPeHH5J
ldey10r5UCwmVVuJHyASErEhCRogrejvt2cA6nAsHzwANAY9PT16pOOjhI75J16zavD2/gOt/OCY
/sHfavA4SGQCxUtW0d8pJn2kZEzpchDWJTQ+oQ8fPlJaDV5N61a7WrdvJk4tW+LPZTqjq7t5Sue2
qlSd09I6+mZc26mSrqxvPW0/n7ta0/g4SV6n/w1OTim9HrxKjogA62zeZa2x9es/B+P3MoIF05aM
pwzItib8toWmPgbZCDtuaHI7p1pV2lNryWlvyyfNtwpYyUmP5U29KrF8RirPMctj47QAfOMUds40
FcqTiaHoXDbLbJ3ppiW7FDTGGT7FwxU43HBE60I7TUoeSTWNVk4C0b8Mv/CkaqDmutH4V7cRBXem
3Yxo0eGINaJWJZ7JFwqhkQFrTbHxJsM+fKLOZXi9Nm0BGjTxya3TEcubypTKSQT+6IDAeZcVHIBy
TtUrXWFbnFd7XD15W2k82UWpKy90cjK9dk/a+VEMHa8OaZRhynE4ENoZX3C8NXKERwEAZ7WWXHpa
bJhG4/Zo134U465tG0e3GQQhOlOd1+EwiFtTV5vHTpcbMsyfWRrkpseNSBGanMJbhyEEzniSYsUi
wnHKcl8p/FrY5kNOZ8+A+D1A8nK7F3ms2yOIWOsBYDt6q9u1dT8jVl8Elwaym298qyv68er22+X8
x+vDLIkMK63qGFdulkuICrna1xoKQdXMmeXR3aSD9PQLlrypl01FjVlpOOcjkO4Yh4PevIAkJHQY
BNOZ4iT2KODyDMXmswIyYkgLFjKWUMvhG+87TbXWOe8XkaB7RtGSaluXgclcs3YC+E4XoRZU6a1M
igeJQFJcnLlAEPZT3tvMADsPZRGBjcOLnoRdto4iTrpppKagMPeGhyH/TERJWeeYA8TYy2/rKY12
qI5qL5YQit0LPxhPJ4diaTCFZFagex+MiwwjEQlLxFo49hCr91g/4hdOL62IcwNlZNCi8dVvrPc0
C/dr25U5MB87kAB/QFpjCuUQvIkcezYN2hVi8HT03HJ9IUgLSZsYoWpDkkXl0TGCwelg+FdpOnub
HB0jLQdyzPXS1JgDi/t+f3menP717mEk26+V771ahiNCwrazWxUPyGvH75P3DwjD2W4V0g3mjfAd
KeRuI+dnWgutcuSdi0vTym6VJHNxlNxmndihEXYWju1Lbb201E+65MlLrdoOfDbKsUFjanBExoIz
9P0irK71OjTDLDZDoQ7OY9f+Jc1tC8U3OjPLDZqJgWHvV70Ub3BUvmWyVZ+7PbCI01eHeBfHFOkI
yqu6sjVNqZ/ZCit21x4PnZDFETv1GGROetbObf3EHgFxPbMyTT/hLPBBGMHw5us8RY+UK93eyf39
xZev0/uLCd/Pr86ur7c3YcaBgDBw9/U6zuW7Hcr53c3Nxe0kAN2c/TsMwhrezdLp3e3Z9ZBltVcl
24yLZ1vWt+HvEuiHLGPRnc+cWez0Ok6S04dn9VFD+KoCi3Cs4fmnYdh0/mm4czswj+Ryk+2bR7Bf
nvpCMx1xITTcMqG5zQutYRc5u2PHykFlBgN9VmHHp+9OHyQkqbdkfCLx77ZE/JAyzL2DzMVpCByg
SQydbsoNc8lC5Su3qnAVxrmlDPvePWzQatnTeCR0fVG85+dJOutx9jW6fTeb7nDkRVzwu6z33vKi
7UNcAJMLIb0by/mudFvwV8U/6Ca7gZ+rTfjiefGrMfy9aqIzXS3Q8k6SkXwRpcPP95laaTp5AOJF
OviCn/8BiD2PgGVuZHN0cmVhbQplbmRvYmoKMTggMCBvYmoKMTM0NQplbmRvYmoKMjIgMCBvYmoK
PDwvTGVuZ3RoIDIzIDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnicdVbbbts4EH33
Vwz8sJssHNd2km2Dog9O2tRe9JImarFAkwdaGtncSqJCUo799zszpOQISGUkgkTyzOWcmdEjTMZT
mPAv3tNy8Or2NazdYAIf6W89eBxMZQPEW1rCZUKb3sB0Bkk+COemMDuF16/fQFIOjpaVR1uhP3lv
Ve6Br+vkBhZf7xK4MmWpqgxyY+GHtr5RBSyM8w6665+mQphNptPj5L/B6QUknwZH9Hro9zUORzBM
TeWtKYDuFaZem4rfZsqr/is2M5zfXS2X/GARVFEc/zmYnraIjcMMNsgrDjLMdUXPnl+Mad/s73bf
3b7yagcWHxttaYs+7G6crtZ8BubNukQKPIPLL9fduq56Fn/eXl+dz07PHsaEakqENVZoKQXz7pBm
75342xn0G2ua9cY0nk0RImNlJm3Y4lt6ZxzCky4KWGFnulDEAjlAy+SwC2khu3MPubbORxiLKqMY
RqA9lGrPCE+a4LwBp8u62NOOlDJHMErMO+w5ijvdYXHqQt7dL10zBGemwp3v7B8SOxtPyZtL5XQK
ifmFlYsoCfvbRgfkg7EkD0ZKje0bX+stVhzjvK6xyvQOLsHkv015ImQ/B2iTlpsminIlDgkfWCC7
0PpV6F9E86ebxXwE75cfl8kI7m5GgD5laCMJGomfuSkK8yTKQFuyXlSWoeBHLJJeR00bal90ciVX
i/ktvIMfcn9F9ujfIplf8uJb2GqnVwVCXTQUykZ7BFerFLtEYjx5f5RbUx5ycX8sLAV42xQYUhmD
TzfKqpTVwyXneukUnK2ye47ONasTh0SOyUMNcLE9O05rktMYLR3TpmnTmYZO4MQTi64mPtD1k/DF
UEgiPOaYOBmB85ZNFxQsFU4olFSJAUcaIl63KFQr33OcWgNphVlnPmoyiHYrFdpnIeiXla/RBdvU
vF7yuaYwSyQ34jZpMcLzah+LrsZU5zpVYnajti0zW1U0LXqqKlagRfFJOgj5pKq9hBVDIZ+px3EH
HbL7hy7gyAVuX0PqAZ774KK73/Gd1RlbYe7rMe4URYZjCuR3QNe07UPcRt2asfKETv4bT34tI+zz
Up5xQ+OEWrhFSV2EvQt1D2fjGauEFTi5OL94iG3KxXqxJSeQvCxRVcwv7bUBiLLZI5IPCHf25GbJ
PYZnS0eM6JO3kOZ4g+SP2yOj7TsaWy0E/RwGwZP20mZJw9UaX6hItNbYk1auVJrhRWoy5Or8K5TU
1e2n657Tz87KVr7eUVkOz4ZU0cPzIVXkTJpKz+SSUy5jhUTmyLMig6qrCSk5blQuDKj7I+oB6Qae
iEbaFcJ6YQIJAWQwrr+kf8NjUDJrkQdJ1q27USsYml9elyiOPbmOrsNINDTHCyI58ktUfK+o1biA
zlMmQuGOjqba07Bxnq2NYtGHODTFX3FdEdlhJMlq2RRen7CBbpTFJiKk8sma2q/2BDh+OZfKOQoq
du5GnGujEz/aESafHNT0RlKXIiVe4odn6iMCdJUWDc9T+PZ9mdwft4ILNR7b5MHxVvkZutTqVaCj
o6gvv+T5R0CPsDbz7TDTGYs7120n4gAtYk8HmV7TwBcttqmmjdqGb4N29En1NKFIZZQNzyeTEP+Q
4M5nArdAvympxv+Az+nnxlr6ipDrw66mzxcH7zHFckV6Op2O5MMO+tfPG7VGOHsgxA/J4Bv9/gdn
hUvLZW5kc3RyZWFtCmVuZG9iagoyMyAwIG9iagoxMjY4CmVuZG9iagoyNyAwIG9iago8PC9MZW5n
dGggMjggMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJy9Vk1z2zYQvfNX7OjQOjOK
Skp1nPbm2k7sjJ24NtNLJgeIXIrokAANgJbVX99dEFBIeWrfSo0sCR9v3759WPgB0kUGKb/CZ9Em
v9ydwMYmKXyk9yZ5SDK/AMJH0cIfOS16D9kS8ioZ9mWwXMHJyXvI2+ToSjk0Ct3bcyMqB/x8yG/h
8st9Dme6bYUqodIG/pLG9aKBS22dhf3zqVcIyzTL3uR/J6vfIL9Ojmi4RaEsCDDYNTuojG7B1QgW
zSOat7dX0FupNn7M1QYRSrmRDgpdIsyO03S2ePNzcrRaAOS0xJMpBjI0vnwXw5yCwm2cgRmvm4Gk
wGWJJTjtA3A6cYlFx8OiafSWJwktW0W0wI7Xd0YXaC2vLZEEaiWlST+2tSxq0BV02lq5ptwIdgeP
gzjMmXBqLxGHLhqJysFW2ho9WKGVwsL5vIhnpHV/+eXr9TmskcjbHssAtEZSHj1ST+R8Zj39Uk4W
wmE5HxKJSo7mpFZgixpbnAesmD1xb3BDhWREO2dSFLbEDlXJXPuOtjJayMlnAwX9RbWYiH//TC7K
8eYrlcoZFI6qbyUheC7bGkMi41pSQpMCDMlDOyQtFGhV4DMVamFpDNVUCxA2ZOpq3W9qCn93cfV5
H2pLuywnGOBQUCHHZOZeIkYMOAa9W0JYNm0wlHUUkAk6wCdpffCKTOIn87PbWGVKPEBx8EoaEhJp
87phP5Q+nkHXm0Fw0ZGMnZEMHs6NNnvNAlIg+z9V4kdaLym/3oXjrOmQkL+Gc8Uwld77c8s+q8Wj
1Mb+PmEv+DR4nhyo4fQn1CgoWQGNIXjdcxUfemRjUKiwZkoegt2DtgKO09Wg6FS29euBX/bSs6gj
q06RPJtX7RRU4+c1Y71gqYHECIt3SyWdDKf+sFFE3/+HGUdIz235kiFJJJKvKUHpeF54GwlBPcZi
zP/AhyAOmrLiRkurZeu30ICnKw3MttjQRpzRfWOt2GDsq74t2pERw3zodh1x00o08h8cLrdRD993
bz43VEvbd5023GxHjVQ0Vo+CxD4/vS3q0WZyl9r0xIA6rjb7BtOxKZTzZaCZKGxgO3QkTSMmDtGi
RymGa+3iNP/Rqbyi89DlG/IIn5lxR+GzGbden37+uC8cVyvK9O3uw9ny3a/pd0/F92Gp6GvrGY5q
vFpkvHFH3J/CkT+8pRnv8PLm8pZYkTz+dA3twS58wVMPfImubsmTP8FNcdMbI3aD8y6eOklpwjkW
2K5JkFU29/93wPT5dstlPv5OkBd58ie9/gUPpe3bZW5kc3RyZWFtCmVuZG9iagoyOCAwIG9iago5
NjAKZW5kb2JqCjMyIDAgb2JqCjw8L0xlbmd0aCAzMyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+
CnN0cmVhbQp4nJVWW1PbOBR+z68445ndBQZD7Fwo7fQhS2iTDrQpuDu7AzwothJr15cgKQn8+/0k
27m4JBRlEsXS+b5z0dE5fqTmiUdN8ynnMG2c3pzRVDWa9BnfaeOx4VkBKqcwpT8DCL0jz6dg0ihw
HvktOjt7R0HaOBhmmsuMa7cv2USTGZ+CEQ2+3QZ0kacpyyKa5JL+ElLPWUKDXGlFq/FlnnHym553
GPzbaJ1TcNU4sBsx5NywJKCP5BhGh25HdidjKaeLm6tPh380vNY2yu7Z8ZGiPGUio1MajtxEwFKW
AOF314hSgiqEmo/dcu3o/sA5cTZW7g9r6jaELThBHCIxpbskil2l5QPkC8lqp1LTuxoNerCrP/w8
DNZSBWwlBQu2JTE7rkP3hxVhzZu1mwUB8M6dg+VFl0WR5EqR82DxJiSLdrm4MmBT0OD3ji7YY69L
zvvCItXya/Gpj9MdTM57UHRepNtFdFdbMciHgqj9RqIjbxuwQdV6K5W/k8p/K1VrJ1XprmP/vk7U
3ke0Hq8TdX6NCOv7ebq7eGrZbCxaQ202VzAzv5DF+5LvA+4MQ1FRYpqJiQhZpgn8Y4F6lE9oTbJp
gtGzaYJ31B5c/o27+KoyAGvUJPkMM0fFjAglI+ZPLOKhSH8qShtOWa2QcvNQc02mIP3S0+oE1vuF
B0Ud+dnepnv+6u397anluajSmxzwFNDzPSfueMj+mlqDarrefpzvGI1Nt9VeafyAZtF0/fZ+XKcC
dtb6/A5wnU79fE2bQZxneaY4omOf8//AwqXM5WrrhT5jxKgMquP7TQepjfZ0FFwMejdI6LI9rbX1
FC2Fjoklie2RZXdTx6RjXjW4quUtc4kkURSymnKRRXzG8ZPpYzKS171/aMxJzZBKE1GkFsueKYyZ
ZDh4aTmQB0pIHp1smRQYxVXTxGU8mIoFB1wRoxngKQce96wiV9bURdnLDZB0vmXeMhYhXAxDk7uw
v1JrdOHxdvDtx1Xf2GuIlGnVlsU2bR0zTUtWtaO5gjM6p3ysTYc1gOFodZmwUegy60U4My3zxMwZ
D7XIsw2uFDcN4ZqYcNjgJAIBNLILLhVkFcVswWEY3McZzNBfjXZjUSFU3SiG8IzHki8EMxJ4tUny
EMFgiWDWKrbCI56TeZI80yOiZc8GoSzeF0oy4/YxjecaivGWxFEiVJ4sRDYFTf/rbcl6f5AvM1hu
agldfO1dX1rBuQx5SSR5iIQBPQwwVQfVLc+EscuoMIfe7dgjGnAdpwjN73QdXs+lZM9FDl8+zXBO
ivo85OkYulresX0xq12vuxGbcuqaN5vLoPEdn/8BVheCzmVuZHN0cmVhbQplbmRvYmoKMzMgMCBv
YmoKOTk1CmVuZG9iagozNyAwIG9iago8PC9MZW5ndGggMzggMCBSL0ZpbHRlciAvRmxhdGVEZWNv
ZGU+PgpzdHJlYW0KeJyNVtFy2zYQfNdX3OShTWYkVZScONFbmiaNO3XjJmozncQPEAmKaEhABkDL
6td3DwQpUkympcdDDQnsHfb29nhHi3lCC/6L97Sa/PD+knZusqCf8b+b3E2SsIDiLa3oxw0WPadk
SZt80uxLaLmiy8vntKkmj6+0l1ZLP/vJitwTX282N/T23YcNvTJVJXRGubH0p7K+FiW9Nc476q5f
ai1puUiSJ5u/J6sXtPl18hiPG1ThldGiVP+EH2RyykwllCYtKulIOTK6PJKr93tjvczIF9bUuwJ3
+eT7SbJq4WonefdNrY+pySQJR5l0qVVbbALep/dvXq0uXixv59i2fNZlkTMS77Z0wJ6dupeahKar
m/sLwqFwf0alQq44mcgyK52bYkE2iJ4a7eRdLbVHsoyjjSeLJ8pyzga5WCCHWGdglFtTkQAcAxXg
jo8+DUvTUgGSrl/+RU7qLDwLtKeR9oPygYpBuhHqPA6ycnuZqlw1KSk/J/pYqFLiJ1UCLEtZAbrm
yswiitK+Vj7kbuL+I4kR+PYIDpXejVKMMBAOGO6dqUA6orRSZEdmT8vUN2nxGlTjHssbxC5YC9UW
wReQhytMXWa0lSQf9g3IVhbiXoGMrUwF60KE+s5YtHtrUmyOUHEzFwsAg3qpPJcWiSrhJV76g2Rd
UF6XqPAdZB54jDg9zbI0RvpB8xyM/XLOGvjfFIJj45xtSkJlU1L5qKojyk/FBPknZruUZKPCSvi0
+LrwjO2xPe0zf/3Hh00EwtK9aaUm6OniAo/2IIElpDOVMkGej/GtjId1457mvO5BYTZsxo8FOGaU
tgtoLyxuLB1oxINjN9belBzqYYd2sLUi/SJhQ3hxUkYorBPVVu1qTjtk2fF5RISHph3ZbGLauq62
0ravQ8kgDHAnuzKdE4sTNgp4NpbsWVAs7cuOZazT0rjGtLqDDY70+XHTTbJUlWIH5SbRx/YAoRaV
2hUeDeYMzWhb+8h6V9NTyNl50DZOcLmGjkOhooYafbQak1mdBk9GxLEnFIJ7ESXtlDr//ASzA/KQ
D6Lal43LRbDclKU58FniSxd8b8sx4ReR6s49IjQU4W0di9tTLOoNzyo7b+GTPkpeLOeL+XKePJrS
ozevny/W63SxWKwXmE54ZNpz9RYGDkLFIrvgcY/ySwv61gP1hitYX7d9IMnT+09nsW9j3N6K9boD
uR1E2fTGApqUfnu3Oc0Glm0ULNs9usfzUDz35OkgL8kT79C2Xs+exwT32RTQk545DzxhWyPkBJoW
QRWEw0RvTOYk8yoU050cI1jzzRX8pSwR9r7VgwT0tlSuQGTRBuZvhMGM4J3b0I3j4ag6m0fMILWm
b9sx1gyXzukb9rqJOoACHa0dGKqk0Ng7H0u5l1Qozsg7k8Y729k60DRXke1tPOCj9Er1BZ2q+Byx
qt9snf9U5nqZJMv/K8928VCFXzFp/lzj9A7KyWhnHjpg8fC4b6bnIGo3SQczFLRaWYrw2dEMVRaM
YVBpq8bUM5krHRyrq3KjjxW+fUEPf/Ali9XFbdAjMlNgRsme8gIyS5ETjSCDdFPh5AwzTu5RmlAi
b8HytFVAA4VPU2l5Kb388OrqCkBPl+F4b6UvKiT0HV2n17W1+MIK1+uHPRrB0U8ylaFVV8k0fCDT
8Pp0I3aSLrn/X28mv+PvX7wOvn1lbmRzdHJlYW0KZW5kb2JqCjM4IDAgb2JqCjEyNjIKZW5kb2Jq
CjQyIDAgb2JqCjw8L0xlbmd0aCA0MyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4
nI1WYVPbOBD9nl+xw4e7dibQJEBpP9LSHrkplCvhZm46fFDsdaLDllxJTsq/v7eybOy2zJwZMLGl
p923b9/mG82O5jSTn3TPqsmrL2e08ZMZ/YHfzeTbZB4XULplFb1bYdEbmi9oVUzafXNaHNPZ2Rta
VZMXSxPYGQ6HF04VgeT6uLqhy8+3K3pvq0qZnArr6G/tQqNKurQ+eOqvPxvDtJjN5y9X/06O39Lq
0+QFHmdb5VQGZE/KMQVLa/x1rALnpDzxt0bvVMkmyLuwZe0os86xr63Jtdm8/H0yP+7QSrtnlynP
dH77frkcoE9p3QSyAHB7jfc1ENjt2kM2esfmiGgZgCY4qvSWdFWXmj15WzGVutJIxxqJgRDPJmzJ
FvFTjUMqxikkHLQPE1BmK8SJ6D0eqkBZzIwESkc+QZQPrslC4xgRrLbW94cJIcY+xYT1iFcbHPNI
e/VISIaP8HrxuiPgmrWkSF+/fHw/nx2f3AOg/3R6LznJAQIQuSDQEJzOgrbGU4NYR3zuJeYHbXIv
aRlk6SlTRmrkg03RCAUX17cxeg26as50oTMlmNMU/BaF2bGbgsDyEamgUD5ubBBND91S1OJrU7CT
EwpnqwGj5++uP9IGhFfKtYWLqhOsA5AXBOlgQMrx0QKRRZVmSaWecQs68wnyDmmDiIz1DoKKUMP1
kA7jCLDW4JVsRGppHcJ3hzfLKakRb1Fa7lD6o3Y2Y+/p9vLz3acLgpZ1LhKIuQpEF3RKxnGUJhTT
1b3dQ7vUV7I+pQyE9qQpxTh1AWURahB3TAm1VetS+22CkuNUjYhqpyUGNgC1ppLu6hGH58Sasoik
KQM460JKejHMOSqExky6jgBD1CThThRYLJqN4SasCjp2ymy4LXRuhVps2codaNDKVE6o2SHEKj4l
L73J0t6y0RYJa2/dgyzINaoJfT5O2yVx06B4KLfPtiySQyCvkLnUUYrQJQiV1Mp7AOboRhgZlOsQ
a4SvmmxLlSiCS7W2TjIH06ELyNNhwvGyEgYT6ZGt2tsyWtuAJB+5Z4WlIhgPtSDCcV9LFQ4Wi9mB
6AMdlNmce92PxK3bvvKiKNX+L4tH8oxlwkJk3XewNjpolP1gzyWw+IBAj1cb7lf7WNBCfG5ocMZw
lIMs6QXH+Tj+ZTHW+pMe9rYpc3GpCpV+lM5XWca14HBr2pImDGuUAfj07ZGBYWlOOY3NjVE7pct2
a2ThuT5M0bdktoNlTOMePgqhnSzmaZE8zEoxz5bSLu2jBLUUGhEPhgFE1pRwJ6/RSNEFnwvm6vwf
aMZGVJuAHpjrH84gW8MZUCjIUdi3rYMOHQjxYRWYCA0K+dg1vO3glWn9fuQiKUnfrD3mrJR3yMH/
raAIyTwYuzeULK0zJRROF4MnoxJi29M4bsxel2V0VduO/26ydmQO2ICs1c/yS1X8OcAh+50Np+8P
kYHeZ09nJ22xfxgfc9jglw/L62cHyLkf0mHivJ29PX173x492usYo96kJo2m0X9heOJmnFacwjD2
PRLXVcW5mLdIsutFMKaMl+IPdnaeiE0iH3Tkrwa0eBoMy9jeuyKPOHDNW7XT1nUCFwviogC4RKzG
7XJ1hw/rOCk4SNHVOGvdUZVsXKoizxVmyP7XUNr7pqWzV31K7kncajyt8OL1aeTwksO2Qna/0VV2
1TiHIROvD99rzAZPF5j21Rqox/Np/FZK4+vrjTjfm3sgflhN/sLPf/rtrzplbmRzdHJlYW0KZW5k
b2JqCjQzIDAgb2JqCjEyOTkKZW5kb2JqCjQ3IDAgb2JqCjw8L0xlbmd0aCA0OCAwIFIvRmlsdGVy
IC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nM1WwW7jNhC96yvm1N0FvKllF81uCyyQerONi6Z1Y6WX
ogeKHllsJFIhKSv++85QlGM53m2BXirDEGxxHufNvDfUI0wvUpjyJ95lnXx9dwlbl0zhR/puk8ck
DQsg3mQNP2S06B2kM8iKpI9LYTaHy8t3kNXJ66X2aDX6tx+tKDzw9Slbwc2v6wwWpq6F3kBhLPyu
rG9FBTfGeQeH66dWI8ymafom+yuZv4fs5+T1/GJGH4B7h/btagmtE1sEUwTQN6+S2bdhGUVf0bN+
jS+FB2k0bVU78Ib+UA5cg1IVSgqvjIbbe8rJISXkSxzA0vkAJmO2RAMtmAa10tuw1FuhXWNs2EGj
ZLQJEKl+qdB7uLte/kJoRzgTyJGyQRDeY934AGZAtISoPeeEAZwZQKd8GX7dr6/vxjhUiIweFKaq
TMcg+CTqpkJQVdU6Ss2jg47pC/D7hoArqMxW6Qjj8LFFLRFqtS09PTIPUKkHpBjUh0oc2FPVKKPN
d6M6h2vxoV9Z+OYi5nBBUaMahmv9AWazaeg0CCmx8biJyQxATJMomeO/KWw+T2ElnOuM3YClxJV9
Ebq6Wq8hF/YkdDafBsEw9y0SDz1isCyoPINYWAOO2gZis1HcTNblcRHOdW7E82wXJ7QF3Xa0CVug
sUaic+elOTTnpUC9RVrPmJ/LTjCmabcl7fdSd9DRc2LoKR3NVXToDykGq5jw0/k+d9oMn5R77lEv
al6SLVZHig/AhbLUVaTgvFKuRJbnJ3JCFMQEFBU6AgVlR4boAmJnDRVzF2dByQrJ96RMwnugYG4M
V3tAcG3ey9ePK9CR9okZpVXsAy5aa+ypUyLIZ/3CgcEp/+yRCHXqFC4z+E5R5CCZnnVJpcqRYo+F
8kVTGfOfTRWAyBknQP9rX2an80eSLfMgVl7Lf+dK9/Y4DMmrxeI54MSZG1UUaLnkLO8cfRfaENry
ysFOWGVax/xNq+kkMvxwsOGgzMiB9UmiWup4mkjUHD4Z2SkOkxOBlkqWR8KJYyEcZhiGgDUt5SdI
wjvl94MppbEs65FDvj/CGW8qqQuBacVDezitQg85idCRmJH7Qko7UakN2yLspM/S02eK/jzA9uEM
PJpXsbzUQZ56ffv4LSAMnmHjCKFYqzXxCMv+1XEnomOZ+jMdHjL0liArxbY8EA8jbsgzN74cmsVE
mNXkoKxRaXh0NkZzv0yt6CjoX2Ryi9wx9nI6/SbI7gZ9WRPDr+BW3rbWin0v/+unhozi4CNKrHNC
nKeT8LID4+uPFb/gvP+TIK+z5Df6/A3ZIP5BZW5kc3RyZWFtCmVuZG9iago0OCAwIG9iago5NzMK
ZW5kb2JqCjUyIDAgb2JqCjw8L0xlbmd0aCA1MyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0
cmVhbQp4nK1W224bNxB911cM9NDagKzqEt+CIIB8q13UjWspLYrIDxR3JDHdJdckV7L+vjMkd3VJ
HlqgkoW1lsPDMzPnzOoVet0+9PidrrJo/fR8DgvX6sHP9Fm0Xlv9EADpIgu4mlDQBfQHMJm34r4+
DIZwfn4Bk6J19KA9Wo3+5MaKuQd+3U2e4P7TeALXpiiEzmBuLPyhrK9EDvfGeQfN65dKIwx6/f7x
5GtreAmTX1tH9dr1xwgz92UX30RR5tiVpjj+sdUfHgZ+Ht8+0zmGFndvP43GY5gJe3B7dH09gdKa
ryh9n9YGZzXeZKkc0J/InQFvK4T1EjX4JUYuMqVEIZXDDNbKL8Pq6PPkHmhlj93oZtRscRQmPAiL
kCknK8fblYYvz3fXg8Hg4oV3h2/vBv3zly7AA5+rXOLuJGphlemE4+hwe/L0AA4ZWeyTWy+VjKwo
ahUDaUON5A1YU3kEIb1aKb/hOxwtjbVUEVilXi2pV+E4vXfmLtRO5ofZGtC4MF4JOilykZXl0wqU
S6GVK1K9GMhijiuhqT4Vn+eVFF4ZOtf8jXp65KbH21I3SX3Lra5VqArfA2kxYzxqKN1QehHCg1yY
cxBIw7kpXINTl28lcpVRJo76MpqT5HeKXNflcfRXOJmAg8ISSN0VKogrUar5hgLok2WKU6Q6CylN
RbkrTU4pYuLsme8RUWyDgjIKYV1WLFJwnps1J5d8AirPK+ctMwbRgLxWsRSMp2jFzEHmiu4diLTm
OTNU8iSuba+Ce4ItqqRhafTXSstAfKdNqd/fGCDh/BsbdA7bTkpxpdFbCZpCeY9xyMwssp7f71n6
P8+SIOgPjUpPtCjw4+EEYa1/mAmHZ+9IF+Jw/X+ZR8PuoDukFo89e+hGiYUVRZ03992FhSwtcBl5
YHDlQyu2IgC/KclSedKApN5Tvfayr2XKH4tlviE40jkXYYEwQ7/GgznAkY0wu1tabocSj7vCZOTu
DEzc7lShcmH3aNeMz0iSCYgl0Ls8vXzp7nWThiIKMl7aHafh9OiKBkR7hgul26kqPMSdqwoMzjOS
xAgiODfaaps5VUiTpiy7QOvEZCnIHiVqzDpg6p0Cnm8ffmtKRTG1tSopkQZNRt36RPh2K3oaXhXx
Jbi7W9JM0Pnw4vKFCAc/WOqIoirpWisHE7AQGzpohbEdK2a0X5FRM0jyTYco+qVFPMnUQvmmkRmj
8SgglZG13Y6bKOBABxnykAMeljm3koGIiEhopSBD7kDSLNsFC1mlVEJDXG1hSjaAdWhKSSw9zxBK
/PucAg9onn4ZzpWOGhLahAozDyJ6R91Jjubs91i3T9t0eE4Ttoxppsdf+7TXa3f40o+XAV3Qy26n
ftwborPlEXVM5yYIfCPKztFqzUtFbSdV1rRYqM34j8lajA1KSKVxTs2IMD2QKRLd+6glx8IZT487
MBcqryxr/I6/MhRaS+jTo9vpcf0zoXlQ7E+EGdJzAdbBs9F8m2JmcrgK4zIZJoJuVxPUnzFmLaiQ
/F8oR5u1dzoIYrlHvyyoIT/Ao3ysrCWhhtftW0mCdnCDEosZdWrY74TfeLD3+vIkaLD0ey+EeDtp
/U7vfwDAYEi5ZW5kc3RyZWFtCmVuZG9iago1MyAwIG9iagoxMjAxCmVuZG9iago1NyAwIG9iago8
PC9MZW5ndGggNTggMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJydVd9vmzAQfuev
OPVhS9Wkw9Au3R4qLWuyZFq3LGHZw7pJLnWACUxim2WV+ON3OEBCIU0yIzA29913v8wtwTwnYGZX
PruR8WrSBU8aJnzA2zOWBtECkE9uBD0Hha6AWODMjTWOgGVDt3sFTmS0RlwxwZnq3Ag6V5CNgTOG
4ZepA+/jKKL8AeaxgFkgVEJDGMZSSSjHx4QzsExCTp3fhv0GnE9GC7dHHBh1fYjnoHwmGTwE1BM0
km2gMOmPPoOb614FYQiCqUTwTLQQBBWfvjSIXSjMPt21enencHLPvICfgFRUsXMUsl4XQg4K6e1S
S8BhEHiJYOi09OOVRHr1uAhc9ESyZcK4yzIj52G8wrlC6cZciTiElc/4Oh6BhESyzGblw7dpfwKZ
B+N30ymaC2HsZXz4RlFPpmFBhQrcJKRCx/RPHkIfQ1g1fGucdTqdM5w1Ybkmbbt9WbFua6TQg7RT
jusUvm+v85Hb1EC1a51rrwPrMngdAbTal6aJt6WBF/hG8EYPzYvdwKo31Y3nGBssq32cNQFnDfKk
AtQB2x1XXSHFumo+5qjfZG6mtpZKsI5hraw38ck9/XVcNtMSuL8M7CKbhwCbs7kfuCOb6fHA2gFp
OiI1HEnL7XQH09O62SByzus9GdQ/lHJtFRrS9WN6cN08Kblj6mZj9yHHf9vFQxHrOvlfDnjGoZ1Q
2I7P4DDWWpmUrA1/76LVvAUn7zHYE7AllJ1GNw79Z8/bX6bHIlrRkCk/ijm8gFv3NhGCPq6V9v8u
AsEk3DCXRfdMgE3auuNW7fwxph5Sk5+osu8YX/H6B3fTmIVlbmRzdHJlYW0KZW5kb2JqCjU4IDAg
b2JqCjYxNwplbmRvYmoKNjIgMCBvYmoKPDwvTGVuZ3RoIDYzIDAgUi9GaWx0ZXIgL0ZsYXRlRGVj
b2RlPj4Kc3RyZWFtCnictVbbbtNAEH33V5wnaNW02E5LAg9IlCYE1IrQmPKAQFqcjW3kS7u7JkTy
xzO+JXbjOE4RY202E8+euezJ7jxAPzOgp08x24H24nYAR2o63tNwtAfNyAxQTHaAS4uMhjBMWAst
X2fA7GMwGMIKtKMPoeIi5Or0SrCFQipja4rJp5mFd1EQsHCORSRw5wkVMx+TSCqJtXyMQw5TN4xj
65fWfwXrWjuiny2XQyqmOOYecwQL4IUYe04syBrSjZYSimwWfrREtIAdhUpEPpYuD8Ey78fPNaNf
4tlFJJ6E5KEChcoFGcaSJpdJMF9wNl9BxrbNpVzEvr+CHzkOn6euVQRGgCnU7yIRlxLB0lMuvsxG
t0jRp29nszMyM1+WftvltFVqCbRKsud1Efl/x7g7GOOE8jyhOaPLWjd6/d5FZ4wEl0g2ZXuT4GtV
L6RbHLv00lMbRoN5Q1E7YZi9C12nYWYY5/TNoEFF0c87YWylvl2IfRitfCheVva7EaOJD0YNo1bn
ln3J/mKlXs+O9nu0ibaRH9jmB50iT4mjpm8KWrj/sacej6TCj2SNcRDH+iU/DsTYwY9DMHbwI/kn
jIZTsGreAcPYuE6aguzE00r4BWeK/c+PqRZ+pDfARjdLqCT/mG142JGmj6iewR5weiW7c94qTHXq
tiLn3VN9oCWhnUtRrc+4m9ctVq29NtzTZY/xGteRQxe/5A8xD22e3/SC33NqSuY5EYqmIgXShxnS
hCs3iEI8w419EwvBVjnq6M+9J7jEFbd58JNajr7Ry7qeeqDfpszh1Gp9J8iRpX2m5y/KRMOxZW5k
c3RyZWFtCmVuZG9iago2MyAwIG9iago2MTEKZW5kb2JqCjY3IDAgb2JqCjw8L0xlbmd0aCA2OCAw
IFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nLVWXU+cQBR951ecp1bjruVDq+2DiR9r
baOpdak+NH1AGGCahVEY3G7Cj+9l+JBdQHebOIQMM8w5986Zm3vnEfquAb14qt6NtA83BwhSTccX
egPtUTPUAlSdG+HEpkWHMEzYvlbiDJgWDg4OYUfa1tdYsiRmcnyWOL5E0c7ta1x8n9o4FVHkxB58
keCWJzJzZrgQqUzRtG9ZzGDqhrFt/9GsT7AvtS2aPvaJFQ6ylLrQSTETQcA88HgEJ4bjeVxyEROf
47oiiyUiZ4F7hoQ9ZjyhlfeL7feaYdWEMmQgrqeClTxKH5jLfa7WqX/ujDNioVGW8jjA8empDbf0
fxe44zIkvpKJp+QHIh57o5JXOpLB406QOFHx65wHWcJgIQ3FPKVtyMUDd8nZlLxjscsqKuHDn4l5
0bsilomYYR6yuBSPrNDuPczJNH5OJzfK8evj6RRSFHoUlqSoqEiUQvanSuWQVFbr1T5qKsKVG18o
EUvldonB/Fjr1Go74/F4h3rlTTM2RtZof0naVstxgnzctKMcd+1x1SqXe0wNjSv2LrC7hp4NgOZo
X9fpNRVwj74MemmH+t4wcHk3qxPDFns86/zuBd72rDZWgLfDqqrgqcfLzh+puS60oOwcJMy2ADQ3
6XO39yxraXIFHrLaI0ne+srXiACrPshXMP1n+CJm4PjyN8e0/VwPY+TPdgYxq1H1OqY+WpWEmrFZ
H+vGAbUSizmmawfUkiybBlQdVmsHFMXTa5jBpIBGnrUDRNnKn0/kbYGd5LUOkMpA3rb4ErAv0MwV
4AvpS5UwNImkRP1P+iqyQnvufMP01Ym2btmsK/9nXIqA6nNd8MsqrippU5Wr20VaFNO9sppeMBlG
IsY7XLlXWZLQnUa1yd8HutSkOGMui+7pDmMZI3VrWvb917UTMBjWb6Kc2NoPev4Bhvv6y2VuZHN0
cmVhbQplbmRvYmoKNjggMCBvYmoKNzA0CmVuZG9iago3MiAwIG9iago8PC9MZW5ndGggNzMgMCBS
L0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJxVUsFS2zAQvesr3qmFGUhjBybpMSWkoQND
CqY9MBwUeW2rtS1Hkgn5+64cxwVpPGuvnt++fastxqMI47D7qCrx5WGK3IkxvvOTi62IOgD6oCp8
Sxg0QxQjycThvwjxBNPpDEklTm5qT7Ymf76wMvMIa5mssbp/THBlqkrWKTJj8Utb38oSK+O8w7B+
tDUhHkfRafJHTL4iuRUnnP5dUA1f0IFH9TzaoXXEsQ6pja6l16bGTvuiA4fCjlRrtd+ffhbR5EhH
b55qx1jHOOmxI0vM4q1JW3UgfH5YXsVxPHs5g/Z4XN0/3S7QWOJjCuTMF5iO9ChYkCvkXxoBScHK
ZFmancPGsBhWac/XNwii+fWVv1hbT9FYo8g5Yi0GlWwY9d8yTg0lUuklZMP4xmrpqdx3tQYpnnNI
tcytrEILS5233NcFXBGUSPh9oxV77mjbUq0IJkPGKkNUJrRf9ly74Hcn4OjxYOr8KVl1jcwX82EU
vY/SBgFOtdxO2lO993LEucvZZTeGFfmi4ml9wp26a62V+8MNuH5rtGUzFmx1tSGLSXTW3Qh8WM9r
mROiixemvE7ET97/AGkz1lhlbmRzdHJlYW0KZW5kb2JqCjczIDAgb2JqCjQ0MwplbmRvYmoKNzcg
MCBvYmoKPDwvTGVuZ3RoIDc4IDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnicnVZb
b5swFH73rzhPW6uGFZuk6fZQKV2SpVOrZoWyh2mVGHMo04AFiLZJ/PgaKBdjLibHQs6J/Z3P5+LL
HtR3GNS0vfa2h84f5uBESIVP7HPQHuFsArx2tgfXBpt0CZiAsUM5DgPRYD6/BMNDJzd+TEOfxsoy
tHYxpLI2trC51w34GHie5f+EXRCC6YbxwfoNmyCKIyjl88GnQFSMT41fSHsPxi06AU7OFEU5Y31m
sdTxRJvMTt8irLVAEriGRCnlKoGvdb0QBu/g6tIL+yJSnMPaGCSZzFSVfSRDTtkvzD7mpDrtQfIO
Nf/o4WxbnDDcijSPRBaxXDwam0pnjg4i04G+dF4NcnbpfX7WRNOmQj77kM2sSCO5iSRjHYMUcy+B
NJu8TGSykscygcVyUe1Lqay05pMFWZ6T0+vu9vj51PAz4fuB2B6HbFRCMzkD1dfGOYysJ5+wmEoj
k5bjRBbZf5zko2YL0mw7TjCPzJLcvbcf9dVDqTfizEprJV+BZBQvp9cjlnv7NO6OSCrk8O2iFXeE
FFJIKncsyZ5G4rLHINs2gQQQV1st6SRrVlBtexb5HUjldqHrlU4qG/nO14+5lGR4Rb3glSge4RiS
wtSL5jge6ParGwv1QK3leMWiKXnJBf/qW7vOIaQw/QC3geP6ENH9gfo2hb9u/Jy/HNN3aPr0OM/u
Kzt/mUbM1sUss7Wh8bMX+PAG7uy7Qxha/3PTq39/3JBGsKQ29X7QEDQ8yR6s/Fq/bS2HAp59ZxZX
BvrC2gsRce2sZW5kc3RyZWFtCmVuZG9iago3OCAwIG9iago1ODQKZW5kb2JqCjgyIDAgb2JqCjw8
L0xlbmd0aCA4MyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nJ1WWU/bQBB+96+Y
p5aKhPogQF+QQghNq6JSYtIHRKXFXttbxTZ416SR/OM7PjbxmTiMZa1nvd9c316voJ5ooKZP0Vq+
8vn+HFyuqPAVX1d5VbRsABSN5cOViYMuQNPBdJQcp4FuwPn5BZi+cvQtEDQKqBheR8QRkMqNeQez
n3MTJqHvk8AGJ4xgwSIRkyXMQi44bOR7HFDQVU37ZP5VjC9g/lCOsHvsoFUgEHNsPMJhGboutYEF
sGLCA+FR4NSKIybWYOVuOPYSASSinz4qmiFN2YxbMec5+PH+ZqLr+sXTAEgAxLaZYGGAYRHLCuNA
gE/W8Ewhoq8xixDzvE59ocHUFAbzloaFKfEXajGHbUaAtWQU8ajFnAUujCcTU0Z2AmCmAQsipCmb
ETcifhrTDXPjiMIIuBeuOCYt1i/Mwpg4BkEDi0LogLMMV2lrhYGIwiWsPBoUprJSM57Wyt5WZ/xg
zrJIx9djs1SiMC1l6ha/sATIVWHmrSDIQ4JyYJqBtIuj85TXWeHyap0gVD+ThS7J8XA4PJahbXRt
YAxGFW5KksAVJMONXCbwu6xLKYJt8dWlS/tNZHMMPocg9cFIVfHVM+Qpfmn4YpLqaTfyuJoQ9jQ6
OpBtwTX+tyIX70TKWmaTaaNjonuRaf9OOi/3+ezSd+VZEsM4bfK5A1knoTeyMlDPvB6CbFDfB7mo
+0Xpw0peyyTfE6Tei5VWPrHI/X1W9Eq63Xn+qeWZtLWdtX0fsjYTGuTsnn1tPvcjK+Trxqg3Mmnd
Pfoh92wnnchF23ai1ZGL7pX9MJ/eb/RalS+zzr7zT5e/Zee0945SXug7/LaUJSl/Jj0OFkMeD/tA
DSq3MXaCulhMDgJV3PYDadullC+2XidPD5Ck6248n291Hcqz/aBpUp9iCcwPOXj6TM+GyPyKhPNE
R3p28ZlR4flhAB/g1rqNowivnJlM/73gnZPDNbWo/4wXTUMbZHfjqunHO+JS0M6e0OLUVH7h8x+O
nUVhZW5kc3RyZWFtCmVuZG9iago4MyAwIG9iago3NTcKZW5kb2JqCjg3IDAgb2JqCjw8L0xlbmd0
aCA4OCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nI1W23LbNhB951fsU5tMZFmU
ojjNQ2ZUX2pl7MaJaXc6nT5A5IpChwRkgJSjjj4+uwBJCZLiCWUNRQC7e87ZC/0Eg34MA/4097SM
Tr+eQW6jAfxB3zx6imJ3AJpbWsLvCR16D/EQknnk7WIYjuDs7D0kZfRqqio0CquTCyPmFfB1ldzB
9ef7BM51WQqVwVwbeJSmqkUB19pWFrrrU60QhoM4fp38F41+g+QmegUvXSPYwOZtb7wB+sEXPb7+
NYpHx01Pgmt3wZm6RzI/MNwci73Z+XPPP2W5j+DnLOPeaBPEfMny8Yin4b7l46HlG0L0hu6T8/Ok
e26laYB/dIuHtnxisyX2cQN/0RplZocxLV4dQ9zGDZ7DVG3jDt/tpPZK5rVBGH+AG51LBRafalQp
wrOsFr7quOImD8n16eRikpw6aqkvRMtIRv1RH/zJZhnQGG1sAzNZIHk1KzQnd1O4v/78cHMBBpfF
2scQMB4MgCp6PBg263IOFVmxz6AUW//SQq0MpjpX8n/M2LhWslwWWCK1T9YPWE4sZNKmtbV01FFM
K6kVVb7mOOQs02nNlj2OLEIutG1pK8BBjYmGDtbECxbCwgxRgagJtKpkKgiCI+Bpt5wzDZqa0wXF
Rpy5Lgr9LFX+IYAsSNF7pOgszqhRhbteKGKwEoXMtpkih20++o3bGdknBkXV6djxIbTVQtc5C//1
cvpnt/EsPFPO98EAMGjRO2POnMhKe4oVsaVfFAq/ScvMvTq8uTS4krq2OwUbYNkNSRoSQexikK7Z
EV17O77YircIXVUb5UzFcmn00khGtZVtX4W9AiGR4+Z0k6sZemBNJS5oyCpRIuRyRfG4JtaqEimD
Kop1IFeTn56Dx/l7+0PXInQDzrAh2IWkYEqTRH4XVs3c531wB1qCvtoo81PSrCgaP7ZOF5AKi7a3
c+qE3ymkVIrWwu0DKRNU50t1Oc1Vm6ewsPibVlxgh13EyWQWnNCD4mI5+pwGV1sBssnfPsPWN4Ot
Z77sq8D9Tk00IyWT8zkaPtfqGKacG+S80NbzSLVSfii0DTTp6pzGDMoVKXFsUFET7BH1SQ6nhbU0
XXyPVMEwzDT65Hazq0uvP0STZU1IKHqD66CQ/XxtwXZ6OQF5Cmko3Fz3WdkOnh9mx2djrz+OiKH8
lG+FYHI8STvd50aXDm73Mtgq4k4vxAp9xAxtauSM4C7Itu2TfdlaZRxy2c6UWomVkIWYFeg7jmZP
KRW3P7Oj1wKNDUqsG43vxg7BNVaLkl4Av8BtelsbI9a+di6/LSUNOrggluWMRtAo7rn/pcKX7T93
IkeIz/4lj5dJ9IU+3wGWOcprZW5kc3RyZWFtCmVuZG9iago4OCAwIG9iagoxMDA2CmVuZG9iago5
MiAwIG9iago8PC9MZW5ndGggOTMgMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJyV
Vl1vGzcQfNevWPihTQBZtaS2cYrCgOuP2kXspLaSogjyQN3tSQzuyDPJs+x/31mSJ+sSB21P8BdN
zu7Ozg7vjg4mUzqQT/5ZNKMfbl7Ryo8O6Hd8rUZ3o2ncQPlH0dBvC2w6pOmMFtUonZvSbE6vXh3S
ohm9uDSBneGwf+pUFUie88U7unh7u6AT2zTKlFRZRx+0C52q6cL64Gn7/NEZptnBdPpy8Xk0f02L
N6MXWD4mz+6e3f67SwprFchxwfqePSl6f3t2Q0WGDpaWvNIGu5hUh+8m6EIFbc3L70fTeQ/o+a5j
UzBtdFjbLtBa3Wuz6nFL4MaUe9zbi7fv35zS9dsFtnzmIkgAIArWbgITopNaI6jHikGhjaAiK1YO
6y6S4VsudJXT8lTaDGRsQGKIthvaA/JS6tGAVJ5jZYkNujr+mxRyUZ50Rd42fUolV6qrA91nltdg
GSWWIIcN8UNb60KH+hFANYrhckw2wbH0j5TJQGwAYU2D5UQ8sih1VbGTlcrZJi3bCmcA17WtdcDr
I2cYie/H1LJbq9aTRZPRo81aF2sw3RnwECHqmtS90rVa1mhfUdhOmOQHjeMZSrqRDraOfWRaGbr+
cH6bMlFtC669cI4OBIU4vluWGp0N1mnuceLmfodwGiFEmpLFV4WkEiY4PPs5img++RGdOT87FkX4
Fo3keHq3dznUX1AhNrX1YxaDhIsne3l9vDk/mc0PX38ag44sdVFK62zB3g+kGxPP+fkINVDq1Xv8
oU1RdyUopFqD61xmjL6VrcefYHljXUl7ArGHehYis7jUy02jMON1wFSMI/mikqVI0ISMBAKl+Y1+
CJ1jaSSyg4rARm03+EWAxmBww6JaHfpxyjAAyEjpnGyPuUS9jWONW463R3956kXvHidHkdYBXfG5
PaLZdLpPv0qeJfvC6VYqosAP4SgH73fSZDL5ckn4+fdtiEFnse1PiS2QPNe1bj3cSptSxp6prRXM
Z23rkqHVzZqFN9TpqGIlLHpq1COqHNSS21qmRiicEctw8DLIu5ykYBiufd8KPKKB3egy0pSn1ucY
URxeOi3KURiPxyclSm3ZgEXot1x0TodHmDjUgKyTeQ1KPRZv8EXnPeZG5g4jJ7HnKbpYhy068ZIn
mZNu2pqbPs9BuVHKwbFM9VDkcQY2sL0onyVj8ETsHTBhcz7aXO8XT5eA2LpMjO1WYjs3Z5fXW8Qe
LFObs+sFPsgxTsB/SAv3n1hpzKr3wZzb/80q3QGsRSEZKjUUA+ELNsppmwflWVoTleKXuxfX8H7c
9fpxSkmqsV1diiXaTbQ3zyvHq75XgrLksJGSUvCskh0sH8+xgmMPriMrriH3Ye9HMfEs4i/SLxn+
VfucwXMxMC0Z515BxitpD+63pRItWpM9JA5KOgD+Yk7fkmF/19g2ah3W6R994CYJBO0C9X1aMol4
iZC5SDQUODUcOTh5sIWt4X64cyu5OoSVByVxZRwG3OxV1k7yPycQw15iK2PFd4iUdqNX6yAKE8nm
14ooOKMajpm2yvto6DUu0bFcnTXv5DUMu1Tuq7CxIEF7Pmz/xrF9Kfh29KRi38VLv5ftOMlSGN7e
zM8LSYzKsNyH0mGRguzsC0iZyb0PmJ9m0UMuOKwblPAdXRVXnXNw1PicPbRaLPYUaM0S9cyn4/jW
SYPn4zu1YpoefgLi2WL0Jz7/AJk/l2JlbmRzdHJlYW0KZW5kb2JqCjkzIDAgb2JqCjEyODAKZW5k
b2JqCjk3IDAgb2JqCjw8L0xlbmd0aCA5OCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVh
bQp4nK1WUVPbOBB+z6/Y4WauZS5J46QhpG/QwEGnkFzw3dxMy4OQ14kOWzKSDM0MP767skIwR+fu
oc4QYVn69tO3365zB4N+AgP+xFGWnXfLCaxcZwC/09+qc9dJwgKIgyzhOKVFh5AMIc07zb4EhiOY
TA4hLTtvz7VHq9H3ZlbkHvg6TRdwNr9K4aMpS6EzyI2Fv5T1tSjgzDjv4On6VGuE4SBJ9tN/OqMp
pJ87b2laVBUKC97ADa7FPYLSGVZIX9oXG8itKUGALBTdQ4XWVSi9uscuPKxVgeDXuP+mk4ye8GQI
7tDeowVVVgWWtFV4ZTRk6IUqHAhLcazFAu8FwQrPMFBZ4400BeExEj3Eok83w4Mt+BXHJpxk3E9I
WpPDl+Xpx/fDZHINmXKydg5dwKod8uO/++PBFCRar3IlhUfXIstyRaaipm3a8yKK0AdIxa3SqwCm
NC0smyMEQfyaKGdG1ny0SFdp0lBIaWrtWRzUBC1ryyCcJ2LmCMDBg/LrANs89hsoUa6FVq50ESvg
s0gZ5kpjRuC7k3a32WiL6+DqbP7n5xnQaVS+eY7EwdbkBi3KkLANcBZpEeMG5YWlR2SvoAjPBFfJ
xlURigSQ6yivYnsw9YCvXARUDdXmcCzrG9ekIEI8SwSvMzbDYL3KUq7pRBStp3SP9vdKlWVkL+G9
kLeubYMjWKFGSzaLSefEULaVczURJF9RgIyBWzLTCk6EFJq8/sIHtX4SeTieTK45YCySMZnh/Ojy
iIpMOzq4beRuMQrPFYe+IwYxuMWVciwqs8hNUZiHrRnwm0cdaLNjbEbzLUKROlWExKwmIxCouCmU
WxP0zSbwHE+mk+sPLRq/9cIVh9Z/z+7+taq9qEXkkTpTxsPpyVEKYSJDJ62qQjU8gt9UyKuMzmkg
Wr+4d0vM0aKWlAtuSo8x+49NI3okITOE3QRs59vDpaFyhRfXFutnnbThFdweh2ZiWy3hTjSDaYb0
ePaS1c/ntcspwOU8PYF0zuLCyew8nS8/wKJAQS2urjKuJaYU607cGGribBZ86jStjL5+6bq8IadS
ifg1+Xjb256VwQGVwS6xO4oH1IqJY9MgKXRrDQdkrw6m4+k1wIJkxaILn/rBGDQscaNNkbku7J3y
6yS1QjsCgMXuZfAq969vqY6+7u914SqdwbQb1KEoXZhLb/gsyfRw3O4bzCQZjN4Tkwsjb0WF3ioK
vehT+JkpBWl4SVl30ONil1j5xsGnQqpCeYVur/sjQkwjGTU8OEiXNLnHMjKZvMpk/H+YnLffoU1D
fp1C04SbV1hU5hml8X9TSoYjonRsBfV32sdsltTSlA0EXHg9bH+HxB8Yvd6P6BxVVRHJBBWv6qoy
1kdiW14UspWzKdM6GAe8M/Trknb/ChfyorZWbBrkk28VUXIwQ9kcZ5R0w2+bNoEvC7FCwrwmxJO0
8wd9vgPMT6nPZW5kc3RyZWFtCmVuZG9iago5OCAwIG9iagoxMDkwCmVuZG9iagoxMDIgMCBvYmoK
PDwvTGVuZ3RoIDEwMyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nJVWXVfiSBB9
51fU8WFXz4kZEhBk31BkcAaVlezuw8w8tEkBvSbd2N1R46/fqnygqHlYOBzQ01331q1bVXmArh9A
l9/1d5x1vtwOYW07XfhKn3XnoROUB6D+ijM4i+jQKQQhRKtOdS+AsAfD4SlEWefwUjk0Ct3xxIiV
A35NowXMbpYRnOssEyqBlTbwtzQuFynMtHUWdq9vuUIIu0FwFP3b6Y0gmncO6d8/bqfnYRCMfgGc
GZEoNB4sfQ8OvmMBT9oktgyaWwSpgA5bcBouVSJj4fDo907Qa0K9ed3iQy4NZqgczPERU3vgwdn5
AoK+x0GAIT24EibeQDAaDX2KFA72SIXhKZGaaaOfpHuhwz5wiksf5rlyxJCzX2KcG+kKuHh2qKzU
ipBaWTEwhfXgJnb6Dk0bdO+U9Zih22RaebCokG99uEhfGBiFyw2CwrV2UjhChQzjjVDSZixXGwG3
QZjKFCEyQtkVEVgY7XSs04NaFkL2YJyvc+uY3Okn5Ab9LpE7z42TxO0frlVljZKISOVLxUivPuK1
EXtPgzA8ckxaMInRRxK9/ihkEmQxTFNNlJnGIldFrBP8A8ZwprWzzki1BlT0T/5BjP5Skk+08WCr
vUsGE5joTJD5rkWGll043m5Tth9XmyK9i/Hz8HJyPf55VOfCVBunhd1u72My/TAYUjJTMvvxLHfx
RipblZ1yqgxG5NltZMQN3VzWofliq9kaixHmyUfMk7DXZwGNju+55SaVxchpN49oSFOCJhtwA5EA
Z9fTUpploZx4bkNcbjGWq0YYKgJdq5kyHBVUqFyYgim9NdbAD30g2Qkho7uPSO1LXqGyYSMvUw5G
/ROeEjyEjD2eI3oQkURTiSmXl5DoL85i5sPUFNYV95TFrNiicfjs2mh/6AU4PoZZFC2+BH635s/Y
XMTSj4NPmuJkyCUcpymNwbej4oYMSlkp9W5etJE5J+VkgqbSsGkHir5D/6QbwkEwYAPtCfEVnSss
iU6/r/Q6T6ufO2Fmfqt1roSV3AQezOnGHEW8qdzISUX+fgn2BP4f0ga7Xg8GXrUdPs/uZDhibb+n
PF8VZ1HyGPs0m1GhrZVtVhB/dsO4fT+sJU2HorEnQbz2aNBlEvWKol5HWjbPjEfTgzbSvbijiTZO
6ynxWJr0lfIkR95QPPpS3jw8dWyst1h2kEjKSSRodj9BXFOm45QByQt3RuJqj3QibZxbWw9Um6/X
aLklxRt8DiCqRRy/UYEoSFMXxaCl7iybK5WZdJW/QFp4EoaqRCEpv4hIt0FsRFNgQaunpkWnaB66
DcURjVAbQSB3iAq2Rm/17gzCVljam3d5E4iNVa8JXu8JCqZjIUHa3HzL5iuaJ5K3OIvHMQwdYubM
h5nUoVJZUuYBSWBlYMv5vu6hhh/Xlp9oSN56wcJvcBVf5SRDUbnj4nlLDw8WJhhjxjO0F3jlo8u+
iX4sxJofaX5RxIuo8ye9/wPb2aIOZW5kc3RyZWFtCmVuZG9iagoxMDMgMCBvYmoKMTExNAplbmRv
YmoKMTA3IDAgb2JqCjw8L0xlbmd0aCAxMDggMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJl
YW0KeJx9Vl1TG0cQfNevmOIhsasEQcI2kIdUEWzHdsUxMbL9YPOwutuTNr7bFfuBrH+fnrm9406Q
iKKE0F1vT09Pz93S8dGMjvknvxfN5JePp7QKk2P6A7+rye1kJhdQfisa+n2Bi85oNqdFNWnvm9H8
hE5Pz2jRTJ68tVF7q+PhS6+qSPx6vbiiNx+uF3TpmkbZkirn6bPxMama3rgQA/Wvd8lqmh/PZk8X
/0xOzmnx5+TJxdHsiOjDnfa1U6WxK4prTZdfXlLRAj79eTJ/IZcC4QMAQlqtdIi6pEbHtSspOtJN
qlXUpPj4hlxFd5nCWihsXapLWmr+GoCzkw6QDytqo21kmGCaTb2joFGHogOwOOhoEArWHp+s1UUE
zymlkOkCkbGGR5JVDegEOUD5VWryEXvVofbF2mSCGUfVtdvKhUF7CHPIGm+8K3QIDMEkdYuHaypT
48LovA5c9+N0AlMJaXlYGg/6zhtcbSwZfPPX59fXHY2srXH4KmQcEUXz1Si+0Js4Jdaj4SoHBHtW
im9nqM3GeebYI20N+pUieX2bjGfxlN0BtUQP1sriZPD4suaC+K6uv8yr5RBdRip1KLxZ6pbKUJMp
asLZVaV9oMq7BhxBETqUXm2Xqvgefh1ZSknteq/bOFPdKVOrJY51FqZo+8+KJ1R9ePWW1iqMvMQv
lXCFjaZQbFDIq+uqa/vDbsrRKUy55bkyetC53rutbFrqDWvl2e7MF80aHAvxB1ChWEMWMmKMHVMv
h9oejaRYMh9HjfquhfDI0NEnqBC9smGDs1lpjX5mTe5reyBJ51yrdSn+RSmNK01l2lKMLepUssF4
dqUAQCp0ce22YVCLnLPRhQElq2KCAGJ4VFMZD4qDuaJvT6xeKR7U1qmu2kNS5Z2CWVf3IK1W355O
CRGGjkijoVQSo7eSBIz1AMiUreq1TBEE01tKG2cHOQEmIr3A5H/zMN0PqvSJ48JYE7m4bkh3mQsf
LPiCsTf+CUSDjgOsvfSj4cxDVq2KNW1cCGZZP3LmAIijnCe0v5gFGVumgGU+2VqSqbeBTGzbKFim
6zVcLgBDbXI4jA2zVTv2hRpX0Y+BjCRnvgpG4O/kIxN17Mf/GKQukGA6FftePjKU8PUPVAx6e44Z
em48HANNLo7mj+yzi8vLxWChMeqFFbYP11lf6P1CchlOsA4Y7ODBJuMKRsExpWVq45crQ0X4An8n
qwpOcZGRO5zzMdPykJXjm7MaH1bKy5BuES8PKpE+sxHL5MerkKMKRVGFTQY5rrndjPr86Jkk9gtW
8evH15fH58/Pb6h0Reodne/NSIzQGpFqt8LcBP4ae4g32qfrVx/p8De6uri+5ncm160yubGf+swY
0wxzsYnuNZDSdi4RJyq8GTDU7XIiNkG2fcZZqzuJlFRHwxsJOC5ZpDSHsJUmtI5q1a+wQiTzMALY
SBwWWAwZa6njVuPsvbjv6HRU2jF3/FAgIm8RmSFAosf3WBuF6Dhqa9o2uv9xIz0ygIX2ESPLOwyp
vXJMmlNZqPVPPbnYAr2PO8xM1OALzqOpwaixrF2DeSdaafx8Pj+7ES/wp2fz2ekNCnhrkXdSsxuF
Y6VXiZ3Y5gd2oChZw+M9gUbzM4QJjYAOShgADYuRLHUF7kYjYDCd/TVAF+pi8OVuL6/bZ8Ys+Ujs
e33GMttuyWirvBmWZ0IrFMeB5k/WSQZiRCBpN1o5tIa9wbLEymLBn8+lf2+QIPw48BO9L94n7wEi
r1c/NoafD1/qQjdLSHgym8qDOI1eX694Hc5nN0B8tZj8jZ9/AdDS9kplbmRzdHJlYW0KZW5kb2Jq
CjEwOCAwIG9iagoxMzQ5CmVuZG9iagoxMTIgMCBvYmoKPDwvTGVuZ3RoIDExMyAwIFIvRmlsdGVy
IC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nJVWTXPbNhC961fs6NAkM7Kij0zt9pCJaju1M/XEsej2
kPEBApckapKQAdCy/n0eQFIipbRpqdFIJIC3u28fHvhEk/GUJv7T/Mpi8PbulFI7mNDv+KaDp8E0
TKDmRxb0W4RJZzSdUZQM6nVTms3p9PSMomLw+rp0bEp2JxdGJI789TG6pavPy4jOdVGIMqZEG/pT
GVeJnK60dZZ216eqZJpNptM30d+D+S8U/TF43Qy5jElqY1g6em5WZ1hNKwYgh/HKsiFpOObSKZFb
EhiwuBm/eTWY/dzCrcZEUeZHpEY+a6NXORe0US4j/cwm1yJWZRogF+fnEeLWmSuLkJsQBoDTeTe/
w7CqWAMUT7iu2NPQzduOa2qA9RzgWqDdQuGULi0VYksizxG3KZF0QrKyThfHBeuSRAdrzeakCXpS
kyWsCpGREb8IH2pEqsQ6prUwTskqF/+cTUihx37JqUboMKilrIwdkacKE8PsDtR3u5Nr/QiGqjWG
W86FlLoqHRUsM1EqW+CpcN2kLNk1S5UoSU6H0V5WKHCpUZMEVirUcdodrG4BBVglJx7BRS6w+H9K
azGeI/LnAwXdLy/vWgU1cRfoUhwrHxMJ2SpN2YYENrrKY4T1VbVKpA3n+cljqTcl2S0a8dLTnsuM
rtIshOIXBRzE7cZEPyypPEdtRng1Nnwk2osKs5ukGjn82tsq4Tp/XwMmWn9oZo0BfrQFaPme5vMp
3QprN9rEZPipUuCsQ7cHu10sl1BiV2Z+6Ww+oXtPc65BiM+zl8q1Txud38l215YhEhtSodLMuwEJ
57hYBx5AI8D8rggy4V7KPR0PO4UNwzYqO9szGIZX3b5V2JZN/pZhHhAMBAwfQXhKlLFuRKvKoQhn
dFxJxmIGEuL1t1QD0pjQwd7sN0MEXRcMzTrw+0hcogZdeiwIMjcs4m1wCE/N0HNTioI/+AL9n+FR
x2o9BX9qMTsaH9Em40b/wx0IrbXpJO4vwwkb23AMxmXjB8muR69sb/N4q1WH/tBmkCnQZGS2Rbn3
O1MYHqhv2CavfNPxgG0HK1ZJ4r3M+aT8DerwsZ3f1G7DtTl15eNF52OhYbrnoX27AwPxD8RC+NrK
7gJ0sI6L6IftwYTzqNSt1fW2Uc/tjg63v7z57v20xoQ3K7eFshyXNpwswTe9j8VaVs1RFTZdXyRf
7z6ez2azs4dg7P7u3Wx6+jDaY+6N2s+QDH2AfZD9bz4bTovWYkED9PA9f6XV9kAnMlfed4lu/Mr2
IMARua09YXEfXb1dXCx257atA65qwA5Sx9+7jhkORBOjBeiJFQmnlYCbHR4B4w7SdUJbXe09+xAy
ZObfCqzv6AZHOjYH+gD+dgZMwc3RkvCqsycRVuNkxva/vAL96LjtMNry6Ps9eRcafsUuK9Cfn+hG
3lTGIM1wXb6sYeOWLlhysQLsfDoKr2nUu77eihSvb7MHQF5Ggy/4fAMOEklPZW5kc3RyZWFtCmVu
ZG9iagoxMTMgMCBvYmoKMTEwNQplbmRvYmoKMTE3IDAgb2JqCjw8L0xlbmd0aCAxMTggMCBSL0Zp
bHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJx9Vdty2zYQfddX7PihdmZcVZekttuXyIkS26kb
12HrznT6AIErERUI0ACoS76+ByBoW5lOSWk4XGAv5+xZ8JFGwzGN4p2fsh78cH9GKz8Y0Uf8V4PH
wThtoPyQNV0W2HRO4wkVy0HnN6bJlM7OzqmoByfXJrAzHL5/78QyULw+FHd09flLQe9sXQtT0tI6
+kO50ApNV9YHT0/XTWuYJqPx+FXxz2B6QcUvg5PZ8PWQ4Gykbr2y5tXxYPJjWoFDUTHJpyVaOltT
gI13olZGhGi0y2xSPiizosZ6rxZKq6DYI9p42kfzzLWnYGnBcBGBFLxdyS7a7CIIvAv8Sn5sRUDI
utVPOY4cC32EeCcZtGe3YedPSWrFJlDE3tmotqVaKpl8U0LfNo11gTaZlyrykmMJx2RYsvfC7YcJ
s2OQyCRg36ZcMnObEQBujQik1Zr1PsfxVrepWORrnN2oktNOBzTKcUmaN6wjlFzNEI59E5qGTal2
dIkCZnJt7FZzueIawPxBR+7tggFkrr8mwHeiRZc5VDUS56wlCi8ZbCIElcrL1vvnRh10JAmnBwf2
sa4c9SqjMqksqBAjHc13gY3vKQUtRyR6EhuBoroECLC1bk1bFapEAHbO/yzoAcaoj4/Otg2h+3Ht
el586DhXLodKzuC/Rs64ZSG88knVdSurLgkMpZVtpOc08dDlrVg3VD0VtWA2tIJugt6TaBrHUkFX
ZZdwj0ytBlna29TJiEqiUSrQJfBXwpU50L31bNZOsPkKdcVSKrGJWJbKQQa+Xa3Yh0g8SinZS6cW
ufrIcI6SeR4e9HOmeYdSblkbtbabUxiWUSxXlg1D3De2MvRJR+JNB/XGMhU2UoEiIESMyzdThhGA
xnNVqV9iYdtALBxGxVEcm2T+lsufEc3sYc4Vd6y+DJRSJl6VkdZBxpHQlz3AcREAv82JHedYq7hz
2erYimeBx15cx5EH63CI8FmC7y1rfQx3KNcHYSQjXw5UiyQjzzL8JwiMpotTJ0qx0Exb4eG7EbqN
ry9nrg2Vdf6YZmXpMP18OGgvJ+twZvK0XToLxK4X22Q6ekPvqnYtHOoXvXQ+GbvbKK35lIpfiaZn
F5NpXvr9y+wg47zGyP5ETdUleJufQ+jmuernI+BW3rbOif1BcbdKOustpvZd7k53pMe1zzj8n9cf
RH9w3XOJNGjiw4zo4nz0ZvL/BTq7qGX9tu5D5QLHo9dpY8/Pd08Vdh+f+a7BMejpPc7aGghoOj5N
HyM6uP66Eyt8pKZ/I+S8GPyG+18pMkmZZW5kc3RyZWFtCmVuZG9iagoxMTggMCBvYmoKOTY2CmVu
ZG9iago0IDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUg
MC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0
ZSA5IDAgUgovRm9udCAxMCAwIFIKPj4KL0NvbnRlbnRzIDUgMCBSCj4+CmVuZG9iagoxMSAwIG9i
ago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMg
MCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgMTQgMCBSCi9G
b250IDE1IDAgUgo+PgovQ29udGVudHMgMTIgMCBSCj4+CmVuZG9iagoxNiAwIG9iago8PC9UeXBl
L1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNv
dXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgMTkgMCBSCi9Gb250IDIwIDAg
Ugo+PgovQ29udGVudHMgMTcgMCBSCj4+CmVuZG9iagoyMSAwIG9iago8PC9UeXBlL1BhZ2UvTWVk
aWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Q
cm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgMjQgMCBSCi9Gb250IDI1IDAgUgo+PgovQ29u
dGVudHMgMjIgMCBSCj4+CmVuZG9iagoyNiAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAg
MCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9Q
REYgL1RleHRdCi9FeHRHU3RhdGUgMjkgMCBSCi9Gb250IDMwIDAgUgo+PgovQ29udGVudHMgMjcg
MCBSCj4+CmVuZG9iagozMSAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQy
XQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRd
Ci9FeHRHU3RhdGUgMzQgMCBSCi9Gb250IDM1IDAgUgo+PgovQ29udGVudHMgMzIgMCBSCj4+CmVu
ZG9iagozNiAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRl
IDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3Rh
dGUgMzkgMCBSCi9Gb250IDQwIDAgUgo+PgovQ29udGVudHMgMzcgMCBSCj4+CmVuZG9iago0MSAw
IG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50
IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgNDQgMCBS
Ci9Gb250IDQ1IDAgUgo+PgovQ29udGVudHMgNDIgMCBSCj4+CmVuZG9iago0NiAwIG9iago8PC9U
eXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9S
ZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgNDkgMCBSCi9Gb250IDUw
IDAgUgo+PgovQ29udGVudHMgNDcgMCBSCj4+CmVuZG9iago1MSAwIG9iago8PC9UeXBlL1BhZ2Uv
TWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8
PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgNTQgMCBSCi9Gb250IDU1IDAgUgo+Pgov
Q29udGVudHMgNTIgMCBSCj4+CmVuZG9iago1NiAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3gg
WzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0
Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgNTkgMCBSCi9Gb250IDYwIDAgUgo+PgovQ29udGVudHMg
NTcgMCBSCj4+CmVuZG9iago2MSAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUg
ODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1Rl
eHRdCi9FeHRHU3RhdGUgNjQgMCBSCi9Gb250IDY1IDAgUgo+PgovQ29udGVudHMgNjIgMCBSCj4+
CmVuZG9iago2NiAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90
YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRH
U3RhdGUgNjkgMCBSCi9Gb250IDcwIDAgUgo+PgovQ29udGVudHMgNjcgMCBSCj4+CmVuZG9iago3
MSAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFy
ZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgNzQg
MCBSCi9Gb250IDc1IDAgUgo+PgovQ29udGVudHMgNzIgMCBSCj4+CmVuZG9iago3NiAwIG9iago8
PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBS
Ci9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgNzkgMCBSCi9Gb250
IDgwIDAgUgo+PgovQ29udGVudHMgNzcgMCBSCj4+CmVuZG9iago4MSAwIG9iago8PC9UeXBlL1Bh
Z2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJj
ZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgODQgMCBSCi9Gb250IDg1IDAgUgo+
PgovQ29udGVudHMgODIgMCBSCj4+CmVuZG9iago4NiAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFC
b3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9j
U2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgODkgMCBSCi9Gb250IDkwIDAgUgo+PgovQ29udGVu
dHMgODcgMCBSCj4+CmVuZG9iago5MSAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1
OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYg
L1RleHRdCi9FeHRHU3RhdGUgOTQgMCBSCi9Gb250IDk1IDAgUgo+PgovQ29udGVudHMgOTIgMCBS
Cj4+CmVuZG9iago5NiAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQov
Um90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9F
eHRHU3RhdGUgOTkgMCBSCi9Gb250IDEwMCAwIFIKPj4KL0NvbnRlbnRzIDk3IDAgUgo+PgplbmRv
YmoKMTAxIDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUg
MC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0
ZSAxMDQgMCBSCi9Gb250IDEwNSAwIFIKPj4KL0NvbnRlbnRzIDEwMiAwIFIKPj4KZW5kb2JqCjEw
NiAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFy
ZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgMTA5
IDAgUgovRm9udCAxMTAgMCBSCj4+Ci9Db250ZW50cyAxMDcgMCBSCj4+CmVuZG9iagoxMTEgMCBv
YmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAz
IDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDExNCAwIFIK
L0ZvbnQgMTE1IDAgUgo+PgovQ29udGVudHMgMTEyIDAgUgo+PgplbmRvYmoKMTE2IDAgb2JqCjw8
L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIK
L1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSAxMTkgMCBSCi9Gb250
IDEyMCAwIFIKPj4KL0NvbnRlbnRzIDExNyAwIFIKPj4KZW5kb2JqCjMgMCBvYmoKPDwgL1R5cGUg
L1BhZ2VzIC9LaWRzIFsKNCAwIFIKMTEgMCBSCjE2IDAgUgoyMSAwIFIKMjYgMCBSCjMxIDAgUgoz
NiAwIFIKNDEgMCBSCjQ2IDAgUgo1MSAwIFIKNTYgMCBSCjYxIDAgUgo2NiAwIFIKNzEgMCBSCjc2
IDAgUgo4MSAwIFIKODYgMCBSCjkxIDAgUgo5NiAwIFIKMTAxIDAgUgoxMDYgMCBSCjExMSAwIFIK
MTE2IDAgUgpdIC9Db3VudCAyMwo+PgplbmRvYmoKMSAwIG9iago8PC9UeXBlIC9DYXRhbG9nIC9Q
YWdlcyAzIDAgUgovTWV0YWRhdGEgMTIxIDAgUgo+PgplbmRvYmoKNyAwIG9iago8PC9UeXBlL0V4
dEdTdGF0ZQovT1BNIDE+PmVuZG9iago5IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjEwIDAg
b2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjE0IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjE1
IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjE5IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2Jq
CjIwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjI0IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5k
b2JqCjI1IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjI5IDAgb2JqCjw8L1I3CjcgMCBSPj4K
ZW5kb2JqCjMwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjM0IDAgb2JqCjw8L1I3CjcgMCBS
Pj4KZW5kb2JqCjM1IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjM5IDAgb2JqCjw8L1I3Cjcg
MCBSPj4KZW5kb2JqCjQwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjQ0IDAgb2JqCjw8L1I3
CjcgMCBSPj4KZW5kb2JqCjQ1IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjQ5IDAgb2JqCjw8
L1I3CjcgMCBSPj4KZW5kb2JqCjUwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjU0IDAgb2Jq
Cjw8L1I3CjcgMCBSPj4KZW5kb2JqCjU1IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjU5IDAg
b2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjYwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjY0
IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjY1IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2Jq
CjY5IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjcwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5k
b2JqCjc0IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjc1IDAgb2JqCjw8L1I4CjggMCBSPj4K
ZW5kb2JqCjc5IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjgwIDAgb2JqCjw8L1I4CjggMCBS
Pj4KZW5kb2JqCjg0IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjg1IDAgb2JqCjw8L1I4Cjgg
MCBSPj4KZW5kb2JqCjg5IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjkwIDAgb2JqCjw8L1I4
CjggMCBSPj4KZW5kb2JqCjk0IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjk1IDAgb2JqCjw8
L1I4CjggMCBSPj4KZW5kb2JqCjk5IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjEwMCAwIG9i
ago8PC9SOAo4IDAgUj4+CmVuZG9iagoxMDQgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKMTA1
IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjEwOSAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9i
agoxMTAgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKMTE0IDAgb2JqCjw8L1I3CjcgMCBSPj4K
ZW5kb2JqCjExNSAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iagoxMTkgMCBvYmoKPDwvUjcKNyAw
IFI+PgplbmRvYmoKMTIwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjggMCBvYmoKPDwvQmFz
ZUZvbnQvQ291cmllci9UeXBlL0ZvbnQKL1N1YnR5cGUvVHlwZTE+PgplbmRvYmoKMTIxIDAgb2Jq
Cjw8L1R5cGUvTWV0YWRhdGEKL1N1YnR5cGUvWE1ML0xlbmd0aCAxMzI4Pj5zdHJlYW0KPD94cGFj
a2V0IGJlZ2luPSfvu78nIGlkPSdXNU0wTXBDZWhpSHpyZVN6TlRjemtjOWQnPz4KPD9hZG9iZS14
YXAtZmlsdGVycyBlc2M9IkNSTEYiPz4KPHg6eG1wbWV0YSB4bWxuczp4PSdhZG9iZTpuczptZXRh
LycgeDp4bXB0az0nWE1QIHRvb2xraXQgMi45LjEtMTMsIGZyYW1ld29yayAxLjYnPgo8cmRmOlJE
RiB4bWxuczpyZGY9J2h0dHA6Ly93d3cudzMub3JnLzE5OTkvMDIvMjItcmRmLXN5bnRheC1ucyMn
IHhtbG5zOmlYPSdodHRwOi8vbnMuYWRvYmUuY29tL2lYLzEuMC8nPgo8cmRmOkRlc2NyaXB0aW9u
IHJkZjphYm91dD0nZDg5NWQ1ZmEtZGEwYy0xMWViLTAwMDAtNjUwOGViOWFkOWM0JyB4bWxuczpw
ZGY9J2h0dHA6Ly9ucy5hZG9iZS5jb20vcGRmLzEuMy8nIHBkZjpQcm9kdWNlcj0nR1BMIEdob3N0
c2NyaXB0IDguNzEnLz4KPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9J2Q4OTVkNWZhLWRhMGMt
MTFlYi0wMDAwLTY1MDhlYjlhZDljNCcgeG1sbnM6eG1wPSdodHRwOi8vbnMuYWRvYmUuY29tL3hh
cC8xLjAvJz48eG1wOk1vZGlmeURhdGU+MjAxMS0wNi0yOVQwMzozNzowNiswMjowMDwveG1wOk1v
ZGlmeURhdGU+Cjx4bXA6Q3JlYXRlRGF0ZT4yMDExLTA2LTI5VDAzOjM3OjA2KzAyOjAwPC94bXA6
Q3JlYXRlRGF0ZT4KPHhtcDpDcmVhdG9yVG9vbD5HTlUgRW5zY3JpcHQgMS42LjUuMjwveG1wOkNy
ZWF0b3JUb29sPjwvcmRmOkRlc2NyaXB0aW9uPgo8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0n
ZDg5NWQ1ZmEtZGEwYy0xMWViLTAwMDAtNjUwOGViOWFkOWM0JyB4bWxuczp4YXBNTT0naHR0cDov
L25zLmFkb2JlLmNvbS94YXAvMS4wL21tLycgeGFwTU06RG9jdW1lbnRJRD0nZDg5NWQ1ZmEtZGEw
Yy0xMWViLTAwMDAtNjUwOGViOWFkOWM0Jy8+CjxyZGY6RGVzY3JpcHRpb24gcmRmOmFib3V0PSdk
ODk1ZDVmYS1kYTBjLTExZWItMDAwMC02NTA4ZWI5YWQ5YzQnIHhtbG5zOmRjPSdodHRwOi8vcHVy
bC5vcmcvZGMvZWxlbWVudHMvMS4xLycgZGM6Zm9ybWF0PSdhcHBsaWNhdGlvbi9wZGYnPjxkYzp0
aXRsZT48cmRmOkFsdD48cmRmOmxpIHhtbDpsYW5nPSd4LWRlZmF1bHQnPkVuc2NyaXB0IE91dHB1
dDwvcmRmOmxpPjwvcmRmOkFsdD48L2RjOnRpdGxlPjwvcmRmOkRlc2NyaXB0aW9uPgo8L3JkZjpS
REY+CjwveDp4bXBtZXRhPgogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCjw/eHBhY2tl
dCBlbmQ9J3cnPz4KZW5kc3RyZWFtCmVuZG9iagoyIDAgb2JqCjw8L1Byb2R1Y2VyKEdQTCBHaG9z
dHNjcmlwdCA4LjcxKQovQ3JlYXRpb25EYXRlKEQ6MjAxMTA2MjkwMzM3MDYrMDInMDAnKQovTW9k
RGF0ZShEOjIwMTEwNjI5MDMzNzA2KzAyJzAwJykKL1RpdGxlKEVuc2NyaXB0IE91dHB1dCkKL0Ny
ZWF0b3IoR05VIEVuc2NyaXB0IDEuNi41LjIpPj5lbmRvYmoKeHJlZgowIDEyMgowMDAwMDAwMDAw
IDY1NTM1IGYgCjAwMDAwMjg4NzIgMDAwMDAgbiAKMDAwMDAzMTgzNSAwMDAwMCBuIAowMDAwMDI4
NjU0IDAwMDAwIG4gCjAwMDAwMjQ5MTQgMDAwMDAgbiAKMDAwMDAwMDAxNSAwMDAwMCBuIAowMDAw
MDAxMjMzIDAwMDAwIG4gCjAwMDAwMjg5MzggMDAwMDAgbiAKMDAwMDAzMDM2NyAwMDAwMCBuIAow
MDAwMDI4OTc5IDAwMDAwIG4gCjAwMDAwMjkwMDggMDAwMDAgbiAKMDAwMDAyNTA3MyAwMDAwMCBu
IAowMDAwMDAxMjUzIDAwMDAwIG4gCjAwMDAwMDIwMTAgMDAwMDAgbiAKMDAwMDAyOTAzOCAwMDAw
MCBuIAowMDAwMDI5MDY4IDAwMDAwIG4gCjAwMDAwMjUyMzUgMDAwMDAgbiAKMDAwMDAwMjAzMCAw
MDAwMCBuIAowMDAwMDAzNDQ3IDAwMDAwIG4gCjAwMDAwMjkwOTggMDAwMDAgbiAKMDAwMDAyOTEy
OCAwMDAwMCBuIAowMDAwMDI1Mzk3IDAwMDAwIG4gCjAwMDAwMDM0NjggMDAwMDAgbiAKMDAwMDAw
NDgwOCAwMDAwMCBuIAowMDAwMDI5MTU4IDAwMDAwIG4gCjAwMDAwMjkxODggMDAwMDAgbiAKMDAw
MDAyNTU1OSAwMDAwMCBuIAowMDAwMDA0ODI5IDAwMDAwIG4gCjAwMDAwMDU4NjEgMDAwMDAgbiAK
MDAwMDAyOTIxOCAwMDAwMCBuIAowMDAwMDI5MjQ4IDAwMDAwIG4gCjAwMDAwMjU3MjEgMDAwMDAg
biAKMDAwMDAwNTg4MSAwMDAwMCBuIAowMDAwMDA2OTQ4IDAwMDAwIG4gCjAwMDAwMjkyNzggMDAw
MDAgbiAKMDAwMDAyOTMwOCAwMDAwMCBuIAowMDAwMDI1ODgzIDAwMDAwIG4gCjAwMDAwMDY5Njgg
MDAwMDAgbiAKMDAwMDAwODMwMiAwMDAwMCBuIAowMDAwMDI5MzM4IDAwMDAwIG4gCjAwMDAwMjkz
NjggMDAwMDAgbiAKMDAwMDAyNjA0NSAwMDAwMCBuIAowMDAwMDA4MzIzIDAwMDAwIG4gCjAwMDAw
MDk2OTQgMDAwMDAgbiAKMDAwMDAyOTM5OCAwMDAwMCBuIAowMDAwMDI5NDI4IDAwMDAwIG4gCjAw
MDAwMjYyMDcgMDAwMDAgbiAKMDAwMDAwOTcxNSAwMDAwMCBuIAowMDAwMDEwNzYwIDAwMDAwIG4g
CjAwMDAwMjk0NTggMDAwMDAgbiAKMDAwMDAyOTQ4OCAwMDAwMCBuIAowMDAwMDI2MzY5IDAwMDAw
IG4gCjAwMDAwMTA3ODAgMDAwMDAgbiAKMDAwMDAxMjA1MyAwMDAwMCBuIAowMDAwMDI5NTE4IDAw
MDAwIG4gCjAwMDAwMjk1NDggMDAwMDAgbiAKMDAwMDAyNjUzMSAwMDAwMCBuIAowMDAwMDEyMDc0
IDAwMDAwIG4gCjAwMDAwMTI3NjMgMDAwMDAgbiAKMDAwMDAyOTU3OCAwMDAwMCBuIAowMDAwMDI5
NjA4IDAwMDAwIG4gCjAwMDAwMjY2OTMgMDAwMDAgbiAKMDAwMDAxMjc4MyAwMDAwMCBuIAowMDAw
MDEzNDY2IDAwMDAwIG4gCjAwMDAwMjk2MzggMDAwMDAgbiAKMDAwMDAyOTY2OCAwMDAwMCBuIAow
MDAwMDI2ODU1IDAwMDAwIG4gCjAwMDAwMTM0ODYgMDAwMDAgbiAKMDAwMDAxNDI2MiAwMDAwMCBu
IAowMDAwMDI5Njk4IDAwMDAwIG4gCjAwMDAwMjk3MjggMDAwMDAgbiAKMDAwMDAyNzAxNyAwMDAw
MCBuIAowMDAwMDE0MjgyIDAwMDAwIG4gCjAwMDAwMTQ3OTcgMDAwMDAgbiAKMDAwMDAyOTc1OCAw
MDAwMCBuIAowMDAwMDI5Nzg4IDAwMDAwIG4gCjAwMDAwMjcxNzkgMDAwMDAgbiAKMDAwMDAxNDgx
NyAwMDAwMCBuIAowMDAwMDE1NDczIDAwMDAwIG4gCjAwMDAwMjk4MTggMDAwMDAgbiAKMDAwMDAy
OTg0OCAwMDAwMCBuIAowMDAwMDI3MzQxIDAwMDAwIG4gCjAwMDAwMTU0OTMgMDAwMDAgbiAKMDAw
MDAxNjMyMiAwMDAwMCBuIAowMDAwMDI5ODc4IDAwMDAwIG4gCjAwMDAwMjk5MDggMDAwMDAgbiAK
MDAwMDAyNzUwMyAwMDAwMCBuIAowMDAwMDE2MzQyIDAwMDAwIG4gCjAwMDAwMTc0MjAgMDAwMDAg
biAKMDAwMDAyOTkzOCAwMDAwMCBuIAowMDAwMDI5OTY4IDAwMDAwIG4gCjAwMDAwMjc2NjUgMDAw
MDAgbiAKMDAwMDAxNzQ0MSAwMDAwMCBuIAowMDAwMDE4NzkzIDAwMDAwIG4gCjAwMDAwMjk5OTgg
MDAwMDAgbiAKMDAwMDAzMDAyOCAwMDAwMCBuIAowMDAwMDI3ODI3IDAwMDAwIG4gCjAwMDAwMTg4
MTQgMDAwMDAgbiAKMDAwMDAxOTk3NiAwMDAwMCBuIAowMDAwMDMwMDU4IDAwMDAwIG4gCjAwMDAw
MzAwODggMDAwMDAgbiAKMDAwMDAyNzk5MCAwMDAwMCBuIAowMDAwMDE5OTk3IDAwMDAwIG4gCjAw
MDAwMjExODUgMDAwMDAgbiAKMDAwMDAzMDExOSAwMDAwMCBuIAowMDAwMDMwMTUwIDAwMDAwIG4g
CjAwMDAwMjgxNTYgMDAwMDAgbiAKMDAwMDAyMTIwNyAwMDAwMCBuIAowMDAwMDIyNjMwIDAwMDAw
IG4gCjAwMDAwMzAxODEgMDAwMDAgbiAKMDAwMDAzMDIxMiAwMDAwMCBuIAowMDAwMDI4MzIyIDAw
MDAwIG4gCjAwMDAwMjI2NTIgMDAwMDAgbiAKMDAwMDAyMzgzMSAwMDAwMCBuIAowMDAwMDMwMjQz
IDAwMDAwIG4gCjAwMDAwMzAyNzQgMDAwMDAgbiAKMDAwMDAyODQ4OCAwMDAwMCBuIAowMDAwMDIz
ODUzIDAwMDAwIG4gCjAwMDAwMjQ4OTMgMDAwMDAgbiAKMDAwMDAzMDMwNSAwMDAwMCBuIAowMDAw
MDMwMzM2IDAwMDAwIG4gCjAwMDAwMzA0MjkgMDAwMDAgbiAKdHJhaWxlcgo8PCAvU2l6ZSAxMjIg
L1Jvb3QgMSAwIFIgL0luZm8gMiAwIFIKL0lEIFs8Mzg1NUQyRkVEOUZGMTY0NDhBOUE5RDJDQTJG
OEFDNzQ+PDM4NTVEMkZFRDlGRjE2NDQ4QTlBOUQyQ0EyRjhBQzc0Pl0KPj4Kc3RhcnR4cmVmCjMy
MDEzCiUlRU9GCg==

--_004_01AA9EC92749BF4894AC2B3039EA4A2C194A07E2CH1PRD0302MB131_
Content-Type: text/plain; name="draft-ietf-ftpext2-hosts-04.txt"
Content-Description: draft-ietf-ftpext2-hosts-04.txt
Content-Disposition: attachment; filename="draft-ietf-ftpext2-hosts-04.txt";
	size=53419; creation-date="Wed, 29 Jun 2011 01:36:51 GMT";
	modification-date="Wed, 29 Jun 2011 01:37:54 GMT"
Content-Transfer-Encoding: base64

DQoNCg0KRlRQRVhUMiBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICBQLiBIZXRobW9uDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIEhldGhtb24gQnJvdGhlcnMNClVwZGF0ZXM6IDk1OSAoaWYg
YXBwcm92ZWQpICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBSLiBNY011cnJheQ0K
SW50ZW5kZWQgc3RhdHVzOiBTdGFuZGFyZHMgVHJhY2sgICAgICAgICAgICAgICAgICAgTWljcm9z
b2Z0IENvcnBvcmF0aW9uDQpFeHBpcmVzOiBEZWNlbWJlciAzMSwgMjAxMSAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIEp1bmUgMjksIDIwMTENCg0KDQogICAgICAgICBGaWxlIFRyYW5z
ZmVyIFByb3RvY29sIEhPU1QgQ29tbWFuZCBmb3IgVmlydHVhbCBIb3N0cw0KICAgICAgICAgICAg
ICAgICAgICAgIGRyYWZ0LWlldGYtZnRwZXh0Mi1ob3N0cy0wNA0KDQpBYnN0cmFjdA0KDQogICBU
aGUgRmlsZSBUcmFuc2ZlciBQcm90b2NvbCwgYXMgZGVmaW5lZCBpbiBSRkMgOTU5IFtSRkMwOTU5
XSwgZG9lcyBub3QNCiAgIHByb3ZpZGUgYSB3YXkgZm9yIEZUUCBjbGllbnRzIGFuZCBzZXJ2ZXJz
IHRvIGRpZmZlcmVudGlhdGUgYmV0d2Vlbg0KICAgbXVsdGlwbGUgRE5TIG5hbWVzIHRoYXQgYXJl
IHJlZ2lzdGVyZWQgZm9yIGEgc2luZ2xlIElQIGFkZHJlc3MuICBUaGlzDQogICBkb2N1bWVudCBk
ZWZpbmVzIGEgbmV3IEZUUCBjb21tYW5kIHRoYXQgcHJvdmlkZXMgYSBtZWNoYW5pc20gZm9yIEZU
UA0KICAgY2xpZW50cyBhbmQgc2VydmVycyB0byBpZGVudGlmeSBpbmRpdmlkdWFsIHZpcnR1YWwg
aG9zdHMgb24gYW4gRlRQDQogICBzZXJ2ZXIuDQoNClN0YXR1cyBvZiB0aGlzIE1lbW8NCg0KICAg
VGhpcyBJbnRlcm5ldC1EcmFmdCBpcyBzdWJtaXR0ZWQgaW4gZnVsbCBjb25mb3JtYW5jZSB3aXRo
IHRoZQ0KICAgcHJvdmlzaW9ucyBvZiBCQ1AgNzggYW5kIEJDUCA3OS4NCg0KICAgSW50ZXJuZXQt
RHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5lZXJpbmcN
CiAgIFRhc2sgRm9yY2UgKElFVEYpLiAgTm90ZSB0aGF0IG90aGVyIGdyb3VwcyBtYXkgYWxzbyBk
aXN0cmlidXRlDQogICB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC1EcmFmdHMuICBUaGUg
bGlzdCBvZiBjdXJyZW50IEludGVybmV0LQ0KICAgRHJhZnRzIGlzIGF0IGh0dHA6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kcmFmdHMvY3VycmVudC8uDQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUg
ZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4IG1vbnRocw0KICAgYW5k
IG1heSBiZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50
cyBhdCBhbnkNCiAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1E
cmFmdHMgYXMgcmVmZXJlbmNlDQogICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhh
biBhcyAid29yayBpbiBwcm9ncmVzcy4iDQoNCiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgd2lsbCBl
eHBpcmUgb24gRGVjZW1iZXIgMzEsIDIwMTEuDQoNCkNvcHlyaWdodCBOb3RpY2UNCg0KICAgQ29w
eXJpZ2h0IChjKSAyMDExIElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25zIGlkZW50aWZpZWQgYXMg
dGhlDQogICBkb2N1bWVudCBhdXRob3JzLiAgQWxsIHJpZ2h0cyByZXNlcnZlZC4NCg0KICAgVGhp
cyBkb2N1bWVudCBpcyBzdWJqZWN0IHRvIEJDUCA3OCBhbmQgdGhlIElFVEYgVHJ1c3QncyBMZWdh
bA0KICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50cw0KICAgKGh0dHA6Ly90
cnVzdGVlLmlldGYub3JnL2xpY2Vuc2UtaW5mbykgaW4gZWZmZWN0IG9uIHRoZSBkYXRlIG9mDQog
ICBwdWJsaWNhdGlvbiBvZiB0aGlzIGRvY3VtZW50LiAgUGxlYXNlIHJldmlldyB0aGVzZSBkb2N1
bWVudHMNCiAgIGNhcmVmdWxseSwgYXMgdGhleSBkZXNjcmliZSB5b3VyIHJpZ2h0cyBhbmQgcmVz
dHJpY3Rpb25zIHdpdGggcmVzcGVjdA0KICAgdG8gdGhpcyBkb2N1bWVudC4gIENvZGUgQ29tcG9u
ZW50cyBleHRyYWN0ZWQgZnJvbSB0aGlzIGRvY3VtZW50IG11c3QNCiAgIGluY2x1ZGUgU2ltcGxp
ZmllZCBCU0QgTGljZW5zZSB0ZXh0IGFzIGRlc2NyaWJlZCBpbiBTZWN0aW9uIDQuZSBvZg0KDQoN
Cg0KSGV0aG1vbiAmIE1jTXVycmF5ICAgICAgRXhwaXJlcyBEZWNlbWJlciAzMSwgMjAxMSAgICAg
ICAgICAgICAgIFtQYWdlIDFdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgRlRQIEhPU1QgQ29tbWFu
ZCBmb3IgVmlydHVhbCBIb3N0cyAgICAgICAgICBKdW5lIDIwMTENCg0KDQogICB0aGUgVHJ1c3Qg
TGVnYWwgUHJvdmlzaW9ucyBhbmQgYXJlIHByb3ZpZGVkIHdpdGhvdXQgd2FycmFudHkgYXMNCiAg
IGRlc2NyaWJlZCBpbiB0aGUgU2ltcGxpZmllZCBCU0QgTGljZW5zZS4NCg0KDQpUYWJsZSBvZiBD
b250ZW50cw0KDQogICAxLiAgSW50cm9kdWN0aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDMNCiAgIDIuICBEb2N1bWVudCBDb252ZW50aW9ucyAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMw0KICAgICAyLjEuICBC
YXNpYyBUb2tlbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICA0DQogICAgIDIuMi4gIFNlcnZlciBSZXBsaWVzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDQNCiAgIDMuICBUaGUgSE9TVCBjb21tYW5kIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNQ0KICAgICAzLjEuICBTeW50YXgg
b2YgdGhlIEhPU1QgY29tbWFuZCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA1DQog
ICAgIDMuMi4gIEhPU1QgY29tbWFuZCBzZW1hbnRpY3MgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gIDgNCiAgICAgICAzLjIuMS4gIFJFSU4gY29tbWFuZCBzZW1hbnRpY3MgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgOA0KICAgICAgIDMuMi4yLiAgVXNlci1QSSB1
c2FnZSBvZiBIT1NUICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA5DQogICAgICAg
My4yLjMuICBTdGF0ZSBEaWFncmFtcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gMTANCiAgICAgMy4zLiAgSE9TVCBjb21tYW5kIGVycm9ycyAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxNw0KICAgICAzLjQuICBGRUFUIHJlc3BvbnNlIGZvciBI
T1NUIGNvbW1hbmQgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE4DQogICA0LiAgU2VjdXJp
dHkgQ29uc2lkZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
MTgNCiAgIDUuICBJQU5BIENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAxOQ0KICAgNi4gIFJlZmVyZW5jZXMgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE5DQogICAgIDYuMS4gIE5vcm1hdGl2
ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTkNCiAg
ICAgNi4yLiAgSW5mb3JtYXRpdmUgUmVmZXJlbmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAyMA0KICAgQXBwZW5kaXggQS4gIFVud29ya2FibGUgQWx0ZXJuYXRpdmVzIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDIwDQogICAgIEEuMS4gIE92ZXJsb2FkaW5nIHRo
ZSBDV0QgY29tbWFuZCAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMjENCiAgICAgQS4y
LiAgT3ZlcmxvYWRpbmcgdGhlIEFDQ1QgY29tbWFuZCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAyMQ0KICAgICBBLjMuICBPdmVybG9hZGluZyB0aGUgVVNFUiBjb21tYW5kIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIDIyDQogICAgIEEuNC4gIENvbmNsdXNpb24gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMjMNCiAgIEFwcGVuZGl4IEIu
ICBBY2tub3dsZWRnZW1lbnRzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAy
Mw0KICAgQXV0aG9ycycgQWRkcmVzc2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIDIzDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQpIZXRobW9uICYgTWNNdXJyYXkgICAgICBFeHBpcmVzIERlY2VtYmVyIDMxLCAyMDExICAg
ICAgICAgICAgICAgW1BhZ2UgMl0NCgwNCkludGVybmV0LURyYWZ0ICAgICBGVFAgSE9TVCBDb21t
YW5kIGZvciBWaXJ0dWFsIEhvc3RzICAgICAgICAgIEp1bmUgMjAxMQ0KDQoNCjEuICBJbnRyb2R1
Y3Rpb24NCg0KICAgSXQgaXMgY29tbW9uIG9uIHRoZSBJbnRlcm5ldCBmb3IgbWFueSBETlMgbmFt
ZXMgdG8gcmVzb2x2ZSB0byBhDQogICBzaW5nbGUgSVAgYWRkcmVzcy4gIFRoaXMgcHJhY3RpY2Ug
aGFzIGludHJvZHVjZWQgdGhlIGNvbmNlcHQgb2YgYQ0KICAgInZpcnR1YWwgaG9zdCIsIHdoZXJl
IGEgaG9zdCBhcHBlYXJzIHRvIGV4aXN0IGFzIGFuIGluZGVwZW5kZW50DQogICBlbnRpdHksIGJ1
dCBpbiByZWFsaXR5IHNoYXJlcyBpdHMgcGh5c2ljYWwgcmVzb3VyY2VzIHdpdGggb25lIG9yIG1v
cmUNCiAgIHNpbWlsYXIgaG9zdHMuDQoNCiAgIFN1Y2ggYW4gYXJyYW5nZW1lbnQgcHJlc2VudHMg
c29tZSBwcm9ibGVtcyBmb3IgRlRQIHNlcnZlcnMsIGFzIGFuIEZUUA0KICAgc2VydmVyIGRpc3Rp
bmd1aXNoZXMgaW5jb21pbmcgRlRQIGNvbm5lY3Rpb25zIGJ5IHRoZWlyIElQIGFkZHJlc3NlcywN
CiAgIG5vdCB0aGVpciBETlMgbmFtZXMsIGJlY2F1c2UgaG9zdHMgYXJlIHVuaXF1ZWx5IGlkZW50
aWZpZWQgYnkgdGhlaXINCiAgIGFkZHJlc3MgcmF0aGVyIHRoYW4gbmFtZS4gIFRoYXQgaXMsIGFs
bCBETlMgbmFtZXMgdGhhdCBzaGFyZSBhbiBJUA0KICAgYWRkcmVzcyBhcmUgaGFuZGxlZCBieSB0
aGUgc2FtZSBGVFAgc2VydmVyIGFuZCBzaGFyZSB0aGUgc2FtZSBOZXR3b3JrDQogICBWaXJ0dWFs
IEZpbGUgU3lzdGVtIChOVkZTKS4NCg0KICAgVGhpcyBtZWFucyB0aGF0IGRpZmZlcmVudCB2aXJ0
dWFsIGhvc3RzIGNhbm5vdCBvZmZlciBkaWZmZXJlbnQNCiAgIHZpcnR1YWwgZmlsZSBzeXN0ZW1z
IHRvIGNsaWVudHMsIG5vciBjYW4gdGhleSBvZmZlciBkaWZmZXJlbnQNCiAgIGF1dGhlbnRpY2F0
aW9uIHN5c3RlbXMuICBBbnkgc2NoZW1lIHRvIG92ZXJjb21lIHRoaXMgaXNzdWUgbmVlZHMgdG8N
CiAgIGluZGljYXRlIG5vdCBvbmx5IHRoZSBkZXN0aW5hdGlvbiBJUCBhZGRyZXNzLCBidXQgYWxz
byB0aGUgdmlydHVhbA0KICAgaG9zdCBuYW1lIHRoYXQgaXMgYXNzb2NpYXRlZCB3aXRoIHRoZSBk
ZXNpcmVkIHZpcnR1YWwgRlRQIHNlcnZlci4NCiAgIFR5cGljYWwgdXNlci1GVFAgcHJvY2Vzc2Vz
IGN1cnJlbnRseSB1c2UgaG9zdG5hbWVzIHRvIHBlcmZvcm0NCiAgIGhvc3RuYW1lIHRvIElQIGFk
ZHJlc3MgcmVzb2x1dGlvbiBhbmQgdGhlbiBpZ25vcmUgaG9zdG5hbWVzIGZvciB0aGUNCiAgIHJl
c3Qgb2YgdGhlIEZUUCBzZXNzaW9uLCB0aGVyZWZvcmUgYW55IG1lY2hhbmlzbSB0byBvdmVyY29t
ZSB0aGlzDQogICBpc3N1ZSB3b3VsZCByZXF1aXJlIG1vZGlmaWNhdGlvbnMgdG8gdGhlIHVzZXIt
UEkgYW5kIHNlcnZlci1QSS4NCg0KICAgSXQgc2hvdWxkIGJlIG5vdGVkIHRoYXQgdGhpcyBzYW1l
IHByb2JsZW0gZXhpc3RlZCBmb3IgSFRUUC8xLjAgYXMNCiAgIGRlZmluZWQgaW4gW1JGQzE5NDVd
LCBhbmQgd2FzIHJlc29sdmVkIGluIEhUVFAvMS4xIGFzIGRlZmluZWQgaW4NCiAgIFtSRkMyNjE2
XSB0aHJvdWdoIHRoZSBhZGRpdGlvbiBvZiB0aGUgSG9zdCByZXF1ZXN0IGhlYWRlci4gIFRoZSBn
b2FsDQogICBvZiB0aGlzIGRvY3VtZW50IGlzIHRvIGJyaW5nIGEgc2ltaWxhciBsZXZlbCBvZiBm
ZWF0dXJlIHBhcml0eSB0byBGVFANCiAgIGJ5IGludHJvZHVjaW5nIGEgbmV3IEhPU1QgY29tbWFu
ZCB0aGF0IGFsbG93cyB1c2VyLUZUUCBwcm9jZXNzZXMgdG8NCiAgIHNwZWNpZnkgd2hpY2ggdmly
dHVhbCBob3N0IHRvIGNvbm5lY3QgdG8gZm9yIGEgc2VydmVyLUZUUCBwcm9jZXNzDQogICB0aGF0
IGlzIGhhbmRsaW5nIHJlcXVlc3RzIGZvciBtdWx0aXBsZSB2aXJ0dWFsIGhvc3RzIG9uIGEgc2lu
Z2xlIElQDQogICBhZGRyZXNzLg0KDQoNCjIuICBEb2N1bWVudCBDb252ZW50aW9ucw0KDQogICBU
aGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJUkVEIiwgIlNIQUxMIiwgIlNI
QUxMIE5PVCIsDQogICAiU0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZ
IiwgYW5kICJPUFRJT05BTCIgaW4gdGhpcw0KICAgZG9jdW1lbnQgYXJlIHRvIGJlIGludGVycHJl
dGVkIGFzIGRlc2NyaWJlZCBpbiBbUkZDMjExOV0uDQoNCiAgIEluIGV4YW1wbGVzLCAiQz4iIGFu
ZCAiUz4iIGluZGljYXRlIGxpbmVzIHNlbnQgYnkgdGhlIGNsaWVudCBhbmQNCiAgIHNlcnZlciwg
cmVzcGVjdGl2ZWx5Lg0KDQogICBUaGlzIGRvY3VtZW50IGFsc28gdXNlcyBub3RhdGlvbiBkZWZp
bmVkIGluIFtSRkMwOTU5XSBhbmQgW1JGQzExMjNdLg0KICAgSW4gcGFydGljdWxhciwgdGhlIHRl
cm1zICJyZXBseSIsICJ1c2VyIiwgIk5WRlMiLCAiTlZUIiwgImZpbGUiLA0KICAgInBhdGhuYW1l
IiwgIkZUUCBjb21tYW5kcyIsICJEVFAiLCAidXNlci1GVFAgcHJvY2VzcyIsICJ1c2VyLVBJIiwN
CiAgICJ1c2VyLURUUCIsICJzZXJ2ZXItRlRQIHByb2Nlc3MiLCAic2VydmVyLVBJIiwgInNlcnZl
ci1EVFAiLCAibW9kZSIsDQoNCg0KDQpIZXRobW9uICYgTWNNdXJyYXkgICAgICBFeHBpcmVzIERl
Y2VtYmVyIDMxLCAyMDExICAgICAgICAgICAgICAgW1BhZ2UgM10NCgwNCkludGVybmV0LURyYWZ0
ICAgICBGVFAgSE9TVCBDb21tYW5kIGZvciBWaXJ0dWFsIEhvc3RzICAgICAgICAgIEp1bmUgMjAx
MQ0KDQoNCiAgICJ0eXBlIiwgImNvbnRyb2wgY29ubmVjdGlvbiIsICJkYXRhIGNvbm5lY3Rpb24i
LCBhbmQgIkFTQ0lJIiwgYXJlIGFsbA0KICAgdXNlZCBoZXJlIGFzIGRlZmluZWQgdGhlcmUuDQoN
CiAgIFN5bnRheCByZXF1aXJlZCBpcyBkZWZpbmVkIHVzaW5nIHRoZSBBdWdtZW50ZWQgQk5GIGRl
ZmluZWQgaW4NCiAgIFtSRkM1MjM0XS4gIFNvbWUgZ2VuZXJhbCBBQk5GIGRlZmluaXRpb25zIGFy
ZSByZXF1aXJlZCB0aHJvdWdob3V0IHRoZQ0KICAgZG9jdW1lbnQ7IHRob3NlIHdpbGwgYmUgZGVm
aW5lZCBsYXRlciBpbiB0aGlzIHNlY3Rpb24uICBBdCBmaXJzdA0KICAgcmVhZGluZywgaXQgbWF5
IGJlIHdpc2UgdG8gc2ltcGx5IHJlY2FsbCB0aGF0IHRoZXNlIGRlZmluaXRpb25zIGV4aXN0DQog
ICBoZXJlLCBhbmQgc2tpcCB0byB0aGUgbmV4dCBzZWN0aW9uLg0KDQoyLjEuICBCYXNpYyBUb2tl
bnMNCg0KICAgVGhpcyBkb2N1bWVudCBpbXBvcnRzIHRoZSBjb3JlIGRlZmluaXRpb25zIGdpdmVu
IGluIEFwcGVuZGl4IEIgb2YNCiAgIFtSRkM1MjM0XS4gIFRoZXJlIGRlZmluaXRpb25zIHdpbGwg
YmUgZm91bmQgZm9yIGJhc2ljIEFCTkYgZWxlbWVudHMNCiAgIGxpa2UgQUxQSEEsIERJR0lULCBT
UCwgZXRjLiAgVG8gdGhhdCwgdGhlIGZvbGxvd2luZyB0ZXJtIGlzIGFkZGVkIGZvcg0KICAgdXNl
IGluIHRoaXMgZG9jdW1lbnQuDQoNCiAgICAgICAgVENIQVIgPSBWQ0hBUiAvIFNQIC8gSFRBQiAg
ICA7IHZpc2libGUgcGx1cyB3aGl0ZSBzcGFjZQ0KDQogICBUaGUgVkNIQVIgKGZyb20gW1JGQzUy
MzRdKSBhbmQgVENIQVIgcnVsZXMgZ2l2ZSBiYXNpYyBjaGFyYWN0ZXIgdHlwZXMNCiAgIGZyb20g
dmFyeWluZyBzdWItc2V0cyBvZiB0aGUgQVNDSUkgY2hhcmFjdGVyIHNldCBmb3IgdXNlIGluIHZh
cmlvdXMNCiAgIGNvbW1hbmRzIGFuZCByZXNwb25zZXMuDQoNCiAgIE5vdGUgdGhhdCBpbiBBQk5G
LCBzdHJpbmcgbGl0ZXJhbHMgYXJlIGNhc2UgaW5zZW5zaXRpdmUuICBUaGF0DQogICBjb252ZW50
aW9uIGlzIHByZXNlcnZlZCBpbiB0aGlzIGRvY3VtZW50LCBhbmQgaW1wbGllcyB0aGF0IEZUUA0K
ICAgY29tbWFuZHMgYW5kIHBhcmFtZXRlcnMgdGhhdCBhcmUgYWRkZWQgYnkgdGhpcyBzcGVjaWZp
Y2F0aW9uIGhhdmUNCiAgIHZhbHVlcyB0aGF0IGNhbiBiZSByZXByZXNlbnRlZCBpbiBhbnkgY2Fz
ZS4gIFRoYXQgaXMsICJIT1NUIiBpcyB0aGUNCiAgIHNhbWUgYXMgImhvc3QiLCAiSG9zdCIsICJI
b1N0IiwgZXRjLiwgYW5kICJmdHAuZXhhbXBsZS5jb20iIGlzIHRoZQ0KICAgc2FtZSBhcyAiRnRw
LkV4YW1wbGUuQ29tIiwgImZUcC5lWGFtcGxlLmNPbSIsIGV0Yy4NCg0KMi4yLiAgU2VydmVyIFJl
cGxpZXMNCg0KICAgU2VjdGlvbiA0LjIgb2YgW1JGQzA5NTldIGRlZmluZXMgdGhlIGZvcm1hdCBh
bmQgbWVhbmluZyBvZiByZXBsaWVzIGJ5DQogICB0aGUgc2VydmVyLVBJIHRvIEZUUCBjb21tYW5k
cyBmcm9tIHRoZSB1c2VyLVBJLiAgVGhvc2UgcmVwbHkNCiAgIGNvbnZlbnRpb25zIGFyZSB1c2Vk
IGhlcmUgd2l0aG91dCBjaGFuZ2UuDQoNCiAgICAgICAgZXJyb3ItcmVzcG9uc2UgPSBlcnJvci1j
b2RlIFNQICpUQ0hBUiBDUkxGDQogICAgICAgIGVycm9yLWNvZGUgICAgID0gKCI0IiAvICI1Iikg
MkRJR0lUDQoNCiAgIEltcGxlbWVudGVycyBzaG91bGQgbm90ZSB0aGF0IHRoZSBBQk5GIHN5bnRh
eCAod2hpY2ggd2FzIG5vdCB1c2VkIGluDQogICBbUkZDMDk1OV0pIHVzZWQgaW4gdGhpcyBkb2N1
bWVudCwgYW5kIG90aGVyIEZUUCByZWxhdGVkIGRvY3VtZW50cywNCiAgIHNvbWV0aW1lcyBzaG93
cyByZXBsaWVzIHVzaW5nIHRoZSBvbmUgbGluZSBmb3JtYXQuICBVbmxlc3Mgb3RoZXJ3aXNlDQog
ICBleHBsaWNpdGx5IHN0YXRlZCwgdGhhdCBpcyBub3QgaW50ZW5kZWQgdG8gaW1wbHkgdGhhdCBt
dWx0aS1saW5lDQogICByZXNwb25zZXMgYXJlIG5vdCBwZXJtaXR0ZWQuICBJbXBsZW1lbnRlcnMg
c2hvdWxkIGFzc3VtZSB0aGF0LCB1bmxlc3MNCiAgIHN0YXRlZCB0byB0aGUgY29udHJhcnksIGFu
eSByZXBseSB0byBhbnkgRlRQIGNvbW1hbmQgKGluY2x1ZGluZyBRVUlUKQ0KICAgY2FuIGJlIG9m
IHRoZSBtdWx0aS1saW5lIGZvcm1hdCBkZXNjcmliZWQgaW4gW1JGQzA5NTldLg0KDQogICBUaHJv
dWdob3V0IHRoaXMgZG9jdW1lbnQsIHJlcGxpZXMgd2lsbCBiZSBpZGVudGlmaWVkIGJ5IHRoZSB0
aHJlZQ0KICAgZGlnaXQgY29kZSB0aGF0IGlzIHRoZWlyIGZpcnN0IGVsZW1lbnQuICBUaHVzIHRo
ZSB0ZXJtICI1MDAgcmVwbHkiDQoNCg0KDQpIZXRobW9uICYgTWNNdXJyYXkgICAgICBFeHBpcmVz
IERlY2VtYmVyIDMxLCAyMDExICAgICAgICAgICAgICAgW1BhZ2UgNF0NCgwNCkludGVybmV0LURy
YWZ0ICAgICBGVFAgSE9TVCBDb21tYW5kIGZvciBWaXJ0dWFsIEhvc3RzICAgICAgICAgIEp1bmUg
MjAxMQ0KDQoNCiAgIG1lYW5zIGEgcmVwbHkgZnJvbSB0aGUgc2VydmVyLVBJIHVzaW5nIHRoZSB0
aHJlZSBkaWdpdCBjb2RlICI1MDAiLg0KDQoNCjMuICBUaGUgSE9TVCBjb21tYW5kDQoNCiAgIEEg
bmV3IGNvbW1hbmQgIkhPU1QiIGlzIGFkZGVkIHRvIHRoZSBGVFAgY29tbWFuZCBzZXQgdG8gYWxs
b3cgdGhlDQogICBzZXJ2ZXItRlRQIHByb2Nlc3MgdG8gZGV0ZXJtaW5lIHRvIHdoaWNoIG9mIHBv
c3NpYmx5IG1hbnkgdmlydHVhbA0KICAgaG9zdHMgdGhlIGNsaWVudCB3aXNoZXMgdG8gY29ubmVj
dC4gIFRoaXMgY29tbWFuZCBTSE9VTEQgYmUgaXNzdWVkDQogICBiZWZvcmUgdGhlIHVzZXIgaXMg
YXV0aGVudGljYXRlZCwgYWxsb3dpbmcgdGhlIGF1dGhlbnRpY2F0aW9uIHNjaGVtZSwNCiAgIGFu
ZCBzZXQgb2YgbGVnYWwgdXNlcnMsIHRvIGJlIGRlcGVuZGVudCB1cG9uIHRoZSB2aXJ0dWFsIGhv
c3QgY2hvc2VuLg0KDQogICBTZXJ2ZXItRlRQIHByb2Nlc3NlcyBNVVNUIHRyZWF0IGEgc2l0dWF0
aW9uIHdoZXJlIHRoZSBIT1NUIGNvbW1hbmQgaXMNCiAgIGlzc3VlZCBtb3JlIHRoYW4gb25jZSBi
ZWZvcmUgdGhlIHVzZXIgaGFzIGJlZW4gYXV0aGVudGljYXRlZCBhcw0KICAgdGhvdWdoIGEgUkVJ
TiBjb21tYW5kIHdhcyBzZW50IGJlZm9yZSBlYWNoIEhPU1QgY29tbWFuZCwgYW5kIHRoZW4NCiAg
IHJlc2V0IHRoZSB1c2VyLVBJIHRvIHRoZSBzdGF0ZSB0aGF0IGV4aXN0ZWQgYWZ0ZXIgdGhlIFRD
UCBjb25uZWN0aW9uDQogICB3YXMgZmlyc3QgZXN0YWJsaXNoZWQgYW5kIHJldHVybiB0aGUgYXBw
cm9wcmlhdGUgcmVwbHkgZm9yIHRoZSBIT1NUDQogICBjb21tYW5kLg0KDQogICBTZXJ2ZXItRlRQ
IHByb2Nlc3NlcyBNVVNUIHRyZWF0IGEgc2l0dWF0aW9uIHdoZXJlIHRoZSBIT1NUIGNvbW1hbmQg
aXMNCiAgIGlzc3VlZCBhZnRlciB0aGUgdXNlciBoYXMgYmVlbiBhdXRoZW50aWNhdGVkIGJ5IHVz
aW5nIG9uZSBvZiB0aGUNCiAgIGZvbGxvd2luZyB0d28gYmVoYXZpb3JzOg0KDQogICBhLiAgVHJl
YXQgdGhlIGxhdGUgSE9TVCBjb21tYW5kIGFzIGFuIGVycm9uZW91cyBzZXF1ZW5jZSBvZiBjb21t
YW5kcw0KICAgICAgIGFuZCByZXR1cm4gYSA1MDMgcmVwbHkuDQoNCiAgIGIuICBUcmVhdCB0aGUg
bGF0ZSBIT1NUIGNvbW1hbmQgYXMgdGhvdWdoIGEgUkVJTiBjb21tYW5kIHdhcyBzZW50DQogICAg
ICAgYmVmb3JlIHRoZSBIT1NUIGNvbW1hbmQgYW5kIHJlc2V0IHRoZSB1c2VyLVBJIHRvIHRoZSBz
dGF0ZSB0aGF0DQogICAgICAgZXhpc3RlZCBhZnRlciB0aGUgVENQIGNvbm5lY3Rpb24gd2FzIGZp
cnN0IGVzdGFibGlzaGVkIGFuZCBiZWZvcmUNCiAgICAgICB0aGUgaW5pdGlhbCB1c2VyIGF1dGhl
bnRpY2F0aW9uIGFuZCB0aGVuIHJldHVybiB0aGUgYXBwcm9wcmlhdGUNCiAgICAgICByZXBseSBm
b3IgdGhlIEhPU1QgY29tbWFuZC4NCg0KICAgU2VydmVycyBzaG91bGQgbm90ZSB0aGF0IHRoZSBy
ZXNwb25zZSB0byB0aGUgSE9TVCBjb21tYW5kIGlzIGENCiAgIHNlbnNpYmxlIHRpbWUgdG8gc2Vu
ZCB0aGVpciAid2VsY29tZSIgbWVzc2FnZS4gIFRoaXMgYWxsb3dzIHRoZQ0KICAgbWVzc2FnZSB0
byBiZSBwZXJzb25hbGl6ZWQgZm9yIGFueSB2aXJ0dWFsIGhvc3RzIHRoYXQgYXJlIHN1cHBvcnRl
ZCwNCiAgIGFuZCBhbHNvIGFsbG93cyB0aGUgY2xpZW50IHRvIGRldGVybWluZSB0aGUgc3VwcG9y
dGVkIGxhbmd1YWdlcywgb3INCiAgIHJlcHJlc2VudGF0aW9ucywgZm9yIHRoZSBtZXNzYWdlLCBh
bmQgb3RoZXIgbWVzc2FnZXMsIHZpYSB0aGUgRkVBVA0KICAgcmVzcG9uc2UsIGFuZCBzZWxlY3Qg
YW4gYXBwcm9wcmlhdGUgb25lIHZpYSB0aGUgTEFORyBjb21tYW5kLiAgU2VlDQogICBbUkZDMjY0
MF0gZm9yIG1vcmUgaW5mb3JtYXRpb24uDQoNCjMuMS4gIFN5bnRheCBvZiB0aGUgSE9TVCBjb21t
YW5kDQoNCiAgIFRoZSBIT1NUIGNvbW1hbmQgaXMgZGVmaW5lZCBhcyBmb2xsb3dzLg0KDQoNCg0K
DQoNCg0KDQoNCg0KSGV0aG1vbiAmIE1jTXVycmF5ICAgICAgRXhwaXJlcyBEZWNlbWJlciAzMSwg
MjAxMSAgICAgICAgICAgICAgIFtQYWdlIDVdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgRlRQIEhP
U1QgQ29tbWFuZCBmb3IgVmlydHVhbCBIb3N0cyAgICAgICAgICBKdW5lIDIwMTENCg0KDQogICAg
IGhvc3QtY29tbWFuZCAgPSAiSE9TVCIgU1AgaG9zdG5hbWUgQ1JMRg0KICAgICBob3N0bmFtZSAg
ICAgID0gZG9tYWluIC8gSVAtbGl0ZXJhbA0KDQogICAgIGRvbWFpbiAgICAgICAgPSBzdWItZG9t
YWluICooIi4iIHN1Yi1kb21haW4pDQogICAgIHN1Yi1kb21haW4gICAgPSBsZXQtZGlnIFtsZGgt
c3RyXQ0KICAgICBsZXQtZGlnICAgICAgID0gQUxQSEEgLyBESUdJVA0KICAgICBsZGgtc3RyICAg
ICAgID0gKiggQUxQSEEgLyBESUdJVCAvICItIiApIGxldC1kaWcNCg0KICAgICBJUC1saXRlcmFs
ICAgID0gKCAiWyIgSVB2NmFkZHJlc3MgIl0iICkgLyBJUHY0YWRkcmVzcw0KDQogICAgIElQdjZh
ZGRyZXNzICAgPSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDYoIGgxNiAiOiIgKSBsczMy
DQogICAgICAgICAgICAgICAgICAgICAvICAgICAgICAgICAgICAgICAgICAgICAiOjoiIDUoIGgx
NiAiOiIgKSBsczMyDQogICAgICAgICAgICAgICAgICAgICAvIFsgICAgICAgICAgICAgICBoMTYg
XSAiOjoiIDQoIGgxNiAiOiIgKSBsczMyDQogICAgICAgICAgICAgICAgICAgICAvIFsgKjEoIGgx
NiAiOiIgKSBoMTYgXSAiOjoiIDMoIGgxNiAiOiIgKSBsczMyDQogICAgICAgICAgICAgICAgICAg
ICAvIFsgKjIoIGgxNiAiOiIgKSBoMTYgXSAiOjoiIDIoIGgxNiAiOiIgKSBsczMyDQogICAgICAg
ICAgICAgICAgICAgICAvIFsgKjMoIGgxNiAiOiIgKSBoMTYgXSAiOjoiICAgIGgxNiAiOiIgICBs
czMyDQogICAgICAgICAgICAgICAgICAgICAvIFsgKjQoIGgxNiAiOiIgKSBoMTYgXSAiOjoiICAg
ICAgICAgICAgICBsczMyDQogICAgICAgICAgICAgICAgICAgICAvIFsgKjUoIGgxNiAiOiIgKSBo
MTYgXSAiOjoiICAgICAgICAgICAgICBoMTYNCiAgICAgICAgICAgICAgICAgICAgIC8gWyAqNigg
aDE2ICI6IiApIGgxNiBdICI6OiINCg0KICAgICBsczMyICAgICAgICAgID0gKCBoMTYgIjoiIGgx
NiApIC8gSVB2NGFkZHJlc3MNCiAgICAgICAgICAgICAgICAgICAgIDsgbGVhc3Qtc2lnbmlmaWNh
bnQgMzIgYml0cyBvZiBhZGRyZXNzDQoNCiAgICAgaDE2ICAgICAgICAgICA9IDEqNEhFWERJRw0K
ICAgICAgICAgICAgICAgICAgICAgOyAxNiBiaXRzIG9mIGFkZHJlc3MgcmVwcmVzZW50ZWQgaW4g
aGV4YWRlY2ltYWwNCg0KICAgICBJUHY0YWRkcmVzcyAgID0gZGVjLW9jdGV0ICIuIiBkZWMtb2N0
ZXQgIi4iIGRlYy1vY3RldCAiLiIgZGVjLW9jdGV0DQoNCiAgICAgZGVjLW9jdGV0ICAgICA9IERJ
R0lUICAgICAgICAgICAgICAgICA7IDAtOQ0KICAgICAgICAgICAgICAgICAgICAgLyAleDMxLTM5
IERJR0lUICAgICAgIDsgMTAtOTkNCiAgICAgICAgICAgICAgICAgICAgIC8gIjEiIDJESUdJVCAg
ICAgICAgICA7IDEwMC0xOTkNCiAgICAgICAgICAgICAgICAgICAgIC8gIjIiICV4MzAtMzQgRElH
SVQgICA7IDIwMC0yNDkNCiAgICAgICAgICAgICAgICAgICAgIC8gIjI1IiAleDMwLTM1ICAgICAg
ICA7IDI1MC0yNTUNCg0KICAgICBob3N0LXJlc3BvbnNlID0gaG9zdC1vayAvIGVycm9yLXJlc3Bv
bnNlDQogICAgIGhvc3Qtb2sgICAgICAgPSAiMjIwIiBbIFNQICpUQ0hBUiBdIENSTEYNCg0KICAg
QXMgd2l0aCBhbGwgRlRQIGNvbW1hbmRzLCB0aGUgIkhPU1QiIGNvbW1hbmQgd29yZCBpcyBjYXNl
DQogICBpbmRlcGVuZGVudCwgYW5kIE1BWSBiZSBzcGVjaWZpZWQgaW4gYW55IGNoYXJhY3RlciBj
YXNlIGRlc2lyZWQuDQoNCiAgIFRoZSAiaG9zdG5hbWUiIChnaXZlbiBhcyBhIHBhcmFtZXRlcikg
c3BlY2lmaWVzIHRoZSB2aXJ0dWFsIGhvc3QgdG8NCiAgIHdoaWNoIGFjY2VzcyBpcyBkZXNpcmVk
LiAgVGhpcyBTSE9VTEQgYmUgdGhlIHNhbWUgaG9zdCBuYW1lIHRoYXQgd2FzDQogICB1c2VkIHRv
IG9idGFpbiB0aGUgSVAgYWRkcmVzcyB0byB3aGljaCB0aGUgRlRQIGNvbnRyb2wgY29ubmVjdGlv
biB3YXMNCiAgIG1hZGUsIGFmdGVyIGFueSBjbGllbnQgY29udmVyc2lvbnMgaGF2ZSBiZWVuIGNv
bXBsZXRlZCB0aGF0IGNvbnZlcnQNCiAgIGFuIGFiYnJldmlhdGVkIG9yIGxvY2FsIGFsaWFzIHRv
IGEgY29tcGxldGUgKGZ1bGx5IHF1YWxpZmllZCkgZG9tYWluDQogICBuYW1lLCBidXQgYmVmb3Jl
IHJlc29sdmluZyBhIEROUyBhbGlhcyAob3duZXIgb2YgYSBDTkFNRSByZXNvdXJjZQ0KICAgcmVj
b3JkKSB0byBpdHMgY2Fub25pY2FsIG5hbWUuDQoNCg0KDQoNCkhldGhtb24gJiBNY011cnJheSAg
ICAgIEV4cGlyZXMgRGVjZW1iZXIgMzEsIDIwMTEgICAgICAgICAgICAgICBbUGFnZSA2XQ0KDA0K
SW50ZXJuZXQtRHJhZnQgICAgIEZUUCBIT1NUIENvbW1hbmQgZm9yIFZpcnR1YWwgSG9zdHMgICAg
ICAgICAgSnVuZSAyMDExDQoNCg0KICAgSW50ZXJuYXRpb25hbGl6YXRpb24gb2YgZG9tYWluIG5h
bWVzIGlzIG9ubHkgc3VwcG9ydGVkIHRocm91Z2ggdGhlDQogICB1c2Ugb2YgUHVueWNvZGUgYXMg
ZGVzY3JpYmVkIGluIFtSRkMzNDkyXS4NCg0KICAgSWYgdGhlIHVzZXIgd2FzIGdpdmVuIGFuIElQ
djQgb3IgSVB2NiBsaXRlcmFsIGFkZHJlc3MsIGFuZA0KICAgY29uc2VxdWVudGx5IHdhcyBub3Qg
cmVxdWlyZWQgdG8gZGVyaXZlIHRoZSBsaXRlcmFsIGFkZHJlc3MgZnJvbSBhDQogICBob3N0bmFt
ZSwgdGhlIGNsaWVudCBNQVkgc2VuZCB0aGUgSE9TVCBjb21tYW5kIHdpdGggdGhlIElQdjQgb3Ig
SVB2Ng0KICAgbGl0ZXJhbCBhZGRyZXNzIGFzIHNwZWNpZmllZCB0byBpdC4gIFdoaWxlIGl0IG1h
eSBzZWVtIGNvdW50ZXItDQogICBpbnR1aXRpdmUgdG8gc3BlY2lmeSBhIGxpdGVyYWwgYWRkcmVz
cyBieSB1c2luZyB0aGUgSE9TVCBjb21tYW5kDQogICBhZnRlciB0aGUgY2xpZW50IGhhcyBhbHJl
YWR5IGNvbm5lY3RlZCB0byB0aGUgc2VydmVyIHVzaW5nIGEgbGl0ZXJhbA0KICAgYWRkcmVzcywg
dGhpcyBzaG91bGQgYmUgZXhwZWN0ZWQgYmVoYXZpb3IgYmVjYXVzZSBhIHVzZXItRlRQIHByb2Nl
c3MNCiAgIHNob3VsZCBub3QgYmUgcmVxdWlyZWQgdG8gZGlmZmVyZW50aWF0ZSBiZXR3ZWVuIGEg
ZnVsbHkgcXVhbGlmaWVkDQogICBkb21haW4gbmFtZSBhbmQgYW4gSVB2NCBvciBJUHY2IG5ldHdv
cmsgbGl0ZXJhbCBhZGRyZXNzLiAgVGhhdCBiZWluZw0KICAgc2FpZCwgaWYgdGhlIElQdjQgb3Ig
SVB2NiBsaXRlcmFsIGFkZHJlc3Mgc3BlY2lmaWVkIGJ5IHRoZSBjbGllbnQNCiAgIGRvZXMgbm90
IG1hdGNoIHRoZSBsaXRlcmFsIGFkZHJlc3MgZm9yIHRoZSBzZXJ2ZXIsIHRoZSBzZXJ2ZXIgTVVT
VA0KICAgcmVzcG9uZCB3aXRoIGEgNTA0IHJlcGx5IHRvIGluZGljYXRlIHRoYXQgdGhlIElQdjQg
b3IgSVB2NiBsaXRlcmFsDQogICBhZGRyZXNzIGlzIG5vdCB2YWxpZC4NCg0KICAgV2hlbiB0aGUg
aG9zdG5hbWUgcGFyYW1ldGVyIGNvbnRhaW5zIGEgbGl0ZXJhbCBhZGRyZXNzLCBzcXVhcmUNCiAg
IGJyYWNrZXRzIGFyZSBleHBlY3RlZCB0byBkaXNhbWJpZ3VhdGUgSVB2NiBhZGRyZXNzIHN5bnRh
eCBmcm9tIHBvcnQNCiAgIG51bWJlcnMgc3ludGF4LiAgVGhlcmVmb3JlLCBpZiB0aGUgbGl0ZXJh
bCBhZGRyZXNzIGlzIGFuIElQdjYNCiAgIGFkZHJlc3MsIHRoZSBJUHY2IGFkZHJlc3MgaXMgcmVx
dWlyZWQgdG8gYmUgZW5jbG9zZWQgaW4gc3F1YXJlDQogICBicmFja2V0cyAoYWZ0ZXIgZWxpbWlu
YXRpbmcgYW55IHN5bnRheCB0aGF0IG1pZ2h0IGFsc28gLSBidXQgaXMgbm90DQogICByZXF1aXJl
ZCB0byAtIGJlIGVuY2xvc2VkIGluIGJyYWNrZXRzLCBhbmQgZnJvbSB3aGljaCB0aGUgc2VydmVy
DQogICBkZWR1Y2VkIHRoYXQgYSBsaXRlcmFsIGFkZHJlc3MgaGFkIGJlZW4gc3BlY2lmaWVkLikg
IEZvciBleGFtcGxlLCB0aGUNCiAgIGZvbGxvd2luZyBleGFtcGxlcyBNQVkgYmUgc2VudCBpZiB0
aGUgY2xpZW50IGhhZCBiZWVuIGluc3RydWN0ZWQgdG8NCiAgIHJlc3BlY3RpdmVseSBjb25uZWN0
IHRvICIxOTIuMC4yLjEiLCAiRkU4MDo6YzAwMDowMjAxIiwgb3INCiAgICIxOTIuMC4yLjEiIGFu
ZCBJUHY2IHN5bnRheCBpcyBwcmVmZXJyZWQ6DQoNCiAgICAgICAgSE9TVCAxOTIuMC4yLjENCiAg
ICAgICAgSE9TVCBbRkU4MDo6YzAwMDowMjAxXQ0KICAgICAgICBIT1NUIFs6OjE5Mi4wLjIuMV0N
Cg0KICAgVGhlIGNsaWVudCBNVVNUIE5PVCBzZW5kIHRoZSBwb3J0IG51bWJlciBhcyBwYXJ0IG9m
IHRoZSBIT1NUIGNvbW1hbmQsDQogICBldmVuIHdoZW4gdGhlIGNsaWVudCBoYXMgYmVlbiBpbnN0
cnVjdGVkIHRvIGNvbm5lY3QgdG8gYSBub24tc3RhbmRhcmQNCiAgIHBvcnQuICBUaGUgcmVhc29u
IGZvciB0aGlzIHJlcXVpcmVtZW50IGlzIHRoYXQgdGhlIHVzZXItUEkgd2lsbCBoYXZlDQogICBl
c3RhYmxpc2hlZCBhIGNvbm5lY3Rpb24gdG8gdGhlIHNlcnZlci1QSSBiZWZvcmUgdGhlIEhPU1Qg
Y29tbWFuZCBpcw0KICAgc2VudCwgdGhlcmVmb3JlIHNwZWNpZnlpbmcgYSBkaWZmZXJlbnQgcG9y
dCB3aXRoIHRoZSBIT1NUIGNvbW1hbmQgaGFzDQogICBubyBtZWFuaW5nLiAgRm9yIGV4YW1wbGUs
IHRoZSBzZXJ2ZXItUEkgTVVTVCByZXNwb25kIHdpdGggYSA1MDEgcmVwbHkNCiAgIGlmIHRoZSBj
bGllbnQgc2VuZHMgYSBIT1NUIGNvbW1hbmQgd2l0aCBzeW50YXggbGlrZSBlaXRoZXIgb2YgdGhl
DQogICBmb2xsb3dpbmcgZXhhbXBsZXM6DQoNCiAgICAgICAgSE9TVCAxOTIuMC4yLjE6MjExMg0K
ICAgICAgICBIT1NUIFtGRTgwOjpjMDAwOjAyMDFdOjIxMTINCg0KICAgVGhlIGhvc3RuYW1lIHBh
cmFtZXRlciBpcyBvdGhlcndpc2UgdG8gYmUgdHJlYXRlZCBhcyBhIGZ1bGx5DQogICBxdWFsaWZp
ZWQgZG9tYWluIG5hbWUgb3IgcmVsYXRpdmUgbmFtZSBhcyB0aG9zZSB0ZXJtcyBhcmUgZGVmaW5l
ZCBpbg0KICAgc2VjdGlvbiAzLjEgb2YgW1JGQzEwMzRdLiAgVGhpcyBpbXBsaWVzIHRoYXQgdGhl
IG5hbWUgaXMgdG8gYmUNCiAgIHRyZWF0ZWQgYXMgYSBjYXNlLWluZGVwZW5kZW50IHN0cmluZywg
bWVhbmluZyB0aGF0IHVwcGVyY2FzZSBBU0NJSQ0KDQoNCg0KSGV0aG1vbiAmIE1jTXVycmF5ICAg
ICAgRXhwaXJlcyBEZWNlbWJlciAzMSwgMjAxMSAgICAgICAgICAgICAgIFtQYWdlIDddDQoMDQpJ
bnRlcm5ldC1EcmFmdCAgICAgRlRQIEhPU1QgQ29tbWFuZCBmb3IgVmlydHVhbCBIb3N0cyAgICAg
ICAgICBKdW5lIDIwMTENCg0KDQogICBjaGFyYWN0ZXJzIGFyZSB0byBiZSB0cmVhdGVkIGFzIGVx
dWl2YWxlbnQgdG8gdGhlaXIgY29ycmVzcG9uZGluZw0KICAgbG93ZXJjYXNlIEFTQ0lJIGNoYXJh
Y3RlcnMsIGJ1dCBvdGhlcndpc2UgcHJlc2VydmVkIGFzIGdpdmVuLiAgSXQNCiAgIGFsc28gaW1w
bGllcyBzb21lIGxpbWl0cyBvbiB0aGUgbGVuZ3RoIG9mIHRoZSBwYXJhbWV0ZXIgYW5kIG9mIHRo
ZQ0KICAgY29tcG9uZW50cyB0aGF0IGNyZWF0ZSBpdHMgaW50ZXJuYWwgc3RydWN0dXJlLiAgVGhv
c2UgbGltaXRzIGFyZSBub3QNCiAgIGFsdGVyZWQgaW4gYW55IHdheSBoZXJlLg0KDQogICBOZWl0
aGVyIFtSRkMxMDM0XSBub3IgW1JGQzEwMzVdIGltcG9zZSBhbnkgb3RoZXIgcmVzdHJpY3Rpb25z
IHVwb24NCiAgIHdoYXQga2luZHMgb2YgbmFtZXMgY2FuIGJlIHN0b3JlZCBpbiB0aGUgRE5TLiAg
VGhpcyBzcGVjaWZpY2F0aW9uLA0KICAgaG93ZXZlciwgb25seSBhbGxvd3MgdGhlIHVzZSBvZiBu
YW1lcyB0aGF0IGNhbiBiZSBpbmZlcnJlZCBmcm9tIHRoZQ0KICAgQUJORiBncmFtbWFyIGdpdmVu
IGZvciB0aGUgImhvc3RuYW1lIi4NCg0KMy4yLiAgSE9TVCBjb21tYW5kIHNlbWFudGljcw0KDQog
ICBVcG9uIHJlY2VpdmluZyB0aGUgSE9TVCBjb21tYW5kLCBiZWZvcmUgYXV0aGVudGljYXRpbmcg
dGhlIHVzZXItUEksIGENCiAgIHNlcnZlci1GVFAgcHJvY2VzcyBTSE9VTEQgdmFsaWRhdGUgdGhh
dCB0aGUgaG9zdG5hbWUgZ2l2ZW4gcmVwcmVzZW50cw0KICAgYSB2YWxpZCB2aXJ0dWFsIGhvc3Qg
Zm9yIHRoYXQgc2VydmVyLCBhbmQsIGlmIGl0IGlzIHZhbGlkLCBlc3RhYmxpc2gNCiAgIHRoZSBh
cHByb3ByaWF0ZSBlbnZpcm9ubWVudCBmb3IgdGhhdCB2aXJ0dWFsIGhvc3QuICBUaGUgcmVzdWx0
YW50DQogICBhY3Rpb25zIG5lZWRlZCB0byBjcmVhdGUgdGhhdCBlbnZpcm9ubWVudCBhcmUgbm90
IHNwZWNpZmllZCBoZXJlLCBhbmQNCiAgIG1heSByYW5nZSBmcm9tIGRvaW5nIG5vdGhpbmcgYXQg
YWxsLCB0byBwZXJmb3JtaW5nIGEgc2ltcGxlIGNoYW5nZSBvZg0KICAgd29ya2luZyBkaXJlY3Rv
cnksIGNoYW5naW5nIGF1dGhlbnRpY2F0aW9uIHNjaGVtZXMgYW5kL29yIHVzZXJuYW1lDQogICBh
bmQgcGFzc3dvcmQgbGlzdHMsIG9yIG1ha2luZyBtdWNoIG1vcmUgZWxhYm9yYXRlIHN0YXRlIGNo
YW5nZXMgLQ0KICAgc3VjaCBhcyBjcmVhdGluZyBpc29sYXRlZCBlbnZpcm9ubWVudHMgZm9yIGVh
Y2ggRlRQIHNlc3Npb24uDQoNCiAgIFRoZSAiMjIwIiByZXBseSBjb2RlIGZvciB0aGUgSE9TVCBj
b21tYW5kIGlzIHRoZSBzYW1lIGFzIHRoZSBjb2RlDQogICB0aGF0IGlzIHVzZWQgaW4gdGhlIGlu
aXRpYWwgIndlbGNvbWUiIG1lc3NhZ2UgdGhhdCBpcyBzZW50IGFmdGVyIHRoZQ0KICAgY29ubmVj
dGlvbiBpcyBlc3RhYmxpc2hlZC4NCg0KICAgSWYgdGhlIGhvc3RuYW1lIHNwZWNpZmllZCB3b3Vs
ZCBub3JtYWxseSBiZSBhY2NlcHRhYmxlLCBidXQgZm9yIGFueQ0KICAgcmVhc29uIGlzIHRlbXBv
cmFyaWx5IHVuYXZhaWxhYmxlLCB0aGUgc2VydmVyLUZUUCBwcm9jZXNzIFNIT1VMRA0KICAgcmVw
bHkgdG8gdGhlIEhPU1QgY29tbWFuZCB3aXRoIGEgNDIxIHJlcGx5IGFuZCBjbG9zZSB0aGUgY29u
bmVjdGlvbi4NCiAgIEluIHRoaXMgcGFydGljdWxhciBzaXR1YXRpb24sIHRoZSBzZXJ2ZXItRlRQ
IHByb2Nlc3MgTUFZIGNob29zZSB0bw0KICAga2VlcCB0aGUgY29ubmVjdGlvbiBvcGVuIGluIG9y
ZGVyIHRvIGFsbG93IHRoZSB1c2VyLVBJIGFuIG9wcG9ydHVuaXR5DQogICB0byBjaG9vc2UgYW5v
dGhlciB2aXJ0dWFsIGhvc3Qgd2l0aCBhIHN1YnNlcXVlbnQgSE9TVCBjb21tYW5kLg0KDQogICBJ
ZiB0aGUgaG9zdG5hbWUgc3BlY2lmaWVkIGlzIHVua25vd24gYXQgdGhlIHNlcnZlciwgb3IgaWYg
dGhlIHNlcnZlcg0KICAgaXMgb3RoZXJ3aXNlIHVud2lsbGluZyB0byB0cmVhdCB0aGUgcGFydGlj
dWxhciBjb25uZWN0aW9uIGFzIGENCiAgIGNvbm5lY3Rpb24gdG8gdGhlIGhvc3RuYW1lIHNwZWNp
ZmllZCwgdGhlIHNlcnZlciBTSE9VTEQgcmVzcG9uZCB3aXRoDQogICBhIDUwNCByZXBseS4NCg0K
My4yLjEuICBSRUlOIGNvbW1hbmQgc2VtYW50aWNzDQoNCiAgIEFzIHNwZWNpZmllZCBpbiBbUkZD
MDk1OV0sIHRoZSBSRUlOIGNvbW1hbmQgcmV0dXJucyB0aGUgc3RhdGUgb2YgdGhlDQogICBjb25u
ZWN0aW9uIHRvIHdoYXQgaXQgd2FzIGltbWVkaWF0ZWx5IGFmdGVyIHRoZSB0cmFuc3BvcnQgY29u
bmVjdGlvbg0KICAgd2FzIG9wZW5lZC4gIFRoaXMgc3BlY2lmaWNhdGlvbiBtYWtlcyBubyBjaGFu
Z2VzIHRvIHRoYXQgYmVoYXZpb3IuDQogICBUaGUgZWZmZWN0IG9mIGEgSE9TVCBjb21tYW5kIE1V
U1QgYmUgcmVzZXQgaWYgYSBSRUlOIGNvbW1hbmQgaXMNCiAgIHBlcmZvcm1lZCwgYW5kIGEgbmV3
IEhPU1QgY29tbWFuZCBNVVNUIGJlIGlzc3VlZCBpbiBvcmRlciB0byBjb25uZWN0DQogICB0byBh
IHZpcnR1YWwgaG9zdC4NCg0KDQoNCg0KSGV0aG1vbiAmIE1jTXVycmF5ICAgICAgRXhwaXJlcyBE
ZWNlbWJlciAzMSwgMjAxMSAgICAgICAgICAgICAgIFtQYWdlIDhdDQoMDQpJbnRlcm5ldC1EcmFm
dCAgICAgRlRQIEhPU1QgQ29tbWFuZCBmb3IgVmlydHVhbCBIb3N0cyAgICAgICAgICBKdW5lIDIw
MTENCg0KDQozLjIuMi4gIFVzZXItUEkgdXNhZ2Ugb2YgSE9TVA0KDQogICBBIHVzZXItUEkgdGhh
dCBjb25mb3JtcyB0byB0aGlzIHNwZWNpZmljYXRpb24gTVVTVCBzZW5kIHRoZSBIT1NUDQogICBj
b21tYW5kIGFmdGVyIG9wZW5pbmcgdGhlIHRyYW5zcG9ydCBjb25uZWN0aW9uLCBvciBhZnRlciBh
bnkgUkVJTg0KICAgY29tbWFuZCwgYmVmb3JlIGF0dGVtcHRpbmcgdG8gYXV0aGVudGljYXRlIHRo
ZSB1c2VyIHdpdGggdGhlIFVTRVINCiAgIGNvbW1hbmQuICBUaGUgZm9sbG93aW5nIGV4YW1wbGUg
aWxsdXN0cmF0ZXMgd2hhdCBhIHR5cGljYWwgbG9naW4NCiAgIHNlcXVlbmNlIG1pZ2h0IGxvb2sg
bGlrZSB3aGVuIHRoZSBIT1NUIGNvbW1hbmQgaXMgdXNlZDoNCg0KICAgICAgICBDPiBIT1NUIGZ0
cC5leGFtcGxlLmNvbQ0KICAgICAgICBTPiAyMjAgSG9zdCBhY2NlcHRlZA0KICAgICAgICBDPiBV
U0VSIGZvbw0KICAgICAgICBTPiAzMzEgUGFzc3dvcmQgcmVxdWlyZWQNCiAgICAgICAgQz4gUEFT
UyBiYXINCiAgICAgICAgUz4gMjMwIFVzZXIgbG9nZ2VkIGluDQoNCiAgIElmIGEgdXNlci1QSSBz
ZW5kcyBhbiBhZGRpdGlvbmFsIEhPU1QgY29tbWFuZCBiZWZvcmUgYXR0ZW1wdGluZyB0bw0KICAg
YXV0aGVudGljYXRlIHRoZSB1c2VyLCBhIHNlcnZlci1GVFAgcHJvY2VzcyB0aGF0IGNvbmZvcm1z
IHRvIHRoaXMNCiAgIHNwZWNpZmljYXRpb24gTVVTVCB0cmVhdCB0aGUgYWRkaXRpb25hbCBIT1NU
IGNvbW1hbmQgYXMgdGhvdWdoIGEgUkVJTg0KICAgY29tbWFuZCB3YXMgc2VudCwgYW5kIHJlc2V0
IHRoZSB1c2VyLVBJIHRvIHRoZSBzdGF0ZSB0aGF0IGV4aXN0ZWQNCiAgIGFmdGVyIHRoZSBUQ1Ag
Y29ubmVjdGlvbiB3YXMgZmlyc3QgZXN0YWJsaXNoZWQuICBGb3IgZXhhbXBsZSwgaWYgYQ0KICAg
dXNlciBzcGVjaWZpZXMgdGhlIHdyb25nIHZpcnR1YWwgaG9zdCBieSBtaXN0YWtlLCBzZW5kaW5n
IGENCiAgIHN1YnNlcXVlbnQgSE9TVCBjb21tYW5kIHdpbGwgcmVjdGlmeSB0aGUgZXJyb3IuICBU
aGUgZm9sbG93aW5nDQogICBleGFtcGxlIGlsbHVzdHJhdGVzIHdoYXQgdGhlIGxvZ2luIHNlcXVl
bmNlIG1pZ2h0IGxvb2sgbGlrZSB3aGVuIHRoZQ0KICAgSE9TVCBjb21tYW5kIGlzIHNlbnQgdHdp
Y2UgYmVmb3JlIGEgdXNlciBoYXMgYmVlbiBhdXRoZW50aWNhdGVkOg0KDQogICAgICAgIEM+IEhP
U1QgZm9vLmV4YW1wbGUuY29tDQogICAgICAgIFM+IDIyMCBIb3N0IGFjY2VwdGVkDQogICAgICAg
IEM+IEhPU1QgYmFyLmV4YW1wbGUuY29tDQogICAgICAgIFM+IDIyMCBIb3N0IGFjY2VwdGVkDQog
ICAgICAgIEM+IFVTRVIgZm9vDQogICAgICAgIFM+IDMzMSBQYXNzd29yZCByZXF1aXJlZA0KICAg
ICAgICBDPiBQQVNTIGJhcg0KICAgICAgICBTPiAyMzAgVXNlciBsb2dnZWQgaW4NCg0KICAgVGhl
IEhPU1QgY29tbWFuZCBjYW4gYmUgdXNlZCBpbiBjb21iaW5hdGlvbiB3aXRoIHRoZSBBQ0NUIGNv
bW1hbmQgdG8NCiAgIGRpZmZlcmVudGlhdGUgYmV0d2VlbiBhIHVzZXIncyB2YXJpb3VzIGFjY291
bnRzIG9uIGEgc3BlY2lmaWMgdmlydHVhbA0KICAgaG9zdC4gIEluIHRoaXMgc2NlbmFyaW8sIHRo
ZSB1c2VyLVBJIHNlbmRzIGEgSE9TVCBjb21tYW5kIHdoaWNoIHRoZQ0KICAgc2VydmVyLVBJIHVz
ZXMgdG8gcm91dGUgYWN0aXZpdHkgdG8gdGhlIGNvcnJlY3QgdmlydHVhbCBob3N0OyB0aGUNCiAg
IHVzZXItUEkgc2VuZHMgY3JlZGVudGlhbHMgdXNpbmcgdGhlIFVTRVIgYW5kIFBBU1MgY29tbWFu
ZHMgd2hpY2ggdGhlDQogICBzZXJ2ZXItUEkgdmFsaWRhdGVzOyB0aGVuLCB0aGUgdXNlci1QSSBz
ZW5kcyBhbiBBQ0NUIGNvbW1hbmQgdG8NCiAgIHNwZWNpZnkgYW55IGFkZGl0aW9uYWwgYWNjb3Vu
dCBpbmZvcm1hdGlvbiBmb3IgdGhlIHNlcnZlci1QSQ0KICAgaW1wbGVtZW50YXRpb24uICBUaGUg
Zm9sbG93aW5nIGV4YW1wbGUgaWxsdXN0cmF0ZXMgYSBzZXF1ZW50aWFsDQogICBzZXJpZXMgb2Yg
Y2xpZW50IGNvbW1hbmRzIHRoYXQgc3BlY2lmeSBib3RoIGEgSE9TVCBhbmQgQUNDVCwgd2l0aCB0
aGUNCiAgIHNlcnZlciByZXNwb25zZXMgb21pdHRlZCBmb3IgYnJldml0eToNCg0KDQoNCg0KDQoN
Cg0KSGV0aG1vbiAmIE1jTXVycmF5ICAgICAgRXhwaXJlcyBEZWNlbWJlciAzMSwgMjAxMSAgICAg
ICAgICAgICAgIFtQYWdlIDldDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgRlRQIEhPU1QgQ29tbWFu
ZCBmb3IgVmlydHVhbCBIb3N0cyAgICAgICAgICBKdW5lIDIwMTENCg0KDQogICAgICAgIEM+IEhP
U1QgZnRwLmV4YW1wbGUuY29tDQogICAgICAgIEM+IFVTRVIgZm9vDQogICAgICAgIEM+IFBBU1Mg
YmFyDQogICAgICAgIEM+IEFDQ1QgcHJvamVjdDENCg0KICAgVGhpcyBpcyBhbHNvIHRydWUgd2hl
biB0aGUgSE9TVCBjb21tYW5kIGlzIHVzZWQgd2l0aCB0aGUgQVVUSCBhbmQNCiAgIEFEQVQgY29t
bWFuZHMgdGhhdCBhcmUgZGlzY3Vzc2VkIGluIFtSRkMyMjI4XSBhbmQgW1JGQzQyMTddLiAgSW4g
dGhpcw0KICAgc2NlbmFyaW8sIHRoZSB1c2VyLVBJIHNlbmRzIGEgSE9TVCBjb21tYW5kIHdoaWNo
IHRoZSBzZXJ2ZXItUEkgdXNlcw0KICAgdG8gcm91dGUgYWN0aXZpdHkgdG8gdGhlIGNvcnJlY3Qg
dmlydHVhbCBob3N0LCB0aGVuIHRoZSB1c2VyLVBJIHVzZXMNCiAgIHRoZSBBVVRIIGFuZCBBREFU
IGNvbW1hbmRzIHRvIG5lZ290aWF0ZSB0aGUgc2VjdXJpdHkgbWVjaGFuaXNtIGFuZA0KICAgcmVs
ZXZhbnQgYXV0aGVudGljYXRpb24gdG9rZW4ocykgd2l0aCB0aGUgc2VydmVyLVBJLCB0aGVuIHRo
ZSB1c2VyLVBJDQogICBzZW5kcyB1c2VyIGNyZWRlbnRpYWxzIHVzaW5nIHRoZSBVU0VSIGFuZCBQ
QVNTIGNvbW1hbmRzIHdoaWNoIHRoZQ0KICAgc2VydmVyLVBJIHZhbGlkYXRlcy4gIEFmdGVyIHdo
aWNoIHRoZSB1c2VyLVBJIE1BWSBzZW5kIGFuIEFDQ1QNCiAgIGNvbW1hbmQgdG8gc3BlY2lmeSBh
bnkgYWRkaXRpb25hbCBhY2NvdW50IGluZm9ybWF0aW9uIGZvciB0aGUNCiAgIHNlcnZlci1QSSBp
bXBsZW1lbnRhdGlvbi4gIFRoZSBmb2xsb3dpbmcgZXhhbXBsZSBpbGx1c3RyYXRlcyBhDQogICBz
ZXF1ZW50aWFsIHNlcmllcyBvZiBjbGllbnQgY29tbWFuZHMgdGhhdCBzcGVjaWZ5IGJvdGggYSBI
T1NUIGFuZA0KICAgQUNDVCB3aGVuIHVzZWQgaW4gY29uanVuY3Rpb24gd2l0aCB0aGUgc2VjdXJp
dHkgY29tbWFuZHMgdGhhdCBhcmUNCiAgIGRpc2N1c3NlZCBpbiBbUkZDMjIyOF0gYW5kIFtSRkM0
MjE3XSwgd2l0aCB0aGUgc2VydmVyIHJlc3BvbnNlcw0KICAgb21pdHRlZCBmb3IgYnJldml0eToN
Cg0KICAgICAgICBDPiBIT1NUIGZ0cC5leGFtcGxlLmNvbQ0KICAgICAgICBDPiBBVVRIIDxtZWNo
YW5pc20tbmFtZT4NCiAgICAgICAgQz4gQURBVCA8YmFzZTY0ZGF0YT4NCiAgICAgICAgQz4gVVNF
UiBmb28NCiAgICAgICAgQz4gUEFTUyBiYXINCiAgICAgICAgQz4gQUNDVCBwcm9qZWN0MQ0KDQoz
LjIuMy4gIFN0YXRlIERpYWdyYW1zDQoNCiAgIFRoZSBzdGF0ZSBkaWFncmFtcyBpbiB0aGlzIHNl
Y3Rpb24gaWxsdXN0cmF0ZSB0eXBpY2FsIHNlcXVlbmNlcyBmb3INCiAgIGNvbW1hbmQgYW5kIHJl
cGx5IGludGVyY2hhbmdlIGJldHdlZW4gdGhlIHVzZXItUEkgYW5kIHNlcnZlci1QSS4NCiAgIFRo
ZXNlIGRpYWdyYW1zIGFyZSBtb2RlbGVkIG9uIHRoZSBzaW1pbGFyIGRpYWdyYW1zIGluIHNlY3Rp
b24gNiBvZg0KICAgW1JGQzA5NTldLg0KDQogICBJbiBlYWNoIGRpYWdyYW0sIHRoZSAoQikgImJl
Z2luIiBzdGF0ZSBpcyBhc3N1bWVkIHRvIG9jY3VyIGFmdGVyIHRoZQ0KICAgdHJhbnNwb3J0IGNv
bm5lY3Rpb24gaGFzIG9wZW5lZCwgb3IgYWZ0ZXIgYSBSRUlOIGNvbW1hbmQgaGFzDQogICBzdWNj
ZWVkZWQuICBPdGhlciBjb21tYW5kcyAoc3VjaCBhcyBGRUFUIFtSRkMyMzg5XSkgdGhhdCByZXF1
aXJlIG5vDQogICBhdXRoZW50aWNhdGlvbiBtYXkgaGF2ZSBpbnRlcnZlbmVkLg0KDQogICBBZGRp
dGlvbmFsbHksIGEgdGhyZWUtZGlnaXQgcmVwbHkgaW5kaWNhdGVzIGEgcHJlY2lzZSBzZXJ2ZXIg
cmVwbHkNCiAgIGNvZGUuICBBIHNpbmdsZSBkaWdpdCBvbiBhIHJlcGx5IHBhdGggaW5kaWNhdGVz
IGFueSBzZXJ2ZXIgcmVwbHkgdGhhdA0KICAgYmVnaW5zIHdpdGggdGhhdCBkaWdpdCwgZXhjZXB0
IHdoZXJlIGEgcHJlY2lzZSBzZXJ2ZXIgcmVwbHkgY29kZSBpcw0KICAgZGVmaW5lZCBvbiBhbm90
aGVyIHBhdGguICBGb3IgZXhhbXBsZSwgYSBzaW5nbGUgZGlnaXQgIjUiIHdpbGwgYXBwbHkNCiAg
IHRvICI1MDAiLCAiNTAxIiwgIjUwMiIsIGV0Yy4sIHdoZW4gdGhvc2UgcmVwbHkgY29kZXMgYXJl
IG5vdA0KICAgZXhwcmVzc2x5IGRlZmluZWQgaW4gdGhlIGRpYWdyYW0uICBGb3IgZWFjaCBjb21t
YW5kIHRoZXJlIGFyZSB0aHJlZQ0KICAgcG9zc2libGUgb3V0Y29tZXM6IHN1Y2Nlc3MgKFMpLCBm
YWlsdXJlIChGKSwgYW5kIGVycm9yIChFKS4gIEluIHRoZQ0KICAgc3RhdGUgZGlhZ3JhbXMgYmVs
b3cgd2UgdXNlIHRoZSBzeW1ib2wgQiBmb3IgImJlZ2luIiwgYW5kIHRoZSBzeW1ib2wNCiAgIFcg
Zm9yICJ3YWl0IGZvciByZXBseSIuDQoNCg0KDQpIZXRobW9uICYgTWNNdXJyYXkgICAgICBFeHBp
cmVzIERlY2VtYmVyIDMxLCAyMDExICAgICAgICAgICAgICBbUGFnZSAxMF0NCgwNCkludGVybmV0
LURyYWZ0ICAgICBGVFAgSE9TVCBDb21tYW5kIGZvciBWaXJ0dWFsIEhvc3RzICAgICAgICAgIEp1
bmUgMjAxMQ0KDQoNCiAgIEluIGVhY2ggb2YgdGhlc2UgZGlhZ3JhbXMsIGEgUkVJTiBjb21tYW5k
IHdpbGwgcmV0dXJuIHRoZSBkaWFncmFtIHRvDQogICB0aGUgKEIpICJiZWdpbiIgc3RhdGUuDQoN
CiAgIFRoZSBzdGF0ZSBkaWFncmFtIGluIEZpZ3VyZSAxIHNob3dzIGEgdHlwaWNhbCBzZXF1ZW5j
ZSBvZiBmbG93IG9mDQogICBjb250cm9sIHdoZW4gSE9TVCBpcyB1c2VkIHdpdGggVVNFUiBhbmQg
UEFTUyB0byBsb2cgaW4gdG8gYQ0KICAgcGFydGljdWxhciBGVFAgdmlydHVhbCBob3N0Lg0KDQog
ICAgICAgICAgICAgICstLS0rICAgSE9TVCAgICArLS0tKyAxLDMsNQ0KICAgICAgICAgICAgICB8
IEIgfC0tLS0tLS0tLS0+fCBXIHwtLS0tLS0tLS0tLS0tLS0tLQ0KICAgICAgICAgICAgICArLS0t
KyAgICAgICAgICAgKy0tLSsgICAgICAgICAgICAgICAgIHwNCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICB8IHwgICAgICAgICAgICAgICAgICB8DQogICAgICAgICAgICAgICAgICAgICAy
LDUwMCw1MDIgfCB8IDQsNTAxLDUwMyw1MDQgICAgfA0KICAgICAgICAgICAgICAgICAtLS0tLS0t
LS0tLS0tLSAgIC0tLS0tLS0tLS0tICAgICAgIHwNCiAgICAgICAgICAgICAgICB8ICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIHwgICAgICBWDQogICAgICAgICAgICAgICAgViAgICAgICAgICAg
ICAgICAgICAxICAgICAgICB8ICAgICstLS0rDQogICAgICAgICAgICAgICstLS0rICAgVVNFUiAg
ICArLS0tKy0tLS0tLS0tLS0tLS0tPnwgRSB8DQogICAgICAgICAgICAgIHwgICB8LS0tLS0tLS0t
LT58IFcgfCAyICAgICAgICB8ICAgICstLS0rDQogICAgICAgICAgICAgICstLS0rICAgICAgICAg
ICArLS0tKy0tLS0tLS0gICB8ICAgICAgXg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IHwgfCAgICAgICAgfCAgfCAgICAgIHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMyB8
IHwgNCw1ICAgIHwgIHwgICAgICB8DQogICAgICAgICAgICAgICAgIC0tLS0tLS0tLS0tLS0tICAg
LS0tLS0gICB8ICB8ICAgICAgfA0KICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAg
ICAgfCAgfCAgfCAgICAgIHwNCiAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIC0tLS0t
LS0tLS0tLS0tLS0tLS0NCiAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAxfCAgICAgIHwg
IHwgIHwNCiAgICAgICAgICAgICAgICBWICAgICAgICAgICAgICAgfCAgICAgIHwgICAtLS0tLS0+
Ky0tLSsNCiAgICAgICAgICAgICAgKy0tLSsgICBQQVNTICAgICstLS0rIDIgIHwgICAgIHwgICAg
fCBTIHwNCiAgICAgICAgICAgICAgfCAgIHwtLS0tLS0tLS0tPnwgVyB8LS0tLS0tLS0tLS0tLS0+
Ky0tLSsNCiAgICAgICAgICAgICAgKy0tLSsgICAgICAgICAgICstLS0rICAgIHwgICAgIHwNCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgIHwgICAgIHwNCiAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgfDQsNSAgIHwgICAgIHwNCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgfCAgICAgIHwgICAgICAtLS0+Ky0tLSsNCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgfCAgICAgICAtLS0tLS0tLS0+fCBGIHwNCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIC0tLS0tLS0tLS0tLS0tLS0+Ky0tLSsNCg0KICAgICAgICAgICAgRmlndXJl
IDE6IFR5cGljYWwgbG9naW4gc2VxdWVuY2Ugd2l0aCBIT1NUIGNvbW1hbmQNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KSGV0aG1vbiAmIE1jTXVycmF5ICAgICAgRXhwaXJlcyBEZWNl
bWJlciAzMSwgMjAxMSAgICAgICAgICAgICAgW1BhZ2UgMTFdDQoMDQpJbnRlcm5ldC1EcmFmdCAg
ICAgRlRQIEhPU1QgQ29tbWFuZCBmb3IgVmlydHVhbCBIb3N0cyAgICAgICAgICBKdW5lIDIwMTEN
Cg0KDQogICBUaGUgc3RhdGUgZGlhZ3JhbSBpbiBGaWd1cmUgMiBzaG93cyB0aGUgZmxvdyBvZiBj
b250cm9sIHdoZW4gYSBIT1NUDQogICBjb21tYW5kIGlzIHNlbnQgYWZ0ZXIgYSB1c2VyIGhhcyBh
bHJlYWR5IHN1Y2Nlc3NmdWxseSBsb2dnZWQgaW4gdG8gYQ0KICAgdmlydHVhbCBob3N0IHdpdGgg
VVNFUiBhbmQgUEFTUy4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8DQogICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8DQogICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIFYgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8DQogICAg
ICAgICAgICAgICstLS0rICAgSE9TVCAgICArLS0tKyAxLDMsNSAgICAgICAgICAgICAgICAgICAg
ICB8DQogICAgICAgICAgICAgIHwgQiB8LS0tLS0tLS0tLT58IFcgfC0tLS0tLS0tLS0tLS0tLS0t
ICAgICAgICAgICB8DQogICAgICAgICAgICAgICstLS0rICAgICAgICAgICArLS0tKyAgICAgICAg
ICAgICAgICAgfCAgICAgICAgICB8DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCB8
ICAgICAgICAgICAgICAgICAgfCAgICAgICAgICB8DQogICAgICAgICAgICAgICAgICAgICAyLDUw
MCw1MDIgfCB8IDQsNTAxLDUwMyw1MDQgICAgfCAgICAgICAgICB8DQogICAgICAgICAgICAgICAg
IC0tLS0tLS0tLS0tLS0tICAgLS0tLS0tLS0tLS0gICAgICAgfCAgICAgICAgICB8DQogICAgICAg
ICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgICAgViAgICAgICAgICB8
DQogICAgICAgICAgICAgICAgViAgICAgICAgICAgICAgICAgICAxICAgICAgICB8ICAgICstLS0r
ICAgICAgICB8DQogICAgICAgICAgICAgICstLS0rICAgVVNFUiAgICArLS0tKy0tLS0tLS0tLS0t
LS0tPnwgRSB8ICAgICAgICB8DQogICAgICAgICAgICAgIHwgICB8LS0tLS0tLS0tLT58IFcgfCAy
ICAgICAgICB8ICAgICstLS0rICAgICAgICB8DQogICAgICAgICAgICAgICstLS0rICAgICAgICAg
ICArLS0tKy0tLS0tLS0gICB8ICAgICAgXiAgICAgICAgICB8DQogICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgfCB8ICAgICAgICB8ICB8ICAgICAgfCAgICAgICAgICB8DQogICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIDMgfCB8IDQsNSAgICB8ICB8ICAgICAgfCAgICAgICAgICB8DQog
ICAgICAgICAgICAgICAgIC0tLS0tLS0tLS0tLS0tICAgLS0tLS0tICB8ICB8ICAgICAgfCAgICAg
ICAgICB8DQogICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICB8ICB8ICB8ICAg
ICAgfCAgICAgICAgICB8DQogICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAtLS0tLS0t
LS0tLS0tLS0tLS0tICAgICAgICAgICB8DQogICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAg
MXwgICAgICB8ICB8ICB8ICAgICAgICAgICAgICAgICB8DQogICAgICAgICAgICAgICAgViAgICAg
ICAgICAgICAgIHwgICAgICB8ICAgLS0tLS0tPistLS0rICBIT1NUICB8DQogICAgICAgICAgICAg
ICstLS0rICAgUEFTUyAgICArLS0tKyAyICB8ICAgICB8ICAgIHwgUyB8LS0tLS0tLS0NCiAgICAg
ICAgICAgICAgfCAgIHwtLS0tLS0tLS0tPnwgVyB8LS0tLS0tLS0tLS0tLS0+Ky0tLSsNCiAgICAg
ICAgICAgICAgKy0tLSsgICAgICAgICAgICstLS0rICAgIHwgICAgIHwNCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgfCAgICAgIHwgICAgIHwNCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgfDQsNSAgIHwgICAgIHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
fCAgICAgIHwgICAgICAtLS0+Ky0tLSsNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
fCAgICAgICAtLS0tLS0tLS0+fCBGIHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IC0tLS0tLS0tLS0tLS0tLS0+Ky0tLSsNCg0KICAgICAgICAgICAgRmlndXJlIDI6IExvZ2luIHNl
cXVlbmNlIHdpdGggcmVwZWF0ZWQgSE9TVCBjb21tYW5kDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQpIZXRobW9uICYgTWNNdXJyYXkgICAgICBFeHBpcmVzIERlY2VtYmVyIDMxLCAyMDEx
ICAgICAgICAgICAgICBbUGFnZSAxMl0NCgwNCkludGVybmV0LURyYWZ0ICAgICBGVFAgSE9TVCBD
b21tYW5kIGZvciBWaXJ0dWFsIEhvc3RzICAgICAgICAgIEp1bmUgMjAxMQ0KDQoNCiAgIEFmdGVy
IGEgdXNlciBoYXMgbG9nZ2VkIGluLCBhbiBhZGRpdGlvbmFsIGFjY291bnQgbWF5IGJlIHJlcXVp
cmVkIGJ5DQogICB0aGUgc2VydmVyIGFuZCBzcGVjaWZpZWQgYnkgdGhlIGNsaWVudCBieSB1c2lu
ZyBBQ0NUIGNvbW1hbmQuICBXaXRoDQogICB0aGlzIGluIG1pbmQsIHRoZSBzdGF0ZSBkaWFncmFt
IGluIEZpZ3VyZSAzIHNob3dzIGEgdHlwaWNhbCBzZXF1ZW5jZQ0KICAgb2YgZmxvdyBvZiBjb250
cm9sIHdoZW4gSE9TVCBpcyB1c2VkIHdpdGggVVNFUiBhbmQgUEFTUyB0byBsb2cgaW4gdG8NCiAg
IGFuIEZUUCB2aXJ0dWFsIGhvc3QgYW5kIEFDQ1QgaXMgdXNlZCB0byBzcGVjaWZ5IGFuIGFjY291
bnQuDQoNCiAgICAgICAgICAgICAgKy0tLSsgICBIT1NUICAgICstLS0rIDEsMyw1DQogICAgICAg
ICAgICAgIHwgQiB8LS0tLS0tLS0tLT58IFcgfC0tLS0tLS0tLS0tLS0tLS0tDQogICAgICAgICAg
ICAgICstLS0rICAgICAgICAgICArLS0tKyAgICAgICAgICAgICAgICAgfA0KICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIHwgfCAgICAgICAgICAgICAgICAgIHwNCiAgICAgICAgICAgICAg
ICAgICAgIDIsNTAwLDUwMiB8IHwgNCw1MDEsNTAzLDUwNCAgICB8DQogICAgICAgICAgICAgICAg
IC0tLS0tLS0tLS0tLS0tICAgLS0tLS0tLS0tLS0tLSAgICAgfA0KICAgICAgICAgICAgICAgIHwg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgIHwNCiAgICAgICAgICAgICAgICBWICAg
ICAgICAgICAgICAgICAgIDEgICAgICAgICAgfCAgICBWDQogICAgICAgICAgICAgICstLS0rICAg
VVNFUiAgICArLS0tKy0tLS0tLS0tLS0tLS0tPistLS0rDQogICAgICAgICAgICAgIHwgICB8LS0t
LS0tLS0tLT58IFcgfCAyICAgICAgIC0tLS0tPnwgRSB8DQogICAgICAgICAgICAgICstLS0rICAg
ICAgICAgICArLS0tKy0tLS0tLSAgfCAgLS0tPistLS0rDQogICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgfCB8ICAgICAgIHwgfCB8IHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
MyB8IHwgNCw1ICAgfCB8IHwgfA0KICAgICAgICAgICAgICAgICAtLS0tLS0tLS0tLS0tLSAgIC0t
LS0tICB8IHwgfCB8DQogICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICB8IHwg
fCB8IHwNCiAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgIHwgfCB8IHwgfA0K
ICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgLS0tLS0tLS0tLSAgfCB8DQogICAgICAg
ICAgICAgICAgfCAgICAgICAgICAgICAgMXwgICAgICB8IHwgICB8IHwNCiAgICAgICAgICAgICAg
ICBWICAgICAgICAgICAgICAgfCAgICAgIHwgfCAgIHwgfA0KICAgICAgICAgICAgICArLS0tKyAg
IFBBU1MgICAgKy0tLSsgMiAgfCAgLS0tLS0tLT4rLS0tKw0KICAgICAgICAgICAgICB8ICAgfC0t
LS0tLS0tLS0+fCBXIHwtLS0tLS0tLS0tLS0tLT58IFMgfA0KICAgICAgICAgICAgICArLS0tKyAg
ICAgICAgICAgKy0tLSsgICAtLS0tLS0tLS0tLT4rLS0tKw0KICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIHwgfCAgIHwgfCAgICAgfCB8DQogICAgICAgICAgICAgICAgICAgICAgICAgICAg
IDMgfCB8NCw1fCB8ICAgICB8IHwNCiAgICAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0gICAt
LS0tLS0tLSAgIHwgIC0tLS0NCiAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICB8
IHwgIHwgIHwgICAgICB8DQogICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgfCB8
ICB8ICB8ICAgICAgfA0KICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgLS0tLS0tLS0t
LS0tICAgICAgIHwNCiAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgMSwzfCAgICB8IHwgIHwg
ICAgICAgICB8DQogICAgICAgICAgICAgICAgViAgICAgICAgICAgICAgIHwgICAyfCB8ICB8ICAg
ICAgICAgVg0KICAgICAgICAgICAgICArLS0tKyAgIEFDQ1QgICAgKy0tLSstLSAgfCAgIC0tLS0t
LT4rLS0tKw0KICAgICAgICAgICAgICB8ICAgfC0tLS0tLS0tLS0+fCBXIHwgNCw1IC0tLS0tLS0t
LT58IEYgfA0KICAgICAgICAgICAgICArLS0tKyAgICAgICAgICAgKy0tLSstLS0tLS0tLS0tLS0t
LT4rLS0tKw0KDQogICAgICAgICAgIEZpZ3VyZSAzOiBMb2dpbiBzZXF1ZW5jZSB3aXRoIEhPU1Qg
YW5kIEFDQ1QgY29tbWFuZHMNCg0KDQoNCg0KDQoNCg0KDQoNCg0KSGV0aG1vbiAmIE1jTXVycmF5
ICAgICAgRXhwaXJlcyBEZWNlbWJlciAzMSwgMjAxMSAgICAgICAgICAgICAgW1BhZ2UgMTNdDQoM
DQpJbnRlcm5ldC1EcmFmdCAgICAgRlRQIEhPU1QgQ29tbWFuZCBmb3IgVmlydHVhbCBIb3N0cyAg
ICAgICAgICBKdW5lIDIwMTENCg0KDQogICBXaGVuIHRoZSBIT1NUIGNvbW1hbmQgaXMgdXNlZCBp
biBjb21iaW5hdGlvbiB3aXRoIHRoZSBGVFAgc2VjdXJpdHkNCiAgIGV4dGVuc2lvbnMgdGhhdCB3
ZXJlIGludHJvZHVjZWQgaW4gW1JGQzIyMjhdLCBpdCBTSE9VTEQgcHJlY2VkZSB0aGUNCiAgIHNl
Y3VyaXR5IGhhbmRzaGFrZS4gIFRoaXMgYWxsb3dzIGJvdGggdXNlci1QSSBhbmQgc2VydmVyLUZU
UA0KICAgcHJvY2Vzc2VzIHRvIG1hcCBhbiBGVFAgSE9TVCB0byBzZWN1cml0eSBkYXRhIGFwcHJv
cHJpYXRlbHkuICBUaGUNCiAgIHN0YXRlIGRpYWdyYW0gaW4gRmlndXJlIDQgc2hvd3MgYSB0eXBp
Y2FsIHNlcXVlbmNlIG9mIGZsb3cgb2YgY29udHJvbA0KICAgd2hlbiBIT1NUIGlzIHVzZWQgd2l0
aCB0aGUgQVVUSCBhbmQgQURBVCBjb21tYW5kcyB0aGF0IGFyZSBkaXNjdXNzZWQNCiAgIGluIFtS
RkMyMjI4XS4NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpIZXRobW9uICYgTWNNdXJy
YXkgICAgICBFeHBpcmVzIERlY2VtYmVyIDMxLCAyMDExICAgICAgICAgICAgICBbUGFnZSAxNF0N
CgwNCkludGVybmV0LURyYWZ0ICAgICBGVFAgSE9TVCBDb21tYW5kIGZvciBWaXJ0dWFsIEhvc3Rz
ICAgICAgICAgIEp1bmUgMjAxMQ0KDQoNCiAgICAgICAgICAgICAgKy0tLSsgICBIT1NUICAgICst
LS0rIDEsMyw1DQogICAgICAgICAgICAgIHwgQiB8LS0tLS0tLS0tLT58IFcgfC0tLS0tLS0tLS0t
LS0tLS0tLQ0KICAgICAgICAgICAgICArLS0tKyAgICAgICAgICAgKy0tLSsgICAgICAgICAgICAg
ICAgICB8DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCB8ICAgICAgICAgICAgICAg
ICAgIHwNCiAgICAgICAgICAgICAgICAgICAgIDIsNTAwLDUwMiB8IHwgNCw1MDEsNTAzLDUwNCAg
ICAgfA0KICAgICAgICAgICAgICAgICAtLS0tLS0tLS0tLS0tLSAgIC0tLS0tLS0tLS0tLS0gICAg
ICB8DQogICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICAg
IHwNCiAgICAgICAgICAgICAgICBWICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAg
fA0KICAgICAgICAgICAgICArLS0tKyAgIEFVVEggICAgKy0tLSsgNCw1ICAgICAgICB8ICAgICB8
DQogICAgICAgICAgICAgIHwgICB8LS0tLS0tLS0tLT58IFcgfC0tLS0tLS0tLS0tPnwgICAgIHwN
CiAgICAgICAgICAgICAgKy0tLSsgICAgICAgICAgICstLS0rICAgICAgICAgICAgfCAgICAgfA0K
ICAgICAgICAgICAgICAgICAgICAgICAgICAgMzM0IHwgfCAgICAgICAgICAgICB8ICAgICB8DQog
ICAgICAgICAgICAgICAgIC0tLS0tLS0tLS0tLS0tICB8ICAgICAgICAgICAgIHwgICAgIHwNCiAg
ICAgICAgICAgICAgICB8ICAgICAgICAgICAgMjM0IHwgICAgICAgICAgICAgfCAgICAgfA0KICAg
ICAgICAgICAgICAgIHwgICAgLS0tLS0tLS0tLS0tICAgICAgICAgICAgICB8ICAgICB8DQogICAg
ICAgICAgICAgICAgViAgIHwgICAgICAgICAgICAgICA0LDUgICAgICAgIHwgICAgIHwNCiAgICAg
ICAgICAgICAgKy0tLSsgfCBBREFUICAgICstLS0rLS0tLS0tLS0tLS0+fCAgICAgfA0KICAgICAg
ICAgICAgICB8ICAgfC0tLS0tLS0tLS0+fCBXIHwgMzM1ICAgICAgICB8ICAgICB8DQogICAgICAg
ICAgICAgICstLS0rIHwgICAgICAgICArLS0tKy0tLS0tICAgICAgIHwgICAgIHwNCiAgICAgICAg
ICAgICAgICBeICAgfCAgICAgICAgICAgfCAgICAgICB8ICAgICAgfCAgICAgfA0KICAgICAgICAg
ICAgICAgIHwgICB8ICAgICAgICAgICB8ICAgICAgIHwgICAgICB8ICAgICB8DQogICAgICAgICAg
ICAgICAgIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tICAgICAgIHwgICAgIHwNCiAgICAgICAgICAg
ICAgICAgICAgfCAgICAgICAgICAgfCAgICAgICAgICAgICAgfCAgICAgfA0KICAgICAgICAgICAg
ICAgIC0tLS0gICAgICAgIDIzNSB8ICAgICAgICAgICAgICB8ICAgICB8DQogICAgICAgICAgICAg
ICB8ICAtLS0tLS0tLS0tLS0tLSAgICAgICAgICAgICAgIHwgICAgIHwNCiAgICAgICAgICAgICAg
IHwgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgVg0KICAgICAgICAgICAgICAg
ViBWICAgICAgICAgICAgICAgICAgMSAgICAgICAgICB8ICAgKy0tLSsNCiAgICAgICAgICAgICAg
Ky0tLSsgICBVU0VSICAgICstLS0rLS0tLS0tLS0tLS0tLS0tPnwgRSB8DQogICAgICAgICAgICAg
IHwgICB8LS0tLS0tLS0tLT58IFcgfCAyICAgICAgICAgIHwgICArLS0tKw0KICAgICAgICAgICAg
ICArLS0tKyAgICAgICAgICAgKy0tLSstLS0tLS0tICAgICB8ICAgICBeDQogICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgfCB8ICAgICAgICB8ICAgIHwgICAgIHwNCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgMyB8IHwgNCw1ICAgIHwgICAgfCAgICAgfA0KICAgICAgICAgICAgICAg
ICAtLS0tLS0tLS0tLS0tLSAgIC0tLS0tLSAgfCAgICB8ICAgICB8DQogICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgICAgICAgfCB8ICAgIHwgICAgIHwNCiAgICAgICAgICAgICAgICB8
ICAgICAgICAgICAgICAgIC0tLS0tLS0tLS0tLS0tLS0tLS0tDQogICAgICAgICAgICAgICAgfCAg
ICAgICAgICAgICAgMXwgICAgICAgfCB8ICAgIHwNCiAgICAgICAgICAgICAgICBWICAgICAgICAg
ICAgICAgfCAgICAgICB8ICAtLS0tLS0tPistLS0rDQogICAgICAgICAgICAgICstLS0rICAgUEFT
UyAgICArLS0tKyAyICAgfCAgICAgIHwgICB8IFMgfA0KICAgICAgICAgICAgICB8ICAgfC0tLS0t
LS0tLS0+fCBXIHwtLS0tLS0tLS0tLS0tLS0+Ky0tLSsNCiAgICAgICAgICAgICAgKy0tLSsgICAg
ICAgICAgICstLS0rICAgICB8ICAgICAgfA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICB8ICAgICAgIHwgICAgICB8DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHw0LDUg
ICAgfCAgICAgIHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgICB8ICAg
ICAgIC0tPistLS0rDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICAgICAgIC0t
LS0tLS0tLT58IEYgfA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgLS0tLS0tLS0t
LS0tLS0tLS0+Ky0tLSsNCg0KICAgICAgICAgRmlndXJlIDQ6IExvZ2luIHNlcXVlbmNlIHdpdGgg
SE9TVCBhbmQgQVVUSC9BREFUIGNvbW1hbmRzDQoNCg0KDQoNCkhldGhtb24gJiBNY011cnJheSAg
ICAgIEV4cGlyZXMgRGVjZW1iZXIgMzEsIDIwMTEgICAgICAgICAgICAgIFtQYWdlIDE1XQ0KDA0K
SW50ZXJuZXQtRHJhZnQgICAgIEZUUCBIT1NUIENvbW1hbmQgZm9yIFZpcnR1YWwgSG9zdHMgICAg
ICAgICAgSnVuZSAyMDExDQoNCg0KICAgQWZ0ZXIgYSB1c2VyIGhhcyBsb2dnZWQgaW4gd2l0aCB0
aGUgc2VjdXJpdHkgY29tbWFuZHMgdGhhdCBhcmUNCiAgIGRpc2N1c3NlZCBpbiBbUkZDMjIyOF0s
IGFuIGFkZGl0aW9uYWwgYWNjb3VudCBtYXkgYmUgcmVxdWlyZWQgYnkgdGhlDQogICBzZXJ2ZXIg
YW5kIHNwZWNpZmllZCBieSB0aGUgY2xpZW50IGJ5IHVzaW5nIEFDQ1QgY29tbWFuZC4gIFRoZSBz
dGF0ZQ0KICAgZGlhZ3JhbSBpbiBGaWd1cmUgNSBzaG93cyBhIHR5cGljYWwgc2VxdWVuY2Ugb2Yg
ZmxvdyBvZiBjb250cm9sIHdoZW4NCiAgIEhPU1QgaXMgdXNlZCB3aXRoIHRoZSBBVVRIIGFuZCBB
REFUIGNvbW1hbmRzIHRvIGxvZyBpbiB0byBhbiBGVFANCiAgIHZpcnR1YWwgaG9zdCBhbmQgQUND
VCBpcyB1c2VkIHRvIHNwZWNpZnkgYW4gYWNjb3VudC4NCg0KICAgICAgICAgICAgICArLS0tKyAg
IEhPU1QgICAgKy0tLSsgMSwzLDUNCiAgICAgICAgICAgICAgfCBCIHwtLS0tLS0tLS0tPnwgVyB8
LS0tLS0tLS0tLS0tLS0tLS0tDQogICAgICAgICAgICAgICstLS0rICAgICAgICAgICArLS0tKyAg
ICAgICAgICAgICAgICAgIHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IHwgICAg
ICAgICAgICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAgICAgMiw1MDAsNTAyIHwgfCA0LDUw
MSw1MDMsNTA0ICAgICB8DQogICAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tICAgLS0tLS0t
LS0tLS0tLS0gICAgIHwNCiAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIHwgICAgfA0KICAgICAgICAgICAgICAgIFYgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgfCAgICB8DQogICAgICAgICAgICAgICstLS0rICAgQVVUSCAgICArLS0tKyA0LDUgICAg
ICAgICB8ICAgIHwNCiAgICAgICAgICAgICAgfCAgIHwtLS0tLS0tLS0tPnwgVyB8LS0tLS0tLS0t
LS0tPnwgICAgfA0KICAgICAgICAgICAgICArLS0tKyAgICAgICAgICAgKy0tLSsgICAgICAgICAg
ICAgfCAgICB8DQogICAgICAgICAgICAgICAgICAgICAgICAgICAzMzQgfCB8ICAgICAgICAgICAg
ICB8ICAgIHwNCiAgICAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0gIHwgICAgICAgICAgICAg
IHwgICAgfA0KICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAyMzQgfCAgICAgICAgICAgICAg
fCAgICB8DQogICAgICAgICAgICAgICAgfCAgICAtLS0tLS0tLS0tLS0gICAgICAgICAgICAgICB8
ICAgIHwNCiAgICAgICAgICAgICAgICBWICAgfCAgICAgICAgICAgICAgIDQsNSAgICAgICAgIHwg
ICAgfA0KICAgICAgICAgICAgICArLS0tKyB8IEFEQVQgICAgKy0tLSstLS0tLS0tLS0tLS0+fCAg
ICB8DQogICAgICAgICAgICAgIHwgICB8LS0tLS0tLS0tLT58IFcgfCAzMzUgICAgICAgICB8ICAg
IHwNCiAgICAgICAgICAgICAgKy0tLSsgfCAgICAgICAgICstLS0rLS0tLS0gICAgICAgIHwgICAg
fA0KICAgICAgICAgICAgICAgIF4gICB8ICAgICAgICAgICB8ICAgICAgIHwgICAgICAgfCAgICB8
DQogICAgICAgICAgICAgICAgfCAgIHwgICAgICAgICAgIHwgICAgICAgfCAgICAgICB8ICAgIHwN
CiAgICAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gICAgICAgIHwgICAgfA0K
ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICB8ICAgICAgICAgICAgICAgfCAgICB8DQog
ICAgICAgICAgICAgICAgLS0tLSAgICAgICAgIDIzNXwgICAgICAgICAgICAgICB8ICAgIHwNCiAg
ICAgICAgICAgICAgIHwgIC0tLS0tLS0tLS0tLS0tICAgICAgICAgICAgICAgIHwgICAgfA0KICAg
ICAgICAgICAgICAgfCB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICB8DQogICAg
ICAgICAgICAgICBWIFYgICAgICAgICAgICAgICAgICAxICAgICAgICAgICB8ICAgIFYNCiAgICAg
ICAgICAgICAgKy0tLSsgICBVU0VSICAgICstLS0rLS0tLS0tLS0tLS0tLS0tPistLS0rDQogICAg
ICAgICAgICAgIHwgICB8LS0tLS0tLS0tLT58IFcgfCAyICAgICAgICAtLS0tLT58IEUgfA0KICAg
ICAgICAgICAgICArLS0tKyAgICAgICAgICAgKy0tLSstLS0tLS0tICB8ICAtLS0+Ky0tLSsNCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IHwgICAgICAgIHwgfCB8IHwNCiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgMyB8IHwgNCw1ICAgIHwgfCB8IHwNCiAgICAgICAgICAgICAg
ICAgLS0tLS0tLS0tLS0tLS0gICAtLS0tLS0gIHwgfCB8IHwNCiAgICAgICAgICAgICAgICB8ICAg
ICAgICAgICAgICAgICAgICAgICB8IHwgfCB8IHwNCiAgICAgICAgICAgICAgICB8ICAgICAgICAg
ICAgICAgIC0tLS0tLS0tLS0tICB8IHwNCiAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAx
fCAgICAgICB8IHwgICB8IHwNCiAgICAgICAgICAgICAgICBWICAgICAgICAgICAgICAgfCAgICAg
ICB8IHwgICB8IHwNCiAgICAgICAgICAgICAgKy0tLSsgICBQQVNTICAgICstLS0rIDIgICB8ICAt
LS0tLS0tPistLS0rDQogICAgICAgICAgICAgIHwgICB8LS0tLS0tLS0tLT58IFcgfC0tLS0tLS0t
LS0tLS0tLT58IFMgfA0KICAgICAgICAgICAgICArLS0tKyAgICAgICAgICAgKy0tLSsgICAtLS0t
LS0tLS0tLS0+Ky0tLSsNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IHwgICB8ICB8
ICAgICB8IHwNCg0KDQoNCkhldGhtb24gJiBNY011cnJheSAgICAgIEV4cGlyZXMgRGVjZW1iZXIg
MzEsIDIwMTEgICAgICAgICAgICAgIFtQYWdlIDE2XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgIEZU
UCBIT1NUIENvbW1hbmQgZm9yIFZpcnR1YWwgSG9zdHMgICAgICAgICAgSnVuZSAyMDExDQoNCg0K
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAzIHwgfDQsNXwgIHwgICAgIHwgfA0KICAgICAg
ICAgICAgICAgICAtLS0tLS0tLS0tLS0tLSAgIC0tLS0tLS0tLSAgIHwgIC0tLS0NCiAgICAgICAg
ICAgICAgICB8ICAgICAgICAgICAgICAgICAgICB8ICB8ICB8ICB8ICAgICAgfA0KICAgICAgICAg
ICAgICAgIHwgICAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLSAgICAgICB8DQogICAgICAgICAg
ICAgICAgfCAgICAgICAgICAgIDEsM3wgICAgfCAgfCAgfCAgICAgICAgIHwNCiAgICAgICAgICAg
ICAgICBWICAgICAgICAgICAgICAgfCAgIDJ8ICB8ICB8ICAgICAgICAgVg0KICAgICAgICAgICAg
ICArLS0tKyAgIEFDQ1QgICAgKy0tLSstLSAgIHwgICAtLS0tLS0+Ky0tLSsNCiAgICAgICAgICAg
ICAgfCAgIHwtLS0tLS0tLS0tPnwgVyB8IDQsNSAgLS0tLS0tLS0tPnwgRiB8DQogICAgICAgICAg
ICAgICstLS0rICAgICAgICAgICArLS0tKy0tLS0tLS0tLS0tLS0tLT4rLS0tKw0KDQogICAgICBG
aWd1cmUgNTogTG9naW4gc2VxdWVuY2Ugd2l0aCBIT1NUIGFuZCBBVVRIL0FEQVQvQUNDVCBjb21t
YW5kcw0KDQozLjMuICBIT1NUIGNvbW1hbmQgZXJyb3JzDQoNCiAgIFRoZSBzZXJ2ZXItUEkgU0hP
VUxEIHJlcGx5IHdpdGggYSA1MDAgb3IgNTAyIHJlcGx5IGlmIHRoZSBIT1NUDQogICBjb21tYW5k
IGlzIHVucmVjb2duaXplZCBvciB1bmltcGxlbWVudGVkLg0KDQogICBBcyBkaXNjdXNzZWQgaW4g
c2VjdGlvbiAzIG9mIHRoaXMgZG9jdW1lbnQsIGlmIGEgSE9TVCBjb21tYW5kIGlzIHNlbnQNCiAg
IGFmdGVyIGEgdXNlciBoYXMgYmVlbiBhdXRoZW50aWNhdGVkIHRoZSBzZXJ2ZXIgU0hPVUxEIGRv
IG9uZSBvZiB0aGUNCiAgIGZvbGxvd2luZzoNCg0KICAgYS4gIFNlbmQgYSA1MDMgcmVwbHkgZm9y
IGFuIGludmFsaWQgc2VxdWVuY2Ugb2YgY29tbWFuZHMuDQoNCiAgIGIuICBUcmVhdCB0aGUgSE9T
VCBjb21tYW5kIGFzIHRob3VnaCBhIFJFSU4gY29tbWFuZCB3YXMgc2VudCBhbmQNCiAgICAgICBy
ZXNldCB0aGUgdXNlci1QSSB0byB0aGUgc3RhdGUgdGhhdCBleGlzdGVkIGFmdGVyIHRoZSBwcmV2
aW91cw0KICAgICAgIEhPU1QgY29tbWFuZCB3YXMgc2VudCBhbmQgYmVmb3JlIHRoZSB1c2VyIGhh
ZCBiZWVuIGF1dGhlbnRpY2F0ZWQsDQogICAgICAgYW5kIHRoZW4gcmV0dXJuIHRoZSBhcHByb3By
aWF0ZSByZXBseSBmb3IgdGhlIEhPU1QgY29tbWFuZC4NCg0KICAgQSA1MDEgcmVwbHkgU0hPVUxE
IGJlIHNlbnQgaWYgdGhlIGhvc3RuYW1lIGdpdmVuIGlzIHN5bnRhY3RpY2FsbHkNCiAgIGludmFs
aWQsIGFuZCBhIDUwNCByZXBseSBTSE9VTEQgYmUgc2VudCBpZiBhIHN5bnRhY3RpY2FsbHkgdmFs
aWQNCiAgIGhvc3RuYW1lIGlzIG5vdCBhIHZhbGlkIHZpcnR1YWwgaG9zdCBuYW1lIGZvciB0aGUg
c2VydmVyLiAgSW4gYWxsDQogICBzdWNoIGNhc2VzLCB0aGUgc2VydmVyLUZUUCBwcm9jZXNzIE1V
U1QgZG8gb25lIG9mIHRoZSBmb2xsb3dpbmc6DQoNCiAgIGEuICBJZ25vcmUgdGhlIEhPU1QgY29t
bWFuZCBhbmQgYWN0IGFzIGlmIGEgSE9TVCBjb21tYW5kIGhhZCBub3QgYmVlbg0KICAgICAgIHNl
bnQuICBBIHVzZXItRlRQIHByb2Nlc3MgTUFZIHRoZW4gc2VuZCBhIHN1YnNlcXVlbnQgSE9TVCBj
b21tYW5kDQogICAgICAgd2l0aCBhIGRpZmZlcmVudCBob3N0bmFtZS4NCg0KICAgYi4gIENsb3Nl
IHRoZSBjb25uZWN0aW9uLg0KDQogICBBIHVzZXItUEkgcmVjZWl2aW5nIGEgNTAwIG9yIDUwMiBy
ZXBseSB0byBhIEhPU1QgY29tbWFuZCBTSE9VTEQNCiAgIGFzc3VtZSB0aGF0IHRoZSBzZXJ2ZXIt
UEkgZG9lcyBub3QgaW1wbGVtZW50IHZpcnR1YWwgc2VydmVycyBieSB1c2luZw0KICAgdGhlIEhP
U1QgY29tbWFuZC4gIFRoZSB1c2VyLVBJIE1BWSB0aGVuIHByb2NlZWQgdG8gbG9naW4gYXMgaWYg
dGhlDQogICBIT1NUIGNvbW1hbmQgaGFkIG5vdCBiZWVuIHNlbnQuDQoNCiAgIEEgdXNlci1QSSBy
ZWNlaXZpbmcgYW4gZXJyb3IgcmVwbHkgdGhhdCBpcyBkaWZmZXJlbnQgZnJvbSB0aGUgZXJyb3Jz
DQogICB0aGF0IGhhdmUgYmVlbiBkZXNjcmliZWQgaGVyZSBTSE9VTEQgYXNzdW1lIHRoYXQgdGhl
IHZpcnR1YWwgSE9TVCBpcw0KICAgdW5hdmFpbGFibGUsIGFuZCB0ZXJtaW5hdGUgY29tbXVuaWNh
dGlvbnMuDQoNCg0KDQoNCkhldGhtb24gJiBNY011cnJheSAgICAgIEV4cGlyZXMgRGVjZW1iZXIg
MzEsIDIwMTEgICAgICAgICAgICAgIFtQYWdlIDE3XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgIEZU
UCBIT1NUIENvbW1hbmQgZm9yIFZpcnR1YWwgSG9zdHMgICAgICAgICAgSnVuZSAyMDExDQoNCg0K
ICAgQSBzZXJ2ZXItUEkgdGhhdCByZWNlaXZlcyBhIFVTRVIgY29tbWFuZCB0byBiZWdpbiB0aGUg
YXV0aGVudGljYXRpb24NCiAgIHNlcXVlbmNlIHdpdGhvdXQgaGF2aW5nIHJlY2VpdmVkIGEgSE9T
VCBjb21tYW5kIFNIT1VMRCBOT1QgcmVqZWN0IHRoZQ0KICAgVVNFUiBjb21tYW5kLiAgQ2xpZW50
cyBjb25mb3JtaW5nIHRvIGVhcmxpZXIgRlRQIHNwZWNpZmljYXRpb25zIGRvDQogICBub3Qgc2Vu
ZCBIT1NUIGNvbW1hbmRzLiAgSW4gdGhpcyBjYXNlIHRoZSBzZXJ2ZXIgTUFZIGFjdCBhcyBpZiBz
b21lDQogICBkZWZhdWx0IHZpcnR1YWwgaG9zdCBoYWQgYmVlbiBleHBsaWNpdGx5IHNlbGVjdGVk
LCBvciBNQVkgZW50ZXIgYW4NCiAgIGVudmlyb25tZW50IHRoYXQgaXMgZGlmZmVyZW50IGZyb20g
dGhhdCBvZiBhbnkgc3VwcG9ydGVkIHZpcnR1YWwNCiAgIGhvc3RzLCBwZXJoYXBzIG9uZSBpbiB3
aGljaCBhIHVuaW9uIG9mIGFsbCBhdmFpbGFibGUgYWNjb3VudHMgZXhpc3RzDQogICBhbmQgd2hp
Y2ggcHJlc2VudHMgYW4gTlZGUyB0aGF0IGFwcGVhcnMgdG8gY29udGFpbiBzdWJkaXJlY3Rvcmll
cw0KICAgdGhhdCBjb250YWluIHRoZSBOVkZTIGZvciBhbGwgc3VwcG9ydGVkIHZpcnR1YWwgaG9z
dHMuDQoNCjMuNC4gIEZFQVQgcmVzcG9uc2UgZm9yIEhPU1QgY29tbWFuZA0KDQogICBXaGVuIHJl
cGx5aW5nIHRvIHRoZSBGRUFUIGNvbW1hbmQgW1JGQzIzODldLCBhIHNlcnZlci1GVFAgcHJvY2Vz
cw0KICAgdGhhdCBzdXBwb3J0cyB0aGUgSE9TVCBjb21tYW5kIE1VU1QgaW5jbHVkZSBhIGxpbmUg
Y29udGFpbmluZyB0aGUNCiAgIHNpbmdsZSB3b3JkICJIT1NUIi4gIFRoaXMgd29yZCBpcyBjYXNl
IGluc2Vuc2l0aXZlLCBhbmQgTUFZIGJlIHNlbnQNCiAgIGluIGFueSBtaXh0dXJlIG9mIHVwcGVy
IG9yIGxvd2VyIGNhc2UsIGhvd2V2ZXIgaXQgU0hPVUxEIGJlIHNlbnQgaW4NCiAgIHVwcGVyIGNh
c2UuICBUaGF0IGlzLCB0aGUgcmVzcG9uc2UgU0hPVUxEIGJlOg0KDQogICAgICAgIEM+IEZFQVQN
CiAgICAgICAgUz4gMjExLSA8YW55IGRlc2NyaXB0aXZlIHRleHQ+DQogICAgICAgIFM+ICAuLi4N
CiAgICAgICAgUz4gIEhPU1QNCiAgICAgICAgUz4gIC4uLg0KICAgICAgICBTPiAyMTEgRW5kDQoN
CiAgIFRoZSBlbGxpcHNlcyBpbmRpY2F0ZSBwbGFjZSBob2xkZXJzIHdoZXJlIG90aGVyIGZlYXR1
cmVzIG1heSBiZQ0KICAgaW5jbHVkZWQsIGFuZCBhcmUgbm90IHJlcXVpcmVkLiAgVGhlIG9uZS1z
cGFjZSBpbmRlbnRhdGlvbiBvZiB0aGUNCiAgIGZlYXR1cmUgbGluZXMgaXMgbWFuZGF0b3J5IFtS
RkMyMzg5XS4NCg0KDQo0LiAgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMNCg0KICAgQXMgZGlzY3Vz
c2VkIGluIHNlY3Rpb24gMyBvZiB0aGlzIGRvY3VtZW50LCBhIHNlcnZlciBpbXBsZW1lbnRhdGlv
bg0KICAgTVVTVCB0cmVhdCBhIEhPU1QgY29tbWFuZCB0aGF0IHdhcyBzZW50IGJlZm9yZSBhIHVz
ZXIgaGFzIGJlZW4NCiAgIGF1dGhlbnRpY2F0ZWQgYXMgdGhvdWdoIGEgUkVJTiBjb21tYW5kIHdh
cyBzZW50LCBhbmQgYSBzZXJ2ZXINCiAgIGltcGxlbWVudGF0aW9uIE1BWSB0cmVhdCBhIEhPU1Qg
Y29tbWFuZCB0aGF0IHdhcyBzZW50IGFmdGVyIGEgdXNlcg0KICAgaGFzIGJlZW4gYXV0aGVudGlj
YXRlZCBhcyB0aG91Z2ggYSBSRUlOIGNvbW1hbmQgd2FzIHNlbnQuICBJbiBlaXRoZXINCiAgIG9m
IHRoZXNlIHNjZW5hcmlvcywgdGhlIHNlcnZlciBpbXBsZW1lbnRhdGlvbiBNVVNUIHJlc2V0IHRo
ZQ0KICAgYXV0aGVudGljYXRpb24gZW52aXJvbm1lbnQsIGFzIHRoYXQgd291bGQgYWxsb3cgZm9y
IHNlZ3JlZ2F0aW9uDQogICBiZXR3ZWVuIHRoZSBzZWN1cml0eSBlbnZpcm9ubWVudHMgZm9yIGVh
Y2ggdmlydHVhbCBob3N0IG9uIGFuIEZUUA0KICAgc2VydmVyLiAgVGhlIGltcGxlbWVudGF0aW9u
IGRldGFpbHMgZm9yIHNlY3VyaXR5IGVudmlyb25tZW50cyBtYXkNCiAgIHZhcnkgZ3JlYXRseSBi
YXNlZCBvbiB0aGUgcmVxdWlyZW1lbnRzIG9mIGVhY2ggc2VydmVyIGltcGxlbWVudGF0aW9uDQog
ICBhbmQgb3BlcmF0aW5nIHN5c3RlbSwgYW5kIHRob3NlIGRldGFpbHMgYXJlIG91dHNpZGUgdGhl
IHNjb3BlIG9mIHRoZQ0KICAgcHJvdG9jb2wgaXRzZWxmLiAgRm9yIGV4YW1wbGUsIGEgdmlydHVh
bCBob3N0ICJmb28uZXhhbXBsZS5jb20iIG9uIGFuDQogICBGVFAgc2VydmVyIG1pZ2h0IHVzZSBh
IHNwZWNpZmljIHVzZXJuYW1lIGFuZCBwYXNzd29yZCBsaXN0LCB3aGlsZSB0aGUNCiAgIHZpcnR1
YWwgaG9zdCAiYmFyLmV4YW1wbGUuY29tIiBvbiB0aGUgc2FtZSBGVFAgc2VydmVyIG1pZ2h0IHVz
ZSBhDQogICBkaWZmZXJlbnQgdXNlcm5hbWUgYW5kIHBhc3N3b3JkIGxpc3QuICBJbiBzdWNoIGEg
c2NlbmFyaW8sIHJlc2V0dGluZw0KICAgdGhlIHNlY3VyaXR5IGVudmlyb25tZW50IGlzIG5lY2Vz
c2FyeSBmb3IgdGhlIHZpcnR1YWwgc2VydmVycyB0bw0KDQoNCg0KSGV0aG1vbiAmIE1jTXVycmF5
ICAgICAgRXhwaXJlcyBEZWNlbWJlciAzMSwgMjAxMSAgICAgICAgICAgICAgW1BhZ2UgMThdDQoM
DQpJbnRlcm5ldC1EcmFmdCAgICAgRlRQIEhPU1QgQ29tbWFuZCBmb3IgVmlydHVhbCBIb3N0cyAg
ICAgICAgICBKdW5lIDIwMTENCg0KDQogICBhcHBlYXIgdG8gYmVoYXZlIGluZGVwZW5kZW50bHkg
ZnJvbSBhIGNsaWVudCBwZXJzcGVjdGl2ZSwgd2hpbGUgdGhlDQogICBhY3R1YWwgc2VydmVyIGlt
cGxlbWVudGF0aW9uIGRldGFpbHMgYXJlIGlycmVsZXZhbnQgYXQgdGhlIHByb3RvY29sDQogICBs
ZXZlbC4NCg0KICAgU2VjdGlvbiAxNS4xLjEgb2YgW1JGQzQyMTddIGRpc2N1c3NlcyB0aGUgdXNl
IG9mIFguNTA5IGNlcnRpZmljYXRlcw0KICAgZm9yIHNlcnZlciBhdXRoZW50aWNhdGlvbi4gIFRh
a2luZyB0aGUgaW5mb3JtYXRpb24gZnJvbSB0aGF0IGRvY3VtZW50DQogICBpbnRvIGFjY291bnQs
IHdoZW4gc2VjdXJpbmcgRlRQIHNlc3Npb25zIHdpdGggdGhlIHNlY3VyaXR5IG1lY2hhbmlzbXMN
CiAgIHRoYXQgYXJlIGRlZmluZWQgaW4gW1JGQzQyMTddLCBjbGllbnQgaW1wbGVtZW50YXRpb25z
IFNIT1VMRCB2ZXJpZnkNCiAgIHRoYXQgdGhlIGhvc3RuYW1lIHRoZXkgc3BlY2lmeSBpbiB0aGUg
cGFyYW1ldGVyIGZvciB0aGUgSE9TVCBjb21tYW5kDQogICBtYXRjaGVzIHRoZSBpZGVudGl0eSB0
aGF0IGlzIHNwZWNpZmllZCBpbiB0aGUgc2VydmVyJ3MgWC41MDkNCiAgIGNlcnRpZmljYXRlIGlu
IG9yZGVyIHRvIHByZXZlbnQgbWFuLWluLXRoZS1taWRkbGUgYXR0YWNrcy4NCg0KICAgQSBnZW5l
cmFsIGRpc2N1c3Npb24gb2YgaXNzdWVzIHJlbGF0ZWQgdG8gdGhlIHNlY3VyaXR5IG9mIEZUUCBj
YW4gYmUNCiAgIGZvdW5kIGluIFtSRkMyNTc3XS4NCg0KDQo1LiAgSUFOQSBDb25zaWRlcmF0aW9u
cw0KDQogICBJQU5BIGlzIHJlcXVlc3RlZCB0byByZWdpc3RlciB0aGUgZm9sbG93aW5nIEZUUCBl
eHRlbnNpb24gYWNjb3JkaW5nDQogICB0byB0aGUgcHJvY2VkdXJlIGVzdGFibGlzaGVkIGJ5IFtS
RkM1Nzk3XToNCg0KICAgKy0tLS0tLSstLS0tLS0tLS0rLS0tLS0tLS0tLS0tLSstLS0tLS0rLS0t
LS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rDQogICB8IGNtZCAgfCBGRUFUICAgIHwgZGVzY3Jp
cHRpb24gfCB0eXBlIHwgY29uZiB8IFJGQyNzL1JlZmVyZW5jZXMgYW5kIHwNCiAgIHwgICAgICB8
IENvZGUgICAgfCAgICAgICAgICAgICB8ICAgICAgfCAgICAgIHwgTm90ZXMgICAgICAgICAgICAg
ICAgfA0KICAgKy0tLS0tLSstLS0tLS0tLS0rLS0tLS0tLS0tLS0tLSstLS0tLS0rLS0tLS0tKy0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0rDQogICB8IEhPU1QgfCBIT1NUICAgIHwgSG9zdG5hbWUgICAg
fCBhICAgIHwgbyAgICB8IFRCRCAgICAgICAgICAgICAgICAgIHwNCiAgICstLS0tLS0rLS0tLS0t
LS0tKy0tLS0tLS0tLS0tLS0rLS0tLS0tKy0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tKw0K
DQogICAgIE5PVEUgVE8gUkZDIEVESVRPUjogUGxlYXNlIHVwZGF0ZSBUQkQgaW4gdGhlIGFib3Zl
IHRhYmxlIHdpdGggdGhlDQogICAgICAgICAgICAgICAgICAgICAgICAgbnVtYmVyIG9mIHRoaXMg
ZG9jdW1lbnQuDQoNCg0KNi4gIFJlZmVyZW5jZXMNCg0KNi4xLiAgTm9ybWF0aXZlIFJlZmVyZW5j
ZXMNCg0KICAgW1JGQzA5NTldICBQb3N0ZWwsIEouIGFuZCBKLiBSZXlub2xkcywgIkZpbGUgVHJh
bnNmZXIgUHJvdG9jb2wNCiAgICAgICAgICAgICAgKEZUUCkiLCBTVEQgOSwgUkZDIDk1OSwgT2N0
b2JlciAxOTg1Lg0KDQogICBbUkZDMTAzNF0gIE1vY2thcGV0cmlzLCBQLiwgIkRvbWFpbiBOYW1l
cyAtIENvbmNlcHRzIGFuZCBGYWNpbGl0aWVzIiwNCiAgICAgICAgICAgICAgU1REIDEzLCBSRkMg
MTAzNCwgTm92ZW1iZXIgMTk4Ny4NCg0KICAgW1JGQzEwMzVdICBNb2NrYXBldHJpcywgUC4sICJE
b21haW4gTmFtZXMgLSBJbXBsZW1lbnRhdGlvbiBhbmQNCiAgICAgICAgICAgICAgU3BlY2lmaWNh
dGlvbiIsIFNURCAxMywgUkZDIDEwMzUsIE5vdmVtYmVyIDE5ODcuDQoNCiAgIFtSRkMxMTIzXSAg
QnJhZGVuLCBSLiwgIlJlcXVpcmVtZW50cyBmb3IgSW50ZXJuZXQgSG9zdHMgLS0NCiAgICAgICAg
ICAgICAgQXBwbGljYXRpb24gYW5kIFN1cHBvcnQiLCBTVEQgMywgUkZDIDExMjMsIE9jdG9iZXIg
MTk4OS4NCg0KDQoNCg0KSGV0aG1vbiAmIE1jTXVycmF5ICAgICAgRXhwaXJlcyBEZWNlbWJlciAz
MSwgMjAxMSAgICAgICAgICAgICAgW1BhZ2UgMTldDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgRlRQ
IEhPU1QgQ29tbWFuZCBmb3IgVmlydHVhbCBIb3N0cyAgICAgICAgICBKdW5lIDIwMTENCg0KDQog
ICBbUkZDMjExOV0gIEJyYWRuZXIsIFMuLCAiS2V5IHdvcmRzIGZvciB1c2UgaW4gUkZDcyB0byBJ
bmRpY2F0ZQ0KICAgICAgICAgICAgICBSZXF1aXJlbWVudCBMZXZlbHMiLCBCQ1AgMTQsIFJGQyAy
MTE5LCBNYXJjaCAxOTk3Lg0KDQogICBbUkZDMjIyOF0gIEhvcm93aXR6LCBNLiBhbmQgUy4gTHVu
dCwgIkZUUCBTZWN1cml0eSBFeHRlbnNpb25zIiwNCiAgICAgICAgICAgICAgUkZDIDIyMjgsIE9j
dG9iZXIgMTk5Ny4NCg0KICAgW1JGQzIzODldICBIZXRobW9uLCBQLiBhbmQgUi4gRWx6LCAiRmVh
dHVyZSBuZWdvdGlhdGlvbiBtZWNoYW5pc20gZm9yDQogICAgICAgICAgICAgIHRoZSBGaWxlIFRy
YW5zZmVyIFByb3RvY29sIiwgUkZDIDIzODksIEF1Z3VzdCAxOTk4Lg0KDQogICBbUkZDMjY0MF0g
IEN1cnRpbiwgVy4sICJJbnRlcm5hdGlvbmFsaXphdGlvbiBvZiB0aGUgRmlsZSBUcmFuc2Zlcg0K
ICAgICAgICAgICAgICBQcm90b2NvbCIsIFJGQyAyNjQwLCBKdWx5IDE5OTkuDQoNCiAgIFtSRkMz
NDkyXSAgQ29zdGVsbG8sIEEuLCAiUHVueWNvZGU6IEEgQm9vdHN0cmluZyBlbmNvZGluZyBvZiBV
bmljb2RlDQogICAgICAgICAgICAgIGZvciBJbnRlcm5hdGlvbmFsaXplZCBEb21haW4gTmFtZXMg
aW4gQXBwbGljYXRpb25zDQogICAgICAgICAgICAgIChJRE5BKSIsIFJGQyAzNDkyLCBNYXJjaCAy
MDAzLg0KDQogICBbUkZDNDIxN10gIEZvcmQtSHV0Y2hpbnNvbiwgUC4sICJTZWN1cmluZyBGVFAg
d2l0aCBUTFMiLCBSRkMgNDIxNywNCiAgICAgICAgICAgICAgT2N0b2JlciAyMDA1Lg0KDQogICBb
UkZDNTIzNF0gIENyb2NrZXIsIEQuIGFuZCBQLiBPdmVyZWxsLCAiQXVnbWVudGVkIEJORiBmb3Ig
U3ludGF4DQogICAgICAgICAgICAgIFNwZWNpZmljYXRpb25zOiBBQk5GIiwgUkZDIDUyMzQsIEph
bnVhcnkgMjAwOC4NCg0KNi4yLiAgSW5mb3JtYXRpdmUgUmVmZXJlbmNlcw0KDQogICBbUkZDMTk0
NV0gIEJlcm5lcnMtTGVlLCBULiwgRmllbGRpbmcsIFIuLCBhbmQgSC4gRnJ5c3R5aywgIkh5cGVy
dGV4dA0KICAgICAgICAgICAgICBUcmFuc2ZlciBQcm90b2NvbCAtLSBIVFRQLzEuMCIsIFJGQyAx
OTQ1LCBNYXkgMTk5Ni4NCg0KICAgW1JGQzI1NzddICBBbGxtYW4sIE0uIGFuZCBTLiBPc3Rlcm1h
bm4sICJGVFAgU2VjdXJpdHkNCiAgICAgICAgICAgICAgQ29uc2lkZXJhdGlvbnMiLCBSRkMgMjU3
NywgTWF5IDE5OTkuDQoNCiAgIFtSRkMyNjE2XSAgRmllbGRpbmcsIFIuLCBHZXR0eXMsIEouLCBN
b2d1bCwgSi4sIEZyeXN0eWssIEguLA0KICAgICAgICAgICAgICBNYXNpbnRlciwgTC4sIExlYWNo
LCBQLiwgYW5kIFQuIEJlcm5lcnMtTGVlLCAiSHlwZXJ0ZXh0DQogICAgICAgICAgICAgIFRyYW5z
ZmVyIFByb3RvY29sIC0tIEhUVFAvMS4xIiwgUkZDIDI2MTYsIEp1bmUgMTk5OS4NCg0KICAgW1JG
QzU3OTddICBLbGVuc2luLCBKLiBhbmQgQS4gSG9lbmVzLCAiRlRQIENvbW1hbmQgYW5kIEV4dGVu
c2lvbg0KICAgICAgICAgICAgICBSZWdpc3RyeSIsIFJGQyA1Nzk3LCBNYXJjaCAyMDEwLg0KDQoN
CkFwcGVuZGl4IEEuICBVbndvcmthYmxlIEFsdGVybmF0aXZlcw0KDQogICBEdWUgdG8gdGhlIGxl
dmVsIG9mIHNjb3BlIGZvciBhZGRpbmcgYSBuZXcgY29tbWFuZCB0byBGVFAsIGEgYnJpZWYNCiAg
IGRpc2N1c3Npb24gb2Ygc3VnZ2VzdGVkIGFsdGVybmF0aXZlcyB0byBhIEhPU1QgY29tbWFuZCBh
bmQgdGhlaXINCiAgIHJlc3BlY3RpdmUgbGltaXRhdGlvbnMgaXMgd2FycmFudGVkLiAgVGhlIHN1
Z2dlc3RlZCBhbHRlcm5hdGl2ZXMgdGhhdA0KICAgYXJlIGRpc2N1c3NlZCBpbiB0aGlzIGFwcGVu
ZGl4IGhhdmUgYmVlbiBwcm9wb3NlZCBpbiB0aGUgcGFzdCwgYnV0DQogICBlYWNoIG9mIHRoZXNl
IGlkZWFzIHdhcyBkZWVtZWQgaW5zdWZmaWNpZW50IGZvciB0aGUgcmVhc29ucyB0aGF0IGFyZQ0K
ICAgbGlzdGVkIHdpdGhpbiBlYWNoIHNlY3Rpb24gb2YgdGhlIGFwcGVuZGl4Lg0KDQoNCg0KDQoN
CkhldGhtb24gJiBNY011cnJheSAgICAgIEV4cGlyZXMgRGVjZW1iZXIgMzEsIDIwMTEgICAgICAg
ICAgICAgIFtQYWdlIDIwXQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgIEZUUCBIT1NUIENvbW1hbmQg
Zm9yIFZpcnR1YWwgSG9zdHMgICAgICAgICAgSnVuZSAyMDExDQoNCg0KQS4xLiAgT3ZlcmxvYWRp
bmcgdGhlIENXRCBjb21tYW5kDQoNCiAgIE9uZSBzdWdnZXN0ZWQgbWV0aG9kIHRvIGVtdWxhdGUg
YSBmb3JtIG9mIHZpcnR1YWwgaG9zdHMgd291bGQgYmUgZm9yDQogICB0aGUgY2xpZW50IHRvIHNp
bXBseSBzZW5kIGEgIkNXRCIgY29tbWFuZCBhZnRlciBjb25uZWN0aW5nLCB1c2luZyB0aGUNCiAg
IHZpcnR1YWwgaG9zdCBuYW1lIGFzIHRoZSBhcmd1bWVudCB0byB0aGUgQ1dEIGNvbW1hbmQuICBU
aGlzIHdvdWxkDQogICBhbGxvdyB0aGUgc2VydmVyLUZUUCBwcm9jZXNzIHRvIGltcGxlbWVudCB0
aGUgZmlsZSBzdG9yZXMgb2YgdGhlDQogICB2aXJ0dWFsIGhvc3RzIGFzIHN1Yi1kaXJlY3Rvcmll
cyBpbiBpdHMgTlZGUy4gIFRoaXMgc3VnZ2VzdGlvbiBpcw0KICAgc2ltcGxlIGluIGNvbmNlcHQs
IGFuZCBtb3N0IHNlcnZlci1GVFAgaW1wbGVtZW50YXRpb25zIHN1cHBvcnQgdGhpcw0KICAgd2l0
aG91dCByZXF1aXJpbmcgYW55IGNvZGUgY2hhbmdlcy4gIFdoaWxlIHRoaXMgbWV0aG9kIGlzIHNp
bXBsZSB0bw0KICAgZGVzY3JpYmUsIGFuZCB0byBpbXBsZW1lbnQsIGl0IHN1ZmZlcnMgZnJvbSBz
ZXZlcmFsIGRyYXdiYWNrczoNCg0KICAgYS4gIFRoZSAiQ1dEIiBjb21tYW5kIGlzIGF2YWlsYWJs
ZSBvbmx5IGFmdGVyIHRoZSB1c2VyLVBJIGhhcw0KICAgICAgIGF1dGhlbnRpY2F0ZWQgaXRzZWxm
IHRvIHRoZSBzZXJ2ZXItRlRQIHByb2Nlc3MuICBUaHVzLCBhbGwNCiAgICAgICB2aXJ0dWFsIGhv
c3RzIHdvdWxkIGJlIHJlcXVpcmVkIHRvIHNoYXJlIGEgY29tbW9uIGF1dGhlbnRpY2F0aW9uDQog
ICAgICAgc2NoZW1lIGlmIHRoZXkgdXNlZCB0aGlzIG1ldGhvZC4NCg0KICAgYi4gIFRvIG1ha2Ug
dGhlIHZpcnR1YWwgaG9zdCB0cnVseSB0cmFuc3BhcmVudCwgZWl0aGVyIHRoZSBzZXJ2ZXItRlRQ
DQogICAgICAgcHJvY2VzcyBuZWVkcyB0byBiZSBtb2RpZmllZCB0byBpbmNsdWRlIGluZm9ybWF0
aW9uIHRoYXQgc2hvd3MNCiAgICAgICB0aGUgc3BlY2lhbCBuYXR1cmUgb2YgdGhpcyBmaXJzdCBD
V0QgY29tbWFuZCAobmVnYXRpbmcgbW9zdCBvZg0KICAgICAgIHRoZSBhZHZhbnRhZ2Ugb2YgdGhp
cyBzY2hlbWUpLCBvciBhbGwgdXNlcnMgbXVzdCBzZWUgdGhlIHNhbWUNCiAgICAgICBpZGVudGlj
YWwgTlZGUyB2aWV3IHVwb24gY29ubmVjdGluZyAodGhleSBtdXN0IGNvbm5lY3QgaW4gdGhlDQog
ICAgICAgc2FtZSBpbml0aWFsIGRpcmVjdG9yeSksIG9yIHRoZSBOVkZTIG11c3QgaW1wbGVtZW50
IHRoZSBmdWxsIHNldA0KICAgICAgIG9mIHZpcnR1YWwgaG9zdCBkaXJlY3RvcmllcyBhdCBlYWNo
IHBvc3NpYmxlIGluaXRpYWwgZGlyZWN0b3J5DQogICAgICAgZm9yIGFueSBwb3NzaWJsZSB1c2Vy
Lg0KDQogICBjLiAgVW5sZXNzIHRoZSBzZXJ2ZXIgaXMgc3BlY2lhbGx5IG1vZGlmaWVkLCBhIHVz
ZXIgY29ubmVjdGluZyB0aGlzDQogICAgICAgd2F5IHRvIGEgdmlydHVhbCBob3N0IHdvdWxkIGJl
IGFibGUgdG8gZWFzaWx5IG1vdmUgdG8gYW55IG90aGVyDQogICAgICAgdmlydHVhbCBob3N0IHN1
cHBvcnRlZCBhdCB0aGUgc2FtZSBzZXJ2ZXItRlRQIHByb2Nlc3MsIGV4cG9zaW5nDQogICAgICAg
dGhlIG5hdHVyZSBvZiB0aGUgdmlydHVhbCBob3N0Lg0KDQpBLjIuICBPdmVybG9hZGluZyB0aGUg
QUNDVCBjb21tYW5kDQoNCiAgIEFub3RoZXIgc3VnZ2VzdGVkIG1ldGhvZCB3b3VsZCBiZSB0byBz
aW1wbHkgb3ZlcmxvYWQgdGhlICJBQ0NUIiBmb3INCiAgIEZUUCB2aXJ0dWFsIGhvc3RzLCBidXQg
dGhpcyBwcm9wb3NhbCBpcyB1bmFjY2VwdGFibGUgZm9yIHNldmVyYWwNCiAgIHJlYXNvbnMgd2l0
aCByZWdhcmQgdG8gd2hlbiB0aGUgQUNDVCBjb21tYW5kIGlzIHNlbnQgZHVyaW5nIHRoZQ0KICAg
cmVxdWVzdCBmbG93LiAgU2VjdGlvbnMgNS40IGFuZCA2IG9mIFtSRkMwOTU5XSBkb2N1bWVudCB0
aGUgcmVxdWVzdA0KICAgZmxvdyBmb3IgYSBsb2dpbiBzZXF1ZW5jZSBhcyBVU0VSIC0+IFBBU1Mg
LT4gQUNDVC4gIFRoaXMgZmxvdyBvZg0KICAgY29tbWFuZHMgbWF5IGJlIGFjY2VwdGFibGUgd2hl
biB5b3UgYXJlIGNvbnNpZGVyaW5nIGEgc2luZ2xlIHVzZXINCiAgIGhhdmluZyBtdWx0aXBsZSBh
Y2NvdW50cyBvbiBhbiBGVFAgc2VydmVyLCBidXQgZmFpbHMgdG8gZGlmZmVyZW50aWF0ZQ0KICAg
YmV0d2VlbiB2aXJ0dWFsIGhvc3RzIHdoZW4geW91IGNvbnNpZGVyIHRoZSBmb2xsb3dpbmcgdHdv
IGlzc3VlczoNCg0KICAgYS4gIFRoZSBmaXJzdCBwcm9ibGVtIHdpdGggb3ZlcmxvYWRpbmcgdGhl
IEFDQ1QgY29tbWFuZCBpcw0KICAgICAgIGNlcnRpZmljYXRlIG5lZ290aWF0aW9uIHdoZW4gdXNp
bmcgdGhlIEZUUCBzZWN1cml0eSBleHRlbnNpb25zDQogICAgICAgdGhhdCBhcmUgZG9jdW1lbnRl
ZCBpbiBbUkZDMjIyOF0gYW5kIFtSRkM0MjE3XS4gIEluIG9yZGVyIHRvDQogICAgICAgc2FmZWd1
YXJkIHVzZXIgY3JlZGVudGlhbHMsIHNlY3VyaXR5IG1lY2hhbmlzbSBhbmQgY2VydGlmaWNhdGUN
CiAgICAgICBuZWdvdGlhdGlvbiBtdXN0IG9jY3VyIGJlZm9yZSBsb2dpbiBjcmVkZW50aWFscyBh
cmUgc2VudCBieSB0aGUNCiAgICAgICBjbGllbnQuICBUaGUgcHJvYmxlbSB3aXRoIHVzaW5nIHRo
ZSBBQ0NUIGNvbW1hbmQgaW4gdGhpcyBzY2VuYXJpbw0KICAgICAgIGlzIHRoYXQgdGhlcmUgaXMg
bm8gd2F5IG9mIGVuc3VyaW5nIHRoYXQgdGhlIGNlcnRpZmljYXRlIG1hdGNoZXMNCg0KDQoNCkhl
dGhtb24gJiBNY011cnJheSAgICAgIEV4cGlyZXMgRGVjZW1iZXIgMzEsIDIwMTEgICAgICAgICAg
ICAgIFtQYWdlIDIxXQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgIEZUUCBIT1NUIENvbW1hbmQgZm9y
IFZpcnR1YWwgSG9zdHMgICAgICAgICAgSnVuZSAyMDExDQoNCg0KICAgICAgIHRoZSBjb3JyZWN0
IHZpcnR1YWwgaG9zdCBiZWZvcmUgdGhlIHVzZXIgY3JlZGVudGlhbHMgYXJlIHNlbnQuDQoNCiAg
IGIuICBUaGUgc2Vjb25kIHByb2JsZW0gd2l0aCBvdmVybG9hZGluZyB0aGUgQUNDVCBjb21tYW5k
IGlzIGhvdyB1c2VyDQogICAgICAgY3JlZGVudGlhbHMgYXJlIGltcGxlbWVudGVkIGZvciBGVFAg
dmlydHVhbCBob3N0cy4gIEZUUCBzZXJ2ZXINCiAgICAgICBpbXBsZW1lbnRhdGlvbnMgbWF5IGFs
bG93IHRoZSB1c2Ugb2YgY3VzdG9tIHVzZXIgY3JlZGVudGlhbHMgb24gYQ0KICAgICAgIHBlci12
aXJ0dWFsLWhvc3QgYmFzaXMuICBGb3IgZXhhbXBsZSwgaW4gb25lIHBhcnRpY3VsYXINCiAgICAg
ICBpbXBsZW1lbnRhdGlvbiB0aGUgdmlydHVhbCBob3N0IG5lZ290aWF0aW9uIG9jY3VycywgYW5k
IHRoZW4gdGhlDQogICAgICAgdXNlciBjcmVkZW50aWFscyBhcmUgbG9va2VkIHVwIHVzaW5nIHRo
ZSBhY2NvdW50IG1lY2hhbmlzbSB0aGF0DQogICAgICAgaXMgc3BlY2lmaWMgdG8gdGhhdCB2aXJ0
dWFsIGhvc3QuICBTbyBvbmNlIGFnYWluIHRoZSB2aXJ0dWFsIGhvc3QNCiAgICAgICBuZWdvdGlh
dGlvbiBtdXN0IHRha2UgcGxhY2UgYmVmb3JlIHRoZSB1c2VyIGNyZWRlbnRpYWxzIGFyZSBzZW50
Lg0KDQpBLjMuICBPdmVybG9hZGluZyB0aGUgVVNFUiBjb21tYW5kDQoNCiAgIEFuIGFkZGl0aW9u
YWwgc3VnZ2VzdGlvbiB3b3VsZCBiZSB0byBvdmVybG9hZCB3ZWxsLWtub3duIHN5bnRheA0KICAg
dGhyb3VnaCB0aGUgZXhpc3RpbmcgVVNFUiBjb21tYW5kLCBhcyBpbGx1c3RyYXRlZCBpbiB0aGUg
Zm9sbG93aW5nDQogICBleGFtcGxlOg0KDQogICAgICAgIEM+IFVTRVIgZm9vQGV4YW1wbGUuY29t
DQogICAgICAgIFM+IDMzMSBQYXNzd29yZCByZXF1aXJlZA0KICAgICAgICBDPiBQQVNTIGJhcg0K
ICAgICAgICBTPiAyMzAgVXNlciBsb2dnZWQgaW4NCg0KICAgSW4gdGhpcyBleGFtcGxlLCB0aGUg
dXNlciAiZm9vIiBtaWdodCBiZSBhdHRlbXB0aW5nIHRvIGxvZyBvbiB0byB0aGUNCiAgIHZpcnR1
YWwgaG9zdCAiZXhhbXBsZS5jb20iIG9uIGFuIEZUUCBzZXJ2ZXIuICBUaGlzIHN1Z2dlc3Rpb24g
bWF5DQogICBzZWVtIHBsYXVzaWJsZSBhdCBmaXJzdCwgYnV0IGludHJvZHVjZXMgc2V2ZXJhbCBp
bXBsZW1lbnRhdGlvbg0KICAgcHJvYmxlbXMuICBGb3IgZXhhbXBsZToNCg0KICAgYS4gIFNvbWUg
bmV0d29yayBlbnZpcm9ubWVudHMgYWxyZWFkeSB1c2UgdGhlICJ1c2VybmFtZUBob3N0bmFtZSIN
CiAgICAgICBzeW50YXggZm9yIG5ldHdvcmsgY3JlZGVudGlhbHMsIHdoZXJlIHRoZSAiaG9zdG5h
bWUiIHBvcnRpb24NCiAgICAgICByZWZlcnMgdG8gdGhlIGxvY2F0aW9uIG9mIHRoZSB1c2VyJ3Mg
Y3JlZGVudGlhbHMgd2l0aGluIHRoZQ0KICAgICAgIG5ldHdvcmsgaGllcmFyY2h5LiAgVXNpbmcg
dGhlICJmb29AZXhhbXBsZS5jb20iIHN5bnRheCBpdCBiZWNvbWVzDQogICAgICAgZGlmZmljdWx0
IHRvIGRpZmZlcmVudGlhdGUgYmV0d2VlbiB0aGUgdXNlciAiZm9vIiBsb2dnaW5nIGludG8gYQ0K
ICAgICAgIHZpcnR1YWwgaG9zdCBuYW1lZCAiZXhhbXBsZS5jb20iIG9uIGFuIEZUUCBzZXJ2ZXIg
dmVyc3VzIHRoZSB1c2VyDQogICAgICAgImZvb0BleGFtcGxlLmNvbSIgbG9nZ2luZyBpbnRvIGFu
IEZUUCBzZXJ2ZXIgd2l0aCBubyBzcGVjaWZpZWQNCiAgICAgICB2aXJ0dWFsIGhvc3QuDQoNCiAg
IGIuICBXaGVuIHVzaW5nIHRoZSBGVFAgc2VjdXJpdHkgZXh0ZW5zaW9ucyB0aGF0IGFyZSBkb2N1
bWVudGVkIGluDQogICAgICAgW1JGQzIyMjhdIGFuZCBbUkZDNDIxN10sIHNlY3VyaXR5IG1lY2hh
bmlzbSBhbmQgY2VydGlmaWNhdGUNCiAgICAgICBuZWdvdGlhdGlvbiBtdXN0IG9jY3VyIGJlZm9y
ZSBsb2dpbiBjcmVkZW50aWFscyBhcmUgc2VudCBieSB0aGUNCiAgICAgICBjbGllbnQuICBNb3Jl
IHNwZWNpZmljYWxseSwgdGhlIEFVVEgvQURBVCBjb21tYW5kcyBtdXN0IGJlIHNlbnQNCiAgICAg
ICBiZWZvcmUgdGhlIFVTRVIgY29tbWFuZCBpbiBvcmRlciB0byBzYWZlZ3VhcmQgdXNlciBjcmVk
ZW50aWFscy4NCiAgICAgICBJZiB5b3Ugb3ZlcmxvYWQgdGhlIFVTRVIgY29tbWFuZCwgdGhlcmUg
aXMgbm8gd2F5IG9mIGVuc3VyaW5nDQogICAgICAgdGhhdCB0aGUgY2VydGlmaWNhdGUgbWF0Y2hl
cyB0aGUgY29ycmVjdCB2aXJ0dWFsIGhvc3QgYmVmb3JlIHRoZQ0KICAgICAgIHVzZXIgY3JlZGVu
dGlhbHMgYXJlIHNlbnQgYnkgdGhlIGNsaWVudC4NCg0KDQoNCg0KDQoNCg0KSGV0aG1vbiAmIE1j
TXVycmF5ICAgICAgRXhwaXJlcyBEZWNlbWJlciAzMSwgMjAxMSAgICAgICAgICAgICAgW1BhZ2Ug
MjJdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgRlRQIEhPU1QgQ29tbWFuZCBmb3IgVmlydHVhbCBI
b3N0cyAgICAgICAgICBKdW5lIDIwMTENCg0KDQpBLjQuICBDb25jbHVzaW9uDQoNCiAgIFRoZSBj
b25jbHVzaW9uIGZyb20gdGhlIGV4YW1pbmF0aW9uIG9mIHRoZSBleGlzdGluZyBwb3NzaWJpbGl0
aWVzDQogICBzZWVtcyB0byBiZSB0aGF0IGluIG9yZGVyIHRvIG9idGFpbiBhbiBhZGVxdWF0ZSBl
bXVsYXRpb24gb2YgInJlYWwiDQogICBGVFAgc2VydmVycywgY2xpZW50IGFuZCBzZXJ2ZXIgbW9k
aWZpY2F0aW9ucyB0byBzdXBwb3J0IHZpcnR1YWwgaG9zdHMNCiAgIGFyZSBuZWNlc3NhcnkuICBU
aGVyZWZvcmUgYSBuZXcgRlRQIGNvbW1hbmQgc2VlbXMgdGhlIG1vc3QgbGlrZWx5DQogICBzb2x1
dGlvbiB0byBwcm92aWRlIHRoZSByZXF1aXJlZCBsZXZlbCBvZiBzdXBwb3J0Lg0KDQoNCkFwcGVu
ZGl4IEIuICBBY2tub3dsZWRnZW1lbnRzDQoNCiAgIFJvYmVydCBFbHogYW5kIFBhdWwgSGV0aG1v
biBwcm92aWRlZCBhIGRldGFpbGVkIGRpc2N1c3Npb24gb2YgdGhlDQogICBIT1NUIGNvbW1hbmQg
aW4gdGhlaXIgSW50ZXJuZXQgZHJhZnQgdGl0bGVkICJFeHRlbnNpb25zIHRvIEZUUCIgYXMNCiAg
IHBhcnQgb2YgdGhlaXIgd29yayB3aXRoIHRoZSBGVFBFWFQgV29ya2luZyBHcm91cCBhdCB0aGUg
SUVURi4gIFRoZWlyDQogICB3b3JrIGZvcm1lZCB0aGUgYmFzaXMgZm9yIG11Y2ggb2YgdGhpcyBk
b2N1bWVudCwgYW5kIHRoZWlyIGhlbHAgaGFzDQogICBiZWVuIGdyZWF0bHkgYXBwcmVjaWF0ZWQu
ICBUaGV5IHdvdWxkIGFsc28gbGlrZSB0byBjcmVkaXQgQmVybmhhcmQNCiAgIFJvc2Vua3JhZW56
ZXIgZm9yIGhhdmluZyBmaXJzdCBzdWdnZXN0ZWQgYW5kIGRlc2NyaWJlZCB0aGUgSE9TVA0KICAg
Y29tbWFuZC4NCg0KICAgQWxleGV5IE1lbG5pa292LCBBbGZyZWQgSG9lbmVzLCBKb2huIEtsZW5z
aW4sIGFuZCBKb2UgVG91Y2ggaGF2ZSBtYWRlDQogICBzZXZlcmFsIHN1Z2dlc3Rpb25zIGFib3V0
IGVhcmxpZXIgdmVyc2lvbnMgb2YgdGhpcyBkb2N1bWVudDsgbWFueSBvZg0KICAgdGhlaXIgc3Vn
Z2VzdGlvbnMgaGF2ZSBiZWVuIGluY29ycG9yYXRlZCwgYW5kIHRoZWlyIGNvbnRyaWJ1dGlvbnMg
YXJlDQogICBncmF0ZWZ1bGx5IGFja25vd2xlZGdlZC4gIEluIGFkZGl0aW9uLCBBbGVjIFJvd2Vs
bCdzIGFzc2lzdGFuY2UgaW4NCiAgIG1ha2luZyBzZWN0aW9ucyBvZiB0aGlzIGRvY3VtZW50IG1v
cmUgcmVhZGFibGUgd2FzIGludmFsdWFibGUuDQoNCg0KQXV0aG9ycycgQWRkcmVzc2VzDQoNCiAg
IFBhdWwgSGV0aG1vbg0KICAgSGV0aG1vbiBCcm90aGVycw0KICAgMjMwNSBDaHVrYXIgUm9hZA0K
ICAgS25veHZpbGxlLCBUTiAgMzc5MjMNCiAgIFVTQQ0KDQogICBFbWFpbDogcGhldGhtb25AaGV0
aG1vbi5jb20NCg0KDQogICBSb2JlcnQgTWNNdXJyYXkNCiAgIE1pY3Jvc29mdCBDb3Jwb3JhdGlv
bg0KICAgT25lIE1pY3Jvc29mdCBXYXkNCiAgIFJlZG1vbmQsIFdBICA5ODA1Mg0KICAgVVNBDQoN
CiAgIEVtYWlsOiByb2JtY21AbWljcm9zb2Z0LmNvbQ0KDQoNCg0KDQoNCg0KDQpIZXRobW9uICYg
TWNNdXJyYXkgICAgICBFeHBpcmVzIERlY2VtYmVyIDMxLCAyMDExICAgICAgICAgICAgICBbUGFn
ZSAyM10NCgwNCg==

--_004_01AA9EC92749BF4894AC2B3039EA4A2C194A07E2CH1PRD0302MB131_
Content-Type: application/xml; name="draft-ietf-ftpext2-hosts-04.xml"
Content-Description: draft-ietf-ftpext2-hosts-04.xml
Content-Disposition: attachment; filename="draft-ietf-ftpext2-hosts-04.xml";
	size=57525; creation-date="Fri, 24 Jun 2011 17:26:09 GMT";
	modification-date="Wed, 29 Jun 2011 01:35:48 GMT"
Content-Transfer-Encoding: base64

PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXMtYXNjaWkiPz4NCjwhRE9DVFlQRSByZmMg
U1lTVEVNICJyZmMyNjI5LmR0ZCJbCgoKPCFFTlRJVFkgUkZDMjExOSBTWVNURU0gImh0dHA6Ly94
bWwucmVzb3VyY2Uub3JnL3B1YmxpYy9yZmMvYmlieG1sL3JlZmVyZW5jZS5SRkMuMjExOS54bWwi
Pgo8IUVOVElUWSBSRkMyNjI5IFNZU1RFTSAiaHR0cDovL3htbC5yZXNvdXJjZS5vcmcvcHVibGlj
L3JmYy9iaWJ4bWwvcmVmZXJlbmNlLlJGQy4yNjI5LnhtbCI+CjwhRU5USVRZIFJGQzM1NTIgU1lT
VEVNICJodHRwOi8veG1sLnJlc291cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnhtbC9yZWZlcmVuY2Uu
UkZDLjM1NTIueG1sIj4KPCFFTlRJVFkgSS1ELm5hcnRlbi1pYW5hLWNvbnNpZGVyYXRpb25zLXJm
YzI0MzRiaXMgU1lTVEVNICJodHRwOi8veG1sLnJlc291cmNlLm9yZy9wdWJsaWMvcmZjL2JpYnht
bDMvcmVmZXJlbmNlLkktRC5uYXJ0ZW4taWFuYS1jb25zaWRlcmF0aW9ucy1yZmMyNDM0YmlzLnht
bCI+Cl0+DQo8P3htbC1zdHlsZXNoZWV0IHR5cGU9J3RleHQveHNsJyBocmVmPSdyZmMyNjI5Lnhz
bHQnID8+DQo8P3JmYyBzdHJpY3Q9InllcyIgPz4NCjw/cmZjIHRvYz0ieWVzIj8+DQo8P3JmYyB0
b2NkZXB0aD0iNCI/Pg0KPD9yZmMgc3ltcmVmcz0ieWVzIj8+DQo8P3JmYyBzb3J0cmVmcz0ieWVz
IiA/Pg0KPD9yZmMgY29tcGFjdD0ieWVzIiA/Pg0KPD9yZmMgc3ViY29tcGFjdD0ibm8iID8+DQo8
cmZjIGNhdGVnb3J5PSJzdGQiIGRvY05hbWU9ImRyYWZ0LWlldGYtZnRwZXh0Mi1ob3N0cy0wNCIg
aXByPSJ0cnVzdDIwMDkwMiIgb2Jzb2xldGVzPSIiIHVwZGF0ZXM9Ijk1OSIgc3VibWlzc2lvblR5
cGU9IklFVEYiIHhtbDpsYW5nPSJlbiI+DQogIDxmcm9udD4NCiAgICA8dGl0bGUgYWJicmV2PSJG
VFAgSE9TVCBDb21tYW5kIGZvciBWaXJ0dWFsIEhvc3RzIj5GaWxlIFRyYW5zZmVyIFByb3RvY29s
IEhPU1QgQ29tbWFuZCBmb3IgVmlydHVhbCBIb3N0czwvdGl0bGU+DQogICAgPGF1dGhvciBmdWxs
bmFtZT0iUGF1bCBIZXRobW9uIiBpbml0aWFscz0iUC4iIHN1cm5hbWU9IkhldGhtb24iPg0KICAg
ICAgPG9yZ2FuaXphdGlvbj5IZXRobW9uIEJyb3RoZXJzPC9vcmdhbml6YXRpb24+DQogICAgICA8
YWRkcmVzcz4NCiAgICAgICAgPHBvc3RhbD4NCiAgICAgICAgICA8c3RyZWV0PjIzMDUgQ2h1a2Fy
IFJvYWQ8L3N0cmVldD4NCiAgICAgICAgICA8Y2l0eT5Lbm94dmlsbGU8L2NpdHk+DQogICAgICAg
ICAgPHJlZ2lvbj5UTjwvcmVnaW9uPg0KICAgICAgICAgIDxjb2RlPjM3OTIzPC9jb2RlPg0KICAg
ICAgICAgIDxjb3VudHJ5PlVTQTwvY291bnRyeT4NCiAgICAgICAgPC9wb3N0YWw+DQogICAgICAg
IDxlbWFpbD5waGV0aG1vbkBoZXRobW9uLmNvbTwvZW1haWw+DQogICAgICA8L2FkZHJlc3M+DQog
ICAgPC9hdXRob3I+DQogICAgPGF1dGhvciBmdWxsbmFtZT0iUm9iZXJ0IE1jTXVycmF5IiBpbml0
aWFscz0iUi4iIHN1cm5hbWU9Ik1jTXVycmF5Ij4NCiAgICAgIDxvcmdhbml6YXRpb24+TWljcm9z
b2Z0IENvcnBvcmF0aW9uPC9vcmdhbml6YXRpb24+DQogICAgICA8YWRkcmVzcz4NCiAgICAgICAg
PHBvc3RhbD4NCiAgICAgICAgICA8c3RyZWV0Pk9uZSBNaWNyb3NvZnQgV2F5PC9zdHJlZXQ+DQog
ICAgICAgICAgPGNpdHk+UmVkbW9uZDwvY2l0eT4NCiAgICAgICAgICA8cmVnaW9uPldBPC9yZWdp
b24+DQogICAgICAgICAgPGNvZGU+OTgwNTI8L2NvZGU+DQogICAgICAgICAgPGNvdW50cnk+VVNB
PC9jb3VudHJ5Pg0KICAgICAgICA8L3Bvc3RhbD4NCiAgICAgICAgPGVtYWlsPnJvYm1jbUBtaWNy
b3NvZnQuY29tPC9lbWFpbD4NCiAgICAgIDwvYWRkcmVzcz4NCiAgICA8L2F1dGhvcj4NCiAgICA8
ZGF0ZSBtb250aD0iSnVuZSIgeWVhcj0iMjAxMSIgLz4NCiAgICA8d29ya2dyb3VwPkZUUEVYVDIg
V29ya2luZyBHcm91cDwvd29ya2dyb3VwPg0KICAgIDxrZXl3b3JkPkZUUDwva2V5d29yZD4NCiAg
ICA8a2V5d29yZD5IT1NUPC9rZXl3b3JkPg0KICAgIDxhYnN0cmFjdD4NCiAgICAgIDx0PlRoZSBG
aWxlIFRyYW5zZmVyIFByb3RvY29sLCBhcyBkZWZpbmVkIGluIFJGQyA5NTkgW1JGQzA5NTldLCBk
b2VzIG5vdCBwcm92aWRlIGEgd2F5IGZvciBGVFAgY2xpZW50cyBhbmQgc2VydmVycyB0byBkaWZm
ZXJlbnRpYXRlIGJldHdlZW4gbXVsdGlwbGUgRE5TIG5hbWVzIHRoYXQgYXJlIHJlZ2lzdGVyZWQg
Zm9yIGEgc2luZ2xlIElQIGFkZHJlc3MuICBUaGlzIGRvY3VtZW50IGRlZmluZXMgYSBuZXcgRlRQ
IGNvbW1hbmQgdGhhdCBwcm92aWRlcyBhIG1lY2hhbmlzbSBmb3IgRlRQIGNsaWVudHMgYW5kIHNl
cnZlcnMgdG8gaWRlbnRpZnkgaW5kaXZpZHVhbCB2aXJ0dWFsIGhvc3RzIG9uIGFuIEZUUCBzZXJ2
ZXIuPC90Pg0KICAgIDwvYWJzdHJhY3Q+DQogIDwvZnJvbnQ+DQogIDxtaWRkbGU+DQogICAgPHNl
Y3Rpb24gdGl0bGU9IkludHJvZHVjdGlvbiIgdG9jPSJkZWZhdWx0Ij4NCiAgICAgIDx0Pkl0IGlz
IGNvbW1vbiBvbiB0aGUgSW50ZXJuZXQgZm9yIG1hbnkgRE5TIG5hbWVzIHRvIHJlc29sdmUgdG8g
YSBzaW5nbGUgSVAgYWRkcmVzcy4gIFRoaXMgcHJhY3RpY2UgaGFzIGludHJvZHVjZWQgdGhlIGNv
bmNlcHQgb2YgYSAidmlydHVhbCBob3N0Iiwgd2hlcmUgYSBob3N0IGFwcGVhcnMgdG8gZXhpc3Qg
YXMgYW4gaW5kZXBlbmRlbnQgZW50aXR5LCBidXQgaW4gcmVhbGl0eSBzaGFyZXMgaXRzIHBoeXNp
Y2FsIHJlc291cmNlcyB3aXRoIG9uZSBvciBtb3JlIHNpbWlsYXIgaG9zdHMuPC90Pg0KICAgICAg
PHQ+U3VjaCBhbiBhcnJhbmdlbWVudCBwcmVzZW50cyBzb21lIHByb2JsZW1zIGZvciBGVFAgc2Vy
dmVycywgYXMgYW4gRlRQIHNlcnZlciBkaXN0aW5ndWlzaGVzIGluY29taW5nIEZUUCBjb25uZWN0
aW9ucyBieSB0aGVpciBJUCBhZGRyZXNzZXMsIG5vdCB0aGVpciBETlMgbmFtZXMsIGJlY2F1c2Ug
aG9zdHMgYXJlIHVuaXF1ZWx5IGlkZW50aWZpZWQgYnkgdGhlaXIgYWRkcmVzcyByYXRoZXIgdGhh
biBuYW1lLiAgVGhhdCBpcywgYWxsIEROUyBuYW1lcyB0aGF0IHNoYXJlIGFuIElQIGFkZHJlc3Mg
YXJlIGhhbmRsZWQgYnkgdGhlIHNhbWUgRlRQIHNlcnZlciBhbmQgc2hhcmUgdGhlIHNhbWUgTmV0
d29yayBWaXJ0dWFsIEZpbGUgU3lzdGVtIChOVkZTKS48L3Q+DQogICAgICA8dD5UaGlzIG1lYW5z
IHRoYXQgZGlmZmVyZW50IHZpcnR1YWwgaG9zdHMgY2Fubm90IG9mZmVyIGRpZmZlcmVudCB2aXJ0
dWFsIGZpbGUgc3lzdGVtcyB0byBjbGllbnRzLCBub3IgY2FuIHRoZXkgb2ZmZXIgZGlmZmVyZW50
IGF1dGhlbnRpY2F0aW9uIHN5c3RlbXMuICBBbnkgc2NoZW1lIHRvIG92ZXJjb21lIHRoaXMgaXNz
dWUgbmVlZHMgdG8gaW5kaWNhdGUgbm90IG9ubHkgdGhlIGRlc3RpbmF0aW9uIElQIGFkZHJlc3Ms
IGJ1dCBhbHNvIHRoZSB2aXJ0dWFsIGhvc3QgbmFtZSB0aGF0IGlzIGFzc29jaWF0ZWQgd2l0aCB0
aGUgZGVzaXJlZCB2aXJ0dWFsIEZUUCBzZXJ2ZXIuICBUeXBpY2FsIHVzZXItRlRQIHByb2Nlc3Nl
cyBjdXJyZW50bHkgdXNlIGhvc3RuYW1lcyB0byBwZXJmb3JtIGhvc3RuYW1lIHRvIElQIGFkZHJl
c3MgcmVzb2x1dGlvbiBhbmQgdGhlbiBpZ25vcmUgaG9zdG5hbWVzIGZvciB0aGUgcmVzdCBvZiB0
aGUgRlRQIHNlc3Npb24sIHRoZXJlZm9yZSBhbnkgbWVjaGFuaXNtIHRvIG92ZXJjb21lIHRoaXMg
aXNzdWUgd291bGQgcmVxdWlyZSBtb2RpZmljYXRpb25zIHRvIHRoZSB1c2VyLVBJIGFuZCBzZXJ2
ZXItUEkuPC90Pg0KICAgICAgPHQ+SXQgc2hvdWxkIGJlIG5vdGVkIHRoYXQgdGhpcyBzYW1lIHBy
b2JsZW0gZXhpc3RlZCBmb3IgSFRUUC8xLjAgYXMgZGVmaW5lZCBpbiA8eHJlZiB0YXJnZXQ9IlJG
QzE5NDUiIHBhZ2Vubz0iZmFsc2UiIGZvcm1hdD0iZGVmYXVsdCI+PC94cmVmPiwgYW5kIHdhcyBy
ZXNvbHZlZCBpbiBIVFRQLzEuMSBhcyBkZWZpbmVkIGluIDx4cmVmIHRhcmdldD0iUkZDMjYxNiIg
cGFnZW5vPSJmYWxzZSIgZm9ybWF0PSJkZWZhdWx0Ij48L3hyZWY+IHRocm91Z2ggdGhlIGFkZGl0
aW9uIG9mIHRoZSBIb3N0IHJlcXVlc3QgaGVhZGVyLiAgVGhlIGdvYWwgb2YgdGhpcyBkb2N1bWVu
dCBpcyB0byBicmluZyBhIHNpbWlsYXIgbGV2ZWwgb2YgZmVhdHVyZSBwYXJpdHkgdG8gRlRQIGJ5
IGludHJvZHVjaW5nIGEgbmV3IEhPU1QgY29tbWFuZCB0aGF0IGFsbG93cyB1c2VyLUZUUCBwcm9j
ZXNzZXMgdG8gc3BlY2lmeSB3aGljaCB2aXJ0dWFsIGhvc3QgdG8gY29ubmVjdCB0byBmb3IgYSBz
ZXJ2ZXItRlRQIHByb2Nlc3MgdGhhdCBpcyBoYW5kbGluZyByZXF1ZXN0cyBmb3IgbXVsdGlwbGUg
dmlydHVhbCBob3N0cyBvbiBhIHNpbmdsZSBJUCBhZGRyZXNzLjwvdD4NCiAgICA8L3NlY3Rpb24+
DQogICAgPHNlY3Rpb24gdGl0bGU9IkRvY3VtZW50IENvbnZlbnRpb25zIiB0b2M9ImRlZmF1bHQi
Pg0KICAgICAgPHQ+VGhlIGtleSB3b3JkcyAiTVVTVCIsICJNVVNUIE5PVCIsICJSRVFVSVJFRCIs
ICJTSEFMTCIsICJTSEFMTCBOT1QiLCAiU0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5E
RUQiLCAgIk1BWSIsIGFuZCAiT1BUSU9OQUwiIGluIHRoaXMgZG9jdW1lbnQgYXJlIHRvIGJlIGlu
dGVycHJldGVkIGFzIGRlc2NyaWJlZCBpbiA8eHJlZiB0YXJnZXQ9IlJGQzIxMTkiIHBhZ2Vubz0i
ZmFsc2UiIGZvcm1hdD0iZGVmYXVsdCI+PC94cmVmPi48L3Q+DQogICAgICA8dD5JbiBleGFtcGxl
cywgIkMmZ3Q7IiBhbmQgIlMmZ3Q7IiBpbmRpY2F0ZSBsaW5lcyBzZW50IGJ5IHRoZSBjbGllbnQg
YW5kIHNlcnZlciwgcmVzcGVjdGl2ZWx5LjwvdD4NCiAgICAgIDx0PlRoaXMgZG9jdW1lbnQgYWxz
byB1c2VzIG5vdGF0aW9uIGRlZmluZWQgaW4gPHhyZWYgdGFyZ2V0PSJSRkMwOTU5IiBwYWdlbm89
ImZhbHNlIiBmb3JtYXQ9ImRlZmF1bHQiPjwveHJlZj4gYW5kIDx4cmVmIHRhcmdldD0iUkZDMTEy
MyIgcGFnZW5vPSJmYWxzZSIgZm9ybWF0PSJkZWZhdWx0Ij48L3hyZWY+LiAgSW4gcGFydGljdWxh
ciwgdGhlIHRlcm1zICJyZXBseSIsICJ1c2VyIiwgIk5WRlMiLCAiTlZUIiwgImZpbGUiLCAicGF0
aG5hbWUiLCAiRlRQIGNvbW1hbmRzIiwgIkRUUCIsICJ1c2VyLUZUUCBwcm9jZXNzIiwgInVzZXIt
UEkiLCAidXNlci1EVFAiLCAic2VydmVyLUZUUCBwcm9jZXNzIiwgInNlcnZlci1QSSIsICJzZXJ2
ZXItRFRQIiwgIm1vZGUiLCAidHlwZSIsICJjb250cm9sIGNvbm5lY3Rpb24iLCAiZGF0YSBjb25u
ZWN0aW9uIiwgYW5kICJBU0NJSSIsIGFyZSBhbGwgdXNlZCBoZXJlIGFzIGRlZmluZWQgdGhlcmUu
PC90Pg0KICAgICAgPHQ+U3ludGF4IHJlcXVpcmVkIGlzIGRlZmluZWQgdXNpbmcgdGhlIEF1Z21l
bnRlZCBCTkYgZGVmaW5lZCBpbiA8eHJlZiB0YXJnZXQ9IlJGQzUyMzQiIHBhZ2Vubz0iZmFsc2Ui
IGZvcm1hdD0iZGVmYXVsdCI+PC94cmVmPi4gIFNvbWUgZ2VuZXJhbCBBQk5GIGRlZmluaXRpb25z
IGFyZSByZXF1aXJlZCB0aHJvdWdob3V0IHRoZSBkb2N1bWVudDsgdGhvc2Ugd2lsbCBiZSBkZWZp
bmVkIGxhdGVyIGluIHRoaXMgc2VjdGlvbi4gIEF0IGZpcnN0IHJlYWRpbmcsIGl0IG1heSBiZSB3
aXNlIHRvIHNpbXBseSByZWNhbGwgdGhhdCB0aGVzZSBkZWZpbml0aW9ucyBleGlzdCBoZXJlLCBh
bmQgc2tpcCB0byB0aGUgbmV4dCBzZWN0aW9uLjwvdD4NCiAgICAgIDxzZWN0aW9uIHRpdGxlPSJC
YXNpYyBUb2tlbnMiIHRvYz0iZGVmYXVsdCI+DQogICAgICAgIDx0PlRoaXMgZG9jdW1lbnQgaW1w
b3J0cyB0aGUgY29yZSBkZWZpbml0aW9ucyBnaXZlbiBpbiBBcHBlbmRpeCBCIG9mIDx4cmVmIHRh
cmdldD0iUkZDNTIzNCIgcGFnZW5vPSJmYWxzZSIgZm9ybWF0PSJkZWZhdWx0IiAvPi4gIFRoZXJl
IGRlZmluaXRpb25zIHdpbGwgYmUgZm91bmQgZm9yIGJhc2ljIEFCTkYgZWxlbWVudHMgbGlrZSBB
TFBIQSwgRElHSVQsIFNQLCBldGMuICBUbyB0aGF0LCB0aGUgZm9sbG93aW5nIHRlcm0gaXMgYWRk
ZWQgZm9yIHVzZSBpbiB0aGlzIGRvY3VtZW50LjwvdD4NCiAgICAgICAgPHQ+DQogICAgICAgICAg
PGZpZ3VyZSB0aXRsZT0iIiBzdXBwcmVzcy10aXRsZT0iZmFsc2UiIGFsaWduPSJsZWZ0IiBhbHQ9
IiIgd2lkdGg9IiIgaGVpZ2h0PSIiPg0KICAgICAgICAgICAgPGFydHdvcmsgdHlwZT0iQUJORiIg
eG1sOnNwYWNlPSJwcmVzZXJ2ZSIgbmFtZT0iIiBhbGlnbj0ibGVmdCIgYWx0PSIiIHdpZHRoPSIi
IGhlaWdodD0iIj48IVtDREFUQVsgICAgIFRDSEFSID0gVkNIQVIgLyBTUCAvIEhUQUIgICAgOyB2
aXNpYmxlIHBsdXMgd2hpdGUgc3BhY2VdXT48L2FydHdvcms+DQogICAgICAgICAgPC9maWd1cmU+
DQogICAgICAgIDwvdD4NCiAgICAgICAgPHQ+VGhlIFZDSEFSIChmcm9tIDx4cmVmIHRhcmdldD0i
UkZDNTIzNCIgcGFnZW5vPSJmYWxzZSIgZm9ybWF0PSJkZWZhdWx0IiAvPikgYW5kIFRDSEFSIHJ1
bGVzIGdpdmUgYmFzaWMgY2hhcmFjdGVyIHR5cGVzIGZyb20gdmFyeWluZyBzdWItc2V0cyBvZiB0
aGUgQVNDSUkgY2hhcmFjdGVyIHNldCBmb3IgdXNlIGluIHZhcmlvdXMgY29tbWFuZHMgYW5kIHJl
c3BvbnNlcy48L3Q+DQogICAgICAgIDx0Pk5vdGUgdGhhdCBpbiBBQk5GLCBzdHJpbmcgbGl0ZXJh
bHMgYXJlIGNhc2UgaW5zZW5zaXRpdmUuICBUaGF0IGNvbnZlbnRpb24gaXMgcHJlc2VydmVkIGlu
IHRoaXMgZG9jdW1lbnQsIGFuZCBpbXBsaWVzIHRoYXQgRlRQIGNvbW1hbmRzIGFuZCBwYXJhbWV0
ZXJzIHRoYXQgYXJlIGFkZGVkIGJ5IHRoaXMgc3BlY2lmaWNhdGlvbiBoYXZlIHZhbHVlcyB0aGF0
IGNhbiBiZSByZXByZXNlbnRlZCBpbiBhbnkgY2FzZS4gIFRoYXQgaXMsICJIT1NUIiBpcyB0aGUg
c2FtZSBhcyAiaG9zdCIsICJIb3N0IiwgIkhvU3QiLCBldGMuLCBhbmQgImZ0cC5leGFtcGxlLmNv
bSIgaXMgdGhlIHNhbWUgYXMgIkZ0cC5FeGFtcGxlLkNvbSIsICJmVHAuZVhhbXBsZS5jT20iLCBl
dGMuPC90Pg0KICAgICAgPC9zZWN0aW9uPg0KICAgICAgPHNlY3Rpb24gdGl0bGU9IlNlcnZlciBS
ZXBsaWVzIiB0b2M9ImRlZmF1bHQiPg0KICAgICAgICA8dD5TZWN0aW9uIDQuMiBvZiA8eHJlZiB0
YXJnZXQ9IlJGQzA5NTkiIHBhZ2Vubz0iZmFsc2UiIGZvcm1hdD0iZGVmYXVsdCIgLz4gZGVmaW5l
cyB0aGUgZm9ybWF0IGFuZCBtZWFuaW5nIG9mIHJlcGxpZXMgYnkgdGhlIHNlcnZlci1QSSB0byBG
VFAgY29tbWFuZHMgZnJvbSB0aGUgdXNlci1QSS4gIFRob3NlIHJlcGx5IGNvbnZlbnRpb25zIGFy
ZSB1c2VkIGhlcmUgd2l0aG91dCBjaGFuZ2UuPC90Pg0KICAgICAgICA8dD4NCiAgICAgICAgICA8
ZmlndXJlIHRpdGxlPSIiIHN1cHByZXNzLXRpdGxlPSJmYWxzZSIgYWxpZ249ImxlZnQiIGFsdD0i
IiB3aWR0aD0iIiBoZWlnaHQ9IiI+DQogICAgICAgICAgICA8YXJ0d29yayB0eXBlPSJBQk5GIiB4
bWw6c3BhY2U9InByZXNlcnZlIiBuYW1lPSIiIGFsaWduPSJsZWZ0IiBhbHQ9IiIgd2lkdGg9IiIg
aGVpZ2h0PSIiPjwhW0NEQVRBWyAgICAgZXJyb3ItcmVzcG9uc2UgPSBlcnJvci1jb2RlIFNQICpU
Q0hBUiBDUkxGDQogICAgIGVycm9yLWNvZGUgICAgID0gKCI0IiAvICI1IikgMkRJR0lUXV0+PC9h
cnR3b3JrPg0KICAgICAgICAgIDwvZmlndXJlPg0KICAgICAgICA8L3Q+DQogICAgICAgIDx0Pklt
cGxlbWVudGVycyBzaG91bGQgbm90ZSB0aGF0IHRoZSBBQk5GIHN5bnRheCAod2hpY2ggd2FzIG5v
dCB1c2VkIGluIDx4cmVmIHRhcmdldD0iUkZDMDk1OSIgcGFnZW5vPSJmYWxzZSIgZm9ybWF0PSJk
ZWZhdWx0IiAvPikgdXNlZCBpbiB0aGlzIGRvY3VtZW50LCBhbmQgb3RoZXIgRlRQIHJlbGF0ZWQg
ZG9jdW1lbnRzLCBzb21ldGltZXMgc2hvd3MgcmVwbGllcyB1c2luZyB0aGUgb25lIGxpbmUgZm9y
bWF0LiAgVW5sZXNzIG90aGVyd2lzZSBleHBsaWNpdGx5IHN0YXRlZCwgdGhhdCBpcyBub3QgaW50
ZW5kZWQgdG8gaW1wbHkgdGhhdCBtdWx0aS1saW5lIHJlc3BvbnNlcyBhcmUgbm90IHBlcm1pdHRl
ZC4gIEltcGxlbWVudGVycyBzaG91bGQgYXNzdW1lIHRoYXQsIHVubGVzcyBzdGF0ZWQgdG8gdGhl
IGNvbnRyYXJ5LCBhbnkgcmVwbHkgdG8gYW55IEZUUCBjb21tYW5kIChpbmNsdWRpbmcgUVVJVCkg
Y2FuIGJlIG9mIHRoZSBtdWx0aS1saW5lIGZvcm1hdCBkZXNjcmliZWQgaW4gPHhyZWYgdGFyZ2V0
PSJSRkMwOTU5IiBwYWdlbm89ImZhbHNlIiBmb3JtYXQ9ImRlZmF1bHQiIC8+LjwvdD4NCiAgICAg
ICAgPHQ+VGhyb3VnaG91dCB0aGlzIGRvY3VtZW50LCByZXBsaWVzIHdpbGwgYmUgaWRlbnRpZmll
ZCBieSB0aGUgdGhyZWUgZGlnaXQgY29kZSB0aGF0IGlzIHRoZWlyIGZpcnN0IGVsZW1lbnQuICBU
aHVzIHRoZSB0ZXJtICI1MDAgcmVwbHkiIG1lYW5zIGEgcmVwbHkgZnJvbSB0aGUgc2VydmVyLVBJ
IHVzaW5nIHRoZSB0aHJlZSBkaWdpdCBjb2RlICI1MDAiLjwvdD4NCiAgICAgIDwvc2VjdGlvbj4N
CiAgICA8L3NlY3Rpb24+DQogICAgPHNlY3Rpb24gdGl0bGU9IlRoZSBIT1NUIGNvbW1hbmQiIHRv
Yz0iZGVmYXVsdCI+DQogICAgICA8dD5BIG5ldyBjb21tYW5kICJIT1NUIiBpcyBhZGRlZCB0byB0
aGUgRlRQIGNvbW1hbmQgc2V0IHRvIGFsbG93IHRoZSBzZXJ2ZXItRlRQIHByb2Nlc3MgdG8gZGV0
ZXJtaW5lIHRvIHdoaWNoIG9mIHBvc3NpYmx5IG1hbnkgdmlydHVhbCBob3N0cyB0aGUgY2xpZW50
IHdpc2hlcyB0byBjb25uZWN0LiAgVGhpcyBjb21tYW5kIFNIT1VMRCBiZSBpc3N1ZWQgYmVmb3Jl
IHRoZSB1c2VyIGlzIGF1dGhlbnRpY2F0ZWQsIGFsbG93aW5nIHRoZSBhdXRoZW50aWNhdGlvbiBz
Y2hlbWUsIGFuZCBzZXQgb2YgbGVnYWwgdXNlcnMsIHRvIGJlIGRlcGVuZGVudCB1cG9uIHRoZSB2
aXJ0dWFsIGhvc3QgY2hvc2VuLjwvdD4NCiAgICAgIDx0PlNlcnZlci1GVFAgcHJvY2Vzc2VzIE1V
U1QgdHJlYXQgYSBzaXR1YXRpb24gd2hlcmUgdGhlIEhPU1QgY29tbWFuZCBpcyBpc3N1ZWQgbW9y
ZSB0aGFuIG9uY2UgYmVmb3JlIHRoZSB1c2VyIGhhcyBiZWVuIGF1dGhlbnRpY2F0ZWQgYXMgdGhv
dWdoIGEgUkVJTiBjb21tYW5kIHdhcyBzZW50IGJlZm9yZSBlYWNoIEhPU1QgY29tbWFuZCwgYW5k
IHRoZW4gcmVzZXQgdGhlIHVzZXItUEkgdG8gdGhlIHN0YXRlIHRoYXQgZXhpc3RlZCBhZnRlciB0
aGUgVENQIGNvbm5lY3Rpb24gd2FzIGZpcnN0IGVzdGFibGlzaGVkIGFuZCByZXR1cm4gdGhlIGFw
cHJvcHJpYXRlIHJlcGx5IGZvciB0aGUgSE9TVCBjb21tYW5kLjwvdD4NCiAgICAgIDx0PlNlcnZl
ci1GVFAgcHJvY2Vzc2VzIE1VU1QgdHJlYXQgYSBzaXR1YXRpb24gd2hlcmUgdGhlIEhPU1QgY29t
bWFuZCBpcyBpc3N1ZWQgYWZ0ZXIgdGhlIHVzZXIgaGFzIGJlZW4gYXV0aGVudGljYXRlZCBieSB1
c2luZyBvbmUgb2YgdGhlIGZvbGxvd2luZyB0d28gYmVoYXZpb3JzOjwvdD4NCiAgICAgIDx0Pg0K
ICAgICAgICA8bGlzdCBzdHlsZT0ibGV0dGVycyI+DQogICAgICAgICAgPHQ+VHJlYXQgdGhlIGxh
dGUgSE9TVCBjb21tYW5kIGFzIGFuIGVycm9uZW91cyBzZXF1ZW5jZSBvZiBjb21tYW5kcyBhbmQg
cmV0dXJuIGEgNTAzIHJlcGx5LjwvdD4NCiAgICAgICAgICA8dD5UcmVhdCB0aGUgbGF0ZSBIT1NU
IGNvbW1hbmQgYXMgdGhvdWdoIGEgUkVJTiBjb21tYW5kIHdhcyBzZW50IGJlZm9yZSB0aGUgSE9T
VCBjb21tYW5kIGFuZCByZXNldCB0aGUgdXNlci1QSSB0byB0aGUgc3RhdGUgdGhhdCBleGlzdGVk
IGFmdGVyIHRoZSBUQ1AgY29ubmVjdGlvbiB3YXMgZmlyc3QgZXN0YWJsaXNoZWQgYW5kIGJlZm9y
ZSB0aGUgaW5pdGlhbCB1c2VyIGF1dGhlbnRpY2F0aW9uIGFuZCB0aGVuIHJldHVybiB0aGUgYXBw
cm9wcmlhdGUgcmVwbHkgZm9yIHRoZSBIT1NUIGNvbW1hbmQuPC90Pg0KICAgICAgICA8L2xpc3Q+
DQogICAgICA8L3Q+DQogICAgICA8dD5TZXJ2ZXJzIHNob3VsZCBub3RlIHRoYXQgdGhlIHJlc3Bv
bnNlIHRvIHRoZSBIT1NUIGNvbW1hbmQgaXMgYSBzZW5zaWJsZSB0aW1lIHRvIHNlbmQgdGhlaXIg
IndlbGNvbWUiIG1lc3NhZ2UuICBUaGlzIGFsbG93cyB0aGUgbWVzc2FnZSB0byBiZSBwZXJzb25h
bGl6ZWQgZm9yIGFueSB2aXJ0dWFsIGhvc3RzIHRoYXQgYXJlIHN1cHBvcnRlZCwgYW5kIGFsc28g
YWxsb3dzIHRoZSBjbGllbnQgdG8gZGV0ZXJtaW5lIHRoZSBzdXBwb3J0ZWQgbGFuZ3VhZ2VzLCBv
ciByZXByZXNlbnRhdGlvbnMsIGZvciB0aGUgbWVzc2FnZSwgYW5kIG90aGVyIG1lc3NhZ2VzLCB2
aWEgdGhlIEZFQVQgcmVzcG9uc2UsIGFuZCBzZWxlY3QgYW4gYXBwcm9wcmlhdGUgb25lIHZpYSB0
aGUgTEFORyBjb21tYW5kLiAgU2VlIDx4cmVmIHRhcmdldD0iUkZDMjY0MCIgcGFnZW5vPSJmYWxz
ZSIgZm9ybWF0PSJkZWZhdWx0Ij48L3hyZWY+IGZvciBtb3JlIGluZm9ybWF0aW9uLjwvdD4NCiAg
ICAgIDxzZWN0aW9uIHRpdGxlPSJTeW50YXggb2YgdGhlIEhPU1QgY29tbWFuZCIgdG9jPSJkZWZh
dWx0Ij4NCiAgICAgICAgPHQ+VGhlIEhPU1QgY29tbWFuZCBpcyBkZWZpbmVkIGFzIGZvbGxvd3Mu
PC90Pg0KICAgICAgICA8dD4NCiAgICAgICAgICA8ZmlndXJlIHRpdGxlPSIiIHN1cHByZXNzLXRp
dGxlPSJmYWxzZSIgYWxpZ249ImxlZnQiIGFsdD0iIiB3aWR0aD0iIiBoZWlnaHQ9IiI+DQogICAg
ICAgICAgICA8YXJ0d29yayB0eXBlPSJBQk5GIiB4bWw6c3BhY2U9InByZXNlcnZlIiBuYW1lPSIi
IGFsaWduPSJsZWZ0IiBhbHQ9IiIgd2lkdGg9IiIgaGVpZ2h0PSIiPjwhW0NEQVRBWyAgaG9zdC1j
b21tYW5kICA9ICJIT1NUIiBTUCBob3N0bmFtZSBDUkxGDQogIGhvc3RuYW1lICAgICAgPSBkb21h
aW4gLyBJUC1saXRlcmFsDQoNCiAgZG9tYWluICAgICAgICA9IHN1Yi1kb21haW4gKigiLiIgc3Vi
LWRvbWFpbikNCiAgc3ViLWRvbWFpbiAgICA9IGxldC1kaWcgW2xkaC1zdHJdDQogIGxldC1kaWcg
ICAgICAgPSBBTFBIQSAvIERJR0lUDQogIGxkaC1zdHIgICAgICAgPSAqKCBBTFBIQSAvIERJR0lU
IC8gIi0iICkgbGV0LWRpZw0KDQogIElQLWxpdGVyYWwgICAgPSAoICJbIiBJUHY2YWRkcmVzcyAi
XSIgKSAvIElQdjRhZGRyZXNzDQoNCiAgSVB2NmFkZHJlc3MgICA9ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgNiggaDE2ICI6IiApIGxzMzINCiAgICAgICAgICAgICAgICAgIC8gICAgICAg
ICAgICAgICAgICAgICAgICI6OiIgNSggaDE2ICI6IiApIGxzMzINCiAgICAgICAgICAgICAgICAg
IC8gWyAgICAgICAgICAgICAgIGgxNiBdICI6OiIgNCggaDE2ICI6IiApIGxzMzINCiAgICAgICAg
ICAgICAgICAgIC8gWyAqMSggaDE2ICI6IiApIGgxNiBdICI6OiIgMyggaDE2ICI6IiApIGxzMzIN
CiAgICAgICAgICAgICAgICAgIC8gWyAqMiggaDE2ICI6IiApIGgxNiBdICI6OiIgMiggaDE2ICI6
IiApIGxzMzINCiAgICAgICAgICAgICAgICAgIC8gWyAqMyggaDE2ICI6IiApIGgxNiBdICI6OiIg
ICAgaDE2ICI6IiAgIGxzMzINCiAgICAgICAgICAgICAgICAgIC8gWyAqNCggaDE2ICI6IiApIGgx
NiBdICI6OiIgICAgICAgICAgICAgIGxzMzINCiAgICAgICAgICAgICAgICAgIC8gWyAqNSggaDE2
ICI6IiApIGgxNiBdICI6OiIgICAgICAgICAgICAgIGgxNg0KICAgICAgICAgICAgICAgICAgLyBb
ICo2KCBoMTYgIjoiICkgaDE2IF0gIjo6Ig0KDQogIGxzMzIgICAgICAgICAgPSAoIGgxNiAiOiIg
aDE2ICkgLyBJUHY0YWRkcmVzcw0KICAgICAgICAgICAgICAgICAgOyBsZWFzdC1zaWduaWZpY2Fu
dCAzMiBiaXRzIG9mIGFkZHJlc3MNCg0KICBoMTYgICAgICAgICAgID0gMSo0SEVYRElHDQogICAg
ICAgICAgICAgICAgICA7IDE2IGJpdHMgb2YgYWRkcmVzcyByZXByZXNlbnRlZCBpbiBoZXhhZGVj
aW1hbA0KDQogIElQdjRhZGRyZXNzICAgPSBkZWMtb2N0ZXQgIi4iIGRlYy1vY3RldCAiLiIgZGVj
LW9jdGV0ICIuIiBkZWMtb2N0ZXQNCg0KICBkZWMtb2N0ZXQgICAgID0gRElHSVQgICAgICAgICAg
ICAgICAgIDsgMC05DQogICAgICAgICAgICAgICAgICAvICV4MzEtMzkgRElHSVQgICAgICAgOyAx
MC05OQ0KICAgICAgICAgICAgICAgICAgLyAiMSIgMkRJR0lUICAgICAgICAgIDsgMTAwLTE5OQ0K
ICAgICAgICAgICAgICAgICAgLyAiMiIgJXgzMC0zNCBESUdJVCAgIDsgMjAwLTI0OQ0KICAgICAg
ICAgICAgICAgICAgLyAiMjUiICV4MzAtMzUgICAgICAgIDsgMjUwLTI1NQ0KDQogIGhvc3QtcmVz
cG9uc2UgPSBob3N0LW9rIC8gZXJyb3ItcmVzcG9uc2UNCiAgaG9zdC1vayAgICAgICA9ICIyMjAi
IFsgU1AgKlRDSEFSIF0gQ1JMRl1dPjwvYXJ0d29yaz4NCiAgICAgICAgICA8L2ZpZ3VyZT4NCiAg
ICAgICAgPC90Pg0KICAgICAgICA8dD5BcyB3aXRoIGFsbCBGVFAgY29tbWFuZHMsIHRoZSAiSE9T
VCIgY29tbWFuZCB3b3JkIGlzIGNhc2UgaW5kZXBlbmRlbnQsIGFuZCBNQVkgYmUgc3BlY2lmaWVk
IGluIGFueSBjaGFyYWN0ZXIgY2FzZSBkZXNpcmVkLjwvdD4NCiAgICAgICAgPHQ+VGhlICJob3N0
bmFtZSIgKGdpdmVuIGFzIGEgcGFyYW1ldGVyKSBzcGVjaWZpZXMgdGhlIHZpcnR1YWwgaG9zdCB0
byB3aGljaCBhY2Nlc3MgaXMgZGVzaXJlZC4gIFRoaXMgU0hPVUxEIGJlIHRoZSBzYW1lIGhvc3Qg
bmFtZSB0aGF0IHdhcyB1c2VkIHRvIG9idGFpbiB0aGUgSVAgYWRkcmVzcyB0byB3aGljaCB0aGUg
RlRQIGNvbnRyb2wgY29ubmVjdGlvbiB3YXMgbWFkZSwgYWZ0ZXIgYW55IGNsaWVudCBjb252ZXJz
aW9ucyBoYXZlIGJlZW4gY29tcGxldGVkIHRoYXQgY29udmVydCBhbiBhYmJyZXZpYXRlZCBvciBs
b2NhbCBhbGlhcyB0byBhIGNvbXBsZXRlIChmdWxseSBxdWFsaWZpZWQpIGRvbWFpbiBuYW1lLCBi
dXQgYmVmb3JlIHJlc29sdmluZyBhIEROUyBhbGlhcyAob3duZXIgb2YgYSBDTkFNRSByZXNvdXJj
ZSByZWNvcmQpIHRvIGl0cyBjYW5vbmljYWwgbmFtZS48L3Q+DQogICAgICAgIDx0PkludGVybmF0
aW9uYWxpemF0aW9uIG9mIGRvbWFpbiBuYW1lcyBpcyBvbmx5IHN1cHBvcnRlZCB0aHJvdWdoIHRo
ZSB1c2Ugb2YgUHVueWNvZGUgYXMgZGVzY3JpYmVkIGluIDx4cmVmIHRhcmdldD0iUkZDMzQ5MiIg
cGFnZW5vPSJmYWxzZSIgZm9ybWF0PSJkZWZhdWx0IiAvPi48L3Q+DQogICAgICAgIDx0PklmIHRo
ZSB1c2VyIHdhcyBnaXZlbiBhbiBJUHY0IG9yIElQdjYgbGl0ZXJhbCBhZGRyZXNzLCBhbmQgY29u
c2VxdWVudGx5IHdhcyBub3QgcmVxdWlyZWQgdG8gZGVyaXZlIHRoZSBsaXRlcmFsIGFkZHJlc3Mg
ZnJvbSBhIGhvc3RuYW1lLCB0aGUgY2xpZW50IE1BWSBzZW5kIHRoZSBIT1NUIGNvbW1hbmQgd2l0
aCB0aGUgSVB2NCBvciBJUHY2IGxpdGVyYWwgYWRkcmVzcyBhcyBzcGVjaWZpZWQgdG8gaXQuICBX
aGlsZSBpdCBtYXkgc2VlbSBjb3VudGVyLWludHVpdGl2ZSB0byBzcGVjaWZ5IGEgbGl0ZXJhbCBh
ZGRyZXNzIGJ5IHVzaW5nIHRoZSBIT1NUIGNvbW1hbmQgYWZ0ZXIgdGhlIGNsaWVudCBoYXMgYWxy
ZWFkeSBjb25uZWN0ZWQgdG8gdGhlIHNlcnZlciB1c2luZyBhIGxpdGVyYWwgYWRkcmVzcywgdGhp
cyBzaG91bGQgYmUgZXhwZWN0ZWQgYmVoYXZpb3IgYmVjYXVzZSBhIHVzZXItRlRQIHByb2Nlc3Mg
c2hvdWxkIG5vdCBiZSByZXF1aXJlZCB0byBkaWZmZXJlbnRpYXRlIGJldHdlZW4gYSBmdWxseSBx
dWFsaWZpZWQgZG9tYWluIG5hbWUgYW5kIGFuIElQdjQgb3IgSVB2NiBuZXR3b3JrIGxpdGVyYWwg
YWRkcmVzcy4gIFRoYXQgYmVpbmcgc2FpZCwgaWYgdGhlIElQdjQgb3IgSVB2NiBsaXRlcmFsIGFk
ZHJlc3Mgc3BlY2lmaWVkIGJ5IHRoZSBjbGllbnQgZG9lcyBub3QgbWF0Y2ggdGhlIGxpdGVyYWwg
YWRkcmVzcyBmb3IgdGhlIHNlcnZlciwgdGhlIHNlcnZlciBNVVNUIHJlc3BvbmQgd2l0aCBhIDUw
NCByZXBseSB0byBpbmRpY2F0ZSB0aGF0IHRoZSBJUHY0IG9yIElQdjYgbGl0ZXJhbCBhZGRyZXNz
IGlzIG5vdCB2YWxpZC48L3Q+DQogICAgICAgIDx0PldoZW4gdGhlIGhvc3RuYW1lIHBhcmFtZXRl
ciBjb250YWlucyBhIGxpdGVyYWwgYWRkcmVzcywgc3F1YXJlIGJyYWNrZXRzIGFyZSBleHBlY3Rl
ZCB0byBkaXNhbWJpZ3VhdGUgSVB2NiBhZGRyZXNzIHN5bnRheCBmcm9tIHBvcnQgbnVtYmVycyBz
eW50YXguICBUaGVyZWZvcmUsIGlmIHRoZSBsaXRlcmFsIGFkZHJlc3MgaXMgYW4gSVB2NiBhZGRy
ZXNzLCB0aGUgSVB2NiBhZGRyZXNzIGlzIHJlcXVpcmVkIHRvIGJlIGVuY2xvc2VkIGluIHNxdWFy
ZSBicmFja2V0cyAoYWZ0ZXIgZWxpbWluYXRpbmcgYW55IHN5bnRheCB0aGF0IG1pZ2h0IGFsc28g
LSBidXQgaXMgbm90IHJlcXVpcmVkIHRvIC0gYmUgZW5jbG9zZWQgaW4gYnJhY2tldHMsIGFuZCBm
cm9tIHdoaWNoIHRoZSBzZXJ2ZXIgZGVkdWNlZCB0aGF0IGEgbGl0ZXJhbCBhZGRyZXNzIGhhZCBi
ZWVuIHNwZWNpZmllZC4pIEZvciBleGFtcGxlLCB0aGUgZm9sbG93aW5nIGV4YW1wbGVzIE1BWSBi
ZSBzZW50IGlmIHRoZSBjbGllbnQgaGFkIGJlZW4gaW5zdHJ1Y3RlZCB0byByZXNwZWN0aXZlbHkg
Y29ubmVjdCB0byAiMTkyLjAuMi4xIiwgIkZFODA6OmMwMDA6MDIwMSIsIG9yICIxOTIuMC4yLjEi
IGFuZCBJUHY2IHN5bnRheCBpcyBwcmVmZXJyZWQ6PC90Pg0KICAgICAgICA8dD4NCiAgICAgICAg
ICA8ZmlndXJlIHRpdGxlPSIiIHN1cHByZXNzLXRpdGxlPSJmYWxzZSIgYWxpZ249ImxlZnQiIGFs
dD0iIiB3aWR0aD0iIiBoZWlnaHQ9IiI+DQogICAgICAgICAgICA8YXJ0d29yayB4bWw6c3BhY2U9
InByZXNlcnZlIiBuYW1lPSIiIHR5cGU9IiIgYWxpZ249ImxlZnQiIGFsdD0iIiB3aWR0aD0iIiBo
ZWlnaHQ9IiI+PCFbQ0RBVEFbICAgICBIT1NUIDE5Mi4wLjIuMQ0KICAgICBIT1NUIFtGRTgwOjpj
MDAwOjAyMDFdDQogICAgIEhPU1QgWzo6MTkyLjAuMi4xXV1dPjwvYXJ0d29yaz4NCiAgICAgICAg
ICA8L2ZpZ3VyZT4NCiAgICAgICAgPC90Pg0KICAgICAgICA8dD5UaGUgY2xpZW50IE1VU1QgTk9U
IHNlbmQgdGhlIHBvcnQgbnVtYmVyIGFzIHBhcnQgb2YgdGhlIEhPU1QgY29tbWFuZCwgZXZlbiB3
aGVuIHRoZSBjbGllbnQgaGFzIGJlZW4gaW5zdHJ1Y3RlZCB0byBjb25uZWN0IHRvIGEgbm9uLXN0
YW5kYXJkIHBvcnQuICBUaGUgcmVhc29uIGZvciB0aGlzIHJlcXVpcmVtZW50IGlzIHRoYXQgdGhl
IHVzZXItUEkgd2lsbCBoYXZlIGVzdGFibGlzaGVkIGEgY29ubmVjdGlvbiB0byB0aGUgc2VydmVy
LVBJIGJlZm9yZSB0aGUgSE9TVCBjb21tYW5kIGlzIHNlbnQsIHRoZXJlZm9yZSBzcGVjaWZ5aW5n
IGEgZGlmZmVyZW50IHBvcnQgd2l0aCB0aGUgSE9TVCBjb21tYW5kIGhhcyBubyBtZWFuaW5nLiAg
Rm9yIGV4YW1wbGUsIHRoZSBzZXJ2ZXItUEkgTVVTVCByZXNwb25kIHdpdGggYSA1MDEgcmVwbHkg
aWYgdGhlIGNsaWVudCBzZW5kcyBhIEhPU1QgY29tbWFuZCB3aXRoIHN5bnRheCBsaWtlIGVpdGhl
ciBvZiB0aGUgZm9sbG93aW5nIGV4YW1wbGVzOjwvdD4NCiAgICAgICAgPHQ+DQogICAgICAgICAg
PGZpZ3VyZSB0aXRsZT0iIiBzdXBwcmVzcy10aXRsZT0iZmFsc2UiIGFsaWduPSJsZWZ0IiBhbHQ9
IiIgd2lkdGg9IiIgaGVpZ2h0PSIiPg0KICAgICAgICAgICAgPGFydHdvcmsgeG1sOnNwYWNlPSJw
cmVzZXJ2ZSIgbmFtZT0iIiB0eXBlPSIiIGFsaWduPSJsZWZ0IiBhbHQ9IiIgd2lkdGg9IiIgaGVp
Z2h0PSIiPjwhW0NEQVRBWyAgICAgSE9TVCAxOTIuMC4yLjE6MjExMg0KICAgICBIT1NUIFtGRTgw
OjpjMDAwOjAyMDFdOjIxMTJdXT48L2FydHdvcms+DQogICAgICAgICAgPC9maWd1cmU+DQogICAg
ICAgIDwvdD4NCiAgICAgICAgPHQ+VGhlIGhvc3RuYW1lIHBhcmFtZXRlciBpcyBvdGhlcndpc2Ug
dG8gYmUgdHJlYXRlZCBhcyBhIGZ1bGx5IHF1YWxpZmllZCBkb21haW4gbmFtZSBvciByZWxhdGl2
ZSBuYW1lIGFzIHRob3NlIHRlcm1zIGFyZSBkZWZpbmVkIGluIHNlY3Rpb24gMy4xIG9mIDx4cmVm
IHRhcmdldD0iUkZDMTAzNCIgcGFnZW5vPSJmYWxzZSIgZm9ybWF0PSJkZWZhdWx0IiAvPi4gIFRo
aXMgaW1wbGllcyB0aGF0IHRoZSBuYW1lIGlzIHRvIGJlIHRyZWF0ZWQgYXMgYSBjYXNlLWluZGVw
ZW5kZW50IHN0cmluZywgbWVhbmluZyB0aGF0IHVwcGVyY2FzZSBBU0NJSSBjaGFyYWN0ZXJzIGFy
ZSB0byBiZSB0cmVhdGVkIGFzIGVxdWl2YWxlbnQgdG8gdGhlaXIgY29ycmVzcG9uZGluZyBsb3dl
cmNhc2UgQVNDSUkgY2hhcmFjdGVycywgYnV0IG90aGVyd2lzZSBwcmVzZXJ2ZWQgYXMgZ2l2ZW4u
ICBJdCBhbHNvIGltcGxpZXMgc29tZSBsaW1pdHMgb24gdGhlIGxlbmd0aCBvZiB0aGUgcGFyYW1l
dGVyIGFuZCBvZiB0aGUgY29tcG9uZW50cyB0aGF0IGNyZWF0ZSBpdHMgaW50ZXJuYWwgc3RydWN0
dXJlLiAgVGhvc2UgbGltaXRzIGFyZSBub3QgYWx0ZXJlZCBpbiBhbnkgd2F5IGhlcmUuPC90Pg0K
ICAgICAgICA8dD5OZWl0aGVyIDx4cmVmIHRhcmdldD0iUkZDMTAzNCIgcGFnZW5vPSJmYWxzZSIg
Zm9ybWF0PSJkZWZhdWx0IiAvPiBub3IgPHhyZWYgdGFyZ2V0PSJSRkMxMDM1IiBwYWdlbm89ImZh
bHNlIiBmb3JtYXQ9ImRlZmF1bHQiIC8+IGltcG9zZSBhbnkgb3RoZXIgcmVzdHJpY3Rpb25zIHVw
b24gd2hhdCBraW5kcyBvZiBuYW1lcyBjYW4gYmUgc3RvcmVkIGluIHRoZSBETlMuICBUaGlzIHNw
ZWNpZmljYXRpb24sIGhvd2V2ZXIsIG9ubHkgYWxsb3dzIHRoZSB1c2Ugb2YgbmFtZXMgdGhhdCBj
YW4gYmUgaW5mZXJyZWQgZnJvbSB0aGUgQUJORiBncmFtbWFyIGdpdmVuIGZvciB0aGUgImhvc3Ru
YW1lIi48L3Q+DQogICAgICA8L3NlY3Rpb24+DQogICAgICA8c2VjdGlvbiB0aXRsZT0iSE9TVCBj
b21tYW5kIHNlbWFudGljcyIgdG9jPSJkZWZhdWx0Ij4NCiAgICAgICAgPHQ+VXBvbiByZWNlaXZp
bmcgdGhlIEhPU1QgY29tbWFuZCwgYmVmb3JlIGF1dGhlbnRpY2F0aW5nIHRoZSB1c2VyLVBJLCBh
IHNlcnZlci1GVFAgcHJvY2VzcyBTSE9VTEQgdmFsaWRhdGUgdGhhdCB0aGUgaG9zdG5hbWUgZ2l2
ZW4gcmVwcmVzZW50cyBhIHZhbGlkIHZpcnR1YWwgaG9zdCBmb3IgdGhhdCBzZXJ2ZXIsIGFuZCwg
aWYgaXQgaXMgdmFsaWQsIGVzdGFibGlzaCB0aGUgYXBwcm9wcmlhdGUgZW52aXJvbm1lbnQgZm9y
IHRoYXQgdmlydHVhbCBob3N0LiAgVGhlIHJlc3VsdGFudCBhY3Rpb25zIG5lZWRlZCB0byBjcmVh
dGUgdGhhdCBlbnZpcm9ubWVudCBhcmUgbm90IHNwZWNpZmllZCBoZXJlLCBhbmQgbWF5IHJhbmdl
IGZyb20gZG9pbmcgbm90aGluZyBhdCBhbGwsIHRvIHBlcmZvcm1pbmcgYSBzaW1wbGUgY2hhbmdl
IG9mIHdvcmtpbmcgZGlyZWN0b3J5LCBjaGFuZ2luZyBhdXRoZW50aWNhdGlvbiBzY2hlbWVzIGFu
ZC9vciB1c2VybmFtZSBhbmQgcGFzc3dvcmQgbGlzdHMsIG9yIG1ha2luZyBtdWNoIG1vcmUgZWxh
Ym9yYXRlIHN0YXRlIGNoYW5nZXMgLSBzdWNoIGFzIGNyZWF0aW5nIGlzb2xhdGVkIGVudmlyb25t
ZW50cyBmb3IgZWFjaCBGVFAgc2Vzc2lvbi48L3Q+DQogICAgICAgIDx0PlRoZSAiMjIwIiByZXBs
eSBjb2RlIGZvciB0aGUgSE9TVCBjb21tYW5kIGlzIHRoZSBzYW1lIGFzIHRoZSBjb2RlIHRoYXQg
aXMgdXNlZCBpbiB0aGUgaW5pdGlhbCAid2VsY29tZSIgbWVzc2FnZSB0aGF0IGlzIHNlbnQgYWZ0
ZXIgdGhlIGNvbm5lY3Rpb24gaXMgZXN0YWJsaXNoZWQuPC90Pg0KICAgICAgICA8dD5JZiB0aGUg
aG9zdG5hbWUgc3BlY2lmaWVkIHdvdWxkIG5vcm1hbGx5IGJlIGFjY2VwdGFibGUsIGJ1dCBmb3Ig
YW55IHJlYXNvbiBpcyB0ZW1wb3JhcmlseSB1bmF2YWlsYWJsZSwgdGhlIHNlcnZlci1GVFAgcHJv
Y2VzcyBTSE9VTEQgcmVwbHkgdG8gdGhlIEhPU1QgY29tbWFuZCB3aXRoIGEgNDIxIHJlcGx5IGFu
ZCBjbG9zZSB0aGUgY29ubmVjdGlvbi4gIEluIHRoaXMgcGFydGljdWxhciBzaXR1YXRpb24sIHRo
ZSBzZXJ2ZXItRlRQIHByb2Nlc3MgTUFZIGNob29zZSB0byBrZWVwIHRoZSBjb25uZWN0aW9uIG9w
ZW4gaW4gb3JkZXIgdG8gYWxsb3cgdGhlIHVzZXItUEkgYW4gb3Bwb3J0dW5pdHkgdG8gY2hvb3Nl
IGFub3RoZXIgdmlydHVhbCBob3N0IHdpdGggYSBzdWJzZXF1ZW50IEhPU1QgY29tbWFuZC48L3Q+
DQogICAgICAgIDx0PklmIHRoZSBob3N0bmFtZSBzcGVjaWZpZWQgaXMgdW5rbm93biBhdCB0aGUg
c2VydmVyLCBvciBpZiB0aGUgc2VydmVyIGlzIG90aGVyd2lzZSB1bndpbGxpbmcgdG8gdHJlYXQg
dGhlIHBhcnRpY3VsYXIgY29ubmVjdGlvbiBhcyBhIGNvbm5lY3Rpb24gdG8gdGhlIGhvc3RuYW1l
IHNwZWNpZmllZCwgdGhlIHNlcnZlciBTSE9VTEQgcmVzcG9uZCB3aXRoIGEgNTA0IHJlcGx5Ljwv
dD4NCiAgICAgICAgPHNlY3Rpb24gdGl0bGU9IlJFSU4gY29tbWFuZCBzZW1hbnRpY3MiIHRvYz0i
ZGVmYXVsdCI+DQogICAgICAgICAgPHQ+QXMgc3BlY2lmaWVkIGluIDx4cmVmIHRhcmdldD0iUkZD
MDk1OSIgcGFnZW5vPSJmYWxzZSIgZm9ybWF0PSJkZWZhdWx0IiAvPiwgdGhlIFJFSU4gY29tbWFu
ZCByZXR1cm5zIHRoZSBzdGF0ZSBvZiB0aGUgY29ubmVjdGlvbiB0byB3aGF0IGl0IHdhcyBpbW1l
ZGlhdGVseSBhZnRlciB0aGUgdHJhbnNwb3J0IGNvbm5lY3Rpb24gd2FzIG9wZW5lZC4gIFRoaXMg
c3BlY2lmaWNhdGlvbiBtYWtlcyBubyBjaGFuZ2VzIHRvIHRoYXQgYmVoYXZpb3IuICBUaGUgZWZm
ZWN0IG9mIGEgSE9TVCBjb21tYW5kIE1VU1QgYmUgcmVzZXQgaWYgYSBSRUlOIGNvbW1hbmQgaXMg
cGVyZm9ybWVkLCBhbmQgYSBuZXcgSE9TVCBjb21tYW5kIE1VU1QgYmUgaXNzdWVkIGluIG9yZGVy
IHRvIGNvbm5lY3QgdG8gYSB2aXJ0dWFsIGhvc3QuPC90Pg0KICAgICAgICA8L3NlY3Rpb24+DQog
ICAgICAgIDxzZWN0aW9uIHRpdGxlPSJVc2VyLVBJIHVzYWdlIG9mIEhPU1QiIHRvYz0iZGVmYXVs
dCI+DQogICAgICAgICAgPHQ+QSB1c2VyLVBJIHRoYXQgY29uZm9ybXMgdG8gdGhpcyBzcGVjaWZp
Y2F0aW9uIE1VU1Qgc2VuZCB0aGUgSE9TVCBjb21tYW5kIGFmdGVyIG9wZW5pbmcgdGhlIHRyYW5z
cG9ydCBjb25uZWN0aW9uLCBvciBhZnRlciBhbnkgUkVJTiBjb21tYW5kLCBiZWZvcmUgYXR0ZW1w
dGluZyB0byBhdXRoZW50aWNhdGUgdGhlIHVzZXIgd2l0aCB0aGUgVVNFUiBjb21tYW5kLiAgVGhl
IGZvbGxvd2luZyBleGFtcGxlIGlsbHVzdHJhdGVzIHdoYXQgYSB0eXBpY2FsIGxvZ2luIHNlcXVl
bmNlIG1pZ2h0IGxvb2sgbGlrZSB3aGVuIHRoZSBIT1NUIGNvbW1hbmQgaXMgdXNlZDo8L3Q+DQog
ICAgICAgICAgPHQ+DQogICAgICAgICAgICA8ZmlndXJlIHRpdGxlPSIiIHN1cHByZXNzLXRpdGxl
PSJmYWxzZSIgYWxpZ249ImxlZnQiIGFsdD0iIiB3aWR0aD0iIiBoZWlnaHQ9IiI+DQogICAgICAg
ICAgICAgIDxhcnR3b3JrIHhtbDpzcGFjZT0icHJlc2VydmUiIG5hbWU9IiIgdHlwZT0iIiBhbGln
bj0ibGVmdCIgYWx0PSIiIHdpZHRoPSIiIGhlaWdodD0iIj48IVtDREFUQVsgICAgIEM+IEhPU1Qg
ZnRwLmV4YW1wbGUuY29tDQogICAgIFM+IDIyMCBIb3N0IGFjY2VwdGVkDQogICAgIEM+IFVTRVIg
Zm9vDQogICAgIFM+IDMzMSBQYXNzd29yZCByZXF1aXJlZA0KICAgICBDPiBQQVNTIGJhcg0KICAg
ICBTPiAyMzAgVXNlciBsb2dnZWQgaW5dXT48L2FydHdvcms+DQogICAgICAgICAgICA8L2ZpZ3Vy
ZT4NCiAgICAgICAgICA8L3Q+DQogICAgICAgICAgPHQ+SWYgYSB1c2VyLVBJIHNlbmRzIGFuIGFk
ZGl0aW9uYWwgSE9TVCBjb21tYW5kIGJlZm9yZSBhdHRlbXB0aW5nIHRvIGF1dGhlbnRpY2F0ZSB0
aGUgdXNlciwgYSBzZXJ2ZXItRlRQIHByb2Nlc3MgdGhhdCBjb25mb3JtcyB0byB0aGlzIHNwZWNp
ZmljYXRpb24gTVVTVCB0cmVhdCB0aGUgYWRkaXRpb25hbCBIT1NUIGNvbW1hbmQgYXMgdGhvdWdo
IGEgUkVJTiBjb21tYW5kIHdhcyBzZW50LCBhbmQgcmVzZXQgdGhlIHVzZXItUEkgdG8gdGhlIHN0
YXRlIHRoYXQgZXhpc3RlZCBhZnRlciB0aGUgVENQIGNvbm5lY3Rpb24gd2FzIGZpcnN0IGVzdGFi
bGlzaGVkLiAgRm9yIGV4YW1wbGUsIGlmIGEgdXNlciBzcGVjaWZpZXMgdGhlIHdyb25nIHZpcnR1
YWwgaG9zdCBieSBtaXN0YWtlLCBzZW5kaW5nIGEgc3Vic2VxdWVudCBIT1NUIGNvbW1hbmQgd2ls
bCByZWN0aWZ5IHRoZSBlcnJvci4gIFRoZSBmb2xsb3dpbmcgZXhhbXBsZSBpbGx1c3RyYXRlcyB3
aGF0IHRoZSBsb2dpbiBzZXF1ZW5jZSBtaWdodCBsb29rIGxpa2Ugd2hlbiB0aGUgSE9TVCBjb21t
YW5kIGlzIHNlbnQgdHdpY2UgYmVmb3JlIGEgdXNlciBoYXMgYmVlbiBhdXRoZW50aWNhdGVkOjwv
dD4NCiAgICAgICAgICA8dD4NCiAgICAgICAgICAgIDxmaWd1cmUgdGl0bGU9IiIgc3VwcHJlc3Mt
dGl0bGU9ImZhbHNlIiBhbGlnbj0ibGVmdCIgYWx0PSIiIHdpZHRoPSIiIGhlaWdodD0iIj4NCiAg
ICAgICAgICAgICAgPGFydHdvcmsgeG1sOnNwYWNlPSJwcmVzZXJ2ZSIgbmFtZT0iIiB0eXBlPSIi
IGFsaWduPSJsZWZ0IiBhbHQ9IiIgd2lkdGg9IiIgaGVpZ2h0PSIiPjwhW0NEQVRBWyAgICAgQz4g
SE9TVCBmb28uZXhhbXBsZS5jb20NCiAgICAgUz4gMjIwIEhvc3QgYWNjZXB0ZWQNCiAgICAgQz4g
SE9TVCBiYXIuZXhhbXBsZS5jb20NCiAgICAgUz4gMjIwIEhvc3QgYWNjZXB0ZWQNCiAgICAgQz4g
VVNFUiBmb28NCiAgICAgUz4gMzMxIFBhc3N3b3JkIHJlcXVpcmVkDQogICAgIEM+IFBBU1MgYmFy
DQogICAgIFM+IDIzMCBVc2VyIGxvZ2dlZCBpbl1dPjwvYXJ0d29yaz4NCiAgICAgICAgICAgIDwv
ZmlndXJlPg0KICAgICAgICAgIDwvdD4NCiAgICAgICAgICA8dD5UaGUgSE9TVCBjb21tYW5kIGNh
biBiZSB1c2VkIGluIGNvbWJpbmF0aW9uIHdpdGggdGhlIEFDQ1QgY29tbWFuZCB0byBkaWZmZXJl
bnRpYXRlIGJldHdlZW4gYSB1c2VyJ3MgdmFyaW91cyBhY2NvdW50cyBvbiBhIHNwZWNpZmljIHZp
cnR1YWwgaG9zdC4gIEluIHRoaXMgc2NlbmFyaW8sIHRoZSB1c2VyLVBJIHNlbmRzIGEgSE9TVCBj
b21tYW5kIHdoaWNoIHRoZSBzZXJ2ZXItUEkgdXNlcyB0byByb3V0ZSBhY3Rpdml0eSB0byB0aGUg
Y29ycmVjdCB2aXJ0dWFsIGhvc3Q7IHRoZSB1c2VyLVBJIHNlbmRzIGNyZWRlbnRpYWxzIHVzaW5n
IHRoZSBVU0VSIGFuZCBQQVNTIGNvbW1hbmRzIHdoaWNoIHRoZSBzZXJ2ZXItUEkgdmFsaWRhdGVz
OyB0aGVuLCB0aGUgdXNlci1QSSBzZW5kcyBhbiBBQ0NUIGNvbW1hbmQgdG8gc3BlY2lmeSBhbnkg
YWRkaXRpb25hbCBhY2NvdW50IGluZm9ybWF0aW9uIGZvciB0aGUgc2VydmVyLVBJIGltcGxlbWVu
dGF0aW9uLiAgVGhlIGZvbGxvd2luZyBleGFtcGxlIGlsbHVzdHJhdGVzIGEgc2VxdWVudGlhbCBz
ZXJpZXMgb2YgY2xpZW50IGNvbW1hbmRzIHRoYXQgc3BlY2lmeSBib3RoIGEgSE9TVCBhbmQgQUND
VCwgd2l0aCB0aGUgc2VydmVyIHJlc3BvbnNlcyBvbWl0dGVkIGZvciBicmV2aXR5OjwvdD4NCiAg
ICAgICAgICA8dD4NCiAgICAgICAgICAgIDxmaWd1cmUgdGl0bGU9IiIgc3VwcHJlc3MtdGl0bGU9
ImZhbHNlIiBhbGlnbj0ibGVmdCIgYWx0PSIiIHdpZHRoPSIiIGhlaWdodD0iIj4NCiAgICAgICAg
ICAgICAgPGFydHdvcmsgeG1sOnNwYWNlPSJwcmVzZXJ2ZSIgbmFtZT0iIiB0eXBlPSIiIGFsaWdu
PSJsZWZ0IiBhbHQ9IiIgd2lkdGg9IiIgaGVpZ2h0PSIiPjwhW0NEQVRBWyAgICAgQz4gSE9TVCBm
dHAuZXhhbXBsZS5jb20NCiAgICAgQz4gVVNFUiBmb28NCiAgICAgQz4gUEFTUyBiYXINCiAgICAg
Qz4gQUNDVCBwcm9qZWN0MV1dPjwvYXJ0d29yaz4NCiAgICAgICAgICAgIDwvZmlndXJlPg0KICAg
ICAgICAgIDwvdD4NCiAgICAgICAgICA8dD5UaGlzIGlzIGFsc28gdHJ1ZSB3aGVuIHRoZSBIT1NU
IGNvbW1hbmQgaXMgdXNlZCB3aXRoIHRoZSBBVVRIIGFuZCBBREFUIGNvbW1hbmRzIHRoYXQgYXJl
IGRpc2N1c3NlZCBpbiA8eHJlZiB0YXJnZXQ9IlJGQzIyMjgiIHBhZ2Vubz0iZmFsc2UiIGZvcm1h
dD0iZGVmYXVsdCIgLz4gYW5kIDx4cmVmIHRhcmdldD0iUkZDNDIxNyIgcGFnZW5vPSJmYWxzZSIg
Zm9ybWF0PSJkZWZhdWx0IiAvPi4gIEluIHRoaXMgc2NlbmFyaW8sIHRoZSB1c2VyLVBJIHNlbmRz
IGEgSE9TVCBjb21tYW5kIHdoaWNoIHRoZSBzZXJ2ZXItUEkgdXNlcyB0byByb3V0ZSBhY3Rpdml0
eSB0byB0aGUgY29ycmVjdCB2aXJ0dWFsIGhvc3QsIHRoZW4gdGhlIHVzZXItUEkgdXNlcyB0aGUg
QVVUSCBhbmQgQURBVCBjb21tYW5kcyB0byBuZWdvdGlhdGUgdGhlIHNlY3VyaXR5IG1lY2hhbmlz
bSBhbmQgcmVsZXZhbnQgYXV0aGVudGljYXRpb24gdG9rZW4ocykgd2l0aCB0aGUgc2VydmVyLVBJ
LCB0aGVuIHRoZSB1c2VyLVBJIHNlbmRzIHVzZXIgY3JlZGVudGlhbHMgdXNpbmcgdGhlIFVTRVIg
YW5kIFBBU1MgY29tbWFuZHMgd2hpY2ggdGhlIHNlcnZlci1QSSB2YWxpZGF0ZXMuICBBZnRlciB3
aGljaCB0aGUgdXNlci1QSSBNQVkgc2VuZCBhbiBBQ0NUIGNvbW1hbmQgdG8gc3BlY2lmeSBhbnkg
YWRkaXRpb25hbCBhY2NvdW50IGluZm9ybWF0aW9uIGZvciB0aGUgc2VydmVyLVBJIGltcGxlbWVu
dGF0aW9uLiAgVGhlIGZvbGxvd2luZyBleGFtcGxlIGlsbHVzdHJhdGVzIGEgc2VxdWVudGlhbCBz
ZXJpZXMgb2YgY2xpZW50IGNvbW1hbmRzIHRoYXQgc3BlY2lmeSBib3RoIGEgSE9TVCBhbmQgQUND
VCB3aGVuIHVzZWQgaW4gY29uanVuY3Rpb24gd2l0aCB0aGUgc2VjdXJpdHkgY29tbWFuZHMgdGhh
dCBhcmUgZGlzY3Vzc2VkIGluIDx4cmVmIHRhcmdldD0iUkZDMjIyOCIgcGFnZW5vPSJmYWxzZSIg
Zm9ybWF0PSJkZWZhdWx0IiAvPiBhbmQgPHhyZWYgdGFyZ2V0PSJSRkM0MjE3IiBwYWdlbm89ImZh
bHNlIiBmb3JtYXQ9ImRlZmF1bHQiIC8+LCB3aXRoIHRoZSBzZXJ2ZXIgcmVzcG9uc2VzIG9taXR0
ZWQgZm9yIGJyZXZpdHk6PC90Pg0KICAgICAgICAgIDx0Pg0KICAgICAgICAgICAgPGZpZ3VyZSB0
aXRsZT0iIiBzdXBwcmVzcy10aXRsZT0iZmFsc2UiIGFsaWduPSJsZWZ0IiBhbHQ9IiIgd2lkdGg9
IiIgaGVpZ2h0PSIiPg0KICAgICAgICAgICAgICA8YXJ0d29yayB4bWw6c3BhY2U9InByZXNlcnZl
IiBuYW1lPSIiIHR5cGU9IiIgYWxpZ249ImxlZnQiIGFsdD0iIiB3aWR0aD0iIiBoZWlnaHQ9IiI+
PCFbQ0RBVEFbICAgICBDPiBIT1NUIGZ0cC5leGFtcGxlLmNvbQ0KICAgICBDPiBBVVRIIDxtZWNo
YW5pc20tbmFtZT4NCiAgICAgQz4gQURBVCA8YmFzZTY0ZGF0YT4NCiAgICAgQz4gVVNFUiBmb28N
CiAgICAgQz4gUEFTUyBiYXINCiAgICAgQz4gQUNDVCBwcm9qZWN0MV1dPjwvYXJ0d29yaz4NCiAg
ICAgICAgICAgIDwvZmlndXJlPg0KICAgICAgICAgIDwvdD4NCiAgICAgICAgPC9zZWN0aW9uPg0K
ICAgICAgICA8c2VjdGlvbiB0aXRsZT0iU3RhdGUgRGlhZ3JhbXMiIHRvYz0iZGVmYXVsdCI+DQog
ICAgICAgICAgPHQ+VGhlIHN0YXRlIGRpYWdyYW1zIGluIHRoaXMgc2VjdGlvbiBpbGx1c3RyYXRl
IHR5cGljYWwgc2VxdWVuY2VzIGZvciBjb21tYW5kIGFuZCByZXBseSBpbnRlcmNoYW5nZSBiZXR3
ZWVuIHRoZSB1c2VyLVBJIGFuZCBzZXJ2ZXItUEkuICBUaGVzZSBkaWFncmFtcyBhcmUgbW9kZWxl
ZCBvbiB0aGUgc2ltaWxhciBkaWFncmFtcyBpbiBzZWN0aW9uIDYgb2YgPHhyZWYgdGFyZ2V0PSJS
RkMwOTU5IiBwYWdlbm89ImZhbHNlIiBmb3JtYXQ9ImRlZmF1bHQiIC8+LjwvdD4NCiAgICAgICAg
ICA8dD5JbiBlYWNoIGRpYWdyYW0sIHRoZSAoQikgImJlZ2luIiBzdGF0ZSBpcyBhc3N1bWVkIHRv
IG9jY3VyIGFmdGVyIHRoZSB0cmFuc3BvcnQgY29ubmVjdGlvbiBoYXMgb3BlbmVkLCBvciBhZnRl
ciBhIFJFSU4gY29tbWFuZCBoYXMgc3VjY2VlZGVkLiAgT3RoZXIgY29tbWFuZHMgKHN1Y2ggYXMg
RkVBVCA8eHJlZiB0YXJnZXQ9IlJGQzIzODkiIHBhZ2Vubz0iZmFsc2UiIGZvcm1hdD0iZGVmYXVs
dCIgLz4pIHRoYXQgcmVxdWlyZSBubyBhdXRoZW50aWNhdGlvbiBtYXkgaGF2ZSBpbnRlcnZlbmVk
LjwvdD4NCiAgICAgICAgICA8dD5BZGRpdGlvbmFsbHksIGEgdGhyZWUtZGlnaXQgcmVwbHkgaW5k
aWNhdGVzIGEgcHJlY2lzZSBzZXJ2ZXIgcmVwbHkgY29kZS4gIEEgc2luZ2xlIGRpZ2l0IG9uIGEg
cmVwbHkgcGF0aCBpbmRpY2F0ZXMgYW55IHNlcnZlciByZXBseSB0aGF0IGJlZ2lucyB3aXRoIHRo
YXQgZGlnaXQsIGV4Y2VwdCB3aGVyZSBhIHByZWNpc2Ugc2VydmVyIHJlcGx5IGNvZGUgaXMgZGVm
aW5lZCBvbiBhbm90aGVyIHBhdGguICBGb3IgZXhhbXBsZSwgYSBzaW5nbGUgZGlnaXQgIjUiIHdp
bGwgYXBwbHkgdG8gIjUwMCIsICI1MDEiLCAiNTAyIiwgZXRjLiwgd2hlbiB0aG9zZSByZXBseSBj
b2RlcyBhcmUgbm90IGV4cHJlc3NseSBkZWZpbmVkIGluIHRoZSBkaWFncmFtLiAgRm9yIGVhY2gg
Y29tbWFuZCB0aGVyZSBhcmUgdGhyZWUgcG9zc2libGUgb3V0Y29tZXM6IHN1Y2Nlc3MgKFMpLCBm
YWlsdXJlIChGKSwgYW5kIGVycm9yIChFKS4gIEluIHRoZSBzdGF0ZSBkaWFncmFtcyBiZWxvdyB3
ZSB1c2UgdGhlIHN5bWJvbCBCIGZvciAiYmVnaW4iLCBhbmQgdGhlIHN5bWJvbCBXIGZvciAid2Fp
dCBmb3IgcmVwbHkiLjwvdD4NCiAgICAgICAgICA8dD5JbiBlYWNoIG9mIHRoZXNlIGRpYWdyYW1z
LCBhIFJFSU4gY29tbWFuZCB3aWxsIHJldHVybiB0aGUgZGlhZ3JhbSB0byB0aGUgKEIpICJiZWdp
biIgc3RhdGUuPC90Pg0KICAgICAgICAgIDx0Pg0KICAgICAgICAgICAgPGZpZ3VyZSB0aXRsZT0i
RmlndXJlIDE6IFR5cGljYWwgbG9naW4gc2VxdWVuY2Ugd2l0aCBIT1NUIGNvbW1hbmQiIHN1cHBy
ZXNzLXRpdGxlPSJmYWxzZSIgYWxpZ249ImxlZnQiIGFsdD0iIiB3aWR0aD0iIiBoZWlnaHQ9IiI+
DQogICAgICAgICAgICAgIDxwcmVhbWJsZT5UaGUgc3RhdGUgZGlhZ3JhbSBpbiBGaWd1cmUgMSBz
aG93cyBhIHR5cGljYWwgc2VxdWVuY2Ugb2YgZmxvdyBvZiBjb250cm9sIHdoZW4gSE9TVCBpcyB1
c2VkIHdpdGggVVNFUiBhbmQgUEFTUyB0byBsb2cgaW4gdG8gYSBwYXJ0aWN1bGFyIEZUUCB2aXJ0
dWFsIGhvc3QuPC9wcmVhbWJsZT4NCiAgICAgICAgICAgICAgPGFydHdvcmsgeG1sOnNwYWNlPSJw
cmVzZXJ2ZSIgbmFtZT0iIiB0eXBlPSIiIGFsaWduPSJsZWZ0IiBhbHQ9IiIgd2lkdGg9IiIgaGVp
Z2h0PSIiPjwhW0NEQVRBWw0KICAgICAgICAgICArLS0tKyAgIEhPU1QgICAgKy0tLSsgMSwzLDUN
CiAgICAgICAgICAgfCBCIHwtLS0tLS0tLS0tPnwgVyB8LS0tLS0tLS0tLS0tLS0tLS0NCiAgICAg
ICAgICAgKy0tLSsgICAgICAgICAgICstLS0rICAgICAgICAgICAgICAgICB8DQogICAgICAgICAg
ICAgICAgICAgICAgICAgICAgfCB8ICAgICAgICAgICAgICAgICAgfA0KICAgICAgICAgICAgICAg
ICAgMiw1MDAsNTAyIHwgfCA0LDUwMSw1MDMsNTA0ICAgIHwNCiAgICAgICAgICAgICAgLS0tLS0t
LS0tLS0tLS0gICAtLS0tLS0tLS0tLSAgICAgICB8DQogICAgICAgICAgICAgfCAgICAgICAgICAg
ICAgICAgICAgICAgICAgICB8ICAgICAgVg0KICAgICAgICAgICAgIFYgICAgICAgICAgICAgICAg
ICAgMSAgICAgICAgfCAgICArLS0tKw0KICAgICAgICAgICArLS0tKyAgIFVTRVIgICAgKy0tLSst
LS0tLS0tLS0tLS0tLT58IEUgfA0KICAgICAgICAgICB8ICAgfC0tLS0tLS0tLS0+fCBXIHwgMiAg
ICAgICAgfCAgICArLS0tKw0KICAgICAgICAgICArLS0tKyAgICAgICAgICAgKy0tLSstLS0tLS0t
ICAgfCAgICAgIF4NCiAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IHwgICAgICAgIHwgIHwg
ICAgICB8DQogICAgICAgICAgICAgICAgICAgICAgICAgIDMgfCB8IDQsNSAgICB8ICB8ICAgICAg
fA0KICAgICAgICAgICAgICAtLS0tLS0tLS0tLS0tLSAgIC0tLS0tICAgfCAgfCAgICAgIHwNCiAg
ICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgIHwgIHwgIHwgICAgICB8DQogICAgICAg
ICAgICAgfCAgICAgICAgICAgICAgICAtLS0tLS0tLS0tLS0tLS0tLS0tDQogICAgICAgICAgICAg
fCAgICAgICAgICAgICAgMXwgICAgICB8ICB8ICB8DQogICAgICAgICAgICAgViAgICAgICAgICAg
ICAgIHwgICAgICB8ICAgLS0tLS0tPistLS0rDQogICAgICAgICAgICstLS0rICAgUEFTUyAgICAr
LS0tKyAyICB8ICAgICB8ICAgIHwgUyB8DQogICAgICAgICAgIHwgICB8LS0tLS0tLS0tLT58IFcg
fC0tLS0tLS0tLS0tLS0tPistLS0rDQogICAgICAgICAgICstLS0rICAgICAgICAgICArLS0tKyAg
ICB8ICAgICB8DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICAgICB8ICAgICB8DQog
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIHw0LDUgICB8ICAgICB8DQogICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIHwgICAgICB8ICAgICAgLS0tPistLS0rDQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIHwgICAgICAgLS0tLS0tLS0tPnwgRiB8DQogICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAtLS0tLS0tLS0tLS0tLS0tPistLS0rXV0+PC9hcnR3b3JrPg0KICAgICAgICAg
ICAgPC9maWd1cmU+DQogICAgICAgICAgPC90Pg0KICAgICAgICAgIDx0Pg0KICAgICAgICAgICAg
PGZpZ3VyZSB0aXRsZT0iRmlndXJlIDI6IExvZ2luIHNlcXVlbmNlIHdpdGggcmVwZWF0ZWQgSE9T
VCBjb21tYW5kIiBzdXBwcmVzcy10aXRsZT0iZmFsc2UiIGFsaWduPSJsZWZ0IiBhbHQ9IiIgd2lk
dGg9IiIgaGVpZ2h0PSIiPg0KICAgICAgICAgICAgICA8cHJlYW1ibGU+VGhlIHN0YXRlIGRpYWdy
YW0gaW4gRmlndXJlIDIgc2hvd3MgdGhlIGZsb3cgb2YgY29udHJvbCB3aGVuIGEgSE9TVCBjb21t
YW5kIGlzIHNlbnQgYWZ0ZXIgYSB1c2VyIGhhcyBhbHJlYWR5IHN1Y2Nlc3NmdWxseSBsb2dnZWQg
aW4gdG8gYSB2aXJ0dWFsIGhvc3Qgd2l0aCBVU0VSIGFuZCBQQVNTLjwvcHJlYW1ibGU+DQogICAg
ICAgICAgICAgIDxhcnR3b3JrIHhtbDpzcGFjZT0icHJlc2VydmUiIG5hbWU9IiIgdHlwZT0iIiBh
bGlnbj0ibGVmdCIgYWx0PSIiIHdpZHRoPSIiIGhlaWdodD0iIj48IVtDREFUQVsNCiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
fA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgfA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICBWICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgfA0KICAgICAgICAgICArLS0tKyAgIEhPU1QgICAgKy0tLSsgMSwzLDUgICAg
ICAgICAgICAgICAgICAgICAgfA0KICAgICAgICAgICB8IEIgfC0tLS0tLS0tLS0+fCBXIHwtLS0t
LS0tLS0tLS0tLS0tLSAgICAgICAgICAgfA0KICAgICAgICAgICArLS0tKyAgICAgICAgICAgKy0t
LSsgICAgICAgICAgICAgICAgIHwgICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIHwgfCAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAg
Miw1MDAsNTAyIHwgfCA0LDUwMSw1MDMsNTA0ICAgIHwgICAgICAgICAgfA0KICAgICAgICAgICAg
ICAtLS0tLS0tLS0tLS0tLSAgIC0tLS0tLS0tLS0tICAgICAgIHwgICAgICAgICAgfA0KICAgICAg
ICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgIFYgICAgICAgICAgfA0K
ICAgICAgICAgICAgIFYgICAgICAgICAgICAgICAgICAgMSAgICAgICAgfCAgICArLS0tKyAgICAg
ICAgfA0KICAgICAgICAgICArLS0tKyAgIFVTRVIgICAgKy0tLSstLS0tLS0tLS0tLS0tLT58IEUg
fCAgICAgICAgfA0KICAgICAgICAgICB8ICAgfC0tLS0tLS0tLS0+fCBXIHwgMiAgICAgICAgfCAg
ICArLS0tKyAgICAgICAgfA0KICAgICAgICAgICArLS0tKyAgICAgICAgICAgKy0tLSstLS0tLS0t
ICAgfCAgICAgIF4gICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgfCAg
ICAgICAgfCAgfCAgICAgIHwgICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAgICAgICAgICAz
IHwgfCA0LDUgICAgfCAgfCAgICAgIHwgICAgICAgICAgfA0KICAgICAgICAgICAgICAtLS0tLS0t
LS0tLS0tLSAgIC0tLS0tLSAgfCAgfCAgICAgIHwgICAgICAgICAgfA0KICAgICAgICAgICAgIHwg
ICAgICAgICAgICAgICAgICAgICAgfCAgfCAgfCAgICAgIHwgICAgICAgICAgfA0KICAgICAgICAg
ICAgIHwgICAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0tLS0tLSAgICAgICAgICAgfA0KICAg
ICAgICAgICAgIHwgICAgICAgICAgICAgIDF8ICAgICAgfCAgfCAgfCAgICAgICAgICAgICAgICAg
fA0KICAgICAgICAgICAgIFYgICAgICAgICAgICAgICB8ICAgICAgfCAgIC0tLS0tLT4rLS0tKyAg
SE9TVCAgfA0KICAgICAgICAgICArLS0tKyAgIFBBU1MgICAgKy0tLSsgMiAgfCAgICAgfCAgICB8
IFMgfC0tLS0tLS0tDQogICAgICAgICAgIHwgICB8LS0tLS0tLS0tLT58IFcgfC0tLS0tLS0tLS0t
LS0tPistLS0rDQogICAgICAgICAgICstLS0rICAgICAgICAgICArLS0tKyAgICB8ICAgICB8DQog
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICAgICB8ICAgICB8DQogICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIHw0LDUgICB8ICAgICB8DQogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIHwgICAgICB8ICAgICAgLS0tPistLS0rDQogICAgICAgICAgICAgICAgICAgICAgICAgICAg
IHwgICAgICAgLS0tLS0tLS0tPnwgRiB8DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAt
LS0tLS0tLS0tLS0tLS0tPistLS0rXV0+PC9hcnR3b3JrPg0KICAgICAgICAgICAgPC9maWd1cmU+
DQogICAgICAgICAgPC90Pg0KICAgICAgICAgIDx0Pg0KICAgICAgICAgICAgPGZpZ3VyZSB0aXRs
ZT0iRmlndXJlIDM6IExvZ2luIHNlcXVlbmNlIHdpdGggSE9TVCBhbmQgQUNDVCBjb21tYW5kcyIg
c3VwcHJlc3MtdGl0bGU9ImZhbHNlIiBhbGlnbj0ibGVmdCIgYWx0PSIiIHdpZHRoPSIiIGhlaWdo
dD0iIj4NCiAgICAgICAgICAgICAgPHByZWFtYmxlPkFmdGVyIGEgdXNlciBoYXMgbG9nZ2VkIGlu
LCBhbiBhZGRpdGlvbmFsIGFjY291bnQgbWF5IGJlIHJlcXVpcmVkIGJ5IHRoZSBzZXJ2ZXIgYW5k
IHNwZWNpZmllZCBieSB0aGUgY2xpZW50IGJ5IHVzaW5nIEFDQ1QgY29tbWFuZC4gIFdpdGggdGhp
cyBpbiBtaW5kLCB0aGUgc3RhdGUgZGlhZ3JhbSBpbiBGaWd1cmUgMyBzaG93cyBhIHR5cGljYWwg
c2VxdWVuY2Ugb2YgZmxvdyBvZiBjb250cm9sIHdoZW4gSE9TVCBpcyB1c2VkIHdpdGggVVNFUiBh
bmQgUEFTUyB0byBsb2cgaW4gdG8gYW4gRlRQIHZpcnR1YWwgaG9zdCBhbmQgQUNDVCBpcyB1c2Vk
IHRvIHNwZWNpZnkgYW4gYWNjb3VudC48L3ByZWFtYmxlPg0KICAgICAgICAgICAgICA8YXJ0d29y
ayB4bWw6c3BhY2U9InByZXNlcnZlIiBuYW1lPSIiIHR5cGU9IiIgYWxpZ249ImxlZnQiIGFsdD0i
IiB3aWR0aD0iIiBoZWlnaHQ9IiI+PCFbQ0RBVEFbDQogICAgICAgICAgICstLS0rICAgSE9TVCAg
ICArLS0tKyAxLDMsNQ0KICAgICAgICAgICB8IEIgfC0tLS0tLS0tLS0+fCBXIHwtLS0tLS0tLS0t
LS0tLS0tLQ0KICAgICAgICAgICArLS0tKyAgICAgICAgICAgKy0tLSsgICAgICAgICAgICAgICAg
IHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IHwgICAgICAgICAgICAgICAgICB8DQog
ICAgICAgICAgICAgICAgICAyLDUwMCw1MDIgfCB8IDQsNTAxLDUwMyw1MDQgICAgfA0KICAgICAg
ICAgICAgICAtLS0tLS0tLS0tLS0tLSAgIC0tLS0tLS0tLS0tLS0gICAgIHwNCiAgICAgICAgICAg
ICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICB8DQogICAgICAgICAgICAgViAg
ICAgICAgICAgICAgICAgICAxICAgICAgICAgIHwgICAgVg0KICAgICAgICAgICArLS0tKyAgIFVT
RVIgICAgKy0tLSstLS0tLS0tLS0tLS0tLT4rLS0tKw0KICAgICAgICAgICB8ICAgfC0tLS0tLS0t
LS0+fCBXIHwgMiAgICAgICAtLS0tLT58IEUgfA0KICAgICAgICAgICArLS0tKyAgICAgICAgICAg
Ky0tLSstLS0tLS0gIHwgIC0tLT4rLS0tKw0KICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwg
fCAgICAgICB8IHwgfCB8DQogICAgICAgICAgICAgICAgICAgICAgICAgIDMgfCB8IDQsNSAgIHwg
fCB8IHwNCiAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0gICAtLS0tLSAgfCB8IHwgfA0KICAg
ICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgfCB8IHwgfCB8DQogICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgICAgICB8IHwgfCB8IHwNCiAgICAgICAgICAgICB8ICAgICAgICAg
ICAgICAgIC0tLS0tLS0tLS0gIHwgfA0KICAgICAgICAgICAgIHwgICAgICAgICAgICAgIDF8ICAg
ICAgfCB8ICAgfCB8DQogICAgICAgICAgICAgViAgICAgICAgICAgICAgIHwgICAgICB8IHwgICB8
IHwNCiAgICAgICAgICAgKy0tLSsgICBQQVNTICAgICstLS0rIDIgIHwgIC0tLS0tLS0+Ky0tLSsN
CiAgICAgICAgICAgfCAgIHwtLS0tLS0tLS0tPnwgVyB8LS0tLS0tLS0tLS0tLS0+fCBTIHwNCiAg
ICAgICAgICAgKy0tLSsgICAgICAgICAgICstLS0rICAgLS0tLS0tLS0tLS0+Ky0tLSsNCiAgICAg
ICAgICAgICAgICAgICAgICAgICAgICB8IHwgICB8IHwgICAgIHwgfA0KICAgICAgICAgICAgICAg
ICAgICAgICAgICAzIHwgfDQsNXwgfCAgICAgfCB8DQogICAgICAgICAgICAgIC0tLS0tLS0tLS0t
LS0tICAgLS0tLS0tLS0gICB8ICAtLS0tDQogICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAg
ICAgfCB8ICB8ICB8ICAgICAgfA0KICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICAgIHwg
fCAgfCAgfCAgICAgIHwNCiAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIC0tLS0tLS0tLS0t
LSAgICAgICB8DQogICAgICAgICAgICAgfCAgICAgICAgICAgIDEsM3wgICAgfCB8ICB8ICAgICAg
ICAgfA0KICAgICAgICAgICAgIFYgICAgICAgICAgICAgICB8ICAgMnwgfCAgfCAgICAgICAgIFYN
CiAgICAgICAgICAgKy0tLSsgICBBQ0NUICAgICstLS0rLS0gIHwgICAtLS0tLS0+Ky0tLSsNCiAg
ICAgICAgICAgfCAgIHwtLS0tLS0tLS0tPnwgVyB8IDQsNSAtLS0tLS0tLS0+fCBGIHwNCiAgICAg
ICAgICAgKy0tLSsgICAgICAgICAgICstLS0rLS0tLS0tLS0tLS0tLS0+Ky0tLStdXT48L2FydHdv
cms+DQogICAgICAgICAgICA8L2ZpZ3VyZT4NCiAgICAgICAgICA8L3Q+DQogICAgICAgICAgPHQ+
DQogICAgICAgICAgICA8ZmlndXJlIHRpdGxlPSJGaWd1cmUgNDogTG9naW4gc2VxdWVuY2Ugd2l0
aCBIT1NUIGFuZCBBVVRIL0FEQVQgY29tbWFuZHMiIHN1cHByZXNzLXRpdGxlPSJmYWxzZSIgYWxp
Z249ImxlZnQiIGFsdD0iIiB3aWR0aD0iIiBoZWlnaHQ9IiI+DQogICAgICAgICAgICAgIDxwcmVh
bWJsZT5XaGVuIHRoZSBIT1NUIGNvbW1hbmQgaXMgdXNlZCBpbiBjb21iaW5hdGlvbiB3aXRoIHRo
ZSBGVFAgc2VjdXJpdHkgZXh0ZW5zaW9ucyB0aGF0IHdlcmUgaW50cm9kdWNlZCBpbiA8eHJlZiB0
YXJnZXQ9IlJGQzIyMjgiIHBhZ2Vubz0iZmFsc2UiIGZvcm1hdD0iZGVmYXVsdCIgLz4sIGl0IFNI
T1VMRCBwcmVjZWRlIHRoZSBzZWN1cml0eSBoYW5kc2hha2UuICBUaGlzIGFsbG93cyBib3RoIHVz
ZXItUEkgYW5kIHNlcnZlci1GVFAgcHJvY2Vzc2VzIHRvIG1hcCBhbiBGVFAgSE9TVCB0byBzZWN1
cml0eSBkYXRhIGFwcHJvcHJpYXRlbHkuICBUaGUgc3RhdGUgZGlhZ3JhbSBpbiBGaWd1cmUgNCBz
aG93cyBhIHR5cGljYWwgc2VxdWVuY2Ugb2YgZmxvdyBvZiBjb250cm9sIHdoZW4gSE9TVCBpcyB1
c2VkIHdpdGggdGhlIEFVVEggYW5kIEFEQVQgY29tbWFuZHMgdGhhdCBhcmUgZGlzY3Vzc2VkIGlu
IDx4cmVmIHRhcmdldD0iUkZDMjIyOCIgcGFnZW5vPSJmYWxzZSIgZm9ybWF0PSJkZWZhdWx0IiAv
Pi48L3ByZWFtYmxlPg0KICAgICAgICAgICAgICA8YXJ0d29yayB4bWw6c3BhY2U9InByZXNlcnZl
IiBuYW1lPSIiIHR5cGU9IiIgYWxpZ249ImxlZnQiIGFsdD0iIiB3aWR0aD0iIiBoZWlnaHQ9IiI+
PCFbQ0RBVEFbDQogICAgICAgICAgICstLS0rICAgSE9TVCAgICArLS0tKyAxLDMsNQ0KICAgICAg
ICAgICB8IEIgfC0tLS0tLS0tLS0+fCBXIHwtLS0tLS0tLS0tLS0tLS0tLS0gDQogICAgICAgICAg
ICstLS0rICAgICAgICAgICArLS0tKyAgICAgICAgICAgICAgICAgIHwNCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICB8IHwgICAgICAgICAgICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAg
Miw1MDAsNTAyIHwgfCA0LDUwMSw1MDMsNTA0ICAgICB8DQogICAgICAgICAgICAgIC0tLS0tLS0t
LS0tLS0tICAgLS0tLS0tLS0tLS0tLSAgICAgIHwNCiAgICAgICAgICAgICB8ICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgfCAgICAgfA0KICAgICAgICAgICAgIFYgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICB8ICAgICB8DQogICAgICAgICAgICstLS0rICAgQVVUSCAgICArLS0tKyA0
LDUgICAgICAgIHwgICAgIHwNCiAgICAgICAgICAgfCAgIHwtLS0tLS0tLS0tPnwgVyB8LS0tLS0t
LS0tLS0+fCAgICAgfA0KICAgICAgICAgICArLS0tKyAgICAgICAgICAgKy0tLSsgICAgICAgICAg
ICB8ICAgICB8DQogICAgICAgICAgICAgICAgICAgICAgICAzMzQgfCB8ICAgICAgICAgICAgIHwg
ICAgIHwNCiAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0gIHwgICAgICAgICAgICAgfCAgICAg
fA0KICAgICAgICAgICAgIHwgICAgICAgICAgICAyMzQgfCAgICAgICAgICAgICB8ICAgICB8DQog
ICAgICAgICAgICAgfCAgICAtLS0tLS0tLS0tLS0gICAgICAgICAgICAgIHwgICAgIHwNCiAgICAg
ICAgICAgICBWICAgfCAgICAgICAgICAgICAgIDQsNSAgICAgICAgfCAgICAgfA0KICAgICAgICAg
ICArLS0tKyB8IEFEQVQgICAgKy0tLSstLS0tLS0tLS0tLT58ICAgICB8DQogICAgICAgICAgIHwg
ICB8LS0tLS0tLS0tLT58IFcgfCAzMzUgICAgICAgIHwgICAgIHwNCiAgICAgICAgICAgKy0tLSsg
fCAgICAgICAgICstLS0rLS0tLS0gICAgICAgfCAgICAgfA0KICAgICAgICAgICAgIF4gICB8ICAg
ICAgICAgICB8ICAgICAgIHwgICAgICB8ICAgICB8DQogICAgICAgICAgICAgfCAgIHwgICAgICAg
ICAgIHwgICAgICAgfCAgICAgIHwgICAgIHwNCiAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0gICAgICAgfCAgICAgfA0KICAgICAgICAgICAgICAgICB8ICAgICAgICAgICB8ICAg
ICAgICAgICAgICB8ICAgICB8DQogICAgICAgICAgICAgLS0tLSAgICAgICAgMjM1IHwgICAgICAg
ICAgICAgIHwgICAgIHwNCiAgICAgICAgICAgIHwgIC0tLS0tLS0tLS0tLS0tICAgICAgICAgICAg
ICAgfCAgICAgfA0KICAgICAgICAgICAgfCB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8
ICAgICBWDQogICAgICAgICAgICBWIFYgICAgICAgICAgICAgICAgICAxICAgICAgICAgIHwgICAr
LS0tKw0KICAgICAgICAgICArLS0tKyAgIFVTRVIgICAgKy0tLSstLS0tLS0tLS0tLS0tLS0+fCBF
IHwNCiAgICAgICAgICAgfCAgIHwtLS0tLS0tLS0tPnwgVyB8IDIgICAgICAgICAgfCAgICstLS0r
DQogICAgICAgICAgICstLS0rICAgICAgICAgICArLS0tKy0tLS0tLS0gICAgIHwgICAgIF4NCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICB8IHwgICAgICAgIHwgICAgfCAgICAgfA0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAzIHwgfCA0LDUgICAgfCAgICB8ICAgICB8DQogICAgICAgICAg
ICAgIC0tLS0tLS0tLS0tLS0tICAgLS0tLS0tICB8ICAgIHwgICAgIHwNCiAgICAgICAgICAgICB8
ICAgICAgICAgICAgICAgICAgICAgICB8IHwgICAgfCAgICAgfA0KICAgICAgICAgICAgIHwgICAg
ICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0tLS0tLS0NCiAgICAgICAgICAgICB8ICAgICAgICAg
ICAgICAxfCAgICAgICB8IHwgICAgfA0KICAgICAgICAgICAgIFYgICAgICAgICAgICAgICB8ICAg
ICAgIHwgIC0tLS0tLS0+Ky0tLSsNCiAgICAgICAgICAgKy0tLSsgICBQQVNTICAgICstLS0rIDIg
ICB8ICAgICAgfCAgIHwgUyB8DQogICAgICAgICAgIHwgICB8LS0tLS0tLS0tLT58IFcgfC0tLS0t
LS0tLS0tLS0tLT4rLS0tKw0KICAgICAgICAgICArLS0tKyAgICAgICAgICAgKy0tLSsgICAgIHwg
ICAgICB8ICANCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgICB8ICAgICAgfA0K
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8NCw1ICAgIHwgICAgICB8DQogICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIHwgICAgICAgfCAgICAgICAtLT4rLS0tKw0KICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICB8ICAgICAgICAtLS0tLS0tLS0+fCBGIHwNCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIC0tLS0tLS0tLS0tLS0tLS0tPistLS0rXV0+PC9hcnR3b3JrPg0KICAg
ICAgICAgICAgPC9maWd1cmU+DQogICAgICAgICAgPC90Pg0KICAgICAgICAgIDx0Pg0KICAgICAg
ICAgICAgPGZpZ3VyZSB0aXRsZT0iRmlndXJlIDU6IExvZ2luIHNlcXVlbmNlIHdpdGggSE9TVCBh
bmQgQVVUSC9BREFUL0FDQ1QgY29tbWFuZHMiIHN1cHByZXNzLXRpdGxlPSJmYWxzZSIgYWxpZ249
ImxlZnQiIGFsdD0iIiB3aWR0aD0iIiBoZWlnaHQ9IiI+DQogICAgICAgICAgICAgIDxwcmVhbWJs
ZT5BZnRlciBhIHVzZXIgaGFzIGxvZ2dlZCBpbiB3aXRoIHRoZSBzZWN1cml0eSBjb21tYW5kcyB0
aGF0IGFyZSBkaXNjdXNzZWQgaW4gPHhyZWYgdGFyZ2V0PSJSRkMyMjI4IiBwYWdlbm89ImZhbHNl
IiBmb3JtYXQ9ImRlZmF1bHQiIC8+LCBhbiBhZGRpdGlvbmFsIGFjY291bnQgbWF5IGJlIHJlcXVp
cmVkIGJ5IHRoZSBzZXJ2ZXIgYW5kIHNwZWNpZmllZCBieSB0aGUgY2xpZW50IGJ5IHVzaW5nIEFD
Q1QgY29tbWFuZC4gIFRoZSBzdGF0ZSBkaWFncmFtIGluIEZpZ3VyZSA1IHNob3dzIGEgdHlwaWNh
bCBzZXF1ZW5jZSBvZiBmbG93IG9mIGNvbnRyb2wgd2hlbiBIT1NUIGlzIHVzZWQgd2l0aCB0aGUg
QVVUSCBhbmQgQURBVCBjb21tYW5kcyB0byBsb2cgaW4gdG8gYW4gRlRQIHZpcnR1YWwgaG9zdCBh
bmQgQUNDVCBpcyB1c2VkIHRvIHNwZWNpZnkgYW4gYWNjb3VudC48L3ByZWFtYmxlPg0KICAgICAg
ICAgICAgICA8YXJ0d29yayB4bWw6c3BhY2U9InByZXNlcnZlIiBuYW1lPSIiIHR5cGU9IiIgYWxp
Z249ImxlZnQiIGFsdD0iIiB3aWR0aD0iIiBoZWlnaHQ9IiI+PCFbQ0RBVEFbDQogICAgICAgICAg
ICstLS0rICAgSE9TVCAgICArLS0tKyAxLDMsNQ0KICAgICAgICAgICB8IEIgfC0tLS0tLS0tLS0+
fCBXIHwtLS0tLS0tLS0tLS0tLS0tLS0gDQogICAgICAgICAgICstLS0rICAgICAgICAgICArLS0t
KyAgICAgICAgICAgICAgICAgIHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IHwgICAg
ICAgICAgICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAgMiw1MDAsNTAyIHwgfCA0LDUwMSw1
MDMsNTA0ICAgICB8DQogICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tICAgLS0tLS0tLS0tLS0t
LS0gICAgIHwNCiAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwg
ICAgfA0KICAgICAgICAgICAgIFYgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICB8
DQogICAgICAgICAgICstLS0rICAgQVVUSCAgICArLS0tKyA0LDUgICAgICAgICB8ICAgIHwNCiAg
ICAgICAgICAgfCAgIHwtLS0tLS0tLS0tPnwgVyB8LS0tLS0tLS0tLS0tPnwgICAgfA0KICAgICAg
ICAgICArLS0tKyAgICAgICAgICAgKy0tLSsgICAgICAgICAgICAgfCAgICB8DQogICAgICAgICAg
ICAgICAgICAgICAgICAzMzQgfCB8ICAgICAgICAgICAgICB8ICAgIHwNCiAgICAgICAgICAgICAg
LS0tLS0tLS0tLS0tLS0gIHwgICAgICAgICAgICAgIHwgICAgfA0KICAgICAgICAgICAgIHwgICAg
ICAgICAgICAyMzQgfCAgICAgICAgICAgICAgfCAgICB8DQogICAgICAgICAgICAgfCAgICAtLS0t
LS0tLS0tLS0gICAgICAgICAgICAgICB8ICAgIHwNCiAgICAgICAgICAgICBWICAgfCAgICAgICAg
ICAgICAgIDQsNSAgICAgICAgIHwgICAgfA0KICAgICAgICAgICArLS0tKyB8IEFEQVQgICAgKy0t
LSstLS0tLS0tLS0tLS0+fCAgICB8DQogICAgICAgICAgIHwgICB8LS0tLS0tLS0tLT58IFcgfCAz
MzUgICAgICAgICB8ICAgIHwNCiAgICAgICAgICAgKy0tLSsgfCAgICAgICAgICstLS0rLS0tLS0g
ICAgICAgIHwgICAgfA0KICAgICAgICAgICAgIF4gICB8ICAgICAgICAgICB8ICAgICAgIHwgICAg
ICAgfCAgICB8DQogICAgICAgICAgICAgfCAgIHwgICAgICAgICAgIHwgICAgICAgfCAgICAgICB8
ICAgIHwNCiAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gICAgICAgIHwgICAg
fA0KICAgICAgICAgICAgICAgICB8ICAgICAgICAgICB8ICAgICAgICAgICAgICAgfCAgICB8DQog
ICAgICAgICAgICAgLS0tLSAgICAgICAgIDIzNXwgICAgICAgICAgICAgICB8ICAgIHwNCiAgICAg
ICAgICAgIHwgIC0tLS0tLS0tLS0tLS0tICAgICAgICAgICAgICAgIHwgICAgfA0KICAgICAgICAg
ICAgfCB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICB8DQogICAgICAgICAgICBW
IFYgICAgICAgICAgICAgICAgICAxICAgICAgICAgICB8ICAgIFYNCiAgICAgICAgICAgKy0tLSsg
ICBVU0VSICAgICstLS0rLS0tLS0tLS0tLS0tLS0tPistLS0rDQogICAgICAgICAgIHwgICB8LS0t
LS0tLS0tLT58IFcgfCAyICAgICAgICAtLS0tLT58IEUgfA0KICAgICAgICAgICArLS0tKyAgICAg
ICAgICAgKy0tLSstLS0tLS0tICB8ICAtLS0+Ky0tLSsNCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICB8IHwgICAgICAgIHwgfCB8IHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgMyB8IHwg
NCw1ICAgIHwgfCB8IHwNCiAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0gICAtLS0tLS0gIHwg
fCB8IHwNCiAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICB8IHwgfCB8IHwNCiAg
ICAgICAgICAgICB8ICAgICAgICAgICAgICAgIC0tLS0tLS0tLS0tICB8IHwNCiAgICAgICAgICAg
ICB8ICAgICAgICAgICAgICAxfCAgICAgICB8IHwgICB8IHwNCiAgICAgICAgICAgICBWICAgICAg
ICAgICAgICAgfCAgICAgICB8IHwgICB8IHwNCiAgICAgICAgICAgKy0tLSsgICBQQVNTICAgICst
LS0rIDIgICB8ICAtLS0tLS0tPistLS0rDQogICAgICAgICAgIHwgICB8LS0tLS0tLS0tLT58IFcg
fC0tLS0tLS0tLS0tLS0tLT58IFMgfA0KICAgICAgICAgICArLS0tKyAgICAgICAgICAgKy0tLSsg
ICAtLS0tLS0tLS0tLS0+Ky0tLSsNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IHwgICB8
ICB8ICAgICB8IHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgMyB8IHw0LDV8ICB8ICAgICB8
IHwNCiAgICAgICAgICAgICAgLS0tLS0tLS0tLS0tLS0gICAtLS0tLS0tLS0gICB8ICAtLS0tDQog
ICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgfCAgfCAgfCAgfCAgICAgIHwNCiAgICAg
ICAgICAgICB8ICAgICAgICAgICAgICAgIC0tLS0tLS0tLS0tLS0gICAgICAgfA0KICAgICAgICAg
ICAgIHwgICAgICAgICAgICAxLDN8ICAgIHwgIHwgIHwgICAgICAgICB8DQogICAgICAgICAgICAg
ViAgICAgICAgICAgICAgIHwgICAyfCAgfCAgfCAgICAgICAgIFYNCiAgICAgICAgICAgKy0tLSsg
ICBBQ0NUICAgICstLS0rLS0gICB8ICAgLS0tLS0tPistLS0rDQogICAgICAgICAgIHwgICB8LS0t
LS0tLS0tLT58IFcgfCA0LDUgIC0tLS0tLS0tLT58IEYgfA0KICAgICAgICAgICArLS0tKyAgICAg
ICAgICAgKy0tLSstLS0tLS0tLS0tLS0tLS0+Ky0tLStdXT48L2FydHdvcms+DQogICAgICAgICAg
ICA8L2ZpZ3VyZT4NCiAgICAgICAgICA8L3Q+DQogICAgICAgIDwvc2VjdGlvbj4NCiAgICAgIDwv
c2VjdGlvbj4NCiAgICAgIDxzZWN0aW9uIHRpdGxlPSJIT1NUIGNvbW1hbmQgZXJyb3JzIiB0b2M9
ImRlZmF1bHQiPg0KICAgICAgICA8dD5UaGUgc2VydmVyLVBJIFNIT1VMRCByZXBseSB3aXRoIGEg
NTAwIG9yIDUwMiByZXBseSBpZiB0aGUgSE9TVCBjb21tYW5kIGlzIHVucmVjb2duaXplZCBvciB1
bmltcGxlbWVudGVkLjwvdD4NCiAgICAgICAgPHQ+QXMgZGlzY3Vzc2VkIGluIHNlY3Rpb24gMyBv
ZiB0aGlzIGRvY3VtZW50LCBpZiBhIEhPU1QgY29tbWFuZCBpcyBzZW50IGFmdGVyIGEgdXNlciBo
YXMgYmVlbiBhdXRoZW50aWNhdGVkIHRoZSBzZXJ2ZXIgU0hPVUxEIGRvIG9uZSBvZiB0aGUgZm9s
bG93aW5nOjwvdD4NCiAgICAgICAgPHQ+DQogICAgICAgICAgPGxpc3Qgc3R5bGU9ImxldHRlcnMi
Pg0KICAgICAgICAgICAgPHQ+U2VuZCBhIDUwMyByZXBseSBmb3IgYW4gaW52YWxpZCBzZXF1ZW5j
ZSBvZiBjb21tYW5kcy48L3Q+DQogICAgICAgICAgICA8dD5UcmVhdCB0aGUgSE9TVCBjb21tYW5k
IGFzIHRob3VnaCBhIFJFSU4gY29tbWFuZCB3YXMgc2VudCBhbmQgcmVzZXQgdGhlIHVzZXItUEkg
dG8gdGhlIHN0YXRlIHRoYXQgZXhpc3RlZCBhZnRlciB0aGUgcHJldmlvdXMgSE9TVCBjb21tYW5k
IHdhcyBzZW50IGFuZCBiZWZvcmUgdGhlIHVzZXIgaGFkIGJlZW4gYXV0aGVudGljYXRlZCwgYW5k
IHRoZW4gcmV0dXJuIHRoZSBhcHByb3ByaWF0ZSByZXBseSBmb3IgdGhlIEhPU1QgY29tbWFuZC48
L3Q+DQogICAgICAgICAgPC9saXN0Pg0KICAgICAgICA8L3Q+DQogICAgICAgIDx0PkEgNTAxIHJl
cGx5IFNIT1VMRCBiZSBzZW50IGlmIHRoZSBob3N0bmFtZSBnaXZlbiBpcyBzeW50YWN0aWNhbGx5
IGludmFsaWQsIGFuZCBhIDUwNCByZXBseSBTSE9VTEQgYmUgc2VudCBpZiBhIHN5bnRhY3RpY2Fs
bHkgdmFsaWQgaG9zdG5hbWUgaXMgbm90IGEgdmFsaWQgdmlydHVhbCBob3N0IG5hbWUgZm9yIHRo
ZSBzZXJ2ZXIuICBJbiBhbGwgc3VjaCBjYXNlcywgdGhlIHNlcnZlci1GVFAgcHJvY2VzcyBNVVNU
IGRvIG9uZSBvZiB0aGUgZm9sbG93aW5nOjwvdD4NCiAgICAgICAgPHQ+DQogICAgICAgICAgPGxp
c3Qgc3R5bGU9ImxldHRlcnMiPg0KICAgICAgICAgICAgPHQ+SWdub3JlIHRoZSBIT1NUIGNvbW1h
bmQgYW5kIGFjdCBhcyBpZiBhIEhPU1QgY29tbWFuZCBoYWQgbm90IGJlZW4gc2VudC4gIEEgdXNl
ci1GVFAgcHJvY2VzcyBNQVkgdGhlbiBzZW5kIGEgc3Vic2VxdWVudCBIT1NUIGNvbW1hbmQgd2l0
aCBhIGRpZmZlcmVudCBob3N0bmFtZS48L3Q+DQogICAgICAgICAgICA8dD5DbG9zZSB0aGUgY29u
bmVjdGlvbi48L3Q+DQogICAgICAgICAgPC9saXN0Pg0KICAgICAgICA8L3Q+DQogICAgICAgIDx0
PkEgdXNlci1QSSByZWNlaXZpbmcgYSA1MDAgb3IgNTAyIHJlcGx5IHRvIGEgSE9TVCBjb21tYW5k
IFNIT1VMRCBhc3N1bWUgdGhhdCB0aGUgc2VydmVyLVBJIGRvZXMgbm90IGltcGxlbWVudCB2aXJ0
dWFsIHNlcnZlcnMgYnkgdXNpbmcgdGhlIEhPU1QgY29tbWFuZC4gIFRoZSB1c2VyLVBJIE1BWSB0
aGVuIHByb2NlZWQgdG8gbG9naW4gYXMgaWYgdGhlIEhPU1QgY29tbWFuZCBoYWQgbm90IGJlZW4g
c2VudC48L3Q+DQogICAgICAgIDx0PkEgdXNlci1QSSByZWNlaXZpbmcgYW4gZXJyb3IgcmVwbHkg
dGhhdCBpcyBkaWZmZXJlbnQgZnJvbSB0aGUgZXJyb3JzIHRoYXQgaGF2ZSBiZWVuIGRlc2NyaWJl
ZCBoZXJlIFNIT1VMRCBhc3N1bWUgdGhhdCB0aGUgdmlydHVhbCBIT1NUIGlzIHVuYXZhaWxhYmxl
LCBhbmQgdGVybWluYXRlIGNvbW11bmljYXRpb25zLjwvdD4NCiAgICAgICAgPHQ+QSBzZXJ2ZXIt
UEkgdGhhdCByZWNlaXZlcyBhIFVTRVIgY29tbWFuZCB0byBiZWdpbiB0aGUgYXV0aGVudGljYXRp
b24gc2VxdWVuY2Ugd2l0aG91dCBoYXZpbmcgcmVjZWl2ZWQgYSBIT1NUIGNvbW1hbmQgU0hPVUxE
IE5PVCByZWplY3QgdGhlIFVTRVIgY29tbWFuZC4gIENsaWVudHMgY29uZm9ybWluZyB0byBlYXJs
aWVyIEZUUCBzcGVjaWZpY2F0aW9ucyBkbyBub3Qgc2VuZCBIT1NUIGNvbW1hbmRzLiAgSW4gdGhp
cyBjYXNlIHRoZSBzZXJ2ZXIgTUFZIGFjdCBhcyBpZiBzb21lIGRlZmF1bHQgdmlydHVhbCBob3N0
IGhhZCBiZWVuIGV4cGxpY2l0bHkgc2VsZWN0ZWQsIG9yIE1BWSBlbnRlciBhbiBlbnZpcm9ubWVu
dCB0aGF0IGlzIGRpZmZlcmVudCBmcm9tIHRoYXQgb2YgYW55IHN1cHBvcnRlZCB2aXJ0dWFsIGhv
c3RzLCBwZXJoYXBzIG9uZSBpbiB3aGljaCBhIHVuaW9uIG9mIGFsbCBhdmFpbGFibGUgYWNjb3Vu
dHMgZXhpc3RzIGFuZCB3aGljaCBwcmVzZW50cyBhbiBOVkZTIHRoYXQgYXBwZWFycyB0byBjb250
YWluIHN1YmRpcmVjdG9yaWVzIHRoYXQgY29udGFpbiB0aGUgTlZGUyBmb3IgYWxsIHN1cHBvcnRl
ZCB2aXJ0dWFsIGhvc3RzLjwvdD4NCiAgICAgIDwvc2VjdGlvbj4NCiAgICAgIDxzZWN0aW9uIHRp
dGxlPSJGRUFUIHJlc3BvbnNlIGZvciBIT1NUIGNvbW1hbmQiIHRvYz0iZGVmYXVsdCI+DQogICAg
ICAgIDx0PldoZW4gcmVwbHlpbmcgdG8gdGhlIEZFQVQgY29tbWFuZCA8eHJlZiB0YXJnZXQ9IlJG
QzIzODkiIHBhZ2Vubz0iZmFsc2UiIGZvcm1hdD0iZGVmYXVsdCIgLz4sIGEgc2VydmVyLUZUUCBw
cm9jZXNzIHRoYXQgc3VwcG9ydHMgdGhlIEhPU1QgY29tbWFuZCBNVVNUIGluY2x1ZGUgYSBsaW5l
IGNvbnRhaW5pbmcgdGhlIHNpbmdsZSB3b3JkICJIT1NUIi4gIFRoaXMgd29yZCBpcyBjYXNlIGlu
c2Vuc2l0aXZlLCBhbmQgTUFZIGJlIHNlbnQgaW4gYW55IG1peHR1cmUgb2YgdXBwZXIgb3IgbG93
ZXIgY2FzZSwgaG93ZXZlciBpdCBTSE9VTEQgYmUgc2VudCBpbiB1cHBlciBjYXNlLiAgVGhhdCBp
cywgdGhlIHJlc3BvbnNlIFNIT1VMRCBiZTo8L3Q+DQogICAgICAgIDx0Pg0KICAgICAgICAgIDxm
aWd1cmUgdGl0bGU9IiIgc3VwcHJlc3MtdGl0bGU9ImZhbHNlIiBhbGlnbj0ibGVmdCIgYWx0PSIi
IHdpZHRoPSIiIGhlaWdodD0iIj4NCiAgICAgICAgICAgIDxhcnR3b3JrIHhtbDpzcGFjZT0icHJl
c2VydmUiIG5hbWU9IiIgdHlwZT0iIiBhbGlnbj0ibGVmdCIgYWx0PSIiIHdpZHRoPSIiIGhlaWdo
dD0iIj48IVtDREFUQVsgICAgIEM+IEZFQVQNCiAgICAgUz4gMjExLSA8YW55IGRlc2NyaXB0aXZl
IHRleHQ+DQogICAgIFM+ICAuLi4NCiAgICAgUz4gIEhPU1QNCiAgICAgUz4gIC4uLg0KICAgICBT
PiAyMTEgRW5kXV0+PC9hcnR3b3JrPg0KICAgICAgICAgIDwvZmlndXJlPg0KICAgICAgICA8L3Q+
DQogICAgICAgIDx0PlRoZSBlbGxpcHNlcyBpbmRpY2F0ZSBwbGFjZSBob2xkZXJzIHdoZXJlIG90
aGVyIGZlYXR1cmVzIG1heSBiZSBpbmNsdWRlZCwgYW5kIGFyZSBub3QgcmVxdWlyZWQuICBUaGUg
b25lLXNwYWNlIGluZGVudGF0aW9uIG9mIHRoZSBmZWF0dXJlIGxpbmVzIGlzIG1hbmRhdG9yeSA8
eHJlZiB0YXJnZXQ9IlJGQzIzODkiIHBhZ2Vubz0iZmFsc2UiIGZvcm1hdD0iZGVmYXVsdCIgLz4u
PC90Pg0KICAgICAgPC9zZWN0aW9uPg0KICAgIDwvc2VjdGlvbj4NCiAgICA8c2VjdGlvbiBhbmNo
b3I9IlNlY3VyaXR5IiB0aXRsZT0iU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMiIHRvYz0iZGVmYXVs
dCI+DQogICAgICA8dD5BcyBkaXNjdXNzZWQgaW4gc2VjdGlvbiAzIG9mIHRoaXMgZG9jdW1lbnQs
IGEgc2VydmVyIGltcGxlbWVudGF0aW9uIE1VU1QgdHJlYXQgYSBIT1NUIGNvbW1hbmQgdGhhdCB3
YXMgc2VudCBiZWZvcmUgYSB1c2VyIGhhcyBiZWVuIGF1dGhlbnRpY2F0ZWQgYXMgdGhvdWdoIGEg
UkVJTiBjb21tYW5kIHdhcyBzZW50LCBhbmQgYSBzZXJ2ZXIgaW1wbGVtZW50YXRpb24gTUFZIHRy
ZWF0IGEgSE9TVCBjb21tYW5kIHRoYXQgd2FzIHNlbnQgYWZ0ZXIgYSB1c2VyIGhhcyBiZWVuIGF1
dGhlbnRpY2F0ZWQgYXMgdGhvdWdoIGEgUkVJTiBjb21tYW5kIHdhcyBzZW50LiAgSW4gZWl0aGVy
IG9mIHRoZXNlIHNjZW5hcmlvcywgdGhlIHNlcnZlciBpbXBsZW1lbnRhdGlvbiBNVVNUIHJlc2V0
IHRoZSBhdXRoZW50aWNhdGlvbiBlbnZpcm9ubWVudCwgYXMgdGhhdCB3b3VsZCBhbGxvdyBmb3Ig
c2VncmVnYXRpb24gYmV0d2VlbiB0aGUgc2VjdXJpdHkgZW52aXJvbm1lbnRzIGZvciBlYWNoIHZp
cnR1YWwgaG9zdCBvbiBhbiBGVFAgc2VydmVyLiAgVGhlIGltcGxlbWVudGF0aW9uIGRldGFpbHMg
Zm9yIHNlY3VyaXR5IGVudmlyb25tZW50cyBtYXkgdmFyeSBncmVhdGx5IGJhc2VkIG9uIHRoZSBy
ZXF1aXJlbWVudHMgb2YgZWFjaCBzZXJ2ZXIgaW1wbGVtZW50YXRpb24gYW5kIG9wZXJhdGluZyBz
eXN0ZW0sIGFuZCB0aG9zZSBkZXRhaWxzIGFyZSBvdXRzaWRlIHRoZSBzY29wZSBvZiB0aGUgcHJv
dG9jb2wgaXRzZWxmLiAgRm9yIGV4YW1wbGUsIGEgdmlydHVhbCBob3N0ICJmb28uZXhhbXBsZS5j
b20iIG9uIGFuIEZUUCBzZXJ2ZXIgbWlnaHQgdXNlIGEgc3BlY2lmaWMgdXNlcm5hbWUgYW5kIHBh
c3N3b3JkIGxpc3QsIHdoaWxlIHRoZSB2aXJ0dWFsIGhvc3QgImJhci5leGFtcGxlLmNvbSIgb24g
dGhlIHNhbWUgRlRQIHNlcnZlciBtaWdodCB1c2UgYSBkaWZmZXJlbnQgdXNlcm5hbWUgYW5kIHBh
c3N3b3JkIGxpc3QuICBJbiBzdWNoIGEgc2NlbmFyaW8sIHJlc2V0dGluZyB0aGUgc2VjdXJpdHkg
ZW52aXJvbm1lbnQgaXMgbmVjZXNzYXJ5IGZvciB0aGUgdmlydHVhbCBzZXJ2ZXJzIHRvIGFwcGVh
ciB0byBiZWhhdmUgaW5kZXBlbmRlbnRseSBmcm9tIGEgY2xpZW50IHBlcnNwZWN0aXZlLCB3aGls
ZSB0aGUgYWN0dWFsIHNlcnZlciBpbXBsZW1lbnRhdGlvbiBkZXRhaWxzIGFyZSBpcnJlbGV2YW50
IGF0IHRoZSBwcm90b2NvbCBsZXZlbC48L3Q+DQogICAgICA8dD5TZWN0aW9uIDE1LjEuMSBvZiA8
eHJlZiB0YXJnZXQ9IlJGQzQyMTciIHBhZ2Vubz0iZmFsc2UiIGZvcm1hdD0iZGVmYXVsdCIgLz4g
ZGlzY3Vzc2VzIHRoZSB1c2Ugb2YgWC41MDkgY2VydGlmaWNhdGVzIGZvciBzZXJ2ZXIgYXV0aGVu
dGljYXRpb24uIFRha2luZyB0aGUgaW5mb3JtYXRpb24gZnJvbSB0aGF0IGRvY3VtZW50IGludG8g
YWNjb3VudCwgd2hlbiBzZWN1cmluZyBGVFAgc2Vzc2lvbnMgd2l0aCB0aGUgc2VjdXJpdHkgbWVj
aGFuaXNtcyB0aGF0IGFyZSBkZWZpbmVkIGluIDx4cmVmIHRhcmdldD0iUkZDNDIxNyIgcGFnZW5v
PSJmYWxzZSIgZm9ybWF0PSJkZWZhdWx0IiAvPiwgY2xpZW50IGltcGxlbWVudGF0aW9ucyBTSE9V
TEQgdmVyaWZ5IHRoYXQgdGhlIGhvc3RuYW1lIHRoZXkgc3BlY2lmeSBpbiB0aGUgcGFyYW1ldGVy
IGZvciB0aGUgSE9TVCBjb21tYW5kIG1hdGNoZXMgdGhlIGlkZW50aXR5IHRoYXQgaXMgc3BlY2lm
aWVkIGluIHRoZSBzZXJ2ZXIncyBYLjUwOSBjZXJ0aWZpY2F0ZSBpbiBvcmRlciB0byBwcmV2ZW50
IG1hbi1pbi10aGUtbWlkZGxlIGF0dGFja3MuPC90Pg0KICAgICAgPHQ+QSBnZW5lcmFsIGRpc2N1
c3Npb24gb2YgaXNzdWVzIHJlbGF0ZWQgdG8gdGhlIHNlY3VyaXR5IG9mIEZUUCBjYW4gYmUgZm91
bmQgaW4gPHhyZWYgdGFyZ2V0PSJSRkMyNTc3IiBwYWdlbm89ImZhbHNlIiBmb3JtYXQ9ImRlZmF1
bHQiIC8+LjwvdD4NCiAgICA8L3NlY3Rpb24+DQogICAgPHNlY3Rpb24gYW5jaG9yPSJJQU5BIiB0
aXRsZT0iSUFOQSBDb25zaWRlcmF0aW9ucyIgdG9jPSJkZWZhdWx0Ij4NCiAgICAgIDx0PklBTkEg
aXMgcmVxdWVzdGVkIHRvIHJlZ2lzdGVyIHRoZSBmb2xsb3dpbmcgRlRQIGV4dGVuc2lvbiBhY2Nv
cmRpbmcgdG8gdGhlIHByb2NlZHVyZSBlc3RhYmxpc2hlZCBieSA8eHJlZiB0YXJnZXQ9IlJGQzU3
OTciIHBhZ2Vubz0iZmFsc2UiIGZvcm1hdD0iZGVmYXVsdCI+PC94cmVmPjo8L3Q+DQogICAgICA8
dGV4dHRhYmxlIHRpdGxlPSIiIHN1cHByZXNzLXRpdGxlPSJmYWxzZSIgYWxpZ249ImNlbnRlciIg
c3R5bGU9ImZ1bGwiPg0KICAgICAgICA8dHRjb2wgYWxpZ249ImxlZnQiPmNtZDwvdHRjb2w+DQog
ICAgICAgIDx0dGNvbCBhbGlnbj0ibGVmdCI+RkVBVA0KQ29kZTwvdHRjb2w+DQogICAgICAgIDx0
dGNvbCBhbGlnbj0ibGVmdCI+ZGVzY3JpcHRpb248L3R0Y29sPg0KICAgICAgICA8dHRjb2wgYWxp
Z249ImxlZnQiPnR5cGU8L3R0Y29sPg0KICAgICAgICA8dHRjb2wgYWxpZ249ImxlZnQiPmNvbmY8
L3R0Y29sPg0KICAgICAgICA8dHRjb2wgYWxpZ249ImxlZnQiPlJGQyNzL1JlZmVyZW5jZXMNCmFu
ZCBOb3RlczwvdHRjb2w+DQogICAgICAgIDxjPkhPU1Q8L2M+DQogICAgICAgIDxjPkhPU1Q8L2M+
DQogICAgICAgIDxjPkhvc3RuYW1lPC9jPg0KICAgICAgICA8Yz5hPC9jPg0KICAgICAgICA8Yz5v
PC9jPg0KICAgICAgICA8Yz5UQkQ8L2M+DQogICAgICAgIDxwb3N0YW1ibGU+Tk9URSBUTyBSRkMg
RURJVE9SOiBQbGVhc2UgdXBkYXRlIFRCRCBpbiB0aGUgYWJvdmUgdGFibGUgd2l0aCB0aGUgbnVt
YmVyIG9mIHRoaXMgZG9jdW1lbnQuPC9wb3N0YW1ibGU+DQogICAgICA8L3RleHR0YWJsZT4NCiAg
ICA8L3NlY3Rpb24+DQogIDwvbWlkZGxlPg0KICA8YmFjaz4NCiAgICA8cmVmZXJlbmNlcyB0aXRs
ZT0iTm9ybWF0aXZlIFJlZmVyZW5jZXMiPg0KICAgICAgPHJlZmVyZW5jZSBhbmNob3I9IlJGQzA5
NTkiPg0KICAgICAgICA8ZnJvbnQ+DQogICAgICAgICAgPHRpdGxlPkZpbGUgVHJhbnNmZXIgUHJv
dG9jb2wgKEZUUCk8L3RpdGxlPg0KICAgICAgICAgIDxhdXRob3IgaW5pdGlhbHM9IkouIiBzdXJu
YW1lPSJQb3N0ZWwiPjwvYXV0aG9yPg0KICAgICAgICAgIDxhdXRob3IgaW5pdGlhbHM9IkouIiBz
dXJuYW1lPSJSZXlub2xkcyI+PC9hdXRob3I+DQogICAgICAgICAgPGRhdGUgeWVhcj0iMTk4NSIg
bW9udGg9Ik9jdG9iZXIiIC8+DQogICAgICAgIDwvZnJvbnQ+DQogICAgICAgIDxzZXJpZXNJbmZv
IG5hbWU9IlNURCIgdmFsdWU9IjkiIC8+DQogICAgICAgIDxzZXJpZXNJbmZvIG5hbWU9IlJGQyIg
dmFsdWU9Ijk1OSIgLz4NCiAgICAgIDwvcmVmZXJlbmNlPg0KICAgICAgPHJlZmVyZW5jZSBhbmNo
b3I9IlJGQzEwMzQiPg0KICAgICAgICA8ZnJvbnQ+DQogICAgICAgICAgPHRpdGxlPkRvbWFpbiBO
YW1lcyAtIENvbmNlcHRzIGFuZCBGYWNpbGl0aWVzPC90aXRsZT4NCiAgICAgICAgICA8YXV0aG9y
IGluaXRpYWxzPSJQLiIgc3VybmFtZT0iTW9ja2FwZXRyaXMiPjwvYXV0aG9yPg0KICAgICAgICAg
IDxkYXRlIHllYXI9IjE5ODciIG1vbnRoPSJOb3ZlbWJlciI+PC9kYXRlPg0KICAgICAgICA8L2Zy
b250Pg0KICAgICAgICA8c2VyaWVzSW5mbyBuYW1lPSJTVEQiIHZhbHVlPSIxMyIgLz4NCiAgICAg
ICAgPHNlcmllc0luZm8gbmFtZT0iUkZDIiB2YWx1ZT0iMTAzNCIgLz4NCiAgICAgIDwvcmVmZXJl
bmNlPg0KICAgICAgPHJlZmVyZW5jZSBhbmNob3I9IlJGQzEwMzUiPg0KICAgICAgICA8ZnJvbnQ+
DQogICAgICAgICAgPHRpdGxlPkRvbWFpbiBOYW1lcyAtIEltcGxlbWVudGF0aW9uIGFuZCBTcGVj
aWZpY2F0aW9uPC90aXRsZT4NCiAgICAgICAgICA8YXV0aG9yIGluaXRpYWxzPSJQLiIgc3VybmFt
ZT0iTW9ja2FwZXRyaXMiPjwvYXV0aG9yPg0KICAgICAgICAgIDxkYXRlIHllYXI9IjE5ODciIG1v
bnRoPSJOb3ZlbWJlciI+PC9kYXRlPg0KICAgICAgICA8L2Zyb250Pg0KICAgICAgICA8c2VyaWVz
SW5mbyBuYW1lPSJTVEQiIHZhbHVlPSIxMyIgLz4NCiAgICAgICAgPHNlcmllc0luZm8gbmFtZT0i
UkZDIiB2YWx1ZT0iMTAzNSIgLz4NCiAgICAgIDwvcmVmZXJlbmNlPg0KICAgICAgPHJlZmVyZW5j
ZSBhbmNob3I9IlJGQzExMjMiPg0KICAgICAgICA8ZnJvbnQ+DQogICAgICAgICAgPHRpdGxlPlJl
cXVpcmVtZW50cyBmb3IgSW50ZXJuZXQgSG9zdHMgLS0gQXBwbGljYXRpb24gYW5kIFN1cHBvcnQ8
L3RpdGxlPg0KICAgICAgICAgIDxhdXRob3IgaW5pdGlhbHM9IlIuIiBzdXJuYW1lPSJCcmFkZW4i
IC8+DQogICAgICAgICAgPGRhdGUgeWVhcj0iMTk4OSIgbW9udGg9Ik9jdG9iZXIiIC8+DQogICAg
ICAgIDwvZnJvbnQ+DQogICAgICAgIDxzZXJpZXNJbmZvIG5hbWU9IlNURCIgdmFsdWU9IjMiIC8+
DQogICAgICAgIDxzZXJpZXNJbmZvIG5hbWU9IlJGQyIgdmFsdWU9IjExMjMiIC8+DQogICAgICA8
L3JlZmVyZW5jZT4NCiAgICAgIDxyZWZlcmVuY2UgYW5jaG9yPSJSRkMyMTE5Ij4NCiAgICAgICAg
PGZyb250Pg0KICAgICAgICAgIDx0aXRsZT5LZXkgd29yZHMgZm9yIHVzZSBpbiBSRkNzIHRvIElu
ZGljYXRlIFJlcXVpcmVtZW50IExldmVsczwvdGl0bGU+DQogICAgICAgICAgPGF1dGhvciBpbml0
aWFscz0iUy4iIHN1cm5hbWU9IkJyYWRuZXIiPjwvYXV0aG9yPg0KICAgICAgICAgIDxkYXRlIHll
YXI9IjE5OTciIG1vbnRoPSJNYXJjaCIgLz4NCiAgICAgICAgPC9mcm9udD4NCiAgICAgICAgPHNl
cmllc0luZm8gbmFtZT0iQkNQIiB2YWx1ZT0iMTQiIC8+DQogICAgICAgIDxzZXJpZXNJbmZvIG5h
bWU9IlJGQyIgdmFsdWU9IjIxMTkiIC8+DQogICAgICA8L3JlZmVyZW5jZT4NCiAgICAgIDxyZWZl
cmVuY2UgYW5jaG9yPSJSRkMyMjI4Ij4NCiAgICAgICAgPGZyb250Pg0KICAgICAgICAgIDx0aXRs
ZT5GVFAgU2VjdXJpdHkgRXh0ZW5zaW9uczwvdGl0bGU+DQogICAgICAgICAgPGF1dGhvciBpbml0
aWFscz0iTS4iIHN1cm5hbWU9Ikhvcm93aXR6Ij48L2F1dGhvcj4NCiAgICAgICAgICA8YXV0aG9y
IGluaXRpYWxzPSJTLiIgc3VybmFtZT0iTHVudCI+PC9hdXRob3I+DQogICAgICAgICAgPGRhdGUg
eWVhcj0iMTk5NyIgbW9udGg9Ik9jdG9iZXIiIC8+DQogICAgICAgIDwvZnJvbnQ+DQogICAgICAg
IDxzZXJpZXNJbmZvIG5hbWU9IlJGQyIgdmFsdWU9IjIyMjgiIC8+DQogICAgICA8L3JlZmVyZW5j
ZT4NCiAgICAgIDxyZWZlcmVuY2UgYW5jaG9yPSJSRkMyMzg5Ij4NCiAgICAgICAgPGZyb250Pg0K
ICAgICAgICAgIDx0aXRsZT5GZWF0dXJlIG5lZ290aWF0aW9uIG1lY2hhbmlzbSBmb3IgdGhlIEZp
bGUgVHJhbnNmZXIgUHJvdG9jb2w8L3RpdGxlPg0KICAgICAgICAgIDxhdXRob3IgaW5pdGlhbHM9
IlAuIiBzdXJuYW1lPSJIZXRobW9uIj48L2F1dGhvcj4NCiAgICAgICAgICA8YXV0aG9yIGluaXRp
YWxzPSJSLiIgc3VybmFtZT0iRWx6Ij48L2F1dGhvcj4NCiAgICAgICAgICA8ZGF0ZSB5ZWFyPSIx
OTk4IiBtb250aD0iQXVndXN0IiAvPg0KICAgICAgICA8L2Zyb250Pg0KICAgICAgICA8c2VyaWVz
SW5mbyBuYW1lPSJSRkMiIHZhbHVlPSIyMzg5IiAvPg0KICAgICAgPC9yZWZlcmVuY2U+DQogICAg
ICA8cmVmZXJlbmNlIGFuY2hvcj0iUkZDMjY0MCI+DQogICAgICAgIDxmcm9udD4NCiAgICAgICAg
ICA8dGl0bGU+SW50ZXJuYXRpb25hbGl6YXRpb24gb2YgdGhlIEZpbGUgVHJhbnNmZXIgUHJvdG9j
b2w8L3RpdGxlPg0KICAgICAgICAgIDxhdXRob3IgaW5pdGlhbHM9IlcuIiBzdXJuYW1lPSJDdXJ0
aW4iPjwvYXV0aG9yPg0KICAgICAgICAgIDxkYXRlIHllYXI9IjE5OTkiIG1vbnRoPSJKdWx5IiAv
Pg0KICAgICAgICA8L2Zyb250Pg0KICAgICAgICA8c2VyaWVzSW5mbyBuYW1lPSJSRkMiIHZhbHVl
PSIyNjQwIiAvPg0KICAgICAgPC9yZWZlcmVuY2U+DQogICAgICA8cmVmZXJlbmNlIGFuY2hvcj0i
UkZDMzQ5MiI+DQogICAgICAgIDxmcm9udD4NCiAgICAgICAgICA8dGl0bGU+UHVueWNvZGU6IEEg
Qm9vdHN0cmluZyBlbmNvZGluZyBvZiBVbmljb2RlIGZvciBJbnRlcm5hdGlvbmFsaXplZCBEb21h
aW4gTmFtZXMgaW4gQXBwbGljYXRpb25zIChJRE5BKTwvdGl0bGU+DQogICAgICAgICAgPGF1dGhv
ciBpbml0aWFscz0iQS4iIHN1cm5hbWU9IkNvc3RlbGxvIj48L2F1dGhvcj4NCiAgICAgICAgICA8
ZGF0ZSB5ZWFyPSIyMDAzIiBtb250aD0iTWFyY2giIC8+DQogICAgICAgIDwvZnJvbnQ+DQogICAg
ICAgIDxzZXJpZXNJbmZvIG5hbWU9IlJGQyIgdmFsdWU9IjM0OTIiIC8+DQogICAgICA8L3JlZmVy
ZW5jZT4NCiAgICAgIDxyZWZlcmVuY2UgYW5jaG9yPSJSRkM0MjE3Ij4NCiAgICAgICAgPGZyb250
Pg0KICAgICAgICAgIDx0aXRsZT5TZWN1cmluZyBGVFAgd2l0aCBUTFM8L3RpdGxlPg0KICAgICAg
ICAgIDxhdXRob3IgaW5pdGlhbHM9IlAuIiBzdXJuYW1lPSJGb3JkLUh1dGNoaW5zb24iPjwvYXV0
aG9yPg0KICAgICAgICAgIDxkYXRlIHllYXI9IjIwMDUiIG1vbnRoPSJPY3RvYmVyIiAvPg0KICAg
ICAgICA8L2Zyb250Pg0KICAgICAgICA8c2VyaWVzSW5mbyBuYW1lPSJSRkMiIHZhbHVlPSI0MjE3
IiAvPg0KICAgICAgPC9yZWZlcmVuY2U+DQogICAgICA8cmVmZXJlbmNlIGFuY2hvcj0iUkZDNTIz
NCI+DQogICAgICAgIDxmcm9udD4NCiAgICAgICAgICA8dGl0bGU+QXVnbWVudGVkIEJORiBmb3Ig
U3ludGF4IFNwZWNpZmljYXRpb25zOiBBQk5GPC90aXRsZT4NCiAgICAgICAgICA8YXV0aG9yIGlu
aXRpYWxzPSJELiIgc3VybmFtZT0iQ3JvY2tlciI+PC9hdXRob3I+DQogICAgICAgICAgPGF1dGhv
ciBpbml0aWFscz0iUC4iIHN1cm5hbWU9Ik92ZXJlbGwiPjwvYXV0aG9yPg0KICAgICAgICAgIDxk
YXRlIHllYXI9IjIwMDgiIG1vbnRoPSJKYW51YXJ5IiAvPg0KICAgICAgICA8L2Zyb250Pg0KICAg
ICAgICA8c2VyaWVzSW5mbyBuYW1lPSJSRkMiIHZhbHVlPSI1MjM0IiAvPg0KICAgICAgPC9yZWZl
cmVuY2U+DQogICAgPC9yZWZlcmVuY2VzPg0KICAgIDxyZWZlcmVuY2VzIHRpdGxlPSJJbmZvcm1h
dGl2ZSBSZWZlcmVuY2VzIj4NCiAgICAgIDxyZWZlcmVuY2UgYW5jaG9yPSJSRkMxOTQ1Ij4NCiAg
ICAgICAgPGZyb250Pg0KICAgICAgICAgIDx0aXRsZT5IeXBlcnRleHQgVHJhbnNmZXIgUHJvdG9j
b2wgLS0gSFRUUC8xLjA8L3RpdGxlPg0KICAgICAgICAgIDxhdXRob3IgaW5pdGlhbHM9IlQuIiBz
dXJuYW1lPSJCZXJuZXJzLUxlZSI+PC9hdXRob3I+DQogICAgICAgICAgPGF1dGhvciBpbml0aWFs
cz0iUi4iIHN1cm5hbWU9IkZpZWxkaW5nIj48L2F1dGhvcj4NCiAgICAgICAgICA8YXV0aG9yIGlu
aXRpYWxzPSJILiIgc3VybmFtZT0iRnJ5c3R5ayI+PC9hdXRob3I+DQogICAgICAgICAgPGRhdGUg
eWVhcj0iMTk5NiIgbW9udGg9Ik1heSIgLz4NCiAgICAgICAgPC9mcm9udD4NCiAgICAgICAgPHNl
cmllc0luZm8gbmFtZT0iUkZDIiB2YWx1ZT0iMTk0NSIgLz4NCiAgICAgIDwvcmVmZXJlbmNlPg0K
ICAgICAgPHJlZmVyZW5jZSBhbmNob3I9IlJGQzI1NzciPg0KICAgICAgICA8ZnJvbnQ+DQogICAg
ICAgICAgPHRpdGxlPkZUUCBTZWN1cml0eSBDb25zaWRlcmF0aW9uczwvdGl0bGU+DQogICAgICAg
ICAgPGF1dGhvciBpbml0aWFscz0iTS4iIHN1cm5hbWU9IkFsbG1hbiI+PC9hdXRob3I+DQogICAg
ICAgICAgPGF1dGhvciBpbml0aWFscz0iUy4iIHN1cm5hbWU9Ik9zdGVybWFubiI+PC9hdXRob3I+
DQogICAgICAgICAgPGRhdGUgeWVhcj0iMTk5OSIgbW9udGg9Ik1heSIgLz4NCiAgICAgICAgPC9m
cm9udD4NCiAgICAgICAgPHNlcmllc0luZm8gbmFtZT0iUkZDIiB2YWx1ZT0iMjU3NyIgLz4NCiAg
ICAgIDwvcmVmZXJlbmNlPg0KICAgICAgPHJlZmVyZW5jZSBhbmNob3I9IlJGQzI2MTYiPg0KICAg
ICAgICA8ZnJvbnQ+DQogICAgICAgICAgPHRpdGxlPkh5cGVydGV4dCBUcmFuc2ZlciBQcm90b2Nv
bCAtLSBIVFRQLzEuMTwvdGl0bGU+DQogICAgICAgICAgPGF1dGhvciBpbml0aWFscz0iUi4iIHN1
cm5hbWU9IkZpZWxkaW5nIj48L2F1dGhvcj4NCiAgICAgICAgICA8YXV0aG9yIGluaXRpYWxzPSJK
LiIgc3VybmFtZT0iR2V0dHlzIj48L2F1dGhvcj4NCiAgICAgICAgICA8YXV0aG9yIGluaXRpYWxz
PSJKLiIgc3VybmFtZT0iTW9ndWwiPjwvYXV0aG9yPg0KICAgICAgICAgIDxhdXRob3IgaW5pdGlh
bHM9IkguIiBzdXJuYW1lPSJGcnlzdHlrIj48L2F1dGhvcj4NCiAgICAgICAgICA8YXV0aG9yIGlu
aXRpYWxzPSJMLiIgc3VybmFtZT0iTWFzaW50ZXIiPjwvYXV0aG9yPg0KICAgICAgICAgIDxhdXRo
b3IgaW5pdGlhbHM9IlAuIiBzdXJuYW1lPSJMZWFjaCI+PC9hdXRob3I+DQogICAgICAgICAgPGF1
dGhvciBpbml0aWFscz0iVC4iIHN1cm5hbWU9IkJlcm5lcnMtTGVlIj48L2F1dGhvcj4NCiAgICAg
ICAgICA8ZGF0ZSB5ZWFyPSIxOTk5IiBtb250aD0iSnVuZSIgLz4NCiAgICAgICAgPC9mcm9udD4N
CiAgICAgICAgPHNlcmllc0luZm8gbmFtZT0iUkZDIiB2YWx1ZT0iMjYxNiIgLz4NCiAgICAgIDwv
cmVmZXJlbmNlPg0KICAgICAgPHJlZmVyZW5jZSBhbmNob3I9IlJGQzU3OTciPg0KICAgICAgICA8
ZnJvbnQ+DQogICAgICAgICAgPHRpdGxlPkZUUCBDb21tYW5kIGFuZCBFeHRlbnNpb24gUmVnaXN0
cnk8L3RpdGxlPg0KICAgICAgICAgIDxhdXRob3IgaW5pdGlhbHM9IkouIiBzdXJuYW1lPSJLbGVu
c2luIj48L2F1dGhvcj4NCiAgICAgICAgICA8YXV0aG9yIGluaXRpYWxzPSJBLiIgc3VybmFtZT0i
SG9lbmVzIj48L2F1dGhvcj4NCiAgICAgICAgICA8ZGF0ZSBtb250aD0iTWFyY2giIHllYXI9IjIw
MTAiIC8+DQogICAgICAgIDwvZnJvbnQ+DQogICAgICAgIDxzZXJpZXNJbmZvIG5hbWU9IlJGQyIg
dmFsdWU9IjU3OTciIC8+DQogICAgICA8L3JlZmVyZW5jZT4NCiAgICA8L3JlZmVyZW5jZXM+DQog
ICAgPHNlY3Rpb24gdGl0bGU9IlVud29ya2FibGUgQWx0ZXJuYXRpdmVzIiB0b2M9ImRlZmF1bHQi
Pg0KICAgICAgPHQ+RHVlIHRvIHRoZSBsZXZlbCBvZiBzY29wZSBmb3IgYWRkaW5nIGEgbmV3IGNv
bW1hbmQgdG8gRlRQLCBhIGJyaWVmIGRpc2N1c3Npb24gb2Ygc3VnZ2VzdGVkIGFsdGVybmF0aXZl
cyB0byBhIEhPU1QgY29tbWFuZCBhbmQgdGhlaXIgcmVzcGVjdGl2ZSBsaW1pdGF0aW9ucyBpcyB3
YXJyYW50ZWQuICBUaGUgc3VnZ2VzdGVkIGFsdGVybmF0aXZlcyB0aGF0IGFyZSBkaXNjdXNzZWQg
aW4gdGhpcyBhcHBlbmRpeCBoYXZlIGJlZW4gcHJvcG9zZWQgaW4gdGhlIHBhc3QsIGJ1dCBlYWNo
IG9mIHRoZXNlIGlkZWFzIHdhcyBkZWVtZWQgaW5zdWZmaWNpZW50IGZvciB0aGUgcmVhc29ucyB0
aGF0IGFyZSBsaXN0ZWQgd2l0aGluIGVhY2ggc2VjdGlvbiBvZiB0aGUgYXBwZW5kaXguPC90Pg0K
ICAgICAgPHNlY3Rpb24gdGl0bGU9Ik92ZXJsb2FkaW5nIHRoZSBDV0QgY29tbWFuZCIgdG9jPSJk
ZWZhdWx0Ij4NCiAgICAgICAgPHQ+T25lIHN1Z2dlc3RlZCBtZXRob2QgdG8gZW11bGF0ZSBhIGZv
cm0gb2YgdmlydHVhbCBob3N0cyB3b3VsZCBiZSBmb3IgdGhlIGNsaWVudCB0byBzaW1wbHkgc2Vu
ZCBhICJDV0QiIGNvbW1hbmQgYWZ0ZXIgY29ubmVjdGluZywgdXNpbmcgdGhlIHZpcnR1YWwgaG9z
dCBuYW1lIGFzIHRoZSBhcmd1bWVudCB0byB0aGUgQ1dEIGNvbW1hbmQuICBUaGlzIHdvdWxkIGFs
bG93IHRoZSBzZXJ2ZXItRlRQIHByb2Nlc3MgdG8gaW1wbGVtZW50IHRoZSBmaWxlIHN0b3JlcyBv
ZiB0aGUgdmlydHVhbCBob3N0cyBhcyBzdWItZGlyZWN0b3JpZXMgaW4gaXRzIE5WRlMuICBUaGlz
IHN1Z2dlc3Rpb24gaXMgc2ltcGxlIGluIGNvbmNlcHQsIGFuZCBtb3N0IHNlcnZlci1GVFAgaW1w
bGVtZW50YXRpb25zIHN1cHBvcnQgdGhpcyB3aXRob3V0IHJlcXVpcmluZyBhbnkgY29kZSBjaGFu
Z2VzLiAgV2hpbGUgdGhpcyBtZXRob2QgaXMgc2ltcGxlIHRvIGRlc2NyaWJlLCBhbmQgdG8gaW1w
bGVtZW50LCBpdCBzdWZmZXJzIGZyb20gc2V2ZXJhbCBkcmF3YmFja3M6PC90Pg0KICAgICAgICA8
dD4NCiAgICAgICAgICA8bGlzdCBzdHlsZT0ibGV0dGVycyI+DQogICAgICAgICAgICA8dD5UaGUg
IkNXRCIgY29tbWFuZCBpcyBhdmFpbGFibGUgb25seSBhZnRlciB0aGUgdXNlci1QSSBoYXMgYXV0
aGVudGljYXRlZCBpdHNlbGYgdG8gdGhlIHNlcnZlci1GVFAgcHJvY2Vzcy4gIFRodXMsIGFsbCB2
aXJ0dWFsIGhvc3RzIHdvdWxkIGJlIHJlcXVpcmVkIHRvIHNoYXJlIGEgY29tbW9uIGF1dGhlbnRp
Y2F0aW9uIHNjaGVtZSBpZiB0aGV5IHVzZWQgdGhpcyBtZXRob2QuPC90Pg0KICAgICAgICAgICAg
PHQ+VG8gbWFrZSB0aGUgdmlydHVhbCBob3N0IHRydWx5IHRyYW5zcGFyZW50LCBlaXRoZXIgdGhl
IHNlcnZlci1GVFAgcHJvY2VzcyBuZWVkcyB0byBiZSBtb2RpZmllZCB0byBpbmNsdWRlIGluZm9y
bWF0aW9uIHRoYXQgc2hvd3MgdGhlIHNwZWNpYWwgbmF0dXJlIG9mIHRoaXMgZmlyc3QgQ1dEIGNv
bW1hbmQgKG5lZ2F0aW5nIG1vc3Qgb2YgdGhlIGFkdmFudGFnZSBvZiB0aGlzIHNjaGVtZSksIG9y
IGFsbCB1c2VycyBtdXN0IHNlZSB0aGUgc2FtZSBpZGVudGljYWwgTlZGUyB2aWV3IHVwb24gY29u
bmVjdGluZyAodGhleSBtdXN0IGNvbm5lY3QgaW4gdGhlIHNhbWUgaW5pdGlhbCBkaXJlY3Rvcnkp
LCBvciB0aGUgTlZGUyBtdXN0IGltcGxlbWVudCB0aGUgZnVsbCBzZXQgb2YgdmlydHVhbCBob3N0
IGRpcmVjdG9yaWVzIGF0IGVhY2ggcG9zc2libGUgaW5pdGlhbCBkaXJlY3RvcnkgZm9yIGFueSBw
b3NzaWJsZSB1c2VyLjwvdD4NCiAgICAgICAgICAgIDx0PlVubGVzcyB0aGUgc2VydmVyIGlzIHNw
ZWNpYWxseSBtb2RpZmllZCwgYSB1c2VyIGNvbm5lY3RpbmcgdGhpcyB3YXkgdG8gYSB2aXJ0dWFs
IGhvc3Qgd291bGQgYmUgYWJsZSB0byBlYXNpbHkgbW92ZSB0byBhbnkgb3RoZXIgdmlydHVhbCBo
b3N0IHN1cHBvcnRlZCBhdCB0aGUgc2FtZSBzZXJ2ZXItRlRQIHByb2Nlc3MsIGV4cG9zaW5nIHRo
ZSBuYXR1cmUgb2YgdGhlIHZpcnR1YWwgaG9zdC48L3Q+DQogICAgICAgICAgPC9saXN0Pg0KICAg
ICAgICA8L3Q+DQogICAgICA8L3NlY3Rpb24+DQogICAgICA8c2VjdGlvbiB0aXRsZT0iT3Zlcmxv
YWRpbmcgdGhlIEFDQ1QgY29tbWFuZCIgdG9jPSJkZWZhdWx0Ij4NCiAgICAgICAgPHQ+QW5vdGhl
ciBzdWdnZXN0ZWQgbWV0aG9kIHdvdWxkIGJlIHRvIHNpbXBseSBvdmVybG9hZCB0aGUgIkFDQ1Qi
IGZvciBGVFAgdmlydHVhbCBob3N0cywgYnV0IHRoaXMgcHJvcG9zYWwgaXMgdW5hY2NlcHRhYmxl
IGZvciBzZXZlcmFsIHJlYXNvbnMgd2l0aCByZWdhcmQgdG8gd2hlbiB0aGUgQUNDVCBjb21tYW5k
IGlzIHNlbnQgZHVyaW5nIHRoZSByZXF1ZXN0IGZsb3cuICBTZWN0aW9ucyA1LjQgYW5kIDYgb2Yg
PHhyZWYgdGFyZ2V0PSJSRkMwOTU5IiBwYWdlbm89ImZhbHNlIiBmb3JtYXQ9ImRlZmF1bHQiIC8+
IGRvY3VtZW50IHRoZSByZXF1ZXN0IGZsb3cgZm9yIGEgbG9naW4gc2VxdWVuY2UgYXMgVVNFUiAt
Jmd0OyBQQVNTIC0mZ3Q7IEFDQ1QuICBUaGlzIGZsb3cgb2YgY29tbWFuZHMgbWF5IGJlIGFjY2Vw
dGFibGUgd2hlbiB5b3UgYXJlIGNvbnNpZGVyaW5nIGEgc2luZ2xlIHVzZXIgaGF2aW5nIG11bHRp
cGxlIGFjY291bnRzIG9uIGFuIEZUUCBzZXJ2ZXIsIGJ1dCBmYWlscyB0byBkaWZmZXJlbnRpYXRl
IGJldHdlZW4gdmlydHVhbCBob3N0cyB3aGVuIHlvdSBjb25zaWRlciB0aGUgZm9sbG93aW5nIHR3
byBpc3N1ZXM6PC90Pg0KICAgICAgICA8dD4NCiAgICAgICAgICA8bGlzdCBzdHlsZT0ibGV0dGVy
cyI+DQogICAgICAgICAgICA8dD5UaGUgZmlyc3QgcHJvYmxlbSB3aXRoIG92ZXJsb2FkaW5nIHRo
ZSBBQ0NUIGNvbW1hbmQgaXMgY2VydGlmaWNhdGUgbmVnb3RpYXRpb24gd2hlbiB1c2luZyB0aGUg
RlRQIHNlY3VyaXR5IGV4dGVuc2lvbnMgdGhhdCBhcmUgZG9jdW1lbnRlZCBpbiA8eHJlZiB0YXJn
ZXQ9IlJGQzIyMjgiIHBhZ2Vubz0iZmFsc2UiIGZvcm1hdD0iZGVmYXVsdCIgLz4gYW5kIDx4cmVm
IHRhcmdldD0iUkZDNDIxNyIgcGFnZW5vPSJmYWxzZSIgZm9ybWF0PSJkZWZhdWx0IiAvPi4gIElu
IG9yZGVyIHRvIHNhZmVndWFyZCB1c2VyIGNyZWRlbnRpYWxzLCBzZWN1cml0eSBtZWNoYW5pc20g
YW5kIGNlcnRpZmljYXRlIG5lZ290aWF0aW9uIG11c3Qgb2NjdXIgYmVmb3JlIGxvZ2luIGNyZWRl
bnRpYWxzIGFyZSBzZW50IGJ5IHRoZSBjbGllbnQuICBUaGUgcHJvYmxlbSB3aXRoIHVzaW5nIHRo
ZSBBQ0NUIGNvbW1hbmQgaW4gdGhpcyBzY2VuYXJpbyBpcyB0aGF0IHRoZXJlIGlzIG5vIHdheSBv
ZiBlbnN1cmluZyB0aGF0IHRoZSBjZXJ0aWZpY2F0ZSBtYXRjaGVzIHRoZSBjb3JyZWN0IHZpcnR1
YWwgaG9zdCBiZWZvcmUgdGhlIHVzZXIgY3JlZGVudGlhbHMgYXJlIHNlbnQuPC90Pg0KICAgICAg
ICAgICAgPHQ+VGhlIHNlY29uZCBwcm9ibGVtIHdpdGggb3ZlcmxvYWRpbmcgdGhlIEFDQ1QgY29t
bWFuZCBpcyBob3cgdXNlciBjcmVkZW50aWFscyBhcmUgaW1wbGVtZW50ZWQgZm9yIEZUUCB2aXJ0
dWFsIGhvc3RzLiAgRlRQIHNlcnZlciBpbXBsZW1lbnRhdGlvbnMgbWF5IGFsbG93IHRoZSB1c2Ug
b2YgY3VzdG9tIHVzZXIgY3JlZGVudGlhbHMgb24gYSBwZXItdmlydHVhbC1ob3N0IGJhc2lzLiAg
Rm9yIGV4YW1wbGUsIGluIG9uZSBwYXJ0aWN1bGFyIGltcGxlbWVudGF0aW9uIHRoZSB2aXJ0dWFs
IGhvc3QgbmVnb3RpYXRpb24gb2NjdXJzLCBhbmQgdGhlbiB0aGUgdXNlciBjcmVkZW50aWFscyBh
cmUgbG9va2VkIHVwIHVzaW5nIHRoZSBhY2NvdW50IG1lY2hhbmlzbSB0aGF0IGlzIHNwZWNpZmlj
IHRvIHRoYXQgdmlydHVhbCBob3N0LiAgU28gb25jZSBhZ2FpbiB0aGUgdmlydHVhbCBob3N0IG5l
Z290aWF0aW9uIG11c3QgdGFrZSBwbGFjZSBiZWZvcmUgdGhlIHVzZXIgY3JlZGVudGlhbHMgYXJl
IHNlbnQuPC90Pg0KICAgICAgICAgIDwvbGlzdD4NCiAgICAgICAgPC90Pg0KICAgICAgPC9zZWN0
aW9uPg0KICAgICAgPHNlY3Rpb24gdGl0bGU9Ik92ZXJsb2FkaW5nIHRoZSBVU0VSIGNvbW1hbmQi
IHRvYz0iZGVmYXVsdCI+DQogICAgICAgIDx0PkFuIGFkZGl0aW9uYWwgc3VnZ2VzdGlvbiB3b3Vs
ZCBiZSB0byBvdmVybG9hZCB3ZWxsLWtub3duIHN5bnRheCB0aHJvdWdoIHRoZSBleGlzdGluZyBV
U0VSIGNvbW1hbmQsIGFzIGlsbHVzdHJhdGVkIGluIHRoZSBmb2xsb3dpbmcgZXhhbXBsZTo8L3Q+
DQogICAgICAgIDx0Pg0KICAgICAgICAgIDxmaWd1cmUgdGl0bGU9IiIgc3VwcHJlc3MtdGl0bGU9
ImZhbHNlIiBhbGlnbj0ibGVmdCIgYWx0PSIiIHdpZHRoPSIiIGhlaWdodD0iIj4NCiAgICAgICAg
ICAgIDxhcnR3b3JrIHhtbDpzcGFjZT0icHJlc2VydmUiIG5hbWU9IiIgdHlwZT0iIiBhbGlnbj0i
bGVmdCIgYWx0PSIiIHdpZHRoPSIiIGhlaWdodD0iIj48IVtDREFUQVsgICAgIEM+IFVTRVIgZm9v
QGV4YW1wbGUuY29tDQogICAgIFM+IDMzMSBQYXNzd29yZCByZXF1aXJlZA0KICAgICBDPiBQQVNT
IGJhcg0KICAgICBTPiAyMzAgVXNlciBsb2dnZWQgaW5dXT48L2FydHdvcms+DQogICAgICAgICAg
PC9maWd1cmU+DQogICAgICAgIDwvdD4NCiAgICAgICAgPHQ+SW4gdGhpcyBleGFtcGxlLCB0aGUg
dXNlciAiZm9vIiBtaWdodCBiZSBhdHRlbXB0aW5nIHRvIGxvZyBvbiB0byB0aGUgdmlydHVhbCBo
b3N0ICJleGFtcGxlLmNvbSIgb24gYW4gRlRQIHNlcnZlci4gIFRoaXMgc3VnZ2VzdGlvbiBtYXkg
c2VlbSBwbGF1c2libGUgYXQgZmlyc3QsIGJ1dCBpbnRyb2R1Y2VzIHNldmVyYWwgaW1wbGVtZW50
YXRpb24gcHJvYmxlbXMuICBGb3IgZXhhbXBsZTo8L3Q+DQogICAgICAgIDx0Pg0KICAgICAgICAg
IDxsaXN0IHN0eWxlPSJsZXR0ZXJzIj4NCiAgICAgICAgICAgIDx0PlNvbWUgbmV0d29yayBlbnZp
cm9ubWVudHMgYWxyZWFkeSB1c2UgdGhlICJ1c2VybmFtZUBob3N0bmFtZSIgc3ludGF4IGZvciBu
ZXR3b3JrIGNyZWRlbnRpYWxzLCB3aGVyZSB0aGUgImhvc3RuYW1lIiBwb3J0aW9uIHJlZmVycyB0
byB0aGUgbG9jYXRpb24gb2YgdGhlIHVzZXIncyBjcmVkZW50aWFscyB3aXRoaW4gdGhlIG5ldHdv
cmsgaGllcmFyY2h5LiAgVXNpbmcgdGhlICJmb29AZXhhbXBsZS5jb20iIHN5bnRheCBpdCBiZWNv
bWVzIGRpZmZpY3VsdCB0byBkaWZmZXJlbnRpYXRlIGJldHdlZW4gdGhlIHVzZXIgImZvbyIgbG9n
Z2luZyBpbnRvIGEgdmlydHVhbCBob3N0IG5hbWVkICJleGFtcGxlLmNvbSIgb24gYW4gRlRQIHNl
cnZlciB2ZXJzdXMgdGhlIHVzZXIgImZvb0BleGFtcGxlLmNvbSIgbG9nZ2luZyBpbnRvIGFuIEZU
UCBzZXJ2ZXIgd2l0aCBubyBzcGVjaWZpZWQgdmlydHVhbCBob3N0LjwvdD4NCiAgICAgICAgICAg
IDx0PldoZW4gdXNpbmcgdGhlIEZUUCBzZWN1cml0eSBleHRlbnNpb25zIHRoYXQgYXJlIGRvY3Vt
ZW50ZWQgaW4gPHhyZWYgdGFyZ2V0PSJSRkMyMjI4IiBwYWdlbm89ImZhbHNlIiBmb3JtYXQ9ImRl
ZmF1bHQiIC8+IGFuZCA8eHJlZiB0YXJnZXQ9IlJGQzQyMTciIHBhZ2Vubz0iZmFsc2UiIGZvcm1h
dD0iZGVmYXVsdCIgLz4sIHNlY3VyaXR5IG1lY2hhbmlzbSBhbmQgY2VydGlmaWNhdGUgbmVnb3Rp
YXRpb24gbXVzdCBvY2N1ciBiZWZvcmUgbG9naW4gY3JlZGVudGlhbHMgYXJlIHNlbnQgYnkgdGhl
IGNsaWVudC4gIE1vcmUgc3BlY2lmaWNhbGx5LCB0aGUgQVVUSC9BREFUIGNvbW1hbmRzIG11c3Qg
YmUgc2VudCBiZWZvcmUgdGhlIFVTRVIgY29tbWFuZCBpbiBvcmRlciB0byBzYWZlZ3VhcmQgdXNl
ciBjcmVkZW50aWFscy4gIElmIHlvdSBvdmVybG9hZCB0aGUgVVNFUiBjb21tYW5kLCB0aGVyZSBp
cyBubyB3YXkgb2YgZW5zdXJpbmcgdGhhdCB0aGUgY2VydGlmaWNhdGUgbWF0Y2hlcyB0aGUgY29y
cmVjdCB2aXJ0dWFsIGhvc3QgYmVmb3JlIHRoZSB1c2VyIGNyZWRlbnRpYWxzIGFyZSBzZW50IGJ5
IHRoZSBjbGllbnQuPC90Pg0KICAgICAgICAgIDwvbGlzdD4NCiAgICAgICAgPC90Pg0KICAgICAg
PC9zZWN0aW9uPg0KICAgICAgPHNlY3Rpb24gdGl0bGU9IkNvbmNsdXNpb24iIHRvYz0iZGVmYXVs
dCI+DQogICAgICAgIDx0PlRoZSBjb25jbHVzaW9uIGZyb20gdGhlIGV4YW1pbmF0aW9uIG9mIHRo
ZSBleGlzdGluZyBwb3NzaWJpbGl0aWVzIHNlZW1zIHRvIGJlIHRoYXQgaW4gb3JkZXIgdG8gb2J0
YWluIGFuIGFkZXF1YXRlIGVtdWxhdGlvbiBvZiAicmVhbCIgRlRQIHNlcnZlcnMsIGNsaWVudCBh
bmQgc2VydmVyIG1vZGlmaWNhdGlvbnMgdG8gc3VwcG9ydCB2aXJ0dWFsIGhvc3RzIGFyZSBuZWNl
c3NhcnkuICBUaGVyZWZvcmUgYSBuZXcgRlRQIGNvbW1hbmQgc2VlbXMgdGhlIG1vc3QgbGlrZWx5
IHNvbHV0aW9uIHRvIHByb3ZpZGUgdGhlIHJlcXVpcmVkIGxldmVsIG9mIHN1cHBvcnQuPC90Pg0K
ICAgICAgPC9zZWN0aW9uPg0KICAgIDwvc2VjdGlvbj4NCiAgICA8c2VjdGlvbiBhbmNob3I9IkFj
a25vd2xlZGdlbWVudHMiIHRpdGxlPSJBY2tub3dsZWRnZW1lbnRzIiB0b2M9ImRlZmF1bHQiPg0K
ICAgICAgPHQ+Um9iZXJ0IEVseiBhbmQgUGF1bCBIZXRobW9uIHByb3ZpZGVkIGEgZGV0YWlsZWQg
ZGlzY3Vzc2lvbiBvZiB0aGUgSE9TVCBjb21tYW5kIGluIHRoZWlyIEludGVybmV0IGRyYWZ0IHRp
dGxlZCAiRXh0ZW5zaW9ucyB0byBGVFAiIGFzIHBhcnQgb2YgdGhlaXIgd29yayB3aXRoIHRoZSBG
VFBFWFQgV29ya2luZyBHcm91cCBhdCB0aGUgSUVURi4gIFRoZWlyIHdvcmsgZm9ybWVkIHRoZSBi
YXNpcyBmb3IgbXVjaCBvZiB0aGlzIGRvY3VtZW50LCBhbmQgdGhlaXIgaGVscCBoYXMgYmVlbiBn
cmVhdGx5IGFwcHJlY2lhdGVkLiAgVGhleSB3b3VsZCBhbHNvIGxpa2UgdG8gY3JlZGl0IEJlcm5o
YXJkIFJvc2Vua3JhZW56ZXIgZm9yIGhhdmluZyBmaXJzdCBzdWdnZXN0ZWQgYW5kIGRlc2NyaWJl
ZCB0aGUgSE9TVCBjb21tYW5kLjwvdD4NCiAgICAgIDx0PkFsZXhleSBNZWxuaWtvdiwgQWxmcmVk
IEhvZW5lcywgSm9obiBLbGVuc2luLCBhbmQgSm9lIFRvdWNoIGhhdmUgbWFkZSBzZXZlcmFsIHN1
Z2dlc3Rpb25zIGFib3V0IGVhcmxpZXIgdmVyc2lvbnMgb2YgdGhpcyBkb2N1bWVudDsgbWFueSBv
ZiB0aGVpciBzdWdnZXN0aW9ucyBoYXZlIGJlZW4gaW5jb3Jwb3JhdGVkLCBhbmQgdGhlaXIgY29u
dHJpYnV0aW9ucyBhcmUgZ3JhdGVmdWxseSBhY2tub3dsZWRnZWQuICBJbiBhZGRpdGlvbiwgQWxl
YyBSb3dlbGwncyBhc3Npc3RhbmNlIGluIG1ha2luZyBzZWN0aW9ucyBvZiB0aGlzIGRvY3VtZW50
IG1vcmUgcmVhZGFibGUgd2FzIGludmFsdWFibGUuPC90Pg0KICAgIDwvc2VjdGlvbj4NCiAgPC9i
YWNrPg0KPC9yZmM+

--_004_01AA9EC92749BF4894AC2B3039EA4A2C194A07E2CH1PRD0302MB131_--

From osa.peter@gmail.com  Wed Jun 29 15:23:22 2011
Return-Path: <osa.peter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 735E011E807B for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 15:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wcTbXdIoOisM for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 15:23:20 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id CE28E21F85A3 for <ietf@ietf.org>; Wed, 29 Jun 2011 15:23:20 -0700 (PDT)
Received: by pzk5 with SMTP id 5so1641522pzk.31 for <ietf@ietf.org>; Wed, 29 Jun 2011 15:23:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=CMeoG4RjdSobLW5Ld4zAYJ5WvbV9w4R/7XCv5AmPmyI=; b=vulSi0LAMSM/cfgsU+q6JszqMbafyG6FV96UiDiBN4sGdFJEZdOZfXeMf0WRRe6m6r igtfRYrHH7L71oGKjK1/UH/Nh0gbdSd4eRmrK9jXFynzRM8nqu2h8X93hxiFH3JZhk/J Bir0XwO6YqJRGPShwu96BnDUwrJ6+Tx6XYgCI=
MIME-Version: 1.0
Received: by 10.142.250.4 with SMTP id x4mr652263wfh.70.1309386200250; Wed, 29 Jun 2011 15:23:20 -0700 (PDT)
Received: by 10.142.213.20 with HTTP; Wed, 29 Jun 2011 15:23:20 -0700 (PDT)
In-Reply-To: <mailman.596.1309365174.3031.ietf@ietf.org>
References: <mailman.596.1309365174.3031.ietf@ietf.org>
Date: Wed, 29 Jun 2011 23:23:20 +0100
Message-ID: <BANLkTinGZZ9q7gSU2yD_Cqb8AoGm1bcSWQ@mail.gmail.com>
Subject: Re: Ietf Digest, Vol 37, Issue 103
From: Amenawon Osa Peter <osa.peter@gmail.com>
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: Wed, 29 Jun 2011 22:23:22 -0000

I as a new member is it possible that i be given a clue on what this
work group aim is to enable me be able to contribute positively.

thank you

On 6/29/11, ietf-request@ietf.org <ietf-request@ietf.org> wrote:
> If you have received this digest without all the individual message
> attachments you will need to update your digest options in your list
> subscription.  To do so, go to
>
> https://www.ietf.org/mailman/listinfo/ietf
>
> Click the 'Unsubscribe or edit options' button, log in, and set "Get
> MIME or Plain Text Digests?" to MIME.  You can set this option
> globally for all the list digests you receive at this point.
>
>
>
> Send Ietf mailing list submissions to
> 	ietf@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.ietf.org/mailman/listinfo/ietf
> or, via email, send a message with subject or body 'help' to
> 	ietf-request@ietf.org
>
> You can reach the person managing the list at
> 	ietf-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ietf digest..."
>
>
> Today's Topics:
>
>    1. HOMENET working group proposal (Jari Arkko)
>    2. RE: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt>
>       (File	Transfer Protocol	HOST Command for Virtual Hosts) to
>       Proposed	Standard (Robert McMurray)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 29 Jun 2011 10:47:18 +0200
> From: Jari Arkko <jari.arkko@piuha.net>
> To: "homegate@ietf.org" <homegate@ietf.org>, IETF Discussion
> 	<ietf@ietf.org>
> Cc: "W. Mark Townsley" <townsley@cisco.com>
> Subject: HOMENET working group proposal
> Message-ID: <4E0AE696.4020603@piuha.net>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> I would like to announce a new effort around home networking and solicit
> some feedback.
>
> HOMENET is a new working group proposal, a variation of the
> HOMEGATE/HOMENET theme that we discussed last year, but this time
> looking at it from a different angle. The old effort was mostly focused
> about what home gateways should do: forwarding, transport, and DNS
> proxying issues. The new effort is about home networks themselves, in
> particular what kind of network architecture and configuration is
> necessary to support IPv6-based home networks. We view IPv4-based home
> networks as "done" at this time (or perhaps as "cannot be changed anyway").
>
> I have been discussing this effort in the background for the last couple
> of month with Mark Townsley and others, and more publicly since early
> June. The proposal has been brought to the IESG, IAB and some
> directorates for discussion, and we've been going back and forth whether
> this is ready to become a working group or needs to be run as a BOF in
> Quebec City. The current plan is that the working group proposal goes to
> IETF-wide review this week, and if the feedback from the community, IAB,
> and the IESG is positive, we will create the working group just in time
> for the IETF. Otherwise, the slot reserved in the agenda for the meeting
> will be used to run the proposal as a BOF.
>
> In any case, I would like to solicit discussion on this topic, and
> perhaps some early drafts as well. Please comment on the charter at
> least. Go here to subscribe https://www.ietf.org/mailman/listinfo/fun
> and below you can find the most recent charter proposal. Please join the
> list and the discussion.
>
> Note that the new proposal was called FUN at the time that we created
> the list. It has now been renamed back to HOMENET to be more
> descriptive. The list will be renamed soon as well (current subscribers
> will stay). Note also that I'm sending this to the old homegate list, to
> inform people who were interested in that. I'd like the discussion to
> happen on the fun@ietf.org list, however.
>
> Jari
>
> Home Networks (homenet)
> -----------------------------------
>
> Current Status: Proposed
> Last Edit: Wednesday, June 29th, 2011
>
> Chairs:
> TBD
>
> Internet Area Directors:
> Ralph Droms <rdroms.ietf@gmail.com>
> Jari Arkko <jari.arkko@piuha.net>
>
> Internet Area Advisor:
> Jari Arkko <jari.arkko@piuha.net>
>
> Routing Area Technical Advisor:
> TBD
>
> Security Area Technical Advisor:
> TBD
>
> Mailing Lists:
> General Discussion: fun@ietf.org
> To Subscribe: https://www.ietf.org/mailman/listinfo/fun
> Archive: http://www.ietf.org/mail-archive/web/fun
>
> Description of Working Group:
>
> This working group focuses on the evolving networking technology
> within and among relatively small ?residential home? networks. For
> example, an obvious trend in home networking is the proliferation of
> networking technology in an increasingly broad range and number of
> devices. This evolution in scale and diversity sets some requirements
> on IETF protocols. Some of the relevant trends include:
>
> o Multiple segments: While less complex L3-toplogies involving as few
> subnets as possible are preferred in home networks for a variety of
> reasons including simpler management and service discovery, the
> introduction of more than one subnet into a home network is enough
> to add complexity that needs to be addressed, and multiple
> dedicated segments are necessary for some cases. For instance, a
> common feature in modern home routers in the ability to support
> both guest and private network segments. Also, link layer
> networking technology is poised to become more heterogeneous, as
> networks begin to employ both traditional Ethernet technology and
> link layers designed for low-powered sensor networks. Finally,
> similar needs for segmentation may occur in other cases, such as
> separating building control or corporate extensions from the
> Internet access network. Different segments may be associated with
> subnets that have different routing and security policies.
>
> o Service providers are deploying IPv6, and support for IPv6 is
> increasingly available in home gateway devices. While IPv6 resembles
> IPv4 in many ways, it changes address allocation principles and allows
> direct IP addressability and routing to devices in the home from the
> Internet. This is a promising area in IPv6 that has proved challenging
> in IPv4 with the proliferation of NAT.
>
> o End-to-end communication is both an opportunity and a concern as it
> enables new applications but also exposes nodes in the internal
> networks to receipt of unwanted traffic from the Internet. Firewalls
> that restrict incoming connections may be used to prevent exposure,
> however, this reduces the efficacy of end-to-end connectivity that
> IPv6 has the potential to restore.
>
> Home networks need to provide the tools to handle these situations in
> a manner accessible to all users of home networks. Manual
> configuration is rarely, if at all, possible. The purpose of this
> working group is to focus on this evolution, in particular as it
> addresses the introduction of IPv6, by developing an architecture
> addressing this full scope of requirements:
>
> o prefix configuration for routers
> o managing routing
> o name resolution
> o service discovery
> o network security
>
> The task of the group is to produce an architecture document that
> outlines how to construct home networks involving multiple routers and
> subnets. This document is expected to apply the IPv6 addressing
> architecture, prefix delegation, global and ULA addresses, source
> address selection rules and other existing components of the IPv6
> architecture. The architecture document should drive what protocols
> changes, if any, are necessary. Specific protocol work described below
> is expected to be within the scope of the working group one the
> architecture work is complete. However, the group is required to
> review its charter and milestones with the IESG and IETF community
> before submitting documents that make protocol changes. It is expected
> that the group has to discuss some of the below solutions, however, in
> order to complete the architecture work.
>
> The group will apply existing protocols to handle the five
> requirements above. For prefix configuration, existing protocols are
> likely sufficient, and at worst may need some small enhancements, such
> as new options. For automatic routing, it is expected that existing
> routing protocols can be used as is, however, a new mechanism may be
> needed in order to turn a selected protocol on by default. For name
> resolution and service discovery, extensions to existing
> multicast-based name resolution protocols are needed to enable them to
> work across subnets.
>
> For network security, the group shall document the concept of
> "advanced security" as a further development of "simple security" from
> RFC 6092. The main goal of this work is to enable a security policy
> that adapts to IPv6 threats as they emerge, taking into account not
> only traffic from the Internet at large, but within and leaving the
> home network itself.
>
> It is expected that the working group will define a set of protocol
> specifications to accomplish the five requirements from
> above. However, it is not in the scope of the working group to define
> entirely new routing protocols or address allocation protocols. As
> noted, additional options or other small extensions may be necessary
> to use the existing protocols in these new configuration tasks. The
> working group shall also not make any changes to IPv6 protocols or
> addressing architecture. Prefix configuration, routing, and security
> related work shall not cause any changes that are not backwards
> compatible to existing IPv6 hosts. There may be host visible changes
> in the work on naming and discovery protocols, however. In its design,
> the working group shall also consider security aspects and the impact
> on manageability. The main focus of the working group is home
> networks, but the group's results may also find applications in other
> small networks.
>
> The working group will liaise with the relevant IETF working
> groups. In particular, the group should work closely with the V6OPS
> working group, review any use or extension of DHCP with the DHC
> working group, and work with additional DNS requirements with the
> DNSEXT and DNSOP working groups. If it turns out that additional
> options are needed for a routing protocol, they will be developed in
> the appropriate Routing Area working group, with the HOMENET working
> group providing the architecture and requirements for such
> enhancements. The working group will also liase with external
> standards bodies where it is expected that there are normative
> dependencies between the specifications of the two bodies.
> It is expected that in the architecture definition stage liaising
> with the Broadband Forum, DLNA, and UPnP Forum is necessary.
>
> Milestones:
>
> Jul 2011 Formation of the working group
> Sep 2011 First WG draft on the architecture
> Dec 2011 Submission of the architecture draft to the IESG as
> Informational RFC
> Dec 2011 Charter re-evaluation based on the architecture work
> Dec 2011 First WG draft on prefix configuration
> Dec 2011 First WG draft on routing
> Jan 2012 First WG draft on name resolution
> Feb 2012 First WG draft on service discovery
> Feb 2012 First WG draft on perimeter security
> Feb 2012 Start of routing related work in the relevant routing area
> working group, if needed
> Mar 2012 Submission of the prefix configuration draft to the IESG as
> Standards Track RFC
> Apr 2012 Submission of the routing draft to the IESG as Informational RFC
> Sep 2012 Submission of the name resolution draft to the IESG as
> Standards Track RFC
> Nov 2012 Submission of the service discovery draft to the IESG as
> Standards Track RFC
> Dec 2012 Submission of the perimeter security draft to the IESG as
> Informational RFC
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 29 Jun 2011 02:04:16 +0000
> From: Robert McMurray <robmcm@microsoft.com>
> To: Paul Ford-Hutchinson <paulfordh@uk.ibm.com>, "ietf@ietf.org"
> 	<ietf@ietf.org>
> Cc: "ftpext@ietf.org" <ftpext@ietf.org>
> Subject: RE: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt>
> 	(File	Transfer Protocol	HOST Command for Virtual Hosts) to Proposed
> 	Standard
> Message-ID:
> 	<01AA9EC92749BF4894AC2B3039EA4A2C194A07E2@CH1PRD0302MB131.namprd03.prod.outlook.com>
> 	
> Content-Type: text/plain; charset="us-ascii"
>
> Thanks, Paul.
>
> I believe that I have addressed all of your comments with the following
> actions:
>
> --------------------
> Section 3:
> --------------------
>
>> Surely the first SHOULD has to be a MUST.
>> Otherwise we have a situation where, upon
>> receipt of a valid HOST, some server
>> implementations will implicitly REIN and
>> clear AUTH/USER/ACCT and some will not.
>
> Agreed - I changed that verbiage.
>
> --------------------
> Section 3.2:
> --------------------
>
>> I suggest that either the "wrapper" concept is
>> dropped from the document altogether...
>
> I removed that verbiage. (That was detail for a possible server
> implementation anyway.)
>
> --------------------
> Section 3.2.2:
> --------------------
>
>> should be "to negotiate the security mechanism
>> and relevant authentication token(s)"
>
> I changed that as well.
>
> --------------------
> Section 4
> --------------------
>
>> The "strong method of encryption" is a bit
>> vague. I don't think we can publish this
>> paragraph without being more explicit about
>> what this really means.
>
> I removed that paragraph. By way of explanation, this was in reference a
> server implementation detail that in hindsight probably shouldn't be in this
> document. More specifically, some FTP servers and clients support Implicit
> FTPS, but that is not defined by RFC and lately considered deprecated, so
> it's best to just remove that information.
>
>> I repeat my initial point - this has to be a MUST.
>
> Agreed - I changed that verbiage.
>
>> I would like some mention of the linkage
>> between the identity returned in an X.509
>> certificate and the parameter to the HOST
>> command at the protocol specification level.
>
> I have attached a new version of the draft that contains suggested wording
> for this request, with all of the other changes that I have addressed as
> well.
>
>
> Thanks!
>
> Robert
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: draft-ietf-ftpext2-hosts-04.pdf
> Type: application/pdf
> Size: 34609 bytes
> Desc: draft-ietf-ftpext2-hosts-04.pdf
> URL:
> <http://www.ietf.org/mail-archive/web/ietf/attachments/20110629/3bfb97e2/attachment.pdf>
> -------------- next part --------------
> An embedded and charset-unspecified text was scrubbed...
> Name: draft-ietf-ftpext2-hosts-04.txt
> URL:
> <http://www.ietf.org/mail-archive/web/ietf/attachments/20110629/3bfb97e2/attachment.txt>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: draft-ietf-ftpext2-hosts-04.xml
> Type: application/xml
> Size: 57525 bytes
> Desc: draft-ietf-ftpext2-hosts-04.xml
> URL:
> <http://www.ietf.org/mail-archive/web/ietf/attachments/20110629/3bfb97e2/attachment.xpdl>
>
> ------------------------------
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>
> End of Ietf Digest, Vol 37, Issue 103
> *************************************
>


-- 
In this Life we blow like the wind, where we blow to we can never
tell, the air we blow out we may not know the density. the only thing
we should know is that some one is waiting to receive the air of life
from us, Lets blow the good air that will keep lives alive for our
better Tomorrow .... Peter Osa A Snr.

From fernando.gont.netbook.win@gmail.com  Wed Jun 29 19:18:53 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2354411E80B7; Wed, 29 Jun 2011 19:18:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.845
X-Spam-Level: 
X-Spam-Status: No, score=-0.845 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_BELOW2=2.154, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id th8yixeSksiw; Wed, 29 Jun 2011 19:18:52 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id AC26211E8072; Wed, 29 Jun 2011 19:18:48 -0700 (PDT)
Received: by ywp31 with SMTP id 31so914432ywp.31 for <multiple recipients>; Wed, 29 Jun 2011 19:18:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=5R1kl567g64jluzP6JJoCOuLzwQdjltc/wElb7GRDE4=; b=OD5+MOcAE4Kb3XF4NjSp7e5fvgRQ4T5MhIXYsUF2Aghxe21tLFF0FCp+GgXKAg6Ovv AnSG2nxKQA9XF4q4Ri5dbcH3T1qfcwkz8FtB7/waFlWtfhmw16/sj0rmM1dxovSmYH1o W9FVI57zNALTx9rvaeTHmjyRNO2iWFNwqnxjc=
Received: by 10.91.151.20 with SMTP id d20mr1391642ago.19.1309400328019; Wed, 29 Jun 2011 19:18:48 -0700 (PDT)
Received: from [192.168.123.103] ([190.48.223.58]) by mx.google.com with ESMTPS id y15sm1579479ann.44.2011.06.29.19.18.30 (version=SSLv3 cipher=OTHER); Wed, 29 Jun 2011 19:18:46 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4E0BDCF3.1090003@gont.com.ar>
Date: Wed, 29 Jun 2011 23:18:27 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net>
In-Reply-To: <4E0AE696.4020603@piuha.net>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: "W. Mark Townsley" <townsley@cisco.com>, "homegate@ietf.org" <homegate@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 02:18:53 -0000

Hi, Jari,

My high level comment/question is: the proposed charter seems to stress
that IPv6 is the driver behind this potential wg effort... however, I
think that this deserves more discussion -- it's not clear to me why/how
typical IPv6 home networks would be much different from their IPv4
counterparts.

Bellow you'll find some comments/questions about the proposed charter.
They are not an argument against or in favour of the creation of the
aforementioned wg, but rather comments and/or requests for clarification...

On 06/29/2011 05:47 AM, Jari Arkko wrote:
[....]
> o Service providers are deploying IPv6, and support for IPv6 is
> increasingly available in home gateway devices. While IPv6 resembles
> IPv4 in many ways, it changes address allocation principles and allows
> direct IP addressability and routing to devices in the home from the
> Internet. This is a promising area in IPv6 that has proved challenging
> in IPv4 with the proliferation of NAT.

NAT devices involve two related but different issues:
* address translation
* an implicit "allow only return traffic" firewall-like functionality

One would hope/expect that the former will be gone with IPv6. However, I
don't think the latter will. As a result, even when you could "address"
nodes that belong to the "home network", you probably won't be able to
get your packets to them, unless those nodes initiated the communication
instance.

For instance (and of the top of my head), this functionality is even
proposed in the "simple security" requirements that had been produced by
v6ops.


> o End-to-end communication is both an opportunity and a concern as it
> enables new applications but also exposes nodes in the internal
> networks to receipt of unwanted traffic from the Internet. Firewalls
> that restrict incoming connections may be used to prevent exposure,
> however, this reduces the efficacy of end-to-end connectivity that
> IPv6 has the potential to restore.

I personally consider this property of "end-to-end connectivity" as
"gone". -- among other reasons, because it would require a change of
mindset. I'm more of the idea that people will replicate the
architecture of their IPv4 networks with IPv6, in which end-systems are
not reachable from the public Internet.

Thanks!
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From cb.list6@gmail.com  Wed Jun 29 19:38:39 2011
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 D4FE621F8641; Wed, 29 Jun 2011 19:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.844
X-Spam-Level: 
X-Spam-Status: No, score=-0.844 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_BELOW2=2.154, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HN8h2CLAetHB; Wed, 29 Jun 2011 19:38:39 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8F7A821F8640; Wed, 29 Jun 2011 19:38:38 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1421862wyj.31 for <multiple recipients>; Wed, 29 Jun 2011 19:38:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ph5hfhyPyWKmcFgm8+2CEinWBQnSXS+Q9rGdTtzOpRg=; b=yAqnlrRQRUpQ3/xbJ2sZtkSRLQWivyAd3N1uKZvPhFLbPNmWMPoHqjjWcx5Ox39FvL x6uNBb9gRMjn7ytYSaz4xpbVvbzJdZOYReN8gGVAGnwHr9w0Puh+PKim8KRHFwK42SYh OvCFtJXxHCA2WPQfb/o6MDKV6K2IPuqRVPDj4=
MIME-Version: 1.0
Received: by 10.216.158.198 with SMTP id q48mr1200283wek.94.1309401517597; Wed, 29 Jun 2011 19:38:37 -0700 (PDT)
Received: by 10.216.39.83 with HTTP; Wed, 29 Jun 2011 19:38:37 -0700 (PDT)
Received: by 10.216.39.83 with HTTP; Wed, 29 Jun 2011 19:38:37 -0700 (PDT)
In-Reply-To: <4E0BDCF3.1090003@gont.com.ar>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar>
Date: Wed, 29 Jun 2011 19:38:37 -0700
Message-ID: <BANLkTinuPcq2r85kzMctFCHDB3Ta=WgA4A@mail.gmail.com>
Subject: Re: HOMENET working group proposal
From: Cameron Byrne <cb.list6@gmail.com>
To: Fernando Gont <fernando@gont.com.ar>
Content-Type: multipart/alternative; boundary=0016367fb5f95324b804a6e4ccc1
Cc: "W. Mark Townsley" <townsley@cisco.com>, IETF Discussion <ietf@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 02:38:40 -0000

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

On Jun 29, 2011 7:19 PM, "Fernando Gont" <fernando@gont.com.ar> wrote:
>
> Hi, Jari,
>
> My high level comment/question is: the proposed charter seems to stress
> that IPv6 is the driver behind this potential wg effort... however, I
> think that this deserves more discussion -- it's not clear to me why/how
> typical IPv6 home networks would be much different from their IPv4
> counterparts.
>
> Bellow you'll find some comments/questions about the proposed charter.
> They are not an argument against or in favour of the creation of the
> aforementioned wg, but rather comments and/or requests for
clarification...
>
> On 06/29/2011 05:47 AM, Jari Arkko wrote:
> [....]
> > o Service providers are deploying IPv6, and support for IPv6 is
> > increasingly available in home gateway devices. While IPv6 resembles
> > IPv4 in many ways, it changes address allocation principles and allows
> > direct IP addressability and routing to devices in the home from the
> > Internet. This is a promising area in IPv6 that has proved challenging
> > in IPv4 with the proliferation of NAT.
>
> NAT devices involve two related but different issues:
> * address translation
> * an implicit "allow only return traffic" firewall-like functionality
>
> One would hope/expect that the former will be gone with IPv6. However, I
> don't think the latter will. As a result, even when you could "address"
> nodes that belong to the "home network", you probably won't be able to
> get your packets to them, unless those nodes initiated the communication
> instance.
>
> For instance (and of the top of my head), this functionality is even
> proposed in the "simple security" requirements that had been produced by
> v6ops.
>
>
> > o End-to-end communication is both an opportunity and a concern as it
> > enables new applications but also exposes nodes in the internal
> > networks to receipt of unwanted traffic from the Internet. Firewalls
> > that restrict incoming connections may be used to prevent exposure,
> > however, this reduces the efficacy of end-to-end connectivity that
> > IPv6 has the potential to restore.
>
> I personally consider this property of "end-to-end connectivity" as
> "gone". -- among other reasons, because it would require a change of
> mindset. I'm more of the idea that people will replicate the
> architecture of their IPv4 networks with IPv6, in which end-systems are
> not reachable from the public Internet.
>

The opportunity for restoring e2e is one of the great opportunities of ipv6
and it is my hope this new WG will drive that with facts and take on fud.

The utility of network based spi firewalls is debatable. Likely a never
ending debate.

Cb
> Thanks!
> --
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@acm.org
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

--0016367fb5f95324b804a6e4ccc1
Content-Type: text/html; charset=ISO-8859-1

<p><br>
On Jun 29, 2011 7:19 PM, &quot;Fernando Gont&quot; &lt;<a href="mailto:fernando@gont.com.ar">fernando@gont.com.ar</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi, Jari,<br>
&gt;<br>
&gt; My high level comment/question is: the proposed charter seems to stress<br>
&gt; that IPv6 is the driver behind this potential wg effort... however, I<br>
&gt; think that this deserves more discussion -- it&#39;s not clear to me why/how<br>
&gt; typical IPv6 home networks would be much different from their IPv4<br>
&gt; counterparts.<br>
&gt;<br>
&gt; Bellow you&#39;ll find some comments/questions about the proposed charter.<br>
&gt; They are not an argument against or in favour of the creation of the<br>
&gt; aforementioned wg, but rather comments and/or requests for clarification...<br>
&gt;<br>
&gt; On 06/29/2011 05:47 AM, Jari Arkko wrote:<br>
&gt; [....]<br>
&gt; &gt; o Service providers are deploying IPv6, and support for IPv6 is<br>
&gt; &gt; increasingly available in home gateway devices. While IPv6 resembles<br>
&gt; &gt; IPv4 in many ways, it changes address allocation principles and allows<br>
&gt; &gt; direct IP addressability and routing to devices in the home from the<br>
&gt; &gt; Internet. This is a promising area in IPv6 that has proved challenging<br>
&gt; &gt; in IPv4 with the proliferation of NAT.<br>
&gt;<br>
&gt; NAT devices involve two related but different issues:<br>
&gt; * address translation<br>
&gt; * an implicit &quot;allow only return traffic&quot; firewall-like functionality<br>
&gt;<br>
&gt; One would hope/expect that the former will be gone with IPv6. However, I<br>
&gt; don&#39;t think the latter will. As a result, even when you could &quot;address&quot;<br>
&gt; nodes that belong to the &quot;home network&quot;, you probably won&#39;t be able to<br>
&gt; get your packets to them, unless those nodes initiated the communication<br>
&gt; instance.<br>
&gt;<br>
&gt; For instance (and of the top of my head), this functionality is even<br>
&gt; proposed in the &quot;simple security&quot; requirements that had been produced by<br>
&gt; v6ops.<br>
&gt;<br>
&gt;<br>
&gt; &gt; o End-to-end communication is both an opportunity and a concern as it<br>
&gt; &gt; enables new applications but also exposes nodes in the internal<br>
&gt; &gt; networks to receipt of unwanted traffic from the Internet. Firewalls<br>
&gt; &gt; that restrict incoming connections may be used to prevent exposure,<br>
&gt; &gt; however, this reduces the efficacy of end-to-end connectivity that<br>
&gt; &gt; IPv6 has the potential to restore.<br>
&gt;<br>
&gt; I personally consider this property of &quot;end-to-end connectivity&quot; as<br>
&gt; &quot;gone&quot;. -- among other reasons, because it would require a change of<br>
&gt; mindset. I&#39;m more of the idea that people will replicate the<br>
&gt; architecture of their IPv4 networks with IPv6, in which end-systems are<br>
&gt; not reachable from the public Internet.<br>
&gt;</p>
<p>The opportunity for restoring e2e is one of the great opportunities of ipv6 and it is my hope this new WG will drive that with facts and take on fud. </p>
<p>The utility of network based spi firewalls is debatable. Likely a never ending debate.</p>
<p>Cb<br>
&gt; Thanks!<br>
&gt; --<br>
&gt; Fernando Gont<br>
&gt; e-mail: <a href="mailto:fernando@gont.com.ar">fernando@gont.com.ar</a> || <a href="mailto:fgont@acm.org">fgont@acm.org</a><br>
&gt; PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Ietf mailing list<br>
&gt; <a href="mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
&gt; <a href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a><br>
</p>

--0016367fb5f95324b804a6e4ccc1--

From fernando.gont.netbook.win@gmail.com  Wed Jun 29 19:57:13 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55ACE21F8677; Wed, 29 Jun 2011 19:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[AWL=1.077,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GjzgCHWLdLSt; Wed, 29 Jun 2011 19:57:12 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6150221F8672; Wed, 29 Jun 2011 19:57:12 -0700 (PDT)
Received: by ywp31 with SMTP id 31so925618ywp.31 for <multiple recipients>; Wed, 29 Jun 2011 19:57:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=ytvjpVPzRjP+aUb6TcSbdH4abJe2RW2gdnDAzWcbHm4=; b=lyESNxbokgqwgDU6rv2G9Qk55TMB5NmeeLwWXDsEgEEyFTcnLC6ck8QHNqVJayYj1k RxhxLI6v8IRNPGU9ujr2vx3cIopTWuv0vaRPmFbqVJmrJgnh/7JLFzDNRww9JUYeSQ49 ZlNThhxbcCvcGCmaMcqRsvHW7lnmqvk4bbtfs=
Received: by 10.91.119.8 with SMTP id w8mr1386584agm.12.1309402631812; Wed, 29 Jun 2011 19:57:11 -0700 (PDT)
Received: from [192.168.123.103] ([190.48.223.58]) by mx.google.com with ESMTPS id g2sm1611058ano.14.2011.06.29.19.57.06 (version=SSLv3 cipher=OTHER); Wed, 29 Jun 2011 19:57:10 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4E0BE5FF.3000409@gont.com.ar>
Date: Wed, 29 Jun 2011 23:57:03 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Cameron Byrne <cb.list6@gmail.com>
Subject: Re: HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net>	<4E0BDCF3.1090003@gont.com.ar> <BANLkTinuPcq2r85kzMctFCHDB3Ta=WgA4A@mail.gmail.com>
In-Reply-To: <BANLkTinuPcq2r85kzMctFCHDB3Ta=WgA4A@mail.gmail.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "W. Mark Townsley" <townsley@cisco.com>, IETF Discussion <ietf@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 02:57:13 -0000

On 06/29/2011 11:38 PM, Cameron Byrne wrote:

> The opportunity for restoring e2e is one of the great opportunities of
> ipv6 

This assumes that e2e reachability is a desired property for all networks.


> and it is my hope this new WG will drive that with facts and take
> on fud.

Wasn't the simple/advanced security RFCs produced by v6ops aimed at
typical home devices?

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From moore@network-heretics.com  Wed Jun 29 20:21:13 2011
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 71E0011E80C1; Wed, 29 Jun 2011 20:21:12 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Hdyl+I-CThn; Wed, 29 Jun 2011 20:21:11 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 19D3C11E8083; Wed, 29 Jun 2011 20:21:11 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 88C0121172; Wed, 29 Jun 2011 23:21:10 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 29 Jun 2011 23:21:10 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=CMm5QgOwpRKcotVtmrAMByvzWDA=; b=UyUyAgNcUOe/x76GjQz5mpBqaSdptXHqOrxFIB9jv641W6PtB2xiXCiJiMpFlpHWa9nnPXLLRpDwXxotLphG0pUf+DcfkQBbVvUrPAjO8iNZXdO5NlV0O2KCMYFYyBLmoDXTykrhTttjbI3OMs5NrRCZMROiyMVv7ZFYggSUCNc=
X-Sasl-enc: mKFHnhiEt5T2IaClvw26X3FD5SBl2rX9hv0DW/p/w6HV 1309404070
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 677DB400F0A; Wed, 29 Jun 2011 23:21:09 -0400 (EDT)
Subject: Re: HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-90-384369889
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <BANLkTinuPcq2r85kzMctFCHDB3Ta=WgA4A@mail.gmail.com>
Date: Wed, 29 Jun 2011 23:20:51 -0400
Message-Id: <3C67E327-1147-46A6-92C5-C52851BC1BC0@network-heretics.com>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <BANLkTinuPcq2r85kzMctFCHDB3Ta=WgA4A@mail.gmail.com>
To: Cameron Byrne <cb.list6@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "W. Mark Townsley" <townsley@cisco.com>, "homegate@ietf.org" <homegate@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 03:21:13 -0000

--Apple-Mail-90-384369889
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 29, 2011, at 10:38 PM, Cameron Byrne wrote:
> The utility of network based spi firewalls is debatable. Likely a =
never ending debate.
>=20

+1


--Apple-Mail-90-384369889
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 29, 2011, at 10:38 PM, Cameron Byrne wrote:</div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-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; "><p>The utility of network based spi firewalls is debatable. Likely a never ending debate.</p></span></blockquote></div><div>+1</div><br></body></html>
--Apple-Mail-90-384369889--

From mohta@necom830.hpcl.titech.ac.jp  Wed Jun 29 20:56:34 2011
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 7A53211E8079 for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 20:56:34 -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=[AWL=-0.000,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Doldmah642XM for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 20:56:34 -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 A4E7911E8072 for <ietf@ietf.org>; Wed, 29 Jun 2011 20:56:33 -0700 (PDT)
Received: (qmail 60689 invoked from network); 30 Jun 2011 04:08:37 -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; 30 Jun 2011 04:08:37 -0000
Message-ID: <4E0BF3D3.5090201@necom830.hpcl.titech.ac.jp>
Date: Thu, 30 Jun 2011 12:56:03 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar>
In-Reply-To: <4E0BDCF3.1090003@gont.com.ar>
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: Thu, 30 Jun 2011 03:56:34 -0000

Fernando Gont wrote:

> I personally consider this property of "end-to-end connectivity" as
> "gone".

How do you think about P2P applications?

							Masataka Ohta

PS

End to end connectivity of IPv4 can be maintained/restored by
PR-IP (port restricted IP) such as A+P, E2ENAT and PE-ARP.

From mrex@sap.com  Wed Jun 29 21:25:34 2011
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 7706C11E80CB for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 21:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.099
X-Spam-Level: 
X-Spam-Status: No, score=-10.099 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wQ5XFvGaCB6p for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 21:25:33 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 9BB0911E80A0 for <ietf@ietf.org>; Wed, 29 Jun 2011 21:25:33 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p5U4PVAj024113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 30 Jun 2011 06:25:31 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201106300425.p5U4PUmx029187@fs4113.wdf.sap.corp>
Subject: Re: HOMENET working group proposal
To: mohta@necom830.hpcl.titech.ac.jp (Masataka Ohta)
Date: Thu, 30 Jun 2011 06:25:30 +0200 (MEST)
In-Reply-To: <4E0BF3D3.5090201@necom830.hpcl.titech.ac.jp> from "Masataka Ohta" at Jun 30, 11 12:56:03 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: 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, 30 Jun 2011 04:25:34 -0000

Masataka Ohta wrote:
> 
> Fernando Gont wrote:
> > 
> > I personally consider this property of "end-to-end connectivity" as
> > "gone".

It's gone for good.

Didn't the internet start out as a Network of Network.
Then there was a time when it became popular to the general
public, and everyone was happy when he had one single PC
with a modem to connect to the internet.

Today we're back to where it started, the internet
is a network of (local) networks, and it is important
to keep the networks properly seperated because of the
unbounded growth of features and bugs/vulnerabilities
in popular operating systems for the computer novice.

The average DSL home route does more than just NAT,
it is a DHCP server vor a private address space,
a DNS server that fakes locally assigned/claimed hostnames
into the DNS name resolution (and continues to work even
if the internet link is down).  You really do not want
devices of everyones home network (e.g the admin web interface
of your DSL router, your NAS, your set-top-box, etc.
to becomme freely accessible from everywhere on the internet,
because it is likely close to impossible to preconfigure
new home&entertainment devices in a fashion that they're
securely accessible only to their rightful average
non-security-geek owners and nobody else, and it will
be entirely impossible to convert any of the existing
installed base of devices into such a fully-accessible-for-owner
and 100%-inaccessible-for-everybody-else configuration.

If IPv6 does not offer the the same properties as the
current IPv4 internet subscription for the average home user
-- which implies NAT, private local network and smooth
local operation when the internet is down -- then
very few will want IPv6 to their homes (I certainly
wouldn't want it), and IPv6 adoption will continue to
drag along for several years.


> 
> How do you think about P2P applications?

NAT-PMP or IGD over UPnP come to mind.


-Martin

From moore@network-heretics.com  Wed Jun 29 21:33:14 2011
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 B824611E80C1 for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 21:33:14 -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=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J-gMdSazR-05 for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 21:33:14 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 0CCB511E80A0 for <ietf@ietf.org>; Wed, 29 Jun 2011 21:33:14 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id B5CDF212CB; Thu, 30 Jun 2011 00:33:13 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Thu, 30 Jun 2011 00:33:13 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=AlQ2O8tyzHa8UsvTKSOrGKDVjzk=; b=DYJQb99xjUAK8kSHl44JI+BXHtGF7c4R24yUGVg9QvWv3WGrdwVdEwezPwCLrP3wjQAQyKN2HmySf+LZZIJED9TECxz7pZnTVDPdY5DG3Q142WXoaI1pgQU/1yWBaeilrEGa1be9CiL/5x4LWbhaX8gQ7tIuxG6xpn0dZBJvDwA=
X-Sasl-enc: IekMA+kR0dqDThT9TNjH6Z1SHadUk8IDyV5FqkIf7cQY 1309408393
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id A469C40356F; Thu, 30 Jun 2011 00:33:11 -0400 (EDT)
Subject: Re: HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <201106300425.p5U4PUmx029187@fs4113.wdf.sap.corp>
Date: Thu, 30 Jun 2011 00:32:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7124D145-9BD6-4A4C-BD80-2578A3C501F1@network-heretics.com>
References: <201106300425.p5U4PUmx029187@fs4113.wdf.sap.corp>
To: mrex@sap.com
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 04:33:14 -0000

On Jun 30, 2011, at 12:25 AM, Martin Rex wrote:

> If IPv6 does not offer the the same properties as the
> current IPv4 internet subscription for the average home user
> -- which implies NAT, private local network and smooth
> local operation when the internet is down -- then
> very few will want IPv6 to their homes (I certainly
> wouldn't want it), and IPv6 adoption will continue to
> drag along for several years.

In other words, you think the networks of the future should be every bit =
as dysfunctional as today's networks.=20

I think we can all agree that (a) ordinary users are not security =
experts, and (b) practically all network protocol servers are vulnerable =
to attack.

However it does not follow that home networks need NAT or private =
address space.  Those are hacks of the 1990s.  They always were =
shortsighted, and they turned out to be an operational disaster.  We can =
do better.

Keith


From melinda.shore@gmail.com  Wed Jun 29 21:51:42 2011
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 9205E21F85BB for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 21:51:40 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vejki4+93gix for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 21:51:40 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1936F21F85B4 for <ietf@ietf.org>; Wed, 29 Jun 2011 21:51:40 -0700 (PDT)
Received: by pvh18 with SMTP id 18so1786224pvh.31 for <ietf@ietf.org>; Wed, 29 Jun 2011 21:51:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=7InmGeT3oCiTkQjpZVrgrVcQT3mlbCvWaYkI8z8T04o=; b=XgBwx9RxgZXJCj7xeGReT9uC3Vk91n+FjKtF+lk32Mu8Rm6aaSsuYqO1MlmK37fsHl CMPNS+TPBLWi4Bbin0QLlH+Rr8eYMB+68xDZazIoO/ySGsZIUbRe5RQrOinbmy/pqhvk 49qeK8gi0QoNfr7IWty0lTqjp7yzqqg8Kev1w=
Received: by 10.142.231.11 with SMTP id d11mr767703wfh.35.1309409499666; Wed, 29 Jun 2011 21:51:39 -0700 (PDT)
Received: from polypro.local (66-230-101-52-rb1.fai.dsl.dynamic.acsalaska.net [66.230.101.52]) by mx.google.com with ESMTPS id t12sm1237827wff.10.2011.06.29.21.51.37 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 29 Jun 2011 21:51:38 -0700 (PDT)
Message-ID: <4E0C00D7.5080700@gmail.com>
Date: Wed, 29 Jun 2011 20:51:35 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: HOMENET working group proposal
References: <201106300425.p5U4PUmx029187@fs4113.wdf.sap.corp> <7124D145-9BD6-4A4C-BD80-2578A3C501F1@network-heretics.com>
In-Reply-To: <7124D145-9BD6-4A4C-BD80-2578A3C501F1@network-heretics.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, 30 Jun 2011 04:51:43 -0000

On 6/29/11 8:32 PM, Keith Moore wrote:
> However it does not follow that home networks need NAT or private address space.  Those are hacks of the 1990s.  They always were shortsighted, and they turned out to be an operational disaster.  We can do better.

We can and should, but it's pretty clear that if the IETF
were good at evangelizing we wouldn't be in this situation
in the first place.  The focus really needs to be on producing
good, secure protocols that work on the networks we've got.

Melinda

From marka@isc.org  Wed Jun 29 21:55:51 2011
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 BA61E21F85FE for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 21:55:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level: 
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[AWL=-0.098, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7pajDupUfj30 for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 21:55:51 -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 968A121F85FD for <ietf@ietf.org>; Wed, 29 Jun 2011 21:55: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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 5BE9C5F98BF; Thu, 30 Jun 2011 04:55:30 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 6F349216C7B; Thu, 30 Jun 2011 04:55:28 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 5D3AB114FB1B; Thu, 30 Jun 2011 14:55:26 +1000 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201106300425.p5U4PUmx029187@fs4113.wdf.sap.corp>
Subject: Re: HOMENET working group proposal
In-reply-to: Your message of "Thu, 30 Jun 2011 06:25:30 +0200." <201106300425.p5U4PUmx029187@fs4113.wdf.sap.corp>
Date: Thu, 30 Jun 2011 14:55:26 +1000
Message-Id: <20110630045526.5D3AB114FB1B@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: Thu, 30 Jun 2011 04:55:51 -0000

In message <201106300425.p5U4PUmx029187@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Masataka Ohta wrote:
> > 
> > Fernando Gont wrote:
> > > 
> > > I personally consider this property of "end-to-end connectivity" as
> > > "gone".
> 
> It's gone for good.

It doesn't have to be.
 
> Didn't the internet start out as a Network of Network.
> Then there was a time when it became popular to the general
> public, and everyone was happy when he had one single PC
> with a modem to connect to the internet.
> 
> Today we're back to where it started, the internet
> is a network of (local) networks, and it is important
> to keep the networks properly seperated because of the
> unbounded growth of features and bugs/vulnerabilities
> in popular operating systems for the computer novice.

Very little of which a standalone firewall helps with.

> The average DSL home route does more than just NAT,
> it is a DHCP server vor a private address space,
> a DNS server that fakes locally assigned/claimed hostnames
> into the DNS name resolution (and continues to work even
> if the internet link is down).  You really do not want
> devices of everyones home network (e.g the admin web interface
> of your DSL router, your NAS, your set-top-box, etc.
> to becomme freely accessible from everywhere on the internet,
> because it is likely close to impossible to preconfigure
> new home&entertainment devices in a fashion that they're
> securely accessible only to their rightful average
> non-security-geek owners and nobody else, and it will
> be entirely impossible to convert any of the existing
> installed base of devices into such a fully-accessible-for-owner
> and 100%-inaccessible-for-everybody-else configuration.

Total utter garbage.  For IPv4 DHCP tells you what is local and
what isn't when the address is assigned.  For IPv6 you know from
the RA's what prefixes are local and what arn't.

About the only thing you want the external router/firewall to do
is to prevent spoofed traffic for internal addresses being delivered.
Everything else should be wide open by default and let the host
firewall deal with the rest.

Too many of us come from a time when machines didn't have firewalls
built into them and you needed a external firewall.  It has warped
our thinking about security.

> If IPv6 does not offer the the same properties as the
> current IPv4 internet subscription for the average home user
> -- which implies NAT, private local network and smooth
> local operation when the internet is down -- then
> very few will want IPv6 to their homes (I certainly
> wouldn't want it), and IPv6 adoption will continue to
> drag along for several years.
> 
> 
> > 
> > How do you think about P2P applications?
> 
> NAT-PMP or IGD over UPnP come to mind.
> 
> 
> -Martin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From mrex@sap.com  Wed Jun 29 22:09:57 2011
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 44B4F11E80EC for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 22:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.174
X-Spam-Level: 
X-Spam-Status: No, score=-10.174 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdWyNylBGweh for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 22:09:54 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id ADB0311E80C8 for <ietf@ietf.org>; Wed, 29 Jun 2011 22:09:53 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p5U59k3f015783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 30 Jun 2011 07:09:51 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201106300509.p5U59j3q001889@fs4113.wdf.sap.corp>
Subject: Re: HOMENET working group proposal
To: moore@network-heretics.com (Keith Moore)
Date: Thu, 30 Jun 2011 07:09:45 +0200 (MEST)
In-Reply-To: <7124D145-9BD6-4A4C-BD80-2578A3C501F1@network-heretics.com> from "Keith Moore" at Jun 30, 11 00:32:52 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: 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, 30 Jun 2011 05:09:57 -0000

Keith Moore wrote:
> 
> In other words, you think the networks of the future should be every
> bit as dysfunctional as today's networks. 

It is not dysfunctional just because it is slightly more complicated
to use that if everything was freely accessible to complete self-service.

> 
> I think we can all agree that (a) ordinary users are not security experts,

agreed

>
> and (b) practically all network protocol servers are vulnerable to attack.

Nope.  The risk is directly related to the complexity of the accessible
parts.

That is why I want the internet gateway to be a NAT, maybe even an IPv4 NAT.
I doesn't take that much to make the outwards facing parts of an IPv4 NAT
completely bug-free.


> 
> However it does not follow that home networks need NAT or private address
> space.  Those are hacks of the 1990s.  They always were shortsighted, and
> they turned out to be an operational disaster.  We can do better.

NAT and private address space for the home networks is as healthy to
the internet population as is water & soap to the health of mankind.

One may have to remind small kids regularly to wash their hands,
but of them grasp the concept and the benefits when they grow up.


-Martin

From moore@network-heretics.com  Wed Jun 29 22:26:38 2011
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 9C5E221F85CE for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 22:26:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c7Ik1pkQwXYG for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 22:26:38 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 10F2C21F85CD for <ietf@ietf.org>; Wed, 29 Jun 2011 22:26:37 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 1FB5420F0F; Thu, 30 Jun 2011 01:26:36 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Thu, 30 Jun 2011 01:26:36 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=HXKdw6IwshoGHaY0eYeoxDrml7Q=; b=rqk6tWTFmUxJB8jirNfsLQt5J6nGTmSSWMxf2vzr1InvhkfzY5tH17qb65bIWDF/rNoAEqaDcSLgcxqQdjKfiLowVgogOKkDJ6zk3pUYAqVfbqAUxJ0ErfascYqEIYcYU46cPN+kBw48Swa1/spItaF+mdkOKJkmiLGcqAAYFBk=
X-Sasl-enc: brfj8yD+SHeLxJ6vbX5GjkQQbgNGNkB+aVtKcUcC/A/T 1309411595
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 5D9DC407626; Thu, 30 Jun 2011 01:26:35 -0400 (EDT)
Subject: Re: HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <201106300509.p5U59j3q001889@fs4113.wdf.sap.corp>
Date: Thu, 30 Jun 2011 01:26:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3597BE26-F405-4D02-AE22-461635453FCF@network-heretics.com>
References: <201106300509.p5U59j3q001889@fs4113.wdf.sap.corp>
To: mrex@sap.com
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 05:26:38 -0000

On Jun 30, 2011, at 1:09 AM, Martin Rex wrote:

(a bunch of stuff in defense of NAT)

Rather than having another of an endless series of discussions about the =
merits of NAT or lack thereof, can we just agree that it should not be =
pre-ordained that this WG should assume NAT as a solution?

Keith


From touch@isi.edu  Wed Jun 29 22:55:32 2011
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 BC41311E811B; Wed, 29 Jun 2011 22:55:32 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4ngXoWRw32c; Wed, 29 Jun 2011 22:55:31 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id DF54211E8116; Wed, 29 Jun 2011 22:55:31 -0700 (PDT)
Received: from [172.16.0.187] (216.156.178.2.ptr.us.xo.net [216.156.178.2]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p5U5t1qT004389 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 29 Jun 2011 22:55:10 -0700 (PDT)
Message-ID: <4E0C0FB3.8080602@isi.edu>
Date: Wed, 29 Jun 2011 22:54:59 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, IETF discussion list <ietf@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>,  draft-ietf-karp-design-guide@tools.ietf.org
Subject: TSVDIR review of draft-ietf-karp-design-guide
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: TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 05:55:32 -0000

Hi, all,

I've reviewed this document as part of the transport area directorate's 
ongoing effort to review key IETF documents. These comments were written 
primarily for the transport area directors, but are copied to the 
document's authors for their information and to allow them to address 
any issues raised. The authors should consider this review together with 
any other last-call comments they receive. Please always CC 
tsv-dir@ietf.org if you reply to or forward this review.

The document discusses design issues for protecting routing protocols.

The most problematic issue is the term "on the wire" which is used in 
various contexts to imply physical, link, network, or transport protocol 
layers. This needs to be clarified.

Transport protection appears to be a potential focus of the design 
guide, but is inconsistently discussed. In some cases, transport issues 
are raised (TCP issues for BGP); in other cases, the relevant transport 
isn't even noted (e.g., RIP over UDP). This should be corrected throughout.

It is important for this document to be more clear on what layers were 
in scope for the design guide, and what guidelines are being given with 
respect to those layers, even in a general sense.

Further information on these issues is provided below. There is 
additional feedback provided below ("other notes") as a suggestion.

I hope this feedback will be useful to the authors, and will be glad to 
provide further assistance either on- or off-list as useful.

Joe

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

 >> please note that some of these comments apply to the 
draft-ietf-karp-threats-reqs-03 as well; further, there is duplicate 
text that is not needed in both these docs. FWIW, the threats-reqs doc 
has many issues as well which are not addressed here.

Of the four issues noted in the intro, the last uses the ambiguous term 
"on the wire". This is confusing in both this and the threats doc, and 
many times both docs us the term 'wire' or 'bits', all of which would 
typically indicate either the link layer or the physical media or both. 
There is no rationale for this focus in either document.

The threats document should more clearly indicate *why* protection 
beyond the routing messages (the SIDR work) is needed, and what the 
expected threats are. These appear to be:
	- routing protocols often rely on information in the
	link, transport or network packets
	- routing protocols often rely on properties of transport
	connections to infer reachability, e.g., if a TCP connection
	cannot stay up, then the endpoint's routes should not be
	considered reachable
(if there are other reasons, please clarify) The threats then appear to be:
	- spoofing link/network addresses
	- spoofing transport ports
	- disrupting the TCP connection (where TCP is used)
Note that falsification (as noted in the threats doc) is not in this 
list since it is (IMO) clearly the purvue of the SIDR work. Also out of 
scope should have been any of the interference issues, unless the 
*performance* of the TCP connection needs protection.

This doc then may need to protect the link or network protocol ID and/or 
transport protocol from interference. This should be more clearly stated 
in the threats doc, IMO, and the term "on the wire" should be avoided.

The discussion of multicast should note that multicast can be 
implemented by broadcast, true multicast, or serial unicast; these may 
have different security requirements.

The document should more clearly indicate the underlying protocol used 
as a key property of a routing protocol, especially because (as above) 
this document appears to focus on guidelines for link, network, and/or 
transport protocols. E.g., the discussion on OSPF, RIP, and ISIS should 
more clearly indicate that, e.g., RIP runs over UDP, OSPF runs over IP 
directly, and IS-IS runs natively over L2. Similar info would be useful 
for BFD, RSVP, etc.

The document is unclear on its overall advice, other than a somewhat 
general description of "do good stuff". E.g., it notes:

       Not all routing protocol authentication mechanisms provide
       support for replay attacks, and the design teams should
       identify such authentication mechanisms and work on them so
       that this can get fixed. The design teams must look at the
       protocols that they are working on and see if packets captured
       from the previous/stale sessions can be replayed.

More specific advice would be, e.g.:

	Not all routing protocol authentication mechanisms provide
	protection from replay attacks. Such deficiencies should
	be addressed at that layer, rather than having design
	teams conclude that such systems thus require lower layer
	(transport, network, or link) protection from replays.

----
Other notes:

Overall, this document would benefit from a revision focused on 
clarification, where the focus of each section and advice were made more 
clear.

The abstract is excessively detailed and doesn't get to the point until 
"This document...". Everything preceding that should be removed, and the 
result should be appended with a few sentences summarizing the 
recommendations.

The intro refers in a lot of detail to the motivation for the doc (some 
of which may be historically important but is not relevant to the doc 
itself), but only briefly notes the KARP threats document. This 
document's observations should be motivated by addressing those threats, 
so it would be important to summarize them in this doc in the intro as 
context.

The summary of RFC 4984 discusses four tightening steps as if they were 
indicated by that RFC; that RFC only suggests tightening itself. This 
doc should more clearly indicate that "The WG identified four...".

-----









From mohta@necom830.hpcl.titech.ac.jp  Wed Jun 29 23:45:50 2011
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 0162111E813B for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 23:45:50 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7r1w6w7ckWYv for <ietf@ietfa.amsl.com>; Wed, 29 Jun 2011 23:45:49 -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 D9EB111E811B for <ietf@ietf.org>; Wed, 29 Jun 2011 23:45:48 -0700 (PDT)
Received: (qmail 62107 invoked from network); 30 Jun 2011 06:57:59 -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; 30 Jun 2011 06:57:59 -0000
Message-ID: <4E0C1B86.6090906@necom830.hpcl.titech.ac.jp>
Date: Thu, 30 Jun 2011 15:45:26 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: HOMENET working group proposal
References: <201106300425.p5U4PUmx029187@fs4113.wdf.sap.corp>
In-Reply-To: <201106300425.p5U4PUmx029187@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-2022-JP
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, 30 Jun 2011 06:45:50 -0000

Martin Rex wrote:

>> How do you think about P2P applications?
> 
> NAT-PMP or IGD over UPnP come to mind.

P2P applications need seed peers with fixed addresses and ports.

						Masataka Ohta

From fernando.gont.netbook.win@gmail.com  Wed Jun 29 23:51:58 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1440D11E8144; Wed, 29 Jun 2011 23:51:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.04
X-Spam-Level: 
X-Spam-Status: No, score=-3.04 tagged_above=-999 required=5 tests=[AWL=0.559,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CJFwMd-Gqvcr; Wed, 29 Jun 2011 23:51:57 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 129C311E813B; Wed, 29 Jun 2011 23:51:57 -0700 (PDT)
Received: by ywp31 with SMTP id 31so984661ywp.31 for <multiple recipients>; Wed, 29 Jun 2011 23:51:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=/0R3YYGmnJ6Lyflfku3ISMCbOSDFXOXl9MZ4HOpp3WU=; b=xADfpU0trLhwnwW5kVQoQ+rTN/eaStuQpFgMfEm4pmfQRNbN2WdfNmYLddJy2e9R2Q V86/HOgP03jOfXzBvhT3RjPLkuNXLnzMpgs6dCyTKm8sh6nGCZ39VfyrshCEp0rucNQM G5zjyenb7T3I6irYs9DFuKq6LPY3cl/g82PPA=
Received: by 10.91.149.5 with SMTP id b5mr1511370ago.91.1309416716566; Wed, 29 Jun 2011 23:51:56 -0700 (PDT)
Received: from [192.168.123.103] ([190.48.246.1]) by mx.google.com with ESMTPS id v9sm1752067anv.4.2011.06.29.23.51.49 (version=SSLv3 cipher=OTHER); Wed, 29 Jun 2011 23:51:55 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4E0C1CF8.7090601@gont.com.ar>
Date: Thu, 30 Jun 2011 03:51:36 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homegate] HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "homegate@ietf.org" <homegate@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 06:51:58 -0000

On 06/30/2011 02:12 AM, Mikael Abrahamsson wrote:
>> My high level comment/question is: the proposed charter seems to
>> stress that IPv6 is the driver behind this potential wg effort...
>> however, I think that this deserves more discussion -- it's not clear
>> to me why/how typical IPv6 home networks would be much different from
>> their IPv4 counterparts.
> 
> In my mind, I see the possibility of /56 PD enabling different subnets
> for different kinds of devices with different security and functional
> needs, and also chaining of L3 devices. This definitely warrants a group
> to look at that.

My point was that, except for the mechanism for PD, I don't see a
substantial difference here that would e.g. prevent this from being
developed for IPv4 (in addition to IPv6). -- Yes, I know we need to
deploy IPv6... but I don't think you can expect people to get rid of
their *working* IPv4 devices... (i.e., not sure why any of this
functionality should be v6-only)


>> One would hope/expect that the former will be gone with IPv6. However,
>> I don't think the latter will. As a result, even when you could
>> "address" nodes that belong to the "home network", you probably won't
>> be able to get your packets to them, unless those nodes initiated the
>> communication instance.
> 
> This is exactly why the whole "system" needs to work, including uPNP
> like functionality for nodes to talk to the firewall(s).

I think this deserves a problem statement that clearly describes what we
expect to be able to do (but currently can't), etc. And, if this is
meant to be v6-only, state why v4 is excluded -- unless we're happy to
have people connect their IPv4-devices, and see that they cannot
communicate anymore.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From fernando.gont.netbook.win@gmail.com  Thu Jun 30 00:09:54 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3B8711E815B for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 00:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.18
X-Spam-Level: 
X-Spam-Status: No, score=-3.18 tagged_above=-999 required=5 tests=[AWL=0.419,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i5dSK2QzyIOM for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 00:09:54 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id D192211E813E for <ietf@ietf.org>; Thu, 30 Jun 2011 00:09:47 -0700 (PDT)
Received: by gxk19 with SMTP id 19so971479gxk.31 for <ietf@ietf.org>; Thu, 30 Jun 2011 00:09:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=iKioZFsTsLsKWKhedVECactvjQZsz0UDnLy2olbaW9M=; b=ZXHP6russJb1HHxjHeA7Nmvkj8lPP0+T5272zaK/ANwcN9rin8IQdkVAYBdxOpC6py fzKWr8dlO97xczm/F1WpbMqyFnOSjEmEmj3G+WPWhtnEcsFntICKMmpauEdrIaj/bFXD D5Whb6tgRTEtb47r9+Ry0wiMi++Xe6Qus2dG0=
Received: by 10.100.49.20 with SMTP id w20mr785827anw.43.1309417787131; Thu, 30 Jun 2011 00:09:47 -0700 (PDT)
Received: from [192.168.123.103] ([190.48.246.1]) by mx.google.com with ESMTPS id c19sm1760596anm.15.2011.06.30.00.09.43 (version=SSLv3 cipher=OTHER); Thu, 30 Jun 2011 00:09:46 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4E0C2132.4030101@gont.com.ar>
Date: Thu, 30 Jun 2011 04:09:38 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <4E0BF3D3.5090201@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4E0BF3D3.5090201@necom830.hpcl.titech.ac.jp>
X-Enigmail-Version: 1.1.2
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, 30 Jun 2011 07:09:54 -0000

On 06/30/2011 12:56 AM, Masataka Ohta wrote:
> Fernando Gont wrote:
> 
>> I personally consider this property of "end-to-end connectivity" as
>> "gone".
> 
> How do you think about P2P applications?

I think about applications that would benefit from e2e connectivity, but
since it is gone, they have to spend quite a bit of effort to traverse
middleboxes such as NATs. -- the network is not dumb anymore.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From fernando.gont.netbook.win@gmail.com  Thu Jun 30 00:25:17 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79E0821F85B2 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 00:25:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.264
X-Spam-Level: 
X-Spam-Status: No, score=-3.264 tagged_above=-999 required=5 tests=[AWL=0.335,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u8RCHqfP0qMk for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 00:25:16 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id E0FD821F85AF for <ietf@ietf.org>; Thu, 30 Jun 2011 00:25:15 -0700 (PDT)
Received: by yie30 with SMTP id 30so990225yie.31 for <ietf@ietf.org>; Thu, 30 Jun 2011 00:25:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=E22bVXcSLBDg/Zpg6X68OfJp3lQS3A779EQomRelhPs=; b=tki9iIkCcKwKL+DF20FQAmQ33SjKQk+DQK7qr3P8LhLy/sjrM1+IVNeXbMoQY0oIyI bmbJ8HTAjkKDGWLMTwF9kuSFSeo9nOukct1uDrUOQ9Wa0cwr48hqsz07W3BxPVTX4scY EVTAXEciSiT8lE/mNybo7WdfHMGtUMn69U5sw=
Received: by 10.101.179.39 with SMTP id g39mr1466151anp.96.1309418710534; Thu, 30 Jun 2011 00:25:10 -0700 (PDT)
Received: from [192.168.123.103] ([190.48.246.1]) by mx.google.com with ESMTPS id b19sm1761725anh.45.2011.06.30.00.25.03 (version=SSLv3 cipher=OTHER); Thu, 30 Jun 2011 00:25:09 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4E0C24CA.9090902@gont.com.ar>
Date: Thu, 30 Jun 2011 04:24:58 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: HOMENET working group proposal
References: <201106300509.p5U59j3q001889@fs4113.wdf.sap.corp> <3597BE26-F405-4D02-AE22-461635453FCF@network-heretics.com>
In-Reply-To: <3597BE26-F405-4D02-AE22-461635453FCF@network-heretics.com>
X-Enigmail-Version: 1.1.2
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, 30 Jun 2011 07:25:20 -0000

On 06/30/2011 02:26 AM, Keith Moore wrote:
> Rather than having another of an endless series of discussions about
> the merits of NAT or lack thereof, can we just agree that it should
> not be pre-ordained that this WG should assume NAT as a solution?

I was originally arguing, at the very least, in favour of a stateful
firewall at the border.

Please correct me if I'm wrong, but this is what the IETF has already
proposed (output of v6ops) for v6.

I don't think you want your home network to be owned as a result of last
"patch Tuesday" set of vulnerabilities... or that you want a brittle
printer or fridge possibly impossible to patch) to be DoSed/owned just
because it was cool to have it available on the Internet. (nor should we
expect them to run a "host-based" firewall).

Many/most networks are there to provide a specific service to their
users (not for us to experiment with) -- whether we like it or not. As
long as they are able to provide that service, I don't find a compelling
reason for them to increase risk through unnecessary increased exposure.

(Yes, in those cases in which you *need* increased exposure, you open
your network -- i.e., "default deny")

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From mohta@necom830.hpcl.titech.ac.jp  Thu Jun 30 01:02:28 2011
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 C574321F8754 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 01:02:28 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wt+lDsBPZvI0 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 01:02:28 -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 F08DB21F874D for <ietf@ietf.org>; Thu, 30 Jun 2011 01:02:27 -0700 (PDT)
Received: (qmail 62802 invoked from network); 30 Jun 2011 08:14: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; 30 Jun 2011 08:14:27 -0000
Message-ID: <4E0C2D6B.4090807@necom830.hpcl.titech.ac.jp>
Date: Thu, 30 Jun 2011 17:01:47 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <4E0BF3D3.5090201@necom830.hpcl.titech.ac.jp> <4E0C2132.4030101@gont.com.ar>
In-Reply-To: <4E0C2132.4030101@gont.com.ar>
Content-Type: text/plain; charset=ISO-2022-JP
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, 30 Jun 2011 08:02:28 -0000

Fernando Gont wrote:

>>> I personally consider this property of "end-to-end connectivity" as
>>> "gone".
>>
>> How do you think about P2P applications?
> 
> I think about applications that would benefit from e2e connectivity, but
> since it is gone, they have to spend quite a bit of effort to traverse
> middleboxes such as NATs. -- the network is not dumb anymore.

As I wrote, with PR-IP such as E2ENAT, the network can be dumb.

If several fixed port numbers are blocked, what's wrong if the
network is dumb?

Anyway, as it is a lot easier for applications to traverse NAT
than to support IPv6, you should better say IPv6 has never
arrived.

						Masataka Ohta

From jari.arkko@piuha.net  Thu Jun 30 02:32:01 2011
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 D403221F87AC; Thu, 30 Jun 2011 02:32:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.999
X-Spam-Level: 
X-Spam-Status: No, score=-100.999 tagged_above=-999 required=5 tests=[AWL=-1.154, BAYES_00=-2.599, FRT_BELOW2=2.154, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PjqqXe1daLkB; Thu, 30 Jun 2011 02:32:01 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id CEA2C21F87AB; Thu, 30 Jun 2011 02:32:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7FAC02CEA0; Thu, 30 Jun 2011 12:31:58 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LV2mS+CqafKu; Thu, 30 Jun 2011 12:31:57 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 069AB2CC39; Thu, 30 Jun 2011 12:31:56 +0300 (EEST)
Message-ID: <4E0C428D.1070508@piuha.net>
Date: Thu, 30 Jun 2011 11:31:57 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar>
In-Reply-To: <4E0BDCF3.1090003@gont.com.ar>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "fun@ietf.org" <fun@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 09:32:02 -0000

Fernando,

First off, I'm switching the reply headers to fun@ietf.org now, deleting 
the old homegate list from this discussion.

Secondly, I would like to explain the motivation behind focusing this 
work on IPv6. Its not so much about IPv6 being different (though I hope 
it is in some respects). The reason why I want this working group to 
focus on IPv6 is that I don't think new IETF work would have much effect 
on IPv4 home network architecture. Whereas I think we have a good chance 
of having an effect in the IPv6 case, given that there is not much 
deployed base yet in home routers, consumer ISPs, etc.

Finally, I don't think we need to take a black-and-white approach to 
discussing the end-to-end model. Obviously we know about the V6OPS 
simple security work. Of course there are firewalls in IPv6, restricting 
incoming traffic. That being said, I think the right architecture for 
IPv6 home networks is that incoming traffic is restricted *by policy* on 
a per-need basis, not by an addressing design that forever prevents us 
from allowing specific incoming protocols. This is what we mean by 
architecture specification from this working group. Practical network 
design that does the right thing and lets people do what they want -- 
not a requirement to open your network up for anything.

Jari

Fernando Gont kirjoitti:
> Hi, Jari,
>
> My high level comment/question is: the proposed charter seems to stress
> that IPv6 is the driver behind this potential wg effort... however, Ie
> think that this deserves more discussion -- it's not clear to me why/how
> typical IPv6 home networks would be much different from their IPv4
> counterparts.
>
> Bellow you'll find some comments/questions about the proposed charter.
> They are not an argument against or in favour of the creation of the
> aforementioned wg, but rather comments and/or requests for clarification...
>
> On 06/29/2011 05:47 AM, Jari Arkko wrote:
> [....]
>   
>> o Service providers are deploying IPv6, and support for IPv6 is
>> increasingly available in home gateway devices. While IPv6 resembles
>> IPv4 in many ways, it changes address allocation principles and allows
>> direct IP addressability and routing to devices in the home from the
>> Internet. This is a promising area in IPv6 that has proved challenging
>> in IPv4 with the proliferation of NAT.
>>     
>
> NAT devices involve two related but different issues:
> * address translation
> * an implicit "allow only return traffic" firewall-like functionality
>
> One would hope/expect that the former will be gone with IPv6. However, I
> don't think the latter will. As a result, even when you could "address"
> nodes that belong to the "home network", you probably won't be able to
> get your packets to them, unless those nodes initiated the communication
> instance.
>
> For instance (and of the top of my head), this functionality is even
> proposed in the "simple security" requirements that had been produced by
> v6ops.
>
>
>   
>> o End-to-end communication is both an opportunity and a concern as it
>> enables new applications but also exposes nodes in the internal
>> networks to receipt of unwanted traffic from the Internet. Firewalls
>> that restrict incoming connections may be used to prevent exposure,
>> however, this reduces the efficacy of end-to-end connectivity that
>> IPv6 has the potential to restore.
>>     
>
> I personally consider this property of "end-to-end connectivity" as
> "gone". -- among other reasons, because it would require a change of
> mindset. I'm more of the idea that people will replicate the
> architecture of their IPv4 networks with IPv6, in which end-systems are
> not reachable from the public Internet.
>
> Thanks!
>   


From jari.arkko@piuha.net  Thu Jun 30 02:38:33 2011
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 C14D221F87B6; Thu, 30 Jun 2011 02:38:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.332
X-Spam-Level: 
X-Spam-Status: No, score=-102.332 tagged_above=-999 required=5 tests=[AWL=0.267, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tEhl9kJXpTwR; Thu, 30 Jun 2011 02:38:33 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id E88CD21F863B; Thu, 30 Jun 2011 02:38:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1DB0E2D3FA; Thu, 30 Jun 2011 12:38: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 pYnOoFUyKm0M; Thu, 30 Jun 2011 12:38:31 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 1D3E42CC39; Thu, 30 Jun 2011 12:38:31 +0300 (EEST)
Message-ID: <4E0C4417.90804@piuha.net>
Date: Thu, 30 Jun 2011 11:38:31 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: [homegate] HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar>
In-Reply-To: <4E0C1CF8.7090601@gont.com.ar>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>, "fun@ietf.org" <fun@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 09:38:33 -0000

Fernando,

> My point was that, except for the mechanism for PD, I don't see a
> substantial difference here that would e.g. prevent this from being
> developed for IPv4 (in addition to IPv6). -- Yes, I know we need to
> deploy IPv6... but I don't think you can expect people to get rid of
> their *working* IPv4 devices... (i.e., not sure why any of this
> functionality should be v6-only)
>   

You have to separate IETF specifications and functionality of real-world 
products. Obviously everyone is going to have IPv4 based home networks 
for a long time.

But their architecture is largely done and cannot be easily affected. 
Vendors are now looking into adding IPv6 into their home routers and 
other devices. I want to be able to show them how to do it right. They 
can, of course, replicate everything exactly as in IPv4. Much of it is 
right, of course, but on some areas I think we can do better. This is 
why the working group should focus on IPv6. If the group is successful, 
IPv4 network design continues to be what it is, but our recommendations 
for the IPv6 network design are adopted by vendors' home devices.

Jari


From fernando.gont.netbook.win@gmail.com  Thu Jun 30 02:47:49 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F049521F87B5; Thu, 30 Jun 2011 02:47:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.359
X-Spam-Level: 
X-Spam-Status: No, score=-3.359 tagged_above=-999 required=5 tests=[AWL=0.240,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5KRPAydaRArx; Thu, 30 Jun 2011 02:47:49 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 51E3221F87B4; Thu, 30 Jun 2011 02:47:49 -0700 (PDT)
Received: by yie30 with SMTP id 30so1034469yie.31 for <multiple recipients>; Thu, 30 Jun 2011 02:47:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=wuvzIDIejO+ynETTjiGZm6BT1MUsU5YUgJqth0FZQjo=; b=jsmfR98hhFZZ2C5vgTwPiNr8ebaH+gvkRe6Q1Fdwt+XnaGsno9DlFm2ZeklgIPnj5y zUFpGYlFRjcnhxYpSuICOypAdWGmSw7XdZXLpU1XcwgM6LiUMiE1QfqvRf4euNt6BlPH KdQeco3X73pHXd4N82Gd+uV59rJ+h8Ln+RYv8=
Received: by 10.101.179.12 with SMTP id g12mr1549559anp.59.1309427268734; Thu, 30 Jun 2011 02:47:48 -0700 (PDT)
Received: from [192.168.123.103] ([190.48.255.131]) by mx.google.com with ESMTPS id x4sm1859142anp.17.2011.06.30.02.47.43 (version=SSLv3 cipher=OTHER); Thu, 30 Jun 2011 02:47:47 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4E0C4631.3010409@gont.com.ar>
Date: Thu, 30 Jun 2011 06:47:29 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [homegate] HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar> <4E0C4417.90804@piuha.net>
In-Reply-To: <4E0C4417.90804@piuha.net>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>, "fun@ietf.org" <fun@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 09:47:50 -0000

Jari,

On 06/30/2011 06:38 AM, Jari Arkko wrote:
> But their architecture is largely done and cannot be easily affected.
> Vendors are now looking into adding IPv6 into their home routers and
> other devices. I want to be able to show them how to do it right. They
> can, of course, replicate everything exactly as in IPv4. Much of it is
> right, of course, but on some areas I think we can do better. This is
> why the working group should focus on IPv6. 

My point is: Will implementation of the produced RFCs lead to home
networks in which stuff works for IPv6 differently from how it works for
IPv4? e.g., your home network would have multiple subnets (thanks to
PD), but a single IPv4 subnet?

If our work focuses only on IPv6, I get the impression that we're
heading in that direction.

If HOMENET is going to improve stuff that we already do with IPv4 (by
leveraging IPv6), then that's fine... but not what I read from this
discussion and the proposed charter.

Thoughts?

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From jari.arkko@piuha.net  Thu Jun 30 03:02:58 2011
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 9E1C421F87AD; Thu, 30 Jun 2011 03:02:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.342
X-Spam-Level: 
X-Spam-Status: No, score=-102.342 tagged_above=-999 required=5 tests=[AWL=0.257, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W7ARBOLY90SB; Thu, 30 Jun 2011 03:02:58 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 0A98721F8737; Thu, 30 Jun 2011 03:02:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 35CCB2CEA0; Thu, 30 Jun 2011 13:02:57 +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 eb0i9G78I0XA; Thu, 30 Jun 2011 13:02:56 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 2A4B62CC39; Thu, 30 Jun 2011 13:02:55 +0300 (EEST)
Message-ID: <4E0C49CD.30505@piuha.net>
Date: Thu, 30 Jun 2011 12:02:53 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: [homegate] HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar> <4E0C4417.90804@piuha.net> <4E0C4631.3010409@gont.com.ar>
In-Reply-To: <4E0C4631.3010409@gont.com.ar>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>, "fun@ietf.org" <fun@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 10:02:58 -0000

Fernando,

> My point is: Will implementation of the produced RFCs lead to home
> networks in which stuff works for IPv6 differently from how it works for
> IPv4? 

That is the plan. And when I say "differently", I mean differences such as

* prefix delegation
* global addresses and firewalls instead of private addresses and NATs
* across-subnet communication internally in the home can be routed, not 
NATted

> e.g., your home network would have multiple subnets (thanks to
> PD), but a single IPv4 subnet?
>   

But the examples you cite are not differences we are really aiming at. 
Multiple subnets is something that generally should be avoided where 
possible, but cannot be completely avoided. It applies to IPv4 and IPv6 
in equal manner, e.g., when you have a Guest and Private SSIDs on your 
wireless. In this case the difference between IPv4 and IPv6 is merely 
that in one case we NAT to the Internet and between the two networks, in 
another case we route/firewall.

> If our work focuses only on IPv6, I get the impression that we're
> heading in that direction.
>
> If HOMENET is going to improve stuff that we already do with IPv4 (by
> leveraging IPv6), then that's fine... but not what I read from this
> discussion and the proposed charter.
>   

My point is that I don't think we can change the IPv4 situation. We can 
affect the way IPv6 is used. Maybe we can even make things better in 
IPv6 than they were in IPv4. So in the end the user experience may 
improve for people who use IPv6, but it is definitely not our goal to 
improve IPv4.

Jari


From otuenehoj@gmail.com  Thu Jun 30 03:10:14 2011
Return-Path: <otuenehoj@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 235DD21F87FE; Thu, 30 Jun 2011 03:10:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.246
X-Spam-Level: 
X-Spam-Status: No, score=-1.246 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hU5AtoI2iixB; Thu, 30 Jun 2011 03:10:12 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 64D0C21F8675; Thu, 30 Jun 2011 03:09:55 -0700 (PDT)
Received: by eye13 with SMTP id 13so853010eye.31 for <multiple recipients>; Thu, 30 Jun 2011 03:09:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=x-rim-org-msg-ref-id:message-id:content-transfer-encoding:reply-to :x-priority:references:in-reply-to:sensitivity:importance:subject:to :from:date:content-type:mime-version; bh=EhOBdsxi/Ci1kkV/znGfwWJx7gU35b5wM0Ol2KQcpxs=; b=I8run+1FZ6jAbD96xBMyKcIsIdJGGaUMQqcTemzeo5Xr81dtMsRugA4w7TmdeZ9NMt 3j9tmgR7CiQ6YJ8qx4LdB6e1ti3xgU0q/60niyHg5yFOP/Ncw0Gd34e5WnBFe83JkCRs A8/dUQcAEZTuHBZj/Fs7UUwg2p8CI/j3xLmA8=
Received: by 10.213.9.14 with SMTP id j14mr583675ebj.127.1309428592823; Thu, 30 Jun 2011 03:09:52 -0700 (PDT)
Received: from 172.18.200.213 (bda-178-239-84-154.bis7.eu.blackberry.com [178.239.84.154]) by mx.google.com with ESMTPS id s11sm1597659eef.15.2011.06.30.03.09.50 (version=SSLv3 cipher=OTHER); Thu, 30 Jun 2011 03:09:51 -0700 (PDT)
X-rim-org-msg-ref-id: 413186229
Message-ID: <413186229-1309428589-cardhu_decombobulator_blackberry.rim.net-1821949261-@b15.c7.bise7.blackberry>
Content-Transfer-Encoding: base64
X-Priority: Normal
References: <mailman.596.1309365174.3031.ietf@ietf.org><BANLkTinGZZ9q7gSU2yD_Cqb8AoGm1bcSWQ@mail.gmail.com>
In-Reply-To: <BANLkTinGZZ9q7gSU2yD_Cqb8AoGm1bcSWQ@mail.gmail.com>
Sensitivity: Normal
Importance: Normal
Subject: Re: Ietf Digest, Vol 37, Issue 103
To: "Amenawon Osa Peter" <osa.peter@gmail.com>, ietf-bounces@ietf.org, ietf@ietf.org
From: otuenehoj@gmail.com
Date: Thu, 30 Jun 2011 10:10:40 +0000
Content-Type: text/plain
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: otuenehoj@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 10:10:14 -0000

RGVhciBQZXRlciwNClRoZSB3b3JrIGdyb3VwIGlzIGEgZGlzY3Vzc2lvbi9lLW1lZXRpbmcgd2hl
cmUgaXNzdWVzL3RvcGljcyBhcmUgcmFpc2VkIGFuZCBkZWxpYmVyYXRlZCBvbi4gVGhlIGlzc3Vl
cyBoYXMgdG8gZG8gdGhlIGludGVybmV0IGFuZCBpdHMgcmVsYXRlZCBpc3N1ZXMuDQoNCktpbmQg
cmVnYXJkcywNCg0KT3R1ZW5laA0KIA0KU2VudCBmcm9tIG15IEJsYWNrQmVycnkgd2lyZWxlc3Mg
ZGV2aWNlIGZyb20gTVRODQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBBbWVu
YXdvbiBPc2EgUGV0ZXIgPG9zYS5wZXRlckBnbWFpbC5jb20+DQpTZW5kZXI6IGlldGYtYm91bmNl
c0BpZXRmLm9yZw0KRGF0ZTogV2VkLCAyOSBKdW4gMjAxMSAyMzoyMzoyMCANClRvOiA8aWV0ZkBp
ZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBJZXRmIERpZ2VzdCwgVm9sIDM3LCBJc3N1ZSAxMDMNCg0K
SSBhcyBhIG5ldyBtZW1iZXIgaXMgaXQgcG9zc2libGUgdGhhdCBpIGJlIGdpdmVuIGEgY2x1ZSBv
biB3aGF0IHRoaXMNCndvcmsgZ3JvdXAgYWltIGlzIHRvIGVuYWJsZSBtZSBiZSBhYmxlIHRvIGNv
bnRyaWJ1dGUgcG9zaXRpdmVseS4NCg0KdGhhbmsgeW91DQoNCk9uIDYvMjkvMTEsIGlldGYtcmVx
dWVzdEBpZXRmLm9yZyA8aWV0Zi1yZXF1ZXN0QGlldGYub3JnPiB3cm90ZToNCj4gSWYgeW91IGhh
dmUgcmVjZWl2ZWQgdGhpcyBkaWdlc3Qgd2l0aG91dCBhbGwgdGhlIGluZGl2aWR1YWwgbWVzc2Fn
ZQ0KPiBhdHRhY2htZW50cyB5b3Ugd2lsbCBuZWVkIHRvIHVwZGF0ZSB5b3VyIGRpZ2VzdCBvcHRp
b25zIGluIHlvdXIgbGlzdA0KPiBzdWJzY3JpcHRpb24uICBUbyBkbyBzbywgZ28gdG8NCj4NCj4g
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmDQo+DQo+IENsaWNrIHRo
ZSAnVW5zdWJzY3JpYmUgb3IgZWRpdCBvcHRpb25zJyBidXR0b24sIGxvZyBpbiwgYW5kIHNldCAi
R2V0DQo+IE1JTUUgb3IgUGxhaW4gVGV4dCBEaWdlc3RzPyIgdG8gTUlNRS4gIFlvdSBjYW4gc2V0
IHRoaXMgb3B0aW9uDQo+IGdsb2JhbGx5IGZvciBhbGwgdGhlIGxpc3QgZGlnZXN0cyB5b3UgcmVj
ZWl2ZSBhdCB0aGlzIHBvaW50Lg0KPg0KPg0KPg0KPiBTZW5kIElldGYgbWFpbGluZyBsaXN0IHN1
Ym1pc3Npb25zIHRvDQo+IAlpZXRmQGlldGYub3JnDQo+DQo+IFRvIHN1YnNjcmliZSBvciB1bnN1
YnNjcmliZSB2aWEgdGhlIFdvcmxkIFdpZGUgV2ViLCB2aXNpdA0KPiAJaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmDQo+IG9yLCB2aWEgZW1haWwsIHNlbmQgYSBtZXNz
YWdlIHdpdGggc3ViamVjdCBvciBib2R5ICdoZWxwJyB0bw0KPiAJaWV0Zi1yZXF1ZXN0QGlldGYu
b3JnDQo+DQo+IFlvdSBjYW4gcmVhY2ggdGhlIHBlcnNvbiBtYW5hZ2luZyB0aGUgbGlzdCBhdA0K
PiAJaWV0Zi1vd25lckBpZXRmLm9yZw0KPg0KPiBXaGVuIHJlcGx5aW5nLCBwbGVhc2UgZWRpdCB5
b3VyIFN1YmplY3QgbGluZSBzbyBpdCBpcyBtb3JlIHNwZWNpZmljDQo+IHRoYW4gIlJlOiBDb250
ZW50cyBvZiBJZXRmIGRpZ2VzdC4uLiINCj4NCj4NCj4gVG9kYXkncyBUb3BpY3M6DQo+DQo+ICAg
IDEuIEhPTUVORVQgd29ya2luZyBncm91cCBwcm9wb3NhbCAoSmFyaSBBcmtrbykNCj4gICAgMi4g
UkU6IFtmdHBleHRdIExhc3QgQ2FsbDogPGRyYWZ0LWlldGYtZnRwZXh0Mi1ob3N0cy0wMi50eHQ+
DQo+ICAgICAgIChGaWxlCVRyYW5zZmVyIFByb3RvY29sCUhPU1QgQ29tbWFuZCBmb3IgVmlydHVh
bCBIb3N0cykgdG8NCj4gICAgICAgUHJvcG9zZWQJU3RhbmRhcmQgKFJvYmVydCBNY011cnJheSkN
Cj4NCj4NCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPg0KPiBNZXNzYWdlOiAxDQo+IERhdGU6IFdlZCwgMjkg
SnVuIDIwMTEgMTA6NDc6MTggKzAyMDANCj4gRnJvbTogSmFyaSBBcmtrbyA8amFyaS5hcmtrb0Bw
aXVoYS5uZXQ+DQo+IFRvOiAiaG9tZWdhdGVAaWV0Zi5vcmciIDxob21lZ2F0ZUBpZXRmLm9yZz4s
IElFVEYgRGlzY3Vzc2lvbg0KPiAJPGlldGZAaWV0Zi5vcmc+DQo+IENjOiAiVy4gTWFyayBUb3du
c2xleSIgPHRvd25zbGV5QGNpc2NvLmNvbT4NCj4gU3ViamVjdDogSE9NRU5FVCB3b3JraW5nIGdy
b3VwIHByb3Bvc2FsDQo+IE1lc3NhZ2UtSUQ6IDw0RTBBRTY5Ni40MDIwNjAzQHBpdWhhLm5ldD4N
Cj4gQ29udGVudC1UeXBlOiB0ZXh0L3BsYWluOyBjaGFyc2V0PXdpbmRvd3MtMTI1MjsgZm9ybWF0
PWZsb3dlZA0KPg0KPiBJIHdvdWxkIGxpa2UgdG8gYW5ub3VuY2UgYSBuZXcgZWZmb3J0IGFyb3Vu
ZCBob21lIG5ldHdvcmtpbmcgYW5kIHNvbGljaXQNCj4gc29tZSBmZWVkYmFjay4NCj4NCj4gSE9N
RU5FVCBpcyBhIG5ldyB3b3JraW5nIGdyb3VwIHByb3Bvc2FsLCBhIHZhcmlhdGlvbiBvZiB0aGUN
Cj4gSE9NRUdBVEUvSE9NRU5FVCB0aGVtZSB0aGF0IHdlIGRpc2N1c3NlZCBsYXN0IHllYXIsIGJ1
dCB0aGlzIHRpbWUNCj4gbG9va2luZyBhdCBpdCBmcm9tIGEgZGlmZmVyZW50IGFuZ2xlLiBUaGUg
b2xkIGVmZm9ydCB3YXMgbW9zdGx5IGZvY3VzZWQNCj4gYWJvdXQgd2hhdCBob21lIGdhdGV3YXlz
IHNob3VsZCBkbzogZm9yd2FyZGluZywgdHJhbnNwb3J0LCBhbmQgRE5TDQo+IHByb3h5aW5nIGlz
c3Vlcy4gVGhlIG5ldyBlZmZvcnQgaXMgYWJvdXQgaG9tZSBuZXR3b3JrcyB0aGVtc2VsdmVzLCBp
bg0KPiBwYXJ0aWN1bGFyIHdoYXQga2luZCBvZiBuZXR3b3JrIGFyY2hpdGVjdHVyZSBhbmQgY29u
ZmlndXJhdGlvbiBpcw0KPiBuZWNlc3NhcnkgdG8gc3VwcG9ydCBJUHY2LWJhc2VkIGhvbWUgbmV0
d29ya3MuIFdlIHZpZXcgSVB2NC1iYXNlZCBob21lDQo+IG5ldHdvcmtzIGFzICJkb25lIiBhdCB0
aGlzIHRpbWUgKG9yIHBlcmhhcHMgYXMgImNhbm5vdCBiZSBjaGFuZ2VkIGFueXdheSIpLg0KPg0K
PiBJIGhhdmUgYmVlbiBkaXNjdXNzaW5nIHRoaXMgZWZmb3J0IGluIHRoZSBiYWNrZ3JvdW5kIGZv
ciB0aGUgbGFzdCBjb3VwbGUNCj4gb2YgbW9udGggd2l0aCBNYXJrIFRvd25zbGV5IGFuZCBvdGhl
cnMsIGFuZCBtb3JlIHB1YmxpY2x5IHNpbmNlIGVhcmx5DQo+IEp1bmUuIFRoZSBwcm9wb3NhbCBo
YXMgYmVlbiBicm91Z2h0IHRvIHRoZSBJRVNHLCBJQUIgYW5kIHNvbWUNCj4gZGlyZWN0b3JhdGVz
IGZvciBkaXNjdXNzaW9uLCBhbmQgd2UndmUgYmVlbiBnb2luZyBiYWNrIGFuZCBmb3J0aCB3aGV0
aGVyDQo+IHRoaXMgaXMgcmVhZHkgdG8gYmVjb21lIGEgd29ya2luZyBncm91cCBvciBuZWVkcyB0
byBiZSBydW4gYXMgYSBCT0YgaW4NCj4gUXVlYmVjIENpdHkuIFRoZSBjdXJyZW50IHBsYW4gaXMg
dGhhdCB0aGUgd29ya2luZyBncm91cCBwcm9wb3NhbCBnb2VzIHRvDQo+IElFVEYtd2lkZSByZXZp
ZXcgdGhpcyB3ZWVrLCBhbmQgaWYgdGhlIGZlZWRiYWNrIGZyb20gdGhlIGNvbW11bml0eSwgSUFC
LA0KPiBhbmQgdGhlIElFU0cgaXMgcG9zaXRpdmUsIHdlIHdpbGwgY3JlYXRlIHRoZSB3b3JraW5n
IGdyb3VwIGp1c3QgaW4gdGltZQ0KPiBmb3IgdGhlIElFVEYuIE90aGVyd2lzZSwgdGhlIHNsb3Qg
cmVzZXJ2ZWQgaW4gdGhlIGFnZW5kYSBmb3IgdGhlIG1lZXRpbmcNCj4gd2lsbCBiZSB1c2VkIHRv
IHJ1biB0aGUgcHJvcG9zYWwgYXMgYSBCT0YuDQo+DQo+IEluIGFueSBjYXNlLCBJIHdvdWxkIGxp
a2UgdG8gc29saWNpdCBkaXNjdXNzaW9uIG9uIHRoaXMgdG9waWMsIGFuZA0KPiBwZXJoYXBzIHNv
bWUgZWFybHkgZHJhZnRzIGFzIHdlbGwuIFBsZWFzZSBjb21tZW50IG9uIHRoZSBjaGFydGVyIGF0
DQo+IGxlYXN0LiBHbyBoZXJlIHRvIHN1YnNjcmliZSBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2Z1bg0KPiBhbmQgYmVsb3cgeW91IGNhbiBmaW5kIHRoZSBtb3N0IHJlY2Vu
dCBjaGFydGVyIHByb3Bvc2FsLiBQbGVhc2Ugam9pbiB0aGUNCj4gbGlzdCBhbmQgdGhlIGRpc2N1
c3Npb24uDQo+DQo+IE5vdGUgdGhhdCB0aGUgbmV3IHByb3Bvc2FsIHdhcyBjYWxsZWQgRlVOIGF0
IHRoZSB0aW1lIHRoYXQgd2UgY3JlYXRlZA0KPiB0aGUgbGlzdC4gSXQgaGFzIG5vdyBiZWVuIHJl
bmFtZWQgYmFjayB0byBIT01FTkVUIHRvIGJlIG1vcmUNCj4gZGVzY3JpcHRpdmUuIFRoZSBsaXN0
IHdpbGwgYmUgcmVuYW1lZCBzb29uIGFzIHdlbGwgKGN1cnJlbnQgc3Vic2NyaWJlcnMNCj4gd2ls
bCBzdGF5KS4gTm90ZSBhbHNvIHRoYXQgSSdtIHNlbmRpbmcgdGhpcyB0byB0aGUgb2xkIGhvbWVn
YXRlIGxpc3QsIHRvDQo+IGluZm9ybSBwZW9wbGUgd2hvIHdlcmUgaW50ZXJlc3RlZCBpbiB0aGF0
LiBJJ2QgbGlrZSB0aGUgZGlzY3Vzc2lvbiB0bw0KPiBoYXBwZW4gb24gdGhlIGZ1bkBpZXRmLm9y
ZyBsaXN0LCBob3dldmVyLg0KPg0KPiBKYXJpDQo+DQo+IEhvbWUgTmV0d29ya3MgKGhvbWVuZXQp
DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+DQo+IEN1cnJlbnQgU3Rh
dHVzOiBQcm9wb3NlZA0KPiBMYXN0IEVkaXQ6IFdlZG5lc2RheSwgSnVuZSAyOXRoLCAyMDExDQo+
DQo+IENoYWlyczoNCj4gVEJEDQo+DQo+IEludGVybmV0IEFyZWEgRGlyZWN0b3JzOg0KPiBSYWxw
aCBEcm9tcyA8cmRyb21zLmlldGZAZ21haWwuY29tPg0KPiBKYXJpIEFya2tvIDxqYXJpLmFya2tv
QHBpdWhhLm5ldD4NCj4NCj4gSW50ZXJuZXQgQXJlYSBBZHZpc29yOg0KPiBKYXJpIEFya2tvIDxq
YXJpLmFya2tvQHBpdWhhLm5ldD4NCj4NCj4gUm91dGluZyBBcmVhIFRlY2huaWNhbCBBZHZpc29y
Og0KPiBUQkQNCj4NCj4gU2VjdXJpdHkgQXJlYSBUZWNobmljYWwgQWR2aXNvcjoNCj4gVEJEDQo+
DQo+IE1haWxpbmcgTGlzdHM6DQo+IEdlbmVyYWwgRGlzY3Vzc2lvbjogZnVuQGlldGYub3JnDQo+
IFRvIFN1YnNjcmliZTogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9mdW4N
Cj4gQXJjaGl2ZTogaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2Z1bg0KPg0K
PiBEZXNjcmlwdGlvbiBvZiBXb3JraW5nIEdyb3VwOg0KPg0KPiBUaGlzIHdvcmtpbmcgZ3JvdXAg
Zm9jdXNlcyBvbiB0aGUgZXZvbHZpbmcgbmV0d29ya2luZyB0ZWNobm9sb2d5DQo+IHdpdGhpbiBh
bmQgYW1vbmcgcmVsYXRpdmVseSBzbWFsbCA/cmVzaWRlbnRpYWwgaG9tZT8gbmV0d29ya3MuIEZv
cg0KPiBleGFtcGxlLCBhbiBvYnZpb3VzIHRyZW5kIGluIGhvbWUgbmV0d29ya2luZyBpcyB0aGUg
cHJvbGlmZXJhdGlvbiBvZg0KPiBuZXR3b3JraW5nIHRlY2hub2xvZ3kgaW4gYW4gaW5jcmVhc2lu
Z2x5IGJyb2FkIHJhbmdlIGFuZCBudW1iZXIgb2YNCj4gZGV2aWNlcy4gVGhpcyBldm9sdXRpb24g
aW4gc2NhbGUgYW5kIGRpdmVyc2l0eSBzZXRzIHNvbWUgcmVxdWlyZW1lbnRzDQo+IG9uIElFVEYg
cHJvdG9jb2xzLiBTb21lIG9mIHRoZSByZWxldmFudCB0cmVuZHMgaW5jbHVkZToNCj4NCj4gbyBN
dWx0aXBsZSBzZWdtZW50czogV2hpbGUgbGVzcyBjb21wbGV4IEwzLXRvcGxvZ2llcyBpbnZvbHZp
bmcgYXMgZmV3DQo+IHN1Ym5ldHMgYXMgcG9zc2libGUgYXJlIHByZWZlcnJlZCBpbiBob21lIG5l
dHdvcmtzIGZvciBhIHZhcmlldHkgb2YNCj4gcmVhc29ucyBpbmNsdWRpbmcgc2ltcGxlciBtYW5h
Z2VtZW50IGFuZCBzZXJ2aWNlIGRpc2NvdmVyeSwgdGhlDQo+IGludHJvZHVjdGlvbiBvZiBtb3Jl
IHRoYW4gb25lIHN1Ym5ldCBpbnRvIGEgaG9tZSBuZXR3b3JrIGlzIGVub3VnaA0KPiB0byBhZGQg
Y29tcGxleGl0eSB0aGF0IG5lZWRzIHRvIGJlIGFkZHJlc3NlZCwgYW5kIG11bHRpcGxlDQo+IGRl
ZGljYXRlZCBzZWdtZW50cyBhcmUgbmVjZXNzYXJ5IGZvciBzb21lIGNhc2VzLiBGb3IgaW5zdGFu
Y2UsIGENCj4gY29tbW9uIGZlYXR1cmUgaW4gbW9kZXJuIGhvbWUgcm91dGVycyBpbiB0aGUgYWJp
bGl0eSB0byBzdXBwb3J0DQo+IGJvdGggZ3Vlc3QgYW5kIHByaXZhdGUgbmV0d29yayBzZWdtZW50
cy4gQWxzbywgbGluayBsYXllcg0KPiBuZXR3b3JraW5nIHRlY2hub2xvZ3kgaXMgcG9pc2VkIHRv
IGJlY29tZSBtb3JlIGhldGVyb2dlbmVvdXMsIGFzDQo+IG5ldHdvcmtzIGJlZ2luIHRvIGVtcGxv
eSBib3RoIHRyYWRpdGlvbmFsIEV0aGVybmV0IHRlY2hub2xvZ3kgYW5kDQo+IGxpbmsgbGF5ZXJz
IGRlc2lnbmVkIGZvciBsb3ctcG93ZXJlZCBzZW5zb3IgbmV0d29ya3MuIEZpbmFsbHksDQo+IHNp
bWlsYXIgbmVlZHMgZm9yIHNlZ21lbnRhdGlvbiBtYXkgb2NjdXIgaW4gb3RoZXIgY2FzZXMsIHN1
Y2ggYXMNCj4gc2VwYXJhdGluZyBidWlsZGluZyBjb250cm9sIG9yIGNvcnBvcmF0ZSBleHRlbnNp
b25zIGZyb20gdGhlDQo+IEludGVybmV0IGFjY2VzcyBuZXR3b3JrLiBEaWZmZXJlbnQgc2VnbWVu
dHMgbWF5IGJlIGFzc29jaWF0ZWQgd2l0aA0KPiBzdWJuZXRzIHRoYXQgaGF2ZSBkaWZmZXJlbnQg
cm91dGluZyBhbmQgc2VjdXJpdHkgcG9saWNpZXMuDQo+DQo+IG8gU2VydmljZSBwcm92aWRlcnMg
YXJlIGRlcGxveWluZyBJUHY2LCBhbmQgc3VwcG9ydCBmb3IgSVB2NiBpcw0KPiBpbmNyZWFzaW5n
bHkgYXZhaWxhYmxlIGluIGhvbWUgZ2F0ZXdheSBkZXZpY2VzLiBXaGlsZSBJUHY2IHJlc2VtYmxl
cw0KPiBJUHY0IGluIG1hbnkgd2F5cywgaXQgY2hhbmdlcyBhZGRyZXNzIGFsbG9jYXRpb24gcHJp
bmNpcGxlcyBhbmQgYWxsb3dzDQo+IGRpcmVjdCBJUCBhZGRyZXNzYWJpbGl0eSBhbmQgcm91dGlu
ZyB0byBkZXZpY2VzIGluIHRoZSBob21lIGZyb20gdGhlDQo+IEludGVybmV0LiBUaGlzIGlzIGEg
cHJvbWlzaW5nIGFyZWEgaW4gSVB2NiB0aGF0IGhhcyBwcm92ZWQgY2hhbGxlbmdpbmcNCj4gaW4g
SVB2NCB3aXRoIHRoZSBwcm9saWZlcmF0aW9uIG9mIE5BVC4NCj4NCj4gbyBFbmQtdG8tZW5kIGNv
bW11bmljYXRpb24gaXMgYm90aCBhbiBvcHBvcnR1bml0eSBhbmQgYSBjb25jZXJuIGFzIGl0DQo+
IGVuYWJsZXMgbmV3IGFwcGxpY2F0aW9ucyBidXQgYWxzbyBleHBvc2VzIG5vZGVzIGluIHRoZSBp
bnRlcm5hbA0KPiBuZXR3b3JrcyB0byByZWNlaXB0IG9mIHVud2FudGVkIHRyYWZmaWMgZnJvbSB0
aGUgSW50ZXJuZXQuIEZpcmV3YWxscw0KPiB0aGF0IHJlc3RyaWN0IGluY29taW5nIGNvbm5lY3Rp
b25zIG1heSBiZSB1c2VkIHRvIHByZXZlbnQgZXhwb3N1cmUsDQo+IGhvd2V2ZXIsIHRoaXMgcmVk
dWNlcyB0aGUgZWZmaWNhY3kgb2YgZW5kLXRvLWVuZCBjb25uZWN0aXZpdHkgdGhhdA0KPiBJUHY2
IGhhcyB0aGUgcG90ZW50aWFsIHRvIHJlc3RvcmUuDQo+DQo+IEhvbWUgbmV0d29ya3MgbmVlZCB0
byBwcm92aWRlIHRoZSB0b29scyB0byBoYW5kbGUgdGhlc2Ugc2l0dWF0aW9ucyBpbg0KPiBhIG1h
bm5lciBhY2Nlc3NpYmxlIHRvIGFsbCB1c2VycyBvZiBob21lIG5ldHdvcmtzLiBNYW51YWwNCj4g
Y29uZmlndXJhdGlvbiBpcyByYXJlbHksIGlmIGF0IGFsbCwgcG9zc2libGUuIFRoZSBwdXJwb3Nl
IG9mIHRoaXMNCj4gd29ya2luZyBncm91cCBpcyB0byBmb2N1cyBvbiB0aGlzIGV2b2x1dGlvbiwg
aW4gcGFydGljdWxhciBhcyBpdA0KPiBhZGRyZXNzZXMgdGhlIGludHJvZHVjdGlvbiBvZiBJUHY2
LCBieSBkZXZlbG9waW5nIGFuIGFyY2hpdGVjdHVyZQ0KPiBhZGRyZXNzaW5nIHRoaXMgZnVsbCBz
Y29wZSBvZiByZXF1aXJlbWVudHM6DQo+DQo+IG8gcHJlZml4IGNvbmZpZ3VyYXRpb24gZm9yIHJv
dXRlcnMNCj4gbyBtYW5hZ2luZyByb3V0aW5nDQo+IG8gbmFtZSByZXNvbHV0aW9uDQo+IG8gc2Vy
dmljZSBkaXNjb3ZlcnkNCj4gbyBuZXR3b3JrIHNlY3VyaXR5DQo+DQo+IFRoZSB0YXNrIG9mIHRo
ZSBncm91cCBpcyB0byBwcm9kdWNlIGFuIGFyY2hpdGVjdHVyZSBkb2N1bWVudCB0aGF0DQo+IG91
dGxpbmVzIGhvdyB0byBjb25zdHJ1Y3QgaG9tZSBuZXR3b3JrcyBpbnZvbHZpbmcgbXVsdGlwbGUg
cm91dGVycyBhbmQNCj4gc3VibmV0cy4gVGhpcyBkb2N1bWVudCBpcyBleHBlY3RlZCB0byBhcHBs
eSB0aGUgSVB2NiBhZGRyZXNzaW5nDQo+IGFyY2hpdGVjdHVyZSwgcHJlZml4IGRlbGVnYXRpb24s
IGdsb2JhbCBhbmQgVUxBIGFkZHJlc3Nlcywgc291cmNlDQo+IGFkZHJlc3Mgc2VsZWN0aW9uIHJ1
bGVzIGFuZCBvdGhlciBleGlzdGluZyBjb21wb25lbnRzIG9mIHRoZSBJUHY2DQo+IGFyY2hpdGVj
dHVyZS4gVGhlIGFyY2hpdGVjdHVyZSBkb2N1bWVudCBzaG91bGQgZHJpdmUgd2hhdCBwcm90b2Nv
bHMNCj4gY2hhbmdlcywgaWYgYW55LCBhcmUgbmVjZXNzYXJ5LiBTcGVjaWZpYyBwcm90b2NvbCB3
b3JrIGRlc2NyaWJlZCBiZWxvdw0KPiBpcyBleHBlY3RlZCB0byBiZSB3aXRoaW4gdGhlIHNjb3Bl
IG9mIHRoZSB3b3JraW5nIGdyb3VwIG9uZSB0aGUNCj4gYXJjaGl0ZWN0dXJlIHdvcmsgaXMgY29t
cGxldGUuIEhvd2V2ZXIsIHRoZSBncm91cCBpcyByZXF1aXJlZCB0bw0KPiByZXZpZXcgaXRzIGNo
YXJ0ZXIgYW5kIG1pbGVzdG9uZXMgd2l0aCB0aGUgSUVTRyBhbmQgSUVURiBjb21tdW5pdHkNCj4g
YmVmb3JlIHN1Ym1pdHRpbmcgZG9jdW1lbnRzIHRoYXQgbWFrZSBwcm90b2NvbCBjaGFuZ2VzLiBJ
dCBpcyBleHBlY3RlZA0KPiB0aGF0IHRoZSBncm91cCBoYXMgdG8gZGlzY3VzcyBzb21lIG9mIHRo
ZSBiZWxvdyBzb2x1dGlvbnMsIGhvd2V2ZXIsIGluDQo+IG9yZGVyIHRvIGNvbXBsZXRlIHRoZSBh
cmNoaXRlY3R1cmUgd29yay4NCj4NCj4gVGhlIGdyb3VwIHdpbGwgYXBwbHkgZXhpc3RpbmcgcHJv
dG9jb2xzIHRvIGhhbmRsZSB0aGUgZml2ZQ0KPiByZXF1aXJlbWVudHMgYWJvdmUuIEZvciBwcmVm
aXggY29uZmlndXJhdGlvbiwgZXhpc3RpbmcgcHJvdG9jb2xzIGFyZQ0KPiBsaWtlbHkgc3VmZmlj
aWVudCwgYW5kIGF0IHdvcnN0IG1heSBuZWVkIHNvbWUgc21hbGwgZW5oYW5jZW1lbnRzLCBzdWNo
DQo+IGFzIG5ldyBvcHRpb25zLiBGb3IgYXV0b21hdGljIHJvdXRpbmcsIGl0IGlzIGV4cGVjdGVk
IHRoYXQgZXhpc3RpbmcNCj4gcm91dGluZyBwcm90b2NvbHMgY2FuIGJlIHVzZWQgYXMgaXMsIGhv
d2V2ZXIsIGEgbmV3IG1lY2hhbmlzbSBtYXkgYmUNCj4gbmVlZGVkIGluIG9yZGVyIHRvIHR1cm4g
YSBzZWxlY3RlZCBwcm90b2NvbCBvbiBieSBkZWZhdWx0LiBGb3IgbmFtZQ0KPiByZXNvbHV0aW9u
IGFuZCBzZXJ2aWNlIGRpc2NvdmVyeSwgZXh0ZW5zaW9ucyB0byBleGlzdGluZw0KPiBtdWx0aWNh
c3QtYmFzZWQgbmFtZSByZXNvbHV0aW9uIHByb3RvY29scyBhcmUgbmVlZGVkIHRvIGVuYWJsZSB0
aGVtIHRvDQo+IHdvcmsgYWNyb3NzIHN1Ym5ldHMuDQo+DQo+IEZvciBuZXR3b3JrIHNlY3VyaXR5
LCB0aGUgZ3JvdXAgc2hhbGwgZG9jdW1lbnQgdGhlIGNvbmNlcHQgb2YNCj4gImFkdmFuY2VkIHNl
Y3VyaXR5IiBhcyBhIGZ1cnRoZXIgZGV2ZWxvcG1lbnQgb2YgInNpbXBsZSBzZWN1cml0eSIgZnJv
bQ0KPiBSRkMgNjA5Mi4gVGhlIG1haW4gZ29hbCBvZiB0aGlzIHdvcmsgaXMgdG8gZW5hYmxlIGEg
c2VjdXJpdHkgcG9saWN5DQo+IHRoYXQgYWRhcHRzIHRvIElQdjYgdGhyZWF0cyBhcyB0aGV5IGVt
ZXJnZSwgdGFraW5nIGludG8gYWNjb3VudCBub3QNCj4gb25seSB0cmFmZmljIGZyb20gdGhlIElu
dGVybmV0IGF0IGxhcmdlLCBidXQgd2l0aGluIGFuZCBsZWF2aW5nIHRoZQ0KPiBob21lIG5ldHdv
cmsgaXRzZWxmLg0KPg0KPiBJdCBpcyBleHBlY3RlZCB0aGF0IHRoZSB3b3JraW5nIGdyb3VwIHdp
bGwgZGVmaW5lIGEgc2V0IG9mIHByb3RvY29sDQo+IHNwZWNpZmljYXRpb25zIHRvIGFjY29tcGxp
c2ggdGhlIGZpdmUgcmVxdWlyZW1lbnRzIGZyb20NCj4gYWJvdmUuIEhvd2V2ZXIsIGl0IGlzIG5v
dCBpbiB0aGUgc2NvcGUgb2YgdGhlIHdvcmtpbmcgZ3JvdXAgdG8gZGVmaW5lDQo+IGVudGlyZWx5
IG5ldyByb3V0aW5nIHByb3RvY29scyBvciBhZGRyZXNzIGFsbG9jYXRpb24gcHJvdG9jb2xzLiBB
cw0KPiBub3RlZCwgYWRkaXRpb25hbCBvcHRpb25zIG9yIG90aGVyIHNtYWxsIGV4dGVuc2lvbnMg
bWF5IGJlIG5lY2Vzc2FyeQ0KPiB0byB1c2UgdGhlIGV4aXN0aW5nIHByb3RvY29scyBpbiB0aGVz
ZSBuZXcgY29uZmlndXJhdGlvbiB0YXNrcy4gVGhlDQo+IHdvcmtpbmcgZ3JvdXAgc2hhbGwgYWxz
byBub3QgbWFrZSBhbnkgY2hhbmdlcyB0byBJUHY2IHByb3RvY29scyBvcg0KPiBhZGRyZXNzaW5n
IGFyY2hpdGVjdHVyZS4gUHJlZml4IGNvbmZpZ3VyYXRpb24sIHJvdXRpbmcsIGFuZCBzZWN1cml0
eQ0KPiByZWxhdGVkIHdvcmsgc2hhbGwgbm90IGNhdXNlIGFueSBjaGFuZ2VzIHRoYXQgYXJlIG5v
dCBiYWNrd2FyZHMNCj4gY29tcGF0aWJsZSB0byBleGlzdGluZyBJUHY2IGhvc3RzLiBUaGVyZSBt
YXkgYmUgaG9zdCB2aXNpYmxlIGNoYW5nZXMNCj4gaW4gdGhlIHdvcmsgb24gbmFtaW5nIGFuZCBk
aXNjb3ZlcnkgcHJvdG9jb2xzLCBob3dldmVyLiBJbiBpdHMgZGVzaWduLA0KPiB0aGUgd29ya2lu
ZyBncm91cCBzaGFsbCBhbHNvIGNvbnNpZGVyIHNlY3VyaXR5IGFzcGVjdHMgYW5kIHRoZSBpbXBh
Y3QNCj4gb24gbWFuYWdlYWJpbGl0eS4gVGhlIG1haW4gZm9jdXMgb2YgdGhlIHdvcmtpbmcgZ3Jv
dXAgaXMgaG9tZQ0KPiBuZXR3b3JrcywgYnV0IHRoZSBncm91cCdzIHJlc3VsdHMgbWF5IGFsc28g
ZmluZCBhcHBsaWNhdGlvbnMgaW4gb3RoZXINCj4gc21hbGwgbmV0d29ya3MuDQo+DQo+IFRoZSB3
b3JraW5nIGdyb3VwIHdpbGwgbGlhaXNlIHdpdGggdGhlIHJlbGV2YW50IElFVEYgd29ya2luZw0K
PiBncm91cHMuIEluIHBhcnRpY3VsYXIsIHRoZSBncm91cCBzaG91bGQgd29yayBjbG9zZWx5IHdp
dGggdGhlIFY2T1BTDQo+IHdvcmtpbmcgZ3JvdXAsIHJldmlldyBhbnkgdXNlIG9yIGV4dGVuc2lv
biBvZiBESENQIHdpdGggdGhlIERIQw0KPiB3b3JraW5nIGdyb3VwLCBhbmQgd29yayB3aXRoIGFk
ZGl0aW9uYWwgRE5TIHJlcXVpcmVtZW50cyB3aXRoIHRoZQ0KPiBETlNFWFQgYW5kIEROU09QIHdv
cmtpbmcgZ3JvdXBzLiBJZiBpdCB0dXJucyBvdXQgdGhhdCBhZGRpdGlvbmFsDQo+IG9wdGlvbnMg
YXJlIG5lZWRlZCBmb3IgYSByb3V0aW5nIHByb3RvY29sLCB0aGV5IHdpbGwgYmUgZGV2ZWxvcGVk
IGluDQo+IHRoZSBhcHByb3ByaWF0ZSBSb3V0aW5nIEFyZWEgd29ya2luZyBncm91cCwgd2l0aCB0
aGUgSE9NRU5FVCB3b3JraW5nDQo+IGdyb3VwIHByb3ZpZGluZyB0aGUgYXJjaGl0ZWN0dXJlIGFu
ZCByZXF1aXJlbWVudHMgZm9yIHN1Y2gNCj4gZW5oYW5jZW1lbnRzLiBUaGUgd29ya2luZyBncm91
cCB3aWxsIGFsc28gbGlhc2Ugd2l0aCBleHRlcm5hbA0KPiBzdGFuZGFyZHMgYm9kaWVzIHdoZXJl
IGl0IGlzIGV4cGVjdGVkIHRoYXQgdGhlcmUgYXJlIG5vcm1hdGl2ZQ0KPiBkZXBlbmRlbmNpZXMg
YmV0d2VlbiB0aGUgc3BlY2lmaWNhdGlvbnMgb2YgdGhlIHR3byBib2RpZXMuDQo+IEl0IGlzIGV4
cGVjdGVkIHRoYXQgaW4gdGhlIGFyY2hpdGVjdHVyZSBkZWZpbml0aW9uIHN0YWdlIGxpYWlzaW5n
DQo+IHdpdGggdGhlIEJyb2FkYmFuZCBGb3J1bSwgRExOQSwgYW5kIFVQblAgRm9ydW0gaXMgbmVj
ZXNzYXJ5Lg0KPg0KPiBNaWxlc3RvbmVzOg0KPg0KPiBKdWwgMjAxMSBGb3JtYXRpb24gb2YgdGhl
IHdvcmtpbmcgZ3JvdXANCj4gU2VwIDIwMTEgRmlyc3QgV0cgZHJhZnQgb24gdGhlIGFyY2hpdGVj
dHVyZQ0KPiBEZWMgMjAxMSBTdWJtaXNzaW9uIG9mIHRoZSBhcmNoaXRlY3R1cmUgZHJhZnQgdG8g
dGhlIElFU0cgYXMNCj4gSW5mb3JtYXRpb25hbCBSRkMNCj4gRGVjIDIwMTEgQ2hhcnRlciByZS1l
dmFsdWF0aW9uIGJhc2VkIG9uIHRoZSBhcmNoaXRlY3R1cmUgd29yaw0KPiBEZWMgMjAxMSBGaXJz
dCBXRyBkcmFmdCBvbiBwcmVmaXggY29uZmlndXJhdGlvbg0KPiBEZWMgMjAxMSBGaXJzdCBXRyBk
cmFmdCBvbiByb3V0aW5nDQo+IEphbiAyMDEyIEZpcnN0IFdHIGRyYWZ0IG9uIG5hbWUgcmVzb2x1
dGlvbg0KPiBGZWIgMjAxMiBGaXJzdCBXRyBkcmFmdCBvbiBzZXJ2aWNlIGRpc2NvdmVyeQ0KPiBG
ZWIgMjAxMiBGaXJzdCBXRyBkcmFmdCBvbiBwZXJpbWV0ZXIgc2VjdXJpdHkNCj4gRmViIDIwMTIg
U3RhcnQgb2Ygcm91dGluZyByZWxhdGVkIHdvcmsgaW4gdGhlIHJlbGV2YW50IHJvdXRpbmcgYXJl
YQ0KPiB3b3JraW5nIGdyb3VwLCBpZiBuZWVkZWQNCj4gTWFyIDIwMTIgU3VibWlzc2lvbiBvZiB0
aGUgcHJlZml4IGNvbmZpZ3VyYXRpb24gZHJhZnQgdG8gdGhlIElFU0cgYXMNCj4gU3RhbmRhcmRz
IFRyYWNrIFJGQw0KPiBBcHIgMjAxMiBTdWJtaXNzaW9uIG9mIHRoZSByb3V0aW5nIGRyYWZ0IHRv
IHRoZSBJRVNHIGFzIEluZm9ybWF0aW9uYWwgUkZDDQo+IFNlcCAyMDEyIFN1Ym1pc3Npb24gb2Yg
dGhlIG5hbWUgcmVzb2x1dGlvbiBkcmFmdCB0byB0aGUgSUVTRyBhcw0KPiBTdGFuZGFyZHMgVHJh
Y2sgUkZDDQo+IE5vdiAyMDEyIFN1Ym1pc3Npb24gb2YgdGhlIHNlcnZpY2UgZGlzY292ZXJ5IGRy
YWZ0IHRvIHRoZSBJRVNHIGFzDQo+IFN0YW5kYXJkcyBUcmFjayBSRkMNCj4gRGVjIDIwMTIgU3Vi
bWlzc2lvbiBvZiB0aGUgcGVyaW1ldGVyIHNlY3VyaXR5IGRyYWZ0IHRvIHRoZSBJRVNHIGFzDQo+
IEluZm9ybWF0aW9uYWwgUkZDDQo+DQo+DQo+DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLQ0KPg0KPiBNZXNzYWdlOiAyDQo+IERhdGU6IFdlZCwgMjkgSnVuIDIwMTEgMDI6MDQ6MTYg
KzAwMDANCj4gRnJvbTogUm9iZXJ0IE1jTXVycmF5IDxyb2JtY21AbWljcm9zb2Z0LmNvbT4NCj4g
VG86IFBhdWwgRm9yZC1IdXRjaGluc29uIDxwYXVsZm9yZGhAdWsuaWJtLmNvbT4sICJpZXRmQGll
dGYub3JnIg0KPiAJPGlldGZAaWV0Zi5vcmc+DQo+IENjOiAiZnRwZXh0QGlldGYub3JnIiA8ZnRw
ZXh0QGlldGYub3JnPg0KPiBTdWJqZWN0OiBSRTogW2Z0cGV4dF0gTGFzdCBDYWxsOiA8ZHJhZnQt
aWV0Zi1mdHBleHQyLWhvc3RzLTAyLnR4dD4NCj4gCShGaWxlCVRyYW5zZmVyIFByb3RvY29sCUhP
U1QgQ29tbWFuZCBmb3IgVmlydHVhbCBIb3N0cykgdG8gUHJvcG9zZWQNCj4gCVN0YW5kYXJkDQo+
IE1lc3NhZ2UtSUQ6DQo+IAk8MDFBQTlFQzkyNzQ5QkY0ODk0QUMyQjMwMzlFQTRBMkMxOTRBMDdF
MkBDSDFQUkQwMzAyTUIxMzEubmFtcHJkMDMucHJvZC5vdXRsb29rLmNvbT4NCj4gCQ0KPiBDb250
ZW50LVR5cGU6IHRleHQvcGxhaW47IGNoYXJzZXQ9InVzLWFzY2lpIg0KPg0KPiBUaGFua3MsIFBh
dWwuDQo+DQo+IEkgYmVsaWV2ZSB0aGF0IEkgaGF2ZSBhZGRyZXNzZWQgYWxsIG9mIHlvdXIgY29t
bWVudHMgd2l0aCB0aGUgZm9sbG93aW5nDQo+IGFjdGlvbnM6DQo+DQo+IC0tLS0tLS0tLS0tLS0t
LS0tLS0tDQo+IFNlY3Rpb24gMzoNCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4NCj4+IFN1cmVs
eSB0aGUgZmlyc3QgU0hPVUxEIGhhcyB0byBiZSBhIE1VU1QuDQo+PiBPdGhlcndpc2Ugd2UgaGF2
ZSBhIHNpdHVhdGlvbiB3aGVyZSwgdXBvbg0KPj4gcmVjZWlwdCBvZiBhIHZhbGlkIEhPU1QsIHNv
bWUgc2VydmVyDQo+PiBpbXBsZW1lbnRhdGlvbnMgd2lsbCBpbXBsaWNpdGx5IFJFSU4gYW5kDQo+
PiBjbGVhciBBVVRIL1VTRVIvQUNDVCBhbmQgc29tZSB3aWxsIG5vdC4NCj4NCj4gQWdyZWVkIC0g
SSBjaGFuZ2VkIHRoYXQgdmVyYmlhZ2UuDQo+DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IFNl
Y3Rpb24gMy4yOg0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPg0KPj4gSSBzdWdnZXN0IHRoYXQg
ZWl0aGVyIHRoZSAid3JhcHBlciIgY29uY2VwdCBpcw0KPj4gZHJvcHBlZCBmcm9tIHRoZSBkb2N1
bWVudCBhbHRvZ2V0aGVyLi4uDQo+DQo+IEkgcmVtb3ZlZCB0aGF0IHZlcmJpYWdlLiAoVGhhdCB3
YXMgZGV0YWlsIGZvciBhIHBvc3NpYmxlIHNlcnZlcg0KPiBpbXBsZW1lbnRhdGlvbiBhbnl3YXku
KQ0KPg0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiBTZWN0aW9uIDMuMi4yOg0KPiAtLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KPg0KPj4gc2hvdWxkIGJlICJ0byBuZWdvdGlhdGUgdGhlIHNlY3VyaXR5
IG1lY2hhbmlzbQ0KPj4gYW5kIHJlbGV2YW50IGF1dGhlbnRpY2F0aW9uIHRva2VuKHMpIg0KPg0K
PiBJIGNoYW5nZWQgdGhhdCBhcyB3ZWxsLg0KPg0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiBT
ZWN0aW9uIDQNCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4NCj4+IFRoZSAic3Ryb25nIG1ldGhv
ZCBvZiBlbmNyeXB0aW9uIiBpcyBhIGJpdA0KPj4gdmFndWUuIEkgZG9uJ3QgdGhpbmsgd2UgY2Fu
IHB1Ymxpc2ggdGhpcw0KPj4gcGFyYWdyYXBoIHdpdGhvdXQgYmVpbmcgbW9yZSBleHBsaWNpdCBh
Ym91dA0KPj4gd2hhdCB0aGlzIHJlYWxseSBtZWFucy4NCj4NCj4gSSByZW1vdmVkIHRoYXQgcGFy
YWdyYXBoLiBCeSB3YXkgb2YgZXhwbGFuYXRpb24sIHRoaXMgd2FzIGluIHJlZmVyZW5jZSBhDQo+
IHNlcnZlciBpbXBsZW1lbnRhdGlvbiBkZXRhaWwgdGhhdCBpbiBoaW5kc2lnaHQgcHJvYmFibHkg
c2hvdWxkbid0IGJlIGluIHRoaXMNCj4gZG9jdW1lbnQuIE1vcmUgc3BlY2lmaWNhbGx5LCBzb21l
IEZUUCBzZXJ2ZXJzIGFuZCBjbGllbnRzIHN1cHBvcnQgSW1wbGljaXQNCj4gRlRQUywgYnV0IHRo
YXQgaXMgbm90IGRlZmluZWQgYnkgUkZDIGFuZCBsYXRlbHkgY29uc2lkZXJlZCBkZXByZWNhdGVk
LCBzbw0KPiBpdCdzIGJlc3QgdG8ganVzdCByZW1vdmUgdGhhdCBpbmZvcm1hdGlvbi4NCj4NCj4+
IEkgcmVwZWF0IG15IGluaXRpYWwgcG9pbnQgLSB0aGlzIGhhcyB0byBiZSBhIE1VU1QuDQo+DQo+
IEFncmVlZCAtIEkgY2hhbmdlZCB0aGF0IHZlcmJpYWdlLg0KPg0KPj4gSSB3b3VsZCBsaWtlIHNv
bWUgbWVudGlvbiBvZiB0aGUgbGlua2FnZQ0KPj4gYmV0d2VlbiB0aGUgaWRlbnRpdHkgcmV0dXJu
ZWQgaW4gYW4gWC41MDkNCj4+IGNlcnRpZmljYXRlIGFuZCB0aGUgcGFyYW1ldGVyIHRvIHRoZSBI
T1NUDQo+PiBjb21tYW5kIGF0IHRoZSBwcm90b2NvbCBzcGVjaWZpY2F0aW9uIGxldmVsLg0KPg0K
PiBJIGhhdmUgYXR0YWNoZWQgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQgdGhhdCBjb250YWlu
cyBzdWdnZXN0ZWQgd29yZGluZw0KPiBmb3IgdGhpcyByZXF1ZXN0LCB3aXRoIGFsbCBvZiB0aGUg
b3RoZXIgY2hhbmdlcyB0aGF0IEkgaGF2ZSBhZGRyZXNzZWQgYXMNCj4gd2VsbC4NCj4NCj4NCj4g
VGhhbmtzIQ0KPg0KPiBSb2JlcnQNCj4gLS0tLS0tLS0tLS0tLS0gbmV4dCBwYXJ0IC0tLS0tLS0t
LS0tLS0tDQo+IEEgbm9uLXRleHQgYXR0YWNobWVudCB3YXMgc2NydWJiZWQuLi4NCj4gTmFtZTog
ZHJhZnQtaWV0Zi1mdHBleHQyLWhvc3RzLTA0LnBkZg0KPiBUeXBlOiBhcHBsaWNhdGlvbi9wZGYN
Cj4gU2l6ZTogMzQ2MDkgYnl0ZXMNCj4gRGVzYzogZHJhZnQtaWV0Zi1mdHBleHQyLWhvc3RzLTA0
LnBkZg0KPiBVUkw6DQo+IDxodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvaWV0
Zi9hdHRhY2htZW50cy8yMDExMDYyOS8zYmZiOTdlMi9hdHRhY2htZW50LnBkZj4NCj4gLS0tLS0t
LS0tLS0tLS0gbmV4dCBwYXJ0IC0tLS0tLS0tLS0tLS0tDQo+IEFuIGVtYmVkZGVkIGFuZCBjaGFy
c2V0LXVuc3BlY2lmaWVkIHRleHQgd2FzIHNjcnViYmVkLi4uDQo+IE5hbWU6IGRyYWZ0LWlldGYt
ZnRwZXh0Mi1ob3N0cy0wNC50eHQNCj4gVVJMOg0KPiA8aHR0cDovL3d3dy5pZXRmLm9yZy9tYWls
LWFyY2hpdmUvd2ViL2lldGYvYXR0YWNobWVudHMvMjAxMTA2MjkvM2JmYjk3ZTIvYXR0YWNobWVu
dC50eHQ+DQo+IC0tLS0tLS0tLS0tLS0tIG5leHQgcGFydCAtLS0tLS0tLS0tLS0tLQ0KPiBBIG5v
bi10ZXh0IGF0dGFjaG1lbnQgd2FzIHNjcnViYmVkLi4uDQo+IE5hbWU6IGRyYWZ0LWlldGYtZnRw
ZXh0Mi1ob3N0cy0wNC54bWwNCj4gVHlwZTogYXBwbGljYXRpb24veG1sDQo+IFNpemU6IDU3NTI1
IGJ5dGVzDQo+IERlc2M6IGRyYWZ0LWlldGYtZnRwZXh0Mi1ob3N0cy0wNC54bWwNCj4gVVJMOg0K
PiA8aHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2lldGYvYXR0YWNobWVudHMv
MjAxMTA2MjkvM2JmYjk3ZTIvYXR0YWNobWVudC54cGRsPg0KPg0KPiAtLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0NCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCj4gSWV0ZiBtYWlsaW5nIGxpc3QNCj4gSWV0ZkBpZXRmLm9yZw0KPiBodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lldGYNCj4NCj4NCj4gRW5kIG9mIEll
dGYgRGlnZXN0LCBWb2wgMzcsIElzc3VlIDEwMw0KPiAqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqDQo+DQoNCg0KLS0gDQpJbiB0aGlzIExpZmUgd2UgYmxvdyBsaWtlIHRoZSB3
aW5kLCB3aGVyZSB3ZSBibG93IHRvIHdlIGNhbiBuZXZlcg0KdGVsbCwgdGhlIGFpciB3ZSBibG93
IG91dCB3ZSBtYXkgbm90IGtub3cgdGhlIGRlbnNpdHkuIHRoZSBvbmx5IHRoaW5nDQp3ZSBzaG91
bGQga25vdyBpcyB0aGF0IHNvbWUgb25lIGlzIHdhaXRpbmcgdG8gcmVjZWl2ZSB0aGUgYWlyIG9m
IGxpZmUNCmZyb20gdXMsIExldHMgYmxvdyB0aGUgZ29vZCBhaXIgdGhhdCB3aWxsIGtlZXAgbGl2
ZXMgYWxpdmUgZm9yIG91cg0KYmV0dGVyIFRvbW9ycm93IC4uLi4gUGV0ZXIgT3NhIEEgU25yLg0K
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCklldGYgbWFp
bGluZyBsaXN0DQpJZXRmQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2lldGYNCg==


From fernando.gont.netbook.win@gmail.com  Thu Jun 30 03:40:25 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03B9B21F882D; Thu, 30 Jun 2011 03:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.413
X-Spam-Level: 
X-Spam-Status: No, score=-3.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pl+ZmQ8mNrlL; Thu, 30 Jun 2011 03:40:24 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id E692121F8822; Thu, 30 Jun 2011 03:40:23 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1036878gxk.31 for <multiple recipients>; Thu, 30 Jun 2011 03:40:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=ceNvLYYz88AOYiiSc3h3adcXQriY4SadLP/RMKLgZ4c=; b=BPio+iKqZtkPtuYXdBhqLnua+MWBo+V7CkLPLzHZNV3IHd5cPvw8HFXruLgce901jQ mFK6uJLMsBuHuEQKv/60phXtbeuNvSu8TH29MGkxx2Cf+IDPIihGrXqb1mtN5suafcvz rSl8y7wZMSrQPypnpYHs7V1JPdRkrfjn5G4uQ=
Received: by 10.101.154.22 with SMTP id g22mr1654733ano.58.1309430423272; Thu, 30 Jun 2011 03:40:23 -0700 (PDT)
Received: from [192.168.123.103] ([190.48.255.131]) by mx.google.com with ESMTPS id r19sm1890175and.26.2011.06.30.03.40.20 (version=SSLv3 cipher=OTHER); Thu, 30 Jun 2011 03:40:22 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4E0C5291.8030104@gont.com.ar>
Date: Thu, 30 Jun 2011 07:40:17 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Mark Townsley <mark@townsley.net>
Subject: Re: [homegate] HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar>	<alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se>	<4E0C1CF8.7090601@gont.com.ar>	<alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se> <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net>
In-Reply-To: <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: fun@ietf.org, homegate@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 10:40:25 -0000

Hi, Mark (and Jari),

Thanks so much for your clarification! All my questions/comments have
been addressed.

Thanks,
Fernando




On 06/30/2011 06:57 AM, Mark Townsley wrote:
> 
> I think the consensus we had in the past BoFs and discussion in and
> around this topic can be summed up as stating that homenet
> deliverables will:
> 
> - coexist with (existing) IPv4 protocols, devices, applications,
> etc. - operate in a (future) IPv6-only home network in the absence of
> IPv4 - be IP-agnostic whenever possible
> 
> In other words, anything we do for the IPv6 homenet cannot actively
> break what's already running on IPv4. Also, trying to define what the
> IPv4 home network should be has long reached a point of diminishing
> returns given the effort in doing so coupled with our ability to
> significantly affect what's already deployed. There's still hope we
> can help direct IPv6, as such that is homenet's primary focus.
> However, when we can define something that is needed for IPv6 in a
> way that is also useful for IPv4 without making significant
> concessions, we should go ahead and do so.
> 
> - Mark
> 
> 
> 
> On Jun 30, 2011, at 9:25 AM, Mikael Abrahamsson wrote:
> 
>> On Thu, 30 Jun 2011, Fernando Gont wrote:
>> 
>>> My point was that, except for the mechanism for PD, I don't see a
>>> substantial difference here that would e.g. prevent this from
>>> being developed for IPv4 (in addition to IPv6). -- Yes, I know we
>>> need to deploy IPv6... but I don't think you can expect people to
>>> get rid of their *working* IPv4 devices... (i.e., not sure why
>>> any of this functionality should be v6-only)
>> 
>> Chaining NAT boxes already work. I also feel that we shouldn't put
>> in a lot of work to develop IPv4 further, that focus should be put
>> on IPv6.
>> 
>>> I think this deserves a problem statement that clearly describes
>>> what we expect to be able to do (but currently can't), etc. And,
>>> if this is meant to be v6-only, state why v4 is excluded --
>>> unless we're happy to have people connect their IPv4-devices, and
>>> see that they cannot communicate anymore.
>> 
>> IPv4 should be excluded because it's a dead end, and we all know
>> it. We're just disagreeing when it's going to die and how.
>> 
>> -- Mikael Abrahamsson    email: swmike@swm.pp.se 
>> _______________________________________________ homegate mailing
>> list homegate@ietf.org 
>> https://www.ietf.org/mailman/listinfo/homegate
> 
> _______________________________________________ homegate mailing
> list homegate@ietf.org 
> https://www.ietf.org/mailman/listinfo/homegate
> 


-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From rdroms.ietf@gmail.com  Thu Jun 30 04:51:55 2011
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 1765521F8797 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 04:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.901
X-Spam-Level: 
X-Spam-Status: No, score=-102.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oL114vYgxpVK for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 04:51:54 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 84EA421F8615 for <ietf@ietf.org>; Thu, 30 Jun 2011 04:51:54 -0700 (PDT)
Received: by qwc23 with SMTP id 23so1771095qwc.31 for <ietf@ietf.org>; Thu, 30 Jun 2011 04:51:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=+fCaME/SXAPIv02dV3ajZhUjVnPRz+zhBsMeLq1VkHo=; b=dnQNuI8YYLneLqob/V232Ln44OmTR4b77LAFTfJbtqeFQ9kwEw6WmDUZzz0nZjSta3 Cm0ITYFM++uOzqI51LRSN/DI69QQcujkRne7Xdaf17jLXDqlyR5VCGo4cfWUJbYmVtVl WPfUXifQvBLJoZeBANEFdVnzAtT7sp3fL6HZI=
Received: by 10.224.174.83 with SMTP id s19mr1396799qaz.251.1309434712485; Thu, 30 Jun 2011 04:51:52 -0700 (PDT)
Received: from [192.168.1.144] (c-24-62-225-5.hsd1.ma.comcast.net [24.62.225.5]) by mx.google.com with ESMTPS id i7sm147076qcb.46.2011.06.30.04.51.50 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 30 Jun 2011 04:51:51 -0700 (PDT)
References: <201106300425.p5U4PUmx029187@fs4113.wdf.sap.corp> <7124D145-9BD6-4A4C-BD80-2578A3C501F1@network-heretics.com> <4E0C00D7.5080700@gmail.com>
In-Reply-To: <4E0C00D7.5080700@gmail.com>
Mime-Version: 1.0 (iPad Mail 8J3)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <528EE998-5197-43BE-8EDD-3DC48921893B@gmail.com>
X-Mailer: iPad Mail (8J3)
From: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: HOMENET working group proposal
Date: Thu, 30 Jun 2011 07:52:35 -0400
To: Melinda Shore <melinda.shore@gmail.com>
Cc: Keith Moore <moore@network-heretics.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 11:51:55 -0000

On Jun 30, 2011, at 12:51 AM, Melinda Shore <melinda.shore@gmail.com> wrote:=


> On 6/29/11 8:32 PM, Keith Moore wrote:
>> However it does not follow that home networks need NAT or private address=
 space.  Those are hacks of the 1990s.  They always were shortsighted, and t=
hey turned out to be an operational disaster.  We can do better.
>=20
> We can and should, but it's pretty clear that if the IETF
> were good at evangelizing we wouldn't be in this situation
> in the first place.  The focus really needs to be on producing
> good, secure protocols that work on the networks we've got.

...or the networks we can see coming in the near future.  ZigBee Alliance is=
 driving an IPv6-based multi-link architecture through planned deployments o=
f SE2.0 by several utilities.  BBF and CableLabs both expect IPv6, end-to-en=
d connectivity=20

Homenet will avoid breaking existing IPv4 deployments in the networks we've g=
ot today, but won't spend resources on unnecessary (in some cases impossible=
) feature parity.

- Ralph
>=20
> Melinda
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From eburger@standardstrack.com  Thu Jun 30 04:58:25 2011
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 7E94621F87F6 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 04:58:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=0.299,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oEYn0eOiM8t8 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 04:58:25 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.194.81]) by ietfa.amsl.com (Postfix) with ESMTP id 0466D21F87EF for <ietf@ietf.org>; Thu, 30 Jun 2011 04:58:25 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:From:Mime-Version:Content-Type:Subject:Date:In-Reply-To:To:References:Message-Id:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=pvDBkcOCOFFZbuz0ktjJFWvwyOf0sAST1TYywNhA+T8SWQpwP0o3UwCIYidpGbYRZXKBuTu7BSzTD3wkPwfEpCGG3UC/oGCuyewkGo7EfzqCgpudTPOeT7qEGB6ol/rO;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.126]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1QcFt0-0004F3-3U for ietf@ietf.org; Thu, 30 Jun 2011 04:58:22 -0700
From: Eric Burger <eburger@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-71-415418646; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: HOMENET working group proposal
Date: Thu, 30 Jun 2011 07:58:20 -0400
In-Reply-To: <528EE998-5197-43BE-8EDD-3DC48921893B@gmail.com>
To: IETF <ietf@ietf.org>
References: <201106300425.p5U4PUmx029187@fs4113.wdf.sap.corp> <7124D145-9BD6-4A4C-BD80-2578A3C501F1@network-heretics.com> <4E0C00D7.5080700@gmail.com> <528EE998-5197-43BE-8EDD-3DC48921893B@gmail.com>
Message-Id: <02A93EDD-2750-4B8D-8609-24055EC0E31C@standardstrack.com>
X-Mailer: Apple Mail (2.1084)
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-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 11:58:25 -0000

--Apple-Mail-71-415418646
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Given the 5-year lead time to get a protocol suite done in the IETF, why =
would we start by looking backward?

On Jun 30, 2011, at 7:52 AM, Ralph Droms wrote:

>=20
>=20
>=20
>=20
> On Jun 30, 2011, at 12:51 AM, Melinda Shore <melinda.shore@gmail.com> =
wrote:
>=20
>> On 6/29/11 8:32 PM, Keith Moore wrote:
>>> However it does not follow that home networks need NAT or private =
address space.  Those are hacks of the 1990s.  They always were =
shortsighted, and they turned out to be an operational disaster.  We can =
do better.
>>=20
>> We can and should, but it's pretty clear that if the IETF
>> were good at evangelizing we wouldn't be in this situation
>> in the first place.  The focus really needs to be on producing
>> good, secure protocols that work on the networks we've got.
>=20
> ...or the networks we can see coming in the near future.  ZigBee =
Alliance is driving an IPv6-based multi-link architecture through =
planned deployments of SE2.0 by several utilities.  BBF and CableLabs =
both expect IPv6, end-to-end connectivity=20
>=20
> Homenet will avoid breaking existing IPv4 deployments in the networks =
we've got today, but won't spend resources on unnecessary (in some cases =
impossible) feature parity.
>=20
> - Ralph
>>=20
>> Melinda
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-71-415418646
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILHzCCBN0w
ggPFoAMCAQICEHGS++YZX6xNEoV0cTSiGKcwDQYJKoZIhvcNAQEFBQAwezELMAkGA1UEBhMCR0Ix
GzAZBgNVBAgMEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBwwHU2FsZm9yZDEaMBgGA1UECgwR
Q29tb2RvIENBIExpbWl0ZWQxITAfBgNVBAMMGEFBQSBDZXJ0aWZpY2F0ZSBTZXJ2aWNlczAeFw0w
NDAxMDEwMDAwMDBaFw0yODEyMzEyMzU5NTlaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQx
FzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsx
ITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJz
dC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVNNRm5pELlzkniii8efNIx
B8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQylbsMTzC9mKALi+VuG6JG+ni8
om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHG
TPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7Nl
yP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu9mIwFIws6wIDAQABo4IBJzCCASMwHwYDVR0j
BBgwFoAUoBEKIz6W8Qfs4q8p74Klf9AwpLQwHQYDVR0OBBYEFImCZ33EnSZwAEu0UEh83j2uBG59
MA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr
BgEFBQcDBDARBgNVHSAECjAIMAYGBFUdIAAwewYDVR0fBHQwcjA4oDagNIYyaHR0cDovL2NybC5j
b21vZG9jYS5jb20vQUFBQ2VydGlmaWNhdGVTZXJ2aWNlcy5jcmwwNqA0oDKGMGh0dHA6Ly9jcmwu
Y29tb2RvLm5ldC9BQUFDZXJ0aWZpY2F0ZVNlcnZpY2VzLmNybDARBglghkgBhvhCAQEEBAMCAQYw
DQYJKoZIhvcNAQEFBQADggEBAJ2Vyzy4fqUJxB6/C8LHdo45PJTGEKpPDMngq4RdiVTgZTvzbRx8
NywlVF+WIfw3hJGdFdwUT4HPVB1rbEVgxy35l1FM+WbKPKCCjKbI8OLp1Er57D9Wyd12jMOCAU9s
APMeGmF0BEcDqcZAV5G8ZSLFJ2dPV9tkWtmNH7qGL/QGrpxp7en0zykX2OBKnxogL5dMUbtGB8SK
N04g4wkxaMeexIud6H4RvDJoEJYRmETYKlFgTYjrdDrfQwYyyDlWjDoRUtNBpEMD9O3vMyfbOeAU
TibJ2PU54om4k123KSZB6rObroP8d3XK6Mq1/uJlSmM+RMTQw16Hc6mYHK9/FX8wggY6MIIFIqAD
AgECAhEAxcM7lN0zgrA71mfq+sG6xjANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0xMDA5MDgwMDAw
MDBaFw0xMTA5MDgyMzU5NTlaMIHhMTUwMwYDVQQLEyxDb21vZG8gVHJ1c3QgTmV0d29yayAtIFBF
UlNPTkEgTk9UIFZBTElEQVRFRDFGMEQGA1UECxM9VGVybXMgYW5kIENvbmRpdGlvbnMgb2YgdXNl
OiBodHRwOi8vd3d3LmNvbW9kby5uZXQvcmVwb3NpdG9yeTEfMB0GA1UECxMWKGMpMjAwMyBDb21v
ZG8gTGltaXRlZDEUMBIGA1UEAxMLRXJpYyBCdXJnZXIxKTAnBgkqhkiG9w0BCQEWGmVidXJnZXJA
c3RhbmRhcmRzdHJhY2suY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqeauFkEq
5Pj7AIAaDRbUWIpoblTKyrjcSfXRaHvjk0jWBTsBPe6oOZjudMK0Vo9A1Sl52BixDgf1/qb2Z+PT
7M0mqSOOsSucEBid48IMvGi79xmKKAVf5jiyFNNAaTZWn76dwNLMkKd/+Ki0fn8kEbb2zG+gGKyZ
MNHiNX+GQfPpHyzo2MTwnb16lXMfGJrGv4uLZS/pY9PENdFQnwV0ASZoqX+ArtLY2xeuC+rYG9xQ
Cz7qiLbJhCJzWsEGETyHLDjE5bN4HB9DsJKtGFLQuOdTanwGigNz9cVH9pLFNQxiotavAouXgqS4
wGvcq4mGP9w9zTychoUqIKsEg9OD1wIDAQABo4ICHDCCAhgwHwYDVR0jBBgwFoAUiYJnfcSdJnAA
S7RQSHzePa4Ebn0wHQYDVR0OBBYEFAlgEOVj6Hl0La8sPRP388HEMiWvMA4GA1UdDwEB/wQEAwIF
oDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgB
hvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0
cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMwgaUGA1UdHwSBnTCBmjBMoEqgSIZGaHR0cDovL2Ny
bC5jb21vZG9jYS5jb20vVVROLVVTRVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWls
LmNybDBKoEigRoZEaHR0cDovL2NybC5jb21vZG8ubmV0L1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0
aGVudGljYXRpb25hbmRFbWFpbC5jcmwwbAYIKwYBBQUHAQEEYDBeMDYGCCsGAQUFBzAChipodHRw
Oi8vY3J0LmNvbW9kb2NhLmNvbS9VVE5BQUFDbGllbnRDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6
Ly9vY3NwLmNvbW9kb2NhLmNvbTAlBgNVHREEHjAcgRplYnVyZ2VyQHN0YW5kYXJkc3RyYWNrLmNv
bTANBgkqhkiG9w0BAQUFAAOCAQEACRTppSEc5DMYn8YXcbfX36iTaNBGw1gUvTNam0U8pXH0E7H3
2d4cTq6DEMu5ifEvxMGBqhUyv0sKxQ7+UvtDwrk7Kiy2L6TUC4zNEklZbtDqY7+Wd7EQZkN4k/zx
kMLlz2VIIRL/Cg48NrBKP5bo1la78NTJx8m4+VForLseEBabxMQoWB/GOVC7WpO/+RCgd93gz6H/
RzW1hnK0Uvu5H3Kz7HEC3R1Qk/sE9nXVzTfoJOMJRnyMS5Ut61mgoWSm/kUtczAlRRYh6IBOhzAl
awoXz+yk9hMCheYRAWx0EamBBpSzvqXj0N2vXYc62v3e3ddcLZncjiB0pYIfCE3s4DGCA/8wggP7
AgEBMIHEMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBD
aXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cu
dXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIEVtYWlsAhEAxcM7lN0zgrA71mfq+sG6xjAJBgUrDgMCGgUAoIICDzAYBgkqhkiG9w0B
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA2MzAxMTU4MjBaMCMGCSqGSIb3DQEJ
BDEWBBRuHw5TIf6NGfIIk+ACd0uL+nsSpTCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAEzbPqqM61f2BSNZMQv7EzqPaDhVpUz/jcFG4sF57T5fmLBO
C7XBDVZgM7eVLLePZXVFgW+5OERpRu+18ZoyrM6TXZjxCqtYGSFGizbj8yKtJrVNJYCbt4a3iI8R
6cMn1NYl4uBIbi4zuf49w/xqenP6pYkKRLSqWhEYUJdp0PVDko+qftzrhKeT6MJuj0JT+OYo2U61
+rGrkDdRXueMYJi1vlaNaQWcOrSuTqt5BynhqyWjGfOi1ZGeQQN/2+mC3SH8IMHZPTEr71nW8qiL
N/AeCWCDZ4jOhg+kDPRDm2LathafdeUhMZLfHUkJWlQAyTCR9OU6k9BUl2nFqjGCumwAAAAAAAA=

--Apple-Mail-71-415418646--

From moore@network-heretics.com  Thu Jun 30 05:17:13 2011
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 6559221F8659 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 05:17:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VJn4NypKP1Z5 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 05:17:12 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id B923221F8641 for <ietf@ietf.org>; Thu, 30 Jun 2011 05:17:12 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id DC26920C9F; Thu, 30 Jun 2011 08:17:11 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 30 Jun 2011 08:17:11 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=xCR5fmNu3Z4CK7ZzKIKA4b8F6Qk=; b=ehkoKJ3OYhP0OWWCb3M/RXbc+lWIuuqhq/4WwJgfr7PuTjtObiFT5Mcee8OXtB0O4jrJ5FOSwmNxx++eQIXtlKcQrptbfygDbPgM0OW/BGm00jBF8Xk+wnGlHIpKLHS0EP5Uck1TZtuYQwNJb+bjQrBiPjX/+L028jrmwy/iolo=
X-Sasl-enc: v1ZEim59GxvcDVd4jK0J9/vXxHy8wrVgRs836pV0pWwr 1309436231
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 0F450400C65; Thu, 30 Jun 2011 08:17:10 -0400 (EDT)
Subject: Re: HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E0C24CA.9090902@gont.com.ar>
Date: Thu, 30 Jun 2011 08:16:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F01354D1-3624-48D5-A6D2-81D4A2C51BE2@network-heretics.com>
References: <201106300509.p5U59j3q001889@fs4113.wdf.sap.corp> <3597BE26-F405-4D02-AE22-461635453FCF@network-heretics.com> <4E0C24CA.9090902@gont.com.ar>
To: Fernando Gont <fernando@gont.com.ar>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 12:17:13 -0000

On Jun 30, 2011, at 3:24 AM, Fernando Gont wrote:

> On 06/30/2011 02:26 AM, Keith Moore wrote:
>> Rather than having another of an endless series of discussions about
>> the merits of NAT or lack thereof, can we just agree that it should
>> not be pre-ordained that this WG should assume NAT as a solution?
>=20
> I was originally arguing, at the very least, in favour of a stateful
> firewall at the border.

I don't think the WG should be bound by existing technologies and =
assumptions.=20

Perimeter security of some kind is probably appropriate.  That doesn't =
mean that it has to look like firewalls do today.  For one thing, users =
shouldn't have to muck with the details of which ports to allow.  For =
another, trying to make security decisions be based on source IP address =
is ridiculous.  And the idea that every application server on a home =
network needs to negotiate access through some application-specific =
external server (as is generally the case with NATs today) is also =
ridiculous.

> Please correct me if I'm wrong, but this is what the IETF has already
> proposed (output of v6ops) for v6.

For some strange reason, I'm not particularly impressed with the output =
of v6ops lately.  Especially in their ability to consider the interests =
of the broader Internet.

Keith



From moore@network-heretics.com  Thu Jun 30 05:22:04 2011
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 88EA321F86D1; Thu, 30 Jun 2011 05:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.524
X-Spam-Level: 
X-Spam-Status: No, score=-3.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PKpLJBXKoj-z; Thu, 30 Jun 2011 05:22:03 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id A57D321F865B; Thu, 30 Jun 2011 05:22:02 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 5BA2820181; Thu, 30 Jun 2011 08:22:02 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 30 Jun 2011 08:22:02 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=ZbxK6nbRyA6gVw3Pu9B3x89x3ZQ=; b=XDADsYdVapmJGfAnUIeXptVhzXAwg59vuxoxncGmAPaRNnMirdAlgBONTps6QFJuBirOaZrJaEXIsVIpRcca0nenzkuMequ1zyictm5txo0xj2FKAKFAeaKJSR85EeaKEc/4QCIz1HfDpnjd3tYb2lmRdQ+KbTL2H/XR0G4l6nw=
X-Sasl-enc: hAibfs0jglKJUk/ZIyoc0FnbVi9AbZxcGXsNVYF2KtJc 1309436521
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 26618402367; Thu, 30 Jun 2011 08:22:01 -0400 (EDT)
Subject: Re: [homegate] HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E0C4631.3010409@gont.com.ar>
Date: Thu, 30 Jun 2011 08:21:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <94830A23-F251-4EDC-8002-11422CF691E2@network-heretics.com>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar> <4E0C4417.90804@piuha.net> <4E0C4631.3010409@gont.com.ar>
To: Fernando Gont <fernando@gont.com.ar>
X-Mailer: Apple Mail (2.1084)
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, IETF Discussion <ietf@ietf.org>, "fun@ietf.org" <fun@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 12:22:04 -0000

On Jun 30, 2011, at 5:47 AM, Fernando Gont wrote:

> Jari,
>=20
> On 06/30/2011 06:38 AM, Jari Arkko wrote:
>> But their architecture is largely done and cannot be easily affected.
>> Vendors are now looking into adding IPv6 into their home routers and
>> other devices. I want to be able to show them how to do it right. =
They
>> can, of course, replicate everything exactly as in IPv4. Much of it =
is
>> right, of course, but on some areas I think we can do better. This is
>> why the working group should focus on IPv6.=20
>=20
> My point is: Will implementation of the produced RFCs lead to home
> networks in which stuff works for IPv6 differently from how it works =
for
> IPv4?

hopefully!

> e.g., your home network would have multiple subnets (thanks to
> PD), but a single IPv4 subnet?

for that specific example, not clear.   my impression is that the =
architecture of home networks should work regardless of whether there's =
a single subnet or multiple subnets.

> If our work focuses only on IPv6, I get the impression that we're
> heading in that direction.

nothing says that some results of the work can't also apply to IPv4.  =
but people are far too mired in outdated assumptions today, such as the =
idea that every network needs a NAT or a firewall that filters based on =
IP addresses and ports.

> If HOMENET is going to improve stuff that we already do with IPv4 (by
> leveraging IPv6), then that's fine...=20

no, that's not fine.   that's painting ourselves (and the Internet) into =
a corner.

Keith


From fernando.gont.netbook.win@gmail.com  Thu Jun 30 06:08:49 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48AE721F86C9; Thu, 30 Jun 2011 06:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.431
X-Spam-Level: 
X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5 tests=[AWL=0.168,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qAid1GG-wRzK; Thu, 30 Jun 2011 06:08:48 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id A5F9721F864A; Thu, 30 Jun 2011 06:08:48 -0700 (PDT)
Received: by yie30 with SMTP id 30so1107630yie.31 for <multiple recipients>; Thu, 30 Jun 2011 06:08:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=a+C1IXj7Enk8hiutt6kv1oK8LpfnjPM/HzGpHoh9kfo=; b=sNzLZ6/zmmCt5sCjp5148MUTTmBuqjGnKXqjBfx70Oxfyj/WAmgRCOszN7RpMqY/mY WSGuiS2/p2vaiAh15nEyqyeQRSlUgQJr79xEjAQgBKFq8vHQaXbZ1359R86qqGJ19DV7 8eFCojQ4HFAMx7EP/McgPAEimhn9G2xfuUIg0=
Received: by 10.101.176.2 with SMTP id d2mr1738637anp.155.1309439328126; Thu, 30 Jun 2011 06:08:48 -0700 (PDT)
Received: from [192.168.123.103] ([190.48.255.131]) by mx.google.com with ESMTPS id b19sm1979890anh.19.2011.06.30.06.08.44 (version=SSLv3 cipher=OTHER); Thu, 30 Jun 2011 06:08:47 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4E0C70FA.5070300@gont.com.ar>
Date: Thu, 30 Jun 2011 09:50:02 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: [homegate] HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar> <4E0C4417.90804@piuha.net> <4E0C4631.3010409@gont.com.ar> <94830A23-F251-4EDC-8002-11422CF691E2@network-heretics.com>
In-Reply-To: <94830A23-F251-4EDC-8002-11422CF691E2@network-heretics.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, IETF Discussion <ietf@ietf.org>, "fun@ietf.org" <fun@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 13:08:49 -0000

On 06/30/2011 09:21 AM, Keith Moore wrote:

>> If our work focuses only on IPv6, I get the impression that we're 
>> heading in that direction.
> 
> nothing says that some results of the work can't also apply to IPv4.
> but people are far too mired in outdated assumptions today, such as
> the idea that every network needs a NAT or a firewall that filters
> based on IP addresses and ports.

I did not even argue about ports or addressing, but rather about who
initiated the communication instance.


>> If HOMENET is going to improve stuff that we already do with IPv4
>> (by leveraging IPv6), then that's fine...
> 
> no, that's not fine.   that's painting ourselves (and the Internet)
> into a corner.

I was mostly referring to not breaking what already works with v4 (i.e.,
not be a MUST for all devices in a home network to support some v6
feature for the network to work, such that our existing v4-only devices
can co-exist in whatever v6 home-network architecture we envision).

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From jmh@joelhalpern.com  Thu Jun 30 06:13:50 2011
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 D271B11E8097; Thu, 30 Jun 2011 06:13:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1k7lrCiy234; Thu, 30 Jun 2011 06:13:50 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob.out.tigertech.net [74.114.88.71]) by ietfa.amsl.com (Postfix) with ESMTP id 0CAAC21F8713; Thu, 30 Jun 2011 06:13:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id E06263228BC8; Thu, 30 Jun 2011 06:13:19 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-50-33.clppva.btas.verizon.net [71.161.50.33]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 74D763228A73; Thu, 30 Jun 2011 06:13:18 -0700 (PDT)
Message-ID: <4E0C7669.3080907@joelhalpern.com>
Date: Thu, 30 Jun 2011 09:13:13 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: [sidr] TSVDIR review of draft-ietf-karp-design-guide
References: <4E0C0FB3.8080602@isi.edu>
In-Reply-To: <4E0C0FB3.8080602@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, draft-ietf-karp-design-guide@tools.ietf.org, IETF discussion list <ietf@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 13:13:50 -0000

I am conufsed by this review of the KARP design guidelines document.
My first reaction was that I had trouble understanding the general 
points.  However, when I looked at the more detailed explaantion, what I 
see is "The threats document should ...".  But this is not a review of 
the threats document.
As a result, when the review then says "the document" I have no idea 
what document is meant.

In addition to that general comment, I am completely unable to 
understand the reviewers concern with the use of the term "on the wire". 
  I can believe that there is an issue with the way it is used, but have 
no clue how to begin to address it.

Similarly, there is an assertion that it is important for the document 
to be more clear on what layers are in and out of scope.  This is 
comment seems to be an assertion by the reviewer not grounded in the 
document.  Neither document is not a scope document.  The scope is 
defined by the charter.  Discussion of layers where it is not needed is 
a distraction.  If there are specific places where such additions would 
be helpful, that is a comment we can react to.

As a lesser issue, it is not clear that the different ways of delivering 
multiple content are actually relevant to the design guidleines 
document.  The different routing protocols have their modes of 
operations.  Ones which send distinct messages to distinct peers are 
different from ones which, as routing protocols sned single messages to 
broadcast or multicast.  As such, it is not at all clear what the 
reviewer is asking be clarified in this regard.

Yours,
Joel M. Halpern

On 6/30/2011 1:54 AM, Joe Touch wrote:
> Hi, all,
>
> I've reviewed this document as part of the transport area directorate's
> ongoing effort to review key IETF documents. These comments were written
> primarily for the transport area directors, but are copied to the
> document's authors for their information and to allow them to address
> any issues raised. The authors should consider this review together with
> any other last-call comments they receive. Please always CC
> tsv-dir@ietf.org if you reply to or forward this review.
>
> The document discusses design issues for protecting routing protocols.
>
> The most problematic issue is the term "on the wire" which is used in
> various contexts to imply physical, link, network, or transport protocol
> layers. This needs to be clarified.
>
> Transport protection appears to be a potential focus of the design
> guide, but is inconsistently discussed. In some cases, transport issues
> are raised (TCP issues for BGP); in other cases, the relevant transport
> isn't even noted (e.g., RIP over UDP). This should be corrected throughout.
>
> It is important for this document to be more clear on what layers were
> in scope for the design guide, and what guidelines are being given with
> respect to those layers, even in a general sense.
>
> Further information on these issues is provided below. There is
> additional feedback provided below ("other notes") as a suggestion.
>
> I hope this feedback will be useful to the authors, and will be glad to
> provide further assistance either on- or off-list as useful.
>
> Joe
>
> ---------------------------------------------------------------------
>
>  >> please note that some of these comments apply to the
> draft-ietf-karp-threats-reqs-03 as well; further, there is duplicate
> text that is not needed in both these docs. FWIW, the threats-reqs doc
> has many issues as well which are not addressed here.
>
> Of the four issues noted in the intro, the last uses the ambiguous term
> "on the wire". This is confusing in both this and the threats doc, and
> many times both docs us the term 'wire' or 'bits', all of which would
> typically indicate either the link layer or the physical media or both.
> There is no rationale for this focus in either document.
>
> The threats document should more clearly indicate *why* protection
> beyond the routing messages (the SIDR work) is needed, and what the
> expected threats are. These appear to be:
> - routing protocols often rely on information in the
> link, transport or network packets
> - routing protocols often rely on properties of transport
> connections to infer reachability, e.g., if a TCP connection
> cannot stay up, then the endpoint's routes should not be
> considered reachable
> (if there are other reasons, please clarify) The threats then appear to be:
> - spoofing link/network addresses
> - spoofing transport ports
> - disrupting the TCP connection (where TCP is used)
> Note that falsification (as noted in the threats doc) is not in this
> list since it is (IMO) clearly the purvue of the SIDR work. Also out of
> scope should have been any of the interference issues, unless the
> *performance* of the TCP connection needs protection.
>
> This doc then may need to protect the link or network protocol ID and/or
> transport protocol from interference. This should be more clearly stated
> in the threats doc, IMO, and the term "on the wire" should be avoided.
>
> The discussion of multicast should note that multicast can be
> implemented by broadcast, true multicast, or serial unicast; these may
> have different security requirements.
>
> The document should more clearly indicate the underlying protocol used
> as a key property of a routing protocol, especially because (as above)
> this document appears to focus on guidelines for link, network, and/or
> transport protocols. E.g., the discussion on OSPF, RIP, and ISIS should
> more clearly indicate that, e.g., RIP runs over UDP, OSPF runs over IP
> directly, and IS-IS runs natively over L2. Similar info would be useful
> for BFD, RSVP, etc.
>
> The document is unclear on its overall advice, other than a somewhat
> general description of "do good stuff". E.g., it notes:
>
> Not all routing protocol authentication mechanisms provide
> support for replay attacks, and the design teams should
> identify such authentication mechanisms and work on them so
> that this can get fixed. The design teams must look at the
> protocols that they are working on and see if packets captured
> from the previous/stale sessions can be replayed.
>
> More specific advice would be, e.g.:
>
> Not all routing protocol authentication mechanisms provide
> protection from replay attacks. Such deficiencies should
> be addressed at that layer, rather than having design
> teams conclude that such systems thus require lower layer
> (transport, network, or link) protection from replays.
>
> ----
> Other notes:
>
> Overall, this document would benefit from a revision focused on
> clarification, where the focus of each section and advice were made more
> clear.
>
> The abstract is excessively detailed and doesn't get to the point until
> "This document...". Everything preceding that should be removed, and the
> result should be appended with a few sentences summarizing the
> recommendations.
>
> The intro refers in a lot of detail to the motivation for the doc (some
> of which may be historically important but is not relevant to the doc
> itself), but only briefly notes the KARP threats document. This
> document's observations should be motivated by addressing those threats,
> so it would be important to summarize them in this doc in the intro as
> context.
>
> The summary of RFC 4984 discusses four tightening steps as if they were
> indicated by that RFC; that RFC only suggests tightening itself. This
> doc should more clearly indicate that "The WG identified four...".
>
> -----
>
>
>
>
>
>
>
>
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>

From touch@isi.edu  Thu Jun 30 06:53:49 2011
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 3141321F85C1; Thu, 30 Jun 2011 06:53:48 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BjZxriZjSnEX; Thu, 30 Jun 2011 06:53:47 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id DEA4921F85AE; Thu, 30 Jun 2011 06:53:44 -0700 (PDT)
Received: from [172.16.0.187] (216.156.178.2.ptr.us.xo.net [216.156.178.2]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p5UDqfj1023899 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 30 Jun 2011 06:52:50 -0700 (PDT)
Message-ID: <4E0C7FA7.6090701@isi.edu>
Date: Thu, 30 Jun 2011 06:52:39 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [sidr] TSVDIR review of draft-ietf-karp-design-guide
References: <4E0C0FB3.8080602@isi.edu> <4E0C7669.3080907@joelhalpern.com>
In-Reply-To: <4E0C7669.3080907@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: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, draft-ietf-karp-design-guide@tools.ietf.org, IETF discussion list <ietf@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 13:53:49 -0000

Hi Joel,

On 6/30/2011 6:13 AM, Joel M. Halpern wrote:
> I am conufsed by this review of the KARP design guidelines document.
> My first reaction was that I had trouble understanding the general
> points. However, when I looked at the more detailed explaantion, what I
> see is "The threats document should ...". But this is not a review of
> the threats document.
> As a result, when the review then says "the document" I have no idea
> what document is meant.

 From the design guide section 1:

       Readers must refer to the [I-D.ietf-karp-threats-reqs] for a
       clear definition of the scope, goals, non goals and the
       audience for the design work being undertaken in KARP WG.

I did so, and found issues there that caused problems here, which is why 
those issues are included.

> In addition to that general comment, I am completely unable to
> understand the reviewers concern with the use of the term "on the wire".
> I can believe that there is an issue with the way it is used, but have
> no clue how to begin to address it.

There are more than a few who frequently refer to a protocol's "packets 
on the wire". This is ambiguous and can mean:

	- app messages (here, routing PDUs)
	- transport messages (e.g., TCP segments)
	- network messages (e.g., IP packets)
	- link messages (e.g., ethernet segments)
	- the physical media (e.g., WIFI)

Protecting each of these results in different kinds of defense. The 
document needs to avoid the use of this term as if it were well-defined 
in the IETF literature and unambiguous within the IETF community.

> Similarly, there is an assertion that it is important for the document
> to be more clear on what layers are in and out of scope. This is comment
> seems to be an assertion by the reviewer not grounded in the document.
> Neither document is not a scope document. The scope is defined by the
> charter.

Neither document should expect that readers are familiar with the 
charter; relevant context should be summarized in the intro (and is not, 
currently).

The KARP charter says:
---
The KARP working group is tasked to work with the routing protocol
working groups in order to improve the communication security of the
packets on the wire used by the routing protocols. This working group is
concerned with message authentication, packet integrity, and denial of
service (DoS) protection. At present, this charter explicitly excludes
confidentiality and non-repudiation concerns.
...
Routing protocols use a range of transport mechanisms and communication
relationships. There are also differences in details among the various
protocols. The working group will attempt to describe the security
relevant characteristics of routings protocols, such as the use or
non-use of TCP, or the frequent use of group communication versus purely
pairwise communication. Using these characteristics, the working group
will then provide suitable common frameworks that can be applied, and
tailored, to improve the communication security of the routing
protocols. In later phases, it is expected that the working group will
investigate the suitably of defining conceptual structures and APIs, so
as to enable further work to be more effective.
---

Again, I note that "on the wire" is not clear, nor the term "packet". 
The term "transport mechanisms" is overloaded, but in the IETF tends to 
refer to layer 4; that's not appropriate here, as some important routing 
protocols are directly layered over L2 or L3.

> Discussion of layers where it is not needed is a distraction.

A design guide to secure routing protocol message exchanges needs to 
clearly identify, by example, the expected kinds of protection needed 
for the message exchange. This breaks down to two parts:

	A- securing the message content
	B- securing any information provided by the way in
	which the messages are exchanged
		1- securing explicit info (e.g., IDs,
		if relied upon by the routing protocol)
		2- securing implicit info (e.g., connection
		status, message ordering or success, etc.,
		as used by the routing protocol)

AFAICT, KARP is focused on (B) which is necessarily in the context of 
L2, L3, and/or L4 {where SIDR addresses (A)}. That's fine, but a 
*design* guide should be more clear about what B means, and what kinds 
of things to look out for or address.

> If there are specific places where such additions would be helpful, that
> is a comment we can react to.

I refer you again to the intro, which states:

...   Section 8.2 calls for "[t]ightening the
       security of the core routing infrastructure."  Four main steps
       were identified for that tightening:

       o  More secure mechanisms and practices for operating routers.
          This work is being addressed in the OPSEC Working Group.

       o  Cleaning up the Internet Routing Registry repository [IRR],
          and securing both the database and the access, so that it
          can be used for routing verifications.  This work should be
          addressed through liaisons with those running the IRR's
          globally.

       o  Specifications for cryptographic validation of routing
       message content.  This work will likely be addressed in the
       SIDR Working Group.

       o  Securing the routing protocols' packets on the wire

       This document addresses the last bullet, securing the packets
       on the wire of the routing protocol exchanges.

The third bullet describes securing routing protocol messages as out of 
scope. The last sentence describes "on the wire" as in scope, again as 
if this were a clear indication of what needs to be protected.

> As a lesser issue, it is not clear that the different ways of delivering
> multiple content are actually relevant to the design guidleines
> document.

Can you please then explain what "on the wire" means if not "differnt 
ways of delivering multiple content"? Isn't that exactly the scope?

 > The different routing protocols have their modes of
> operations. Ones which send distinct messages to distinct peers are
> different from ones which, as routing protocols sned single messages to
> broadcast or multicast. As such, it is not at all clear what the
> reviewer is asking be clarified in this regard.

The difference between unicast and multicast is important, but so is the 
difference between whether a protocol relies on a connection being up, 
or message delivery being ordered. Again, specifically:

	B- securing any information provided by the way in
	which the messages are exchanged
		1- securing explicit info (e.g., IDs,
		if relied upon by the routing protocol)
		2- securing implicit info (e.g., connection
		status, message ordering or success, etc.,
		as used by the routing protocol)

IMO, neither B1 nor B2 is sufficiently addressed in this doc, and 
neither can be addressed in the absence of a clear discussion of the 
different properties of L2, L3, and/or L4 as they impact routing 
protocols over which they operate.

Joe

> Yours,
> Joel M. Halpern
>
> On 6/30/2011 1:54 AM, Joe Touch wrote:
>> Hi, all,
>>
>> I've reviewed this document as part of the transport area directorate's
>> ongoing effort to review key IETF documents. These comments were written
>> primarily for the transport area directors, but are copied to the
>> document's authors for their information and to allow them to address
>> any issues raised. The authors should consider this review together with
>> any other last-call comments they receive. Please always CC
>> tsv-dir@ietf.org if you reply to or forward this review.
>>
>> The document discusses design issues for protecting routing protocols.
>>
>> The most problematic issue is the term "on the wire" which is used in
>> various contexts to imply physical, link, network, or transport protocol
>> layers. This needs to be clarified.
>>
>> Transport protection appears to be a potential focus of the design
>> guide, but is inconsistently discussed. In some cases, transport issues
>> are raised (TCP issues for BGP); in other cases, the relevant transport
>> isn't even noted (e.g., RIP over UDP). This should be corrected
>> throughout.
>>
>> It is important for this document to be more clear on what layers were
>> in scope for the design guide, and what guidelines are being given with
>> respect to those layers, even in a general sense.
>>
>> Further information on these issues is provided below. There is
>> additional feedback provided below ("other notes") as a suggestion.
>>
>> I hope this feedback will be useful to the authors, and will be glad to
>> provide further assistance either on- or off-list as useful.
>>
>> Joe
>>
>> ---------------------------------------------------------------------
>>
>> >> please note that some of these comments apply to the
>> draft-ietf-karp-threats-reqs-03 as well; further, there is duplicate
>> text that is not needed in both these docs. FWIW, the threats-reqs doc
>> has many issues as well which are not addressed here.
>>
>> Of the four issues noted in the intro, the last uses the ambiguous term
>> "on the wire". This is confusing in both this and the threats doc, and
>> many times both docs us the term 'wire' or 'bits', all of which would
>> typically indicate either the link layer or the physical media or both.
>> There is no rationale for this focus in either document.
>>
>> The threats document should more clearly indicate *why* protection
>> beyond the routing messages (the SIDR work) is needed, and what the
>> expected threats are. These appear to be:
>> - routing protocols often rely on information in the
>> link, transport or network packets
>> - routing protocols often rely on properties of transport
>> connections to infer reachability, e.g., if a TCP connection
>> cannot stay up, then the endpoint's routes should not be
>> considered reachable
>> (if there are other reasons, please clarify) The threats then appear
>> to be:
>> - spoofing link/network addresses
>> - spoofing transport ports
>> - disrupting the TCP connection (where TCP is used)
>> Note that falsification (as noted in the threats doc) is not in this
>> list since it is (IMO) clearly the purvue of the SIDR work. Also out of
>> scope should have been any of the interference issues, unless the
>> *performance* of the TCP connection needs protection.
>>
>> This doc then may need to protect the link or network protocol ID and/or
>> transport protocol from interference. This should be more clearly stated
>> in the threats doc, IMO, and the term "on the wire" should be avoided.
>>
>> The discussion of multicast should note that multicast can be
>> implemented by broadcast, true multicast, or serial unicast; these may
>> have different security requirements.
>>
>> The document should more clearly indicate the underlying protocol used
>> as a key property of a routing protocol, especially because (as above)
>> this document appears to focus on guidelines for link, network, and/or
>> transport protocols. E.g., the discussion on OSPF, RIP, and ISIS should
>> more clearly indicate that, e.g., RIP runs over UDP, OSPF runs over IP
>> directly, and IS-IS runs natively over L2. Similar info would be useful
>> for BFD, RSVP, etc.
>>
>> The document is unclear on its overall advice, other than a somewhat
>> general description of "do good stuff". E.g., it notes:
>>
>> Not all routing protocol authentication mechanisms provide
>> support for replay attacks, and the design teams should
>> identify such authentication mechanisms and work on them so
>> that this can get fixed. The design teams must look at the
>> protocols that they are working on and see if packets captured
>> from the previous/stale sessions can be replayed.
>>
>> More specific advice would be, e.g.:
>>
>> Not all routing protocol authentication mechanisms provide
>> protection from replay attacks. Such deficiencies should
>> be addressed at that layer, rather than having design
>> teams conclude that such systems thus require lower layer
>> (transport, network, or link) protection from replays.
>>
>> ----
>> Other notes:
>>
>> Overall, this document would benefit from a revision focused on
>> clarification, where the focus of each section and advice were made more
>> clear.
>>
>> The abstract is excessively detailed and doesn't get to the point until
>> "This document...". Everything preceding that should be removed, and the
>> result should be appended with a few sentences summarizing the
>> recommendations.
>>
>> The intro refers in a lot of detail to the motivation for the doc (some
>> of which may be historically important but is not relevant to the doc
>> itself), but only briefly notes the KARP threats document. This
>> document's observations should be motivated by addressing those threats,
>> so it would be important to summarize them in this doc in the intro as
>> context.
>>
>> The summary of RFC 4984 discusses four tightening steps as if they were
>> indicated by that RFC; that RFC only suggests tightening itself. This
>> doc should more clearly indicate that "The WG identified four...".
>>
>> -----
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> sidr mailing list
>> sidr@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidr
>>

From jnc@mercury.lcs.mit.edu  Thu Jun 30 07:05:07 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9368521F8666 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 07:05: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HdAVJv7fmrHc for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 07:05:07 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB1521F8664 for <ietf@ietf.org>; Thu, 30 Jun 2011 07:05:06 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id EF41A18C16D; Thu, 30 Jun 2011 10:05:05 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: HOMENET working group proposal
Message-Id: <20110630140505.EF41A18C16D@mercury.lcs.mit.edu>
Date: Thu, 30 Jun 2011 10:05:05 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 14:05:07 -0000

    > From: Melinda Shore <melinda.shore@gmail.com>

    > The focus really needs to be on producing good, secure protocols 

The majority of intrusions now seem to be exploiting bugs (and in some cases
bad configurations) in the end-hosts; protocol security flaws are rarely the
problem. This makes sense, as there's a lot more code in the applications
(i.e. places for bugs which can be exploited) than there is in the protocol
itself.

Firewalls do help, and so it's worth spending some time on doing a good job
to make them effective while yet being flexible. But let's not kid ourselves
that anything we can do will totally solve the problem.

	Noel

From jmh@joelhalpern.com  Thu Jun 30 07:15:32 2011
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 7E18611E8116; Thu, 30 Jun 2011 07:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d8V01vzYOs8U; Thu, 30 Jun 2011 07:15:31 -0700 (PDT)
Received: from hgblob.out.tigertech.net (hgblob.out.tigertech.net [74.114.88.71]) by ietfa.amsl.com (Postfix) with ESMTP id 0C01321F8684; Thu, 30 Jun 2011 07:15:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id DF739325B2B1; Thu, 30 Jun 2011 07:14:58 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-50-33.clppva.btas.verizon.net [71.161.50.33]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 207733228BC8; Thu, 30 Jun 2011 07:14:57 -0700 (PDT)
Message-ID: <4E0C84DC.7020401@joelhalpern.com>
Date: Thu, 30 Jun 2011 10:14:52 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: [sidr] TSVDIR review of draft-ietf-karp-design-guide
References: <4E0C0FB3.8080602@isi.edu> <4E0C7669.3080907@joelhalpern.com> <4E0C7FA7.6090701@isi.edu>
In-Reply-To: <4E0C7FA7.6090701@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, draft-ietf-karp-design-guide@tools.ietf.org, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 14:15:32 -0000

How much of this would change if the abstract began with:
This document captures the design guidance that the KARP working group 
is using at the time of publication for guiding the chartered security 
analysis and proposal work that it is doing.

And we put that in the front of the intro as well.
(The abstract needs to be replaced with an actual abstract.  I had 
thought that could be resolved in parallel with the IETF last call.)

Would that help, or would you have the same concerns?

Yours,
Joel

On 6/30/2011 9:52 AM, Joe Touch wrote:
> Hi Joel,
>
> On 6/30/2011 6:13 AM, Joel M. Halpern wrote:
>> I am conufsed by this review of the KARP design guidelines document.
>> My first reaction was that I had trouble understanding the general
>> points. However, when I looked at the more detailed explaantion, what I
>> see is "The threats document should ...". But this is not a review of
>> the threats document.
>> As a result, when the review then says "the document" I have no idea
>> what document is meant.
>
>  From the design guide section 1:
>
> Readers must refer to the [I-D.ietf-karp-threats-reqs] for a
> clear definition of the scope, goals, non goals and the
> audience for the design work being undertaken in KARP WG.
>
> I did so, and found issues there that caused problems here, which is why
> those issues are included.
>
>> In addition to that general comment, I am completely unable to
>> understand the reviewers concern with the use of the term "on the wire".
>> I can believe that there is an issue with the way it is used, but have
>> no clue how to begin to address it.
>
> There are more than a few who frequently refer to a protocol's "packets
> on the wire". This is ambiguous and can mean:
>
> - app messages (here, routing PDUs)
> - transport messages (e.g., TCP segments)
> - network messages (e.g., IP packets)
> - link messages (e.g., ethernet segments)
> - the physical media (e.g., WIFI)
>
> Protecting each of these results in different kinds of defense. The
> document needs to avoid the use of this term as if it were well-defined
> in the IETF literature and unambiguous within the IETF community.
>
>> Similarly, there is an assertion that it is important for the document
>> to be more clear on what layers are in and out of scope. This is comment
>> seems to be an assertion by the reviewer not grounded in the document.
>> Neither document is not a scope document. The scope is defined by the
>> charter.
>
> Neither document should expect that readers are familiar with the
> charter; relevant context should be summarized in the intro (and is not,
> currently).
>
> The KARP charter says:
> ---
> The KARP working group is tasked to work with the routing protocol
> working groups in order to improve the communication security of the
> packets on the wire used by the routing protocols. This working group is
> concerned with message authentication, packet integrity, and denial of
> service (DoS) protection. At present, this charter explicitly excludes
> confidentiality and non-repudiation concerns.
> ...
> Routing protocols use a range of transport mechanisms and communication
> relationships. There are also differences in details among the various
> protocols. The working group will attempt to describe the security
> relevant characteristics of routings protocols, such as the use or
> non-use of TCP, or the frequent use of group communication versus purely
> pairwise communication. Using these characteristics, the working group
> will then provide suitable common frameworks that can be applied, and
> tailored, to improve the communication security of the routing
> protocols. In later phases, it is expected that the working group will
> investigate the suitably of defining conceptual structures and APIs, so
> as to enable further work to be more effective.
> ---
>
> Again, I note that "on the wire" is not clear, nor the term "packet".
> The term "transport mechanisms" is overloaded, but in the IETF tends to
> refer to layer 4; that's not appropriate here, as some important routing
> protocols are directly layered over L2 or L3.
>
>> Discussion of layers where it is not needed is a distraction.
>
> A design guide to secure routing protocol message exchanges needs to
> clearly identify, by example, the expected kinds of protection needed
> for the message exchange. This breaks down to two parts:
>
> A- securing the message content
> B- securing any information provided by the way in
> which the messages are exchanged
> 1- securing explicit info (e.g., IDs,
> if relied upon by the routing protocol)
> 2- securing implicit info (e.g., connection
> status, message ordering or success, etc.,
> as used by the routing protocol)
>
> AFAICT, KARP is focused on (B) which is necessarily in the context of
> L2, L3, and/or L4 {where SIDR addresses (A)}. That's fine, but a
> *design* guide should be more clear about what B means, and what kinds
> of things to look out for or address.
>
>> If there are specific places where such additions would be helpful, that
>> is a comment we can react to.
>
> I refer you again to the intro, which states:
>
> ... Section 8.2 calls for "[t]ightening the
> security of the core routing infrastructure." Four main steps
> were identified for that tightening:
>
> o More secure mechanisms and practices for operating routers.
> This work is being addressed in the OPSEC Working Group.
>
> o Cleaning up the Internet Routing Registry repository [IRR],
> and securing both the database and the access, so that it
> can be used for routing verifications. This work should be
> addressed through liaisons with those running the IRR's
> globally.
>
> o Specifications for cryptographic validation of routing
> message content. This work will likely be addressed in the
> SIDR Working Group.
>
> o Securing the routing protocols' packets on the wire
>
> This document addresses the last bullet, securing the packets
> on the wire of the routing protocol exchanges.
>
> The third bullet describes securing routing protocol messages as out of
> scope. The last sentence describes "on the wire" as in scope, again as
> if this were a clear indication of what needs to be protected.
>
>> As a lesser issue, it is not clear that the different ways of delivering
>> multiple content are actually relevant to the design guidleines
>> document.
>
> Can you please then explain what "on the wire" means if not "differnt
> ways of delivering multiple content"? Isn't that exactly the scope?
>
>  > The different routing protocols have their modes of
>> operations. Ones which send distinct messages to distinct peers are
>> different from ones which, as routing protocols sned single messages to
>> broadcast or multicast. As such, it is not at all clear what the
>> reviewer is asking be clarified in this regard.
>
> The difference between unicast and multicast is important, but so is the
> difference between whether a protocol relies on a connection being up,
> or message delivery being ordered. Again, specifically:
>
> B- securing any information provided by the way in
> which the messages are exchanged
> 1- securing explicit info (e.g., IDs,
> if relied upon by the routing protocol)
> 2- securing implicit info (e.g., connection
> status, message ordering or success, etc.,
> as used by the routing protocol)
>
> IMO, neither B1 nor B2 is sufficiently addressed in this doc, and
> neither can be addressed in the absence of a clear discussion of the
> different properties of L2, L3, and/or L4 as they impact routing
> protocols over which they operate.
>
> Joe
>
>> Yours,
>> Joel M. Halpern
>>
>> On 6/30/2011 1:54 AM, Joe Touch wrote:
>>> Hi, all,
>>>
>>> I've reviewed this document as part of the transport area directorate's
>>> ongoing effort to review key IETF documents. These comments were written
>>> primarily for the transport area directors, but are copied to the
>>> document's authors for their information and to allow them to address
>>> any issues raised. The authors should consider this review together with
>>> any other last-call comments they receive. Please always CC
>>> tsv-dir@ietf.org if you reply to or forward this review.
>>>
>>> The document discusses design issues for protecting routing protocols.
>>>
>>> The most problematic issue is the term "on the wire" which is used in
>>> various contexts to imply physical, link, network, or transport protocol
>>> layers. This needs to be clarified.
>>>
>>> Transport protection appears to be a potential focus of the design
>>> guide, but is inconsistently discussed. In some cases, transport issues
>>> are raised (TCP issues for BGP); in other cases, the relevant transport
>>> isn't even noted (e.g., RIP over UDP). This should be corrected
>>> throughout.
>>>
>>> It is important for this document to be more clear on what layers were
>>> in scope for the design guide, and what guidelines are being given with
>>> respect to those layers, even in a general sense.
>>>
>>> Further information on these issues is provided below. There is
>>> additional feedback provided below ("other notes") as a suggestion.
>>>
>>> I hope this feedback will be useful to the authors, and will be glad to
>>> provide further assistance either on- or off-list as useful.
>>>
>>> Joe
>>>
>>> ---------------------------------------------------------------------
>>>
>>> >> please note that some of these comments apply to the
>>> draft-ietf-karp-threats-reqs-03 as well; further, there is duplicate
>>> text that is not needed in both these docs. FWIW, the threats-reqs doc
>>> has many issues as well which are not addressed here.
>>>
>>> Of the four issues noted in the intro, the last uses the ambiguous term
>>> "on the wire". This is confusing in both this and the threats doc, and
>>> many times both docs us the term 'wire' or 'bits', all of which would
>>> typically indicate either the link layer or the physical media or both.
>>> There is no rationale for this focus in either document.
>>>
>>> The threats document should more clearly indicate *why* protection
>>> beyond the routing messages (the SIDR work) is needed, and what the
>>> expected threats are. These appear to be:
>>> - routing protocols often rely on information in the
>>> link, transport or network packets
>>> - routing protocols often rely on properties of transport
>>> connections to infer reachability, e.g., if a TCP connection
>>> cannot stay up, then the endpoint's routes should not be
>>> considered reachable
>>> (if there are other reasons, please clarify) The threats then appear
>>> to be:
>>> - spoofing link/network addresses
>>> - spoofing transport ports
>>> - disrupting the TCP connection (where TCP is used)
>>> Note that falsification (as noted in the threats doc) is not in this
>>> list since it is (IMO) clearly the purvue of the SIDR work. Also out of
>>> scope should have been any of the interference issues, unless the
>>> *performance* of the TCP connection needs protection.
>>>
>>> This doc then may need to protect the link or network protocol ID and/or
>>> transport protocol from interference. This should be more clearly stated
>>> in the threats doc, IMO, and the term "on the wire" should be avoided.
>>>
>>> The discussion of multicast should note that multicast can be
>>> implemented by broadcast, true multicast, or serial unicast; these may
>>> have different security requirements.
>>>
>>> The document should more clearly indicate the underlying protocol used
>>> as a key property of a routing protocol, especially because (as above)
>>> this document appears to focus on guidelines for link, network, and/or
>>> transport protocols. E.g., the discussion on OSPF, RIP, and ISIS should
>>> more clearly indicate that, e.g., RIP runs over UDP, OSPF runs over IP
>>> directly, and IS-IS runs natively over L2. Similar info would be useful
>>> for BFD, RSVP, etc.
>>>
>>> The document is unclear on its overall advice, other than a somewhat
>>> general description of "do good stuff". E.g., it notes:
>>>
>>> Not all routing protocol authentication mechanisms provide
>>> support for replay attacks, and the design teams should
>>> identify such authentication mechanisms and work on them so
>>> that this can get fixed. The design teams must look at the
>>> protocols that they are working on and see if packets captured
>>> from the previous/stale sessions can be replayed.
>>>
>>> More specific advice would be, e.g.:
>>>
>>> Not all routing protocol authentication mechanisms provide
>>> protection from replay attacks. Such deficiencies should
>>> be addressed at that layer, rather than having design
>>> teams conclude that such systems thus require lower layer
>>> (transport, network, or link) protection from replays.
>>>
>>> ----
>>> Other notes:
>>>
>>> Overall, this document would benefit from a revision focused on
>>> clarification, where the focus of each section and advice were made more
>>> clear.
>>>
>>> The abstract is excessively detailed and doesn't get to the point until
>>> "This document...". Everything preceding that should be removed, and the
>>> result should be appended with a few sentences summarizing the
>>> recommendations.
>>>
>>> The intro refers in a lot of detail to the motivation for the doc (some
>>> of which may be historically important but is not relevant to the doc
>>> itself), but only briefly notes the KARP threats document. This
>>> document's observations should be motivated by addressing those threats,
>>> so it would be important to summarize them in this doc in the intro as
>>> context.
>>>
>>> The summary of RFC 4984 discusses four tightening steps as if they were
>>> indicated by that RFC; that RFC only suggests tightening itself. This
>>> doc should more clearly indicate that "The WG identified four...".
>>>
>>> -----
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> sidr mailing list
>>> sidr@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sidr
>>>
>

From touch@isi.edu  Thu Jun 30 07:19:50 2011
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 0CE8A11E8116; Thu, 30 Jun 2011 07:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 39zQUmt3eHOn; Thu, 30 Jun 2011 07:19:48 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id CED0511E8083; Thu, 30 Jun 2011 07:19:48 -0700 (PDT)
Received: from [172.16.0.187] (216.156.178.2.ptr.us.xo.net [216.156.178.2]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id p5UEJTnX024096 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 30 Jun 2011 07:19:32 -0700 (PDT)
Message-ID: <4E0C85EF.9050909@isi.edu>
Date: Thu, 30 Jun 2011 07:19:27 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [sidr] TSVDIR review of draft-ietf-karp-design-guide
References: <4E0C0FB3.8080602@isi.edu> <4E0C7669.3080907@joelhalpern.com> <4E0C7FA7.6090701@isi.edu> <4E0C84DC.7020401@joelhalpern.com>
In-Reply-To: <4E0C84DC.7020401@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: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, draft-ietf-karp-design-guide@tools.ietf.org, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 14:19:50 -0000

Hi, Joel,

On 6/30/2011 7:14 AM, Joel M. Halpern wrote:
> How much of this would change if the abstract began with:
> This document captures the design guidance that the KARP working group
> is using at the time of publication for guiding the chartered security
> analysis and proposal work that it is doing.
>
> And we put that in the front of the intro as well.
> (The abstract needs to be replaced with an actual abstract. I had
> thought that could be resolved in parallel with the IETF last call.)
>
> Would that help, or would you have the same concerns?

Regarding the context of what the WG focus and scope is, merely 
referring to the WG isn't sufficient. The relevant points of scope need 
to be included or explained.

However, this doesn't need to refer to the WG at all. The history of the 
doc is not relevant on that point, except perhaps in the Acks. For the 
intro and abstract, a clear statement of scope is needed.

Joe

> On 6/30/2011 9:52 AM, Joe Touch wrote:
>> Hi Joel,
>>
>> On 6/30/2011 6:13 AM, Joel M. Halpern wrote:
>>> I am conufsed by this review of the KARP design guidelines document.
>>> My first reaction was that I had trouble understanding the general
>>> points. However, when I looked at the more detailed explaantion, what I
>>> see is "The threats document should ...". But this is not a review of
>>> the threats document.
>>> As a result, when the review then says "the document" I have no idea
>>> what document is meant.
>>
>> From the design guide section 1:
>>
>> Readers must refer to the [I-D.ietf-karp-threats-reqs] for a
>> clear definition of the scope, goals, non goals and the
>> audience for the design work being undertaken in KARP WG.
>>
>> I did so, and found issues there that caused problems here, which is why
>> those issues are included.
>>
>>> In addition to that general comment, I am completely unable to
>>> understand the reviewers concern with the use of the term "on the wire".
>>> I can believe that there is an issue with the way it is used, but have
>>> no clue how to begin to address it.
>>
>> There are more than a few who frequently refer to a protocol's "packets
>> on the wire". This is ambiguous and can mean:
>>
>> - app messages (here, routing PDUs)
>> - transport messages (e.g., TCP segments)
>> - network messages (e.g., IP packets)
>> - link messages (e.g., ethernet segments)
>> - the physical media (e.g., WIFI)
>>
>> Protecting each of these results in different kinds of defense. The
>> document needs to avoid the use of this term as if it were well-defined
>> in the IETF literature and unambiguous within the IETF community.
>>
>>> Similarly, there is an assertion that it is important for the document
>>> to be more clear on what layers are in and out of scope. This is comment
>>> seems to be an assertion by the reviewer not grounded in the document.
>>> Neither document is not a scope document. The scope is defined by the
>>> charter.
>>
>> Neither document should expect that readers are familiar with the
>> charter; relevant context should be summarized in the intro (and is not,
>> currently).
>>
>> The KARP charter says:
>> ---
>> The KARP working group is tasked to work with the routing protocol
>> working groups in order to improve the communication security of the
>> packets on the wire used by the routing protocols. This working group is
>> concerned with message authentication, packet integrity, and denial of
>> service (DoS) protection. At present, this charter explicitly excludes
>> confidentiality and non-repudiation concerns.
>> ...
>> Routing protocols use a range of transport mechanisms and communication
>> relationships. There are also differences in details among the various
>> protocols. The working group will attempt to describe the security
>> relevant characteristics of routings protocols, such as the use or
>> non-use of TCP, or the frequent use of group communication versus purely
>> pairwise communication. Using these characteristics, the working group
>> will then provide suitable common frameworks that can be applied, and
>> tailored, to improve the communication security of the routing
>> protocols. In later phases, it is expected that the working group will
>> investigate the suitably of defining conceptual structures and APIs, so
>> as to enable further work to be more effective.
>> ---
>>
>> Again, I note that "on the wire" is not clear, nor the term "packet".
>> The term "transport mechanisms" is overloaded, but in the IETF tends to
>> refer to layer 4; that's not appropriate here, as some important routing
>> protocols are directly layered over L2 or L3.
>>
>>> Discussion of layers where it is not needed is a distraction.
>>
>> A design guide to secure routing protocol message exchanges needs to
>> clearly identify, by example, the expected kinds of protection needed
>> for the message exchange. This breaks down to two parts:
>>
>> A- securing the message content
>> B- securing any information provided by the way in
>> which the messages are exchanged
>> 1- securing explicit info (e.g., IDs,
>> if relied upon by the routing protocol)
>> 2- securing implicit info (e.g., connection
>> status, message ordering or success, etc.,
>> as used by the routing protocol)
>>
>> AFAICT, KARP is focused on (B) which is necessarily in the context of
>> L2, L3, and/or L4 {where SIDR addresses (A)}. That's fine, but a
>> *design* guide should be more clear about what B means, and what kinds
>> of things to look out for or address.
>>
>>> If there are specific places where such additions would be helpful, that
>>> is a comment we can react to.
>>
>> I refer you again to the intro, which states:
>>
>> ... Section 8.2 calls for "[t]ightening the
>> security of the core routing infrastructure." Four main steps
>> were identified for that tightening:
>>
>> o More secure mechanisms and practices for operating routers.
>> This work is being addressed in the OPSEC Working Group.
>>
>> o Cleaning up the Internet Routing Registry repository [IRR],
>> and securing both the database and the access, so that it
>> can be used for routing verifications. This work should be
>> addressed through liaisons with those running the IRR's
>> globally.
>>
>> o Specifications for cryptographic validation of routing
>> message content. This work will likely be addressed in the
>> SIDR Working Group.
>>
>> o Securing the routing protocols' packets on the wire
>>
>> This document addresses the last bullet, securing the packets
>> on the wire of the routing protocol exchanges.
>>
>> The third bullet describes securing routing protocol messages as out of
>> scope. The last sentence describes "on the wire" as in scope, again as
>> if this were a clear indication of what needs to be protected.
>>
>>> As a lesser issue, it is not clear that the different ways of delivering
>>> multiple content are actually relevant to the design guidleines
>>> document.
>>
>> Can you please then explain what "on the wire" means if not "differnt
>> ways of delivering multiple content"? Isn't that exactly the scope?
>>
>> > The different routing protocols have their modes of
>>> operations. Ones which send distinct messages to distinct peers are
>>> different from ones which, as routing protocols sned single messages to
>>> broadcast or multicast. As such, it is not at all clear what the
>>> reviewer is asking be clarified in this regard.
>>
>> The difference between unicast and multicast is important, but so is the
>> difference between whether a protocol relies on a connection being up,
>> or message delivery being ordered. Again, specifically:
>>
>> B- securing any information provided by the way in
>> which the messages are exchanged
>> 1- securing explicit info (e.g., IDs,
>> if relied upon by the routing protocol)
>> 2- securing implicit info (e.g., connection
>> status, message ordering or success, etc.,
>> as used by the routing protocol)
>>
>> IMO, neither B1 nor B2 is sufficiently addressed in this doc, and
>> neither can be addressed in the absence of a clear discussion of the
>> different properties of L2, L3, and/or L4 as they impact routing
>> protocols over which they operate.
>>
>> Joe
>>
>>> Yours,
>>> Joel M. Halpern
>>>
>>> On 6/30/2011 1:54 AM, Joe Touch wrote:
>>>> Hi, all,
>>>>
>>>> I've reviewed this document as part of the transport area directorate's
>>>> ongoing effort to review key IETF documents. These comments were
>>>> written
>>>> primarily for the transport area directors, but are copied to the
>>>> document's authors for their information and to allow them to address
>>>> any issues raised. The authors should consider this review together
>>>> with
>>>> any other last-call comments they receive. Please always CC
>>>> tsv-dir@ietf.org if you reply to or forward this review.
>>>>
>>>> The document discusses design issues for protecting routing protocols.
>>>>
>>>> The most problematic issue is the term "on the wire" which is used in
>>>> various contexts to imply physical, link, network, or transport
>>>> protocol
>>>> layers. This needs to be clarified.
>>>>
>>>> Transport protection appears to be a potential focus of the design
>>>> guide, but is inconsistently discussed. In some cases, transport issues
>>>> are raised (TCP issues for BGP); in other cases, the relevant transport
>>>> isn't even noted (e.g., RIP over UDP). This should be corrected
>>>> throughout.
>>>>
>>>> It is important for this document to be more clear on what layers were
>>>> in scope for the design guide, and what guidelines are being given with
>>>> respect to those layers, even in a general sense.
>>>>
>>>> Further information on these issues is provided below. There is
>>>> additional feedback provided below ("other notes") as a suggestion.
>>>>
>>>> I hope this feedback will be useful to the authors, and will be glad to
>>>> provide further assistance either on- or off-list as useful.
>>>>
>>>> Joe
>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>> >> please note that some of these comments apply to the
>>>> draft-ietf-karp-threats-reqs-03 as well; further, there is duplicate
>>>> text that is not needed in both these docs. FWIW, the threats-reqs doc
>>>> has many issues as well which are not addressed here.
>>>>
>>>> Of the four issues noted in the intro, the last uses the ambiguous term
>>>> "on the wire". This is confusing in both this and the threats doc, and
>>>> many times both docs us the term 'wire' or 'bits', all of which would
>>>> typically indicate either the link layer or the physical media or both.
>>>> There is no rationale for this focus in either document.
>>>>
>>>> The threats document should more clearly indicate *why* protection
>>>> beyond the routing messages (the SIDR work) is needed, and what the
>>>> expected threats are. These appear to be:
>>>> - routing protocols often rely on information in the
>>>> link, transport or network packets
>>>> - routing protocols often rely on properties of transport
>>>> connections to infer reachability, e.g., if a TCP connection
>>>> cannot stay up, then the endpoint's routes should not be
>>>> considered reachable
>>>> (if there are other reasons, please clarify) The threats then appear
>>>> to be:
>>>> - spoofing link/network addresses
>>>> - spoofing transport ports
>>>> - disrupting the TCP connection (where TCP is used)
>>>> Note that falsification (as noted in the threats doc) is not in this
>>>> list since it is (IMO) clearly the purvue of the SIDR work. Also out of
>>>> scope should have been any of the interference issues, unless the
>>>> *performance* of the TCP connection needs protection.
>>>>
>>>> This doc then may need to protect the link or network protocol ID
>>>> and/or
>>>> transport protocol from interference. This should be more clearly
>>>> stated
>>>> in the threats doc, IMO, and the term "on the wire" should be avoided.
>>>>
>>>> The discussion of multicast should note that multicast can be
>>>> implemented by broadcast, true multicast, or serial unicast; these may
>>>> have different security requirements.
>>>>
>>>> The document should more clearly indicate the underlying protocol used
>>>> as a key property of a routing protocol, especially because (as above)
>>>> this document appears to focus on guidelines for link, network, and/or
>>>> transport protocols. E.g., the discussion on OSPF, RIP, and ISIS should
>>>> more clearly indicate that, e.g., RIP runs over UDP, OSPF runs over IP
>>>> directly, and IS-IS runs natively over L2. Similar info would be useful
>>>> for BFD, RSVP, etc.
>>>>
>>>> The document is unclear on its overall advice, other than a somewhat
>>>> general description of "do good stuff". E.g., it notes:
>>>>
>>>> Not all routing protocol authentication mechanisms provide
>>>> support for replay attacks, and the design teams should
>>>> identify such authentication mechanisms and work on them so
>>>> that this can get fixed. The design teams must look at the
>>>> protocols that they are working on and see if packets captured
>>>> from the previous/stale sessions can be replayed.
>>>>
>>>> More specific advice would be, e.g.:
>>>>
>>>> Not all routing protocol authentication mechanisms provide
>>>> protection from replay attacks. Such deficiencies should
>>>> be addressed at that layer, rather than having design
>>>> teams conclude that such systems thus require lower layer
>>>> (transport, network, or link) protection from replays.
>>>>
>>>> ----
>>>> Other notes:
>>>>
>>>> Overall, this document would benefit from a revision focused on
>>>> clarification, where the focus of each section and advice were made
>>>> more
>>>> clear.
>>>>
>>>> The abstract is excessively detailed and doesn't get to the point until
>>>> "This document...". Everything preceding that should be removed, and
>>>> the
>>>> result should be appended with a few sentences summarizing the
>>>> recommendations.
>>>>
>>>> The intro refers in a lot of detail to the motivation for the doc (some
>>>> of which may be historically important but is not relevant to the doc
>>>> itself), but only briefly notes the KARP threats document. This
>>>> document's observations should be motivated by addressing those
>>>> threats,
>>>> so it would be important to summarize them in this doc in the intro as
>>>> context.
>>>>
>>>> The summary of RFC 4984 discusses four tightening steps as if they were
>>>> indicated by that RFC; that RFC only suggests tightening itself. This
>>>> doc should more clearly indicate that "The WG identified four...".
>>>>
>>>> -----
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> sidr mailing list
>>>> sidr@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/sidr
>>>>
>>

From marshall.eubanks@gmail.com  Thu Jun 30 07:22:07 2011
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8FEF21F8531; Thu, 30 Jun 2011 07:22:07 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZZgjdK0SJiiD; Thu, 30 Jun 2011 07:22:06 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5E321F8532; Thu, 30 Jun 2011 07:22:06 -0700 (PDT)
Received: by gwb20 with SMTP id 20so1126387gwb.31 for <multiple recipients>; Thu, 30 Jun 2011 07:22:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; bh=04dPZxIj9j4wlqky9j5N8MIkchDQJ6iy7bhFUzg2VZ8=; b=O0Z8EKbHZ+m7DUTMIrVhdQTH1UomU+mj+sIthxa6+//PnPYarVn+o6NNJ79DhRECVe LfpVMwhHTpn2WzAluiiwjYnv6VKs/fDB8PC8iaEnlBtPkg5R8JIwS//wiSK9UtSpDbhx VbQUa8Wit9LoJYcLkx0sqNMLveyLooM/e/OTE=
Received: by 10.150.12.10 with SMTP id 10mr1892145ybl.77.1309443725596; Thu, 30 Jun 2011 07:22:05 -0700 (PDT)
Received: from [10.0.1.14] (c-67-188-32-245.hsd1.ca.comcast.net [67.188.32.245]) by mx.google.com with ESMTPS id i30sm1667452yhm.21.2011.06.30.07.22.04 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 30 Jun 2011 07:22:05 -0700 (PDT)
From: Marshall Eubanks <marshall.eubanks@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: tsv-dir review of draft-ietf-pim-mtid-08
Date: Thu, 30 Jun 2011 10:22:02 -0400
Message-Id: <A9EFAA60-85DE-40F1-86C3-B9652E9CC0EA@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Cc: TSV Area <tsv-area@ietf.org>, pim@ietf.org, Transport Directorate <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 14:22:08 -0000

I've reviewed this document as part of the transport area directorate's =
ongoing effort to review key IETF documents. These comments were written =
primarily for the transport area directors, but are copied to the =
document's authors for their information and to allow them to address =
any issues raised. The authors should consider this review together with =
any other last-call comments they receive. Please always CC =
tsv-dir@ietf.org if you reply to or forward this review.

Note : I also reviewed the WG mailing list discussions for this =
document.=20

This draft is basically ready for publication, but has some issues that =
in my opinion should be fixed before publication.

There are, however, some issues that I think that should be addressed, =
either in a follow-on document, or a revision of this document.=20

draft-ietf-pim-mtid  introduces a new type of PIM Join Attribute =
[RFC5384], the MT-ID Join Attribute, that extends
PIM signaling to cover multiple topologies and to enable the =
identification of which topology should be used when
constructing a particular multicast distribution tree.=20

Multiple topologies have been used for some time in unicast (they are =
supported by IS-IS and OSPF), and also in multicast. The most common =
multicast requirement for multiple topologies is for video transport, =
where important or expensive video streams (say, of sporting events) are =
protected from disruption by multiple transport on completely different =
network paths. In that use, if a network link goes down or becomes =
congested or otherwise suboptimal, another source of the video data is =
already present and the display can be seamlessly switched to the other =
copy of the stream. This use case is alluded to in the document.=20

Another use case for multiple-topologies is to separate out different =
types of traffic (say, latency sensitive traffic from larger, bulk, =
flows). This is not alluded to in this document, and it is not clear to =
what extent this was intended. These multiple topologies may or may not =
result
in the replication of data, and so may not be intended by the author. =
However, I would say that this could be used to support this, and so it =
will be. If there is some reason NOT to use this mechanism for this =
purpose, some description of the reasons why would be in order.=20

This document sets up a numerical variable, the  MT-ID Join Attribute, =
to assign to multicast topologies, to be used to separate different =
topologies for different paths. This number for a given multicast =
topology need not be the same as any unicast multiple topology =
identifiers, and similarly the multicast topologies and the underlying =
unicast topologies may be different.=20

This document is sort, straight-forward, and relatively well-written. I =
had a few non-fatal issues.  (I would be glad to suggest some text for =
any of these issues to the authors if they interested.)=20

Minor Issues :

Section 3.2=20

"- As shown earlier, this value is not required to be the same as the =
MT-ID used by the unicast routing protocols that contribute routes to =
the topology. In practice, when only one unicast routing protocol (such =
as OSPF or IS-IS) is used, the PIM MT-ID is RECOMMENDED to be assigned =
using the same value as the IGP topology identifier. Using the same =
example presented earlier, if
every route in PIM 500 is contributed by OSPF 1000, it is RECOMMENDED to =
name this RPF topology as PIM 1000 instead of PIM 500. This is for the =
purpose of reducing management overhead and simplifying =
troubleshooting."

In the actual example, PIM 500 is not the same network topology as OSPF =
1000 (it has an extra link, to the source, obtained by MBGP). This is =
specifically mentioned previously in the text. So, this is NOT the same =
example as presented earlier and it is NOT clear that this =
recommendation applies here.=20

If this is left as is, it will certainly confuse some people. I would =
suggest adding text to clarify this, or creating another example where =
the
unicast and multicast topologies are the same.

Section 4.2.3=20

"- There is at most 1 PIM MT-ID attribute encoded. If there are multiple =
PIM MT-ID Join Attributes included, only the last one is accepted for =
this particular source. Processing of the rest of the Join message =
continues."

Is this a typo ?=20

s/at most/at least/=20

would seem to be appropriate. (It says, "at most" 1, and then describes =
what do to if there is more than 1.) Otherwise, please explain what is =
meant.

Section 6.

The Labels for Section 6.1 and 6.2 are the same. I suspect this is just =
a typo, and they should be

6.1. PIM-Hello Options

6.2. PIM Join Attribute Types

More Substantive Issues :

I had two substantive issues with this document.=20

1.) The range for the topologies. It is highly likely that the users of =
this capability would want to use multiple topologies differently for =
different multicast address ranges. For example, use of two topologies =
is likely to be an expensive customer option, that not all customers =
would pay for, and so would not apply to all multicast addresses. Or, =
the backup typologies may (probably will be) tailored differently for =
different customers in different locations. Or, topologies might be =
tailored for different data types (different backups for real time video =
conferencing versus TV broadcast transmissions, say). This is very =
briefly alluded to in Section 3.1, but no consideration is given to =
issues arising from this.

For example, suppose I have two customers, and I wish to have one basic =
topology (say, PIM 100) for 239.10/16, and I wish to have two backup =
topologies for the two customers (say, PIM 1001 for 239.10.1/24 and PIM =
1002 for 239.10.2/24.) Can I have PIM 100 cover both the PIM 1001 and =
PIM 1002 range ? Are there issues with this ? Would it be better to =
split PIM 100 into pieces to match 1001 and 1002 ? Nothing like this is =
discussed

I can easily see interoperability issues arising from this (i.e., vendor =
A might allow PIM 100 to overlap PIM 1001 and PIM 1002, and vendor B =
might not). I think that some text to discuss the entire issue of =
ranging (presumably, that they can be allowed and overlaps SHOULD be =
supported) is needed.

Again, this could be out of scope here, but, then, where will it appear =
?=20

2.) There is very little discussion as to how to use this capability. =
Now, this might be considered out of scope for this document, but there =
will be issues, and I do not see a follow-on in the pipeline.=20

Issues include sharing of links and the general connections between =
topologies. It is likely that in real uses, a portion of the multiple =
topologies may be either physically shared or directly linked. It may =
not be possible to engineer out all single points of failure, for =
example an undersea cable. This is possible with the first use case =
(independent topologies for video) and likely with the second (different =
topologies for different types of content).=20

Issues I see here include

- the actual multicast data will not include any PIM attributes.  How, =
then, is a midpoint router receiving two copies of every packet know =
that it shouldn't just drop one, and only populate one of the =
downstreams ? Or, should it replicate one input into both downstream =
topologies ? I can easily see interop issues here, and possibly even =
more basic transport issues from replicated data.=20

- if at any point the two multicast topologies go through a shared LAN =
or switch or any sort of multiple access network, how are the =
topological flows going to be kept distinct. (This is similar to the =
above, but the actual routers might be kept separate.)=20

- what happens with failovers ? If a link fails, SHOULD the backup links =
not collapse the topologies ? Again, I think some thought and text would =
be useful.

If there is a solution to this, it may be simple (you MUST use tunnels) =
or it may be complicated. In either case, some text here would be good.=20=


Regards
Marshall=20=

From kathleen.moriarty@emc.com  Wed Jun 29 15:21:04 2011
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 4EB6421F859D; Wed, 29 Jun 2011 15:21: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61S+nrCkHx5a; Wed, 29 Jun 2011 15:21:03 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 77B0121F858F; Wed, 29 Jun 2011 15:21:03 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p5TML2St010592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jun 2011 18:21:02 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 29 Jun 2011 18:20:53 -0400
Received: from mxhub25.corp.emc.com (mxhub25.corp.emc.com [10.254.110.181]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p5TMKpdF032341; Wed, 29 Jun 2011 18:20:52 -0400
Received: from mx06a.corp.emc.com ([169.254.1.199]) by mxhub25.corp.emc.com ([10.254.110.181]) with mapi; Wed, 29 Jun 2011 18:20:24 -0400
From: <kathleen.moriarty@emc.com>
To: <ietf@ietf.org>, <saag@ietf.org>
Date: Wed, 29 Jun 2011 18:20:49 -0400
Subject: MILE 'side meeting' Monday night July 25th
Thread-Topic: MILE 'side meeting' Monday night July 25th
Thread-Index: Acw2qs0JHh8mbHuURqqcTPxt3owf0A==
Message-ID: <AE31510960917D478171C79369B660FA0E03253CAF@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:15 -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, 29 Jun 2011 22:21:04 -0000

Hello,

This email is to announce that we will be holding a side meeting for a pre-=
working group to review the proposed charter and some of the work to be com=
pleted in the proposed group.  The side meeting will take place Monday, Jul=
y 25th following the Technical Plenary, at 19:30 PM.

Thank you,
Kathleen & Brian


Managed Incident Lightweight Exchange (mile)
--------------------------------------------

Proposed Working Group Charter

 Chairs:
     Kathleen Moriarty <kathleen.moriarty@emc.com<mailto:kathleen.moriarty@=
emc.com>>
     Brian Trammell <trammell@tik.ee.ethz.ch<mailto:trammell@tik.ee.ethz.ch=
>>

 Security Area Directors:
     Stephen Farrell <stephen.farrell@cs.tcd.ie<mailto:stephen.farrell@cs.t=
cd.ie>>
     Sean Turner <turners@ieca.com<mailto:turners@ieca.com>>

 Security Area Advisor:
     Sean Turner <turners@ieca.com<mailto:turners@ieca.com>>

 Mailing Lists:
     General Discussion: mile@ietf.org<mailto:mile@ietf.org>
     To Subscribe:       http://www.ietf.org/mailman/listinfo/mile
     Archive:            http://www.ietf.org/mail-archive/web/mile

Description of Working Group:


The Managed Incident Lightweight Exchange (MILE) pre-working group will dev=
elop standards and extensions for the purpose of improving incident informa=
tion sharing and handling capabilities based on the work developed in the I=
ETF Extended INCident Handling (INCH) working group.  The Incident Object D=
escription Exchange Format (IODEF) in RFC5070 and Real-time Inter-network D=
efense (RID) in RFC6045 were developed in the INCH working group by interna=
tional Computer Security Incident Response Teams (CSIRTs) and industry to m=
eet the needs of a global community interested in sharing, handling, and ex=
changing incident information.  The extensions and guidance created by the =
MILE working group assists with the daily operations of CSIRTs at an organi=
zation, service provider, law enforcement, and at the country level.  The a=
pplication of IODEF and RID to interdomain incident information cooperative=
 exchange and sharing has recently expanded and the need for extensions has=
 become more important. Efforts continue to deploy IODEF and RID, as well a=
s to extend them to support specific use cases covering reporting and mitig=
ation of current threats such as anti-phishing extensions.

An incident could be a benign configuration issue, IT incident, an infracti=
on to a service level agreement (SLA), a system compromise, socially engine=
ered phishing attack, or a denial-of-service (DoS) attack, etc..  When an i=
ncident is detected, the response may include simply filing a report, notif=
ication to the source of the incident, a request to a third party for resol=
ution/mitigation, or a request to locate the source.  IODEF defines a data =
representation that provides a standard format for sharing information comm=
only exchanged about computer security incidents.  RID enables the secure e=
xchange of incident related information in an IODEF format providing option=
s for security, privacy, and policy setting.

MILE leverages collaboration and sharing experiences with the work develope=
d in the INCH working group which includes the data model detailed in the I=
ODEF, existing extensions to the IODEF for Anti-phishing (RFC5901), and RID=
 (RFC6045, RFC6046) for the secure exchange of information.  MILE will also=
 leverage the experience gained in using IODEF and RID in operational conte=
xts. Related work, drafted outside of INCH will also be reviewed and includ=
es RFC5941, Sharing Transaction Fraud Data.

The MILE working group provides coordination for these various extension ef=
forts to improve the capabilities for exchanging incident information.  MIL=
E has several objectives with the first being a description a subset of IOD=
EF focused on ease of deployment and applicability to current information s=
ecurity data sharing use cases.  MILE also describes a generalization of RI=
D for secure exchange of other security-relevant XML formats.  MILE produce=
s additional guidance needed for the successful exchange of incident inform=
ation for new use cases according to policy, security, and privacy requirem=
ents.  Finally, MILE produces a document template with guidance for definin=
g IODEF extensions to be followed when producing extensions to IODEF as app=
ropriate, for:

  * labeling incident reports with data protection, data retention, and oth=
er policies, regulations, and
    laws restricting the handling of those reports
  * reporting on mail service abuse incidents
  * reporting forensic data generated during incident investigation
  * reporting indicators of compromise in incident reports
  * reporting on financial fraud incidents
  * reporting incidents involving virtualized environments
  * referencing SCAP enumerations from within incident reports
  * profiling and reporting on characteristics of malware suspected or conf=
irmed to be involved in an incident
  * profiling and reporting on characteristics of actors (persons or groups=
) suspected or confirmed to be
    involved in an incident
  * reporting on misuse incidents








From dwhite@olp.net  Wed Jun 29 22:11:35 2011
Return-Path: <dwhite@olp.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73D9B11E80C8; Wed, 29 Jun 2011 22:11:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.265
X-Spam-Level: 
X-Spam-Status: No, score=-3.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oUVqLjCz6Yxo; Wed, 29 Jun 2011 22:11:35 -0700 (PDT)
Received: from pinky.olp.net (pinky2.olp.net [67.217.151.213]) by ietfa.amsl.com (Postfix) with ESMTP id 6C6F811E8127; Wed, 29 Jun 2011 22:11:27 -0700 (PDT)
Received: from quark.olp.net (olp-67-217-144-186.olp.net [67.217.144.186]) by pinky.olp.net (Postfix) with ESMTP id 2304229301A; Thu, 30 Jun 2011 00:11:24 -0500 (CDT)
Received: by quark.olp.net (Postfix, from userid 1000) id D112C7B208F; Thu, 30 Jun 2011 00:11:23 -0500 (CDT)
Date: Thu, 30 Jun 2011 00:11:23 -0500
From: Dan White <dwhite@olp.net>
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: HOMENET working group proposal
Message-ID: <20110630051123.GD4013@dan.olp.net>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <4E0BDCF3.1090003@gont.com.ar>
X-OS: Linux quark 2.6.39-1-amd64 x86_64
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:15 -0700
Cc: "homegate@ietf.org" <homegate@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 05:11:35 -0000

On 29/06/11 23:18 -0300, Fernando Gont wrote:
>On 06/29/2011 05:47 AM, Jari Arkko wrote:
>[....]
>> o Service providers are deploying IPv6, and support for IPv6 is
>> increasingly available in home gateway devices. While IPv6 resembles
>> IPv4 in many ways, it changes address allocation principles and allows
>> direct IP addressability and routing to devices in the home from the
>> Internet. This is a promising area in IPv6 that has proved challenging
>> in IPv4 with the proliferation of NAT.
>
>NAT devices involve two related but different issues:
>* address translation
>* an implicit "allow only return traffic" firewall-like functionality

I'll add a 3rd component, which is application protocol mangling.

What's given NAT a particularly bad name in recent years are the
consistently poor SIP ALG implementations in many home routers, along with
IPSEC ALGs, and other ALGs that attempt to fix the problem in the wrong
way.

End-to-end communication might be better approached as the desire to
default to a configuration in which ALGs are no longer necessary, and then
address firewalling separately, which could just as well default to a no
inbound connection policy.

>> o End-to-end communication is both an opportunity and a concern as it
>> enables new applications but also exposes nodes in the internal
>> networks to receipt of unwanted traffic from the Internet. Firewalls
>> that restrict incoming connections may be used to prevent exposure,
>> however, this reduces the efficacy of end-to-end connectivity that
>> IPv6 has the potential to restore.
>
>I personally consider this property of "end-to-end connectivity" as
>"gone". -- among other reasons, because it would require a change of
>mindset. I'm more of the idea that people will replicate the
>architecture of their IPv4 networks with IPv6, in which end-systems are
>not reachable from the public Internet.

Home networks are bound to grow complex quite quickly. There's certainly
value in using a model that residential users are familiar with, but it
should be balanced by the inevitable need to address complexity that will
outgrow the ability of many users to manage.

A typically complex home network in the near future might be: alarm
systems, utility and environmental monitoring, lifeline SIP service (911),
Super Bowl broadcasts, etc., all connected via one home gateway device,
which may have several outsourced/managed devices installed behind it.

Having a simpler demarcation-like gateway device, which defers a lot of
that complexity to other components in the network (such as end-to-end
security), should go a long way in providing a sustainable model.

-- 
Dan White

From swmike@swm.pp.se  Wed Jun 29 22:12:21 2011
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 C4DE911E80C8; Wed, 29 Jun 2011 22:12: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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4hpLWTbUTFH6; Wed, 29 Jun 2011 22:12:21 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id BC12911E8128; Wed, 29 Jun 2011 22:12:20 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 5E7509C; Thu, 30 Jun 2011 07:12:18 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 5B39D9A; Thu, 30 Jun 2011 07:12:18 +0200 (CEST)
Date: Thu, 30 Jun 2011 07:12:18 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: [homegate] HOMENET working group proposal
In-Reply-To: <4E0BDCF3.1090003@gont.com.ar>
Message-ID: <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar>
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-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:15 -0700
Cc: "homegate@ietf.org" <homegate@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 05:12:22 -0000

On Wed, 29 Jun 2011, Fernando Gont wrote:

> My high level comment/question is: the proposed charter seems to stress 
> that IPv6 is the driver behind this potential wg effort... however, I 
> think that this deserves more discussion -- it's not clear to me why/how 
> typical IPv6 home networks would be much different from their IPv4 
> counterparts.

In my mind, I see the possibility of /56 PD enabling different subnets for 
different kinds of devices with different security and functional needs, 
and also chaining of L3 devices. This definitely warrants a group to look 
at that.

A more routed home instead of pure L2 one.

> One would hope/expect that the former will be gone with IPv6. However, I 
> don't think the latter will. As a result, even when you could "address" 
> nodes that belong to the "home network", you probably won't be able to 
> get your packets to them, unless those nodes initiated the communication 
> instance.

This is exactly why the whole "system" needs to work, including uPNP like 
functionality for nodes to talk to the firewall(s).

> I personally consider this property of "end-to-end connectivity" as 
> "gone". -- among other reasons, because it would require a change of 
> mindset. I'm more of the idea that people will replicate the 
> architecture of their IPv4 networks with IPv6, in which end-systems are 
> not reachable from the public Internet.

I think this will also change, but not for all devices from all of the 
Internet. Still, I believe there is a place for a working group to look at 
this.

I have subscribed already.

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

From swmike@swm.pp.se  Thu Jun 30 00:26:02 2011
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 2A3EA21F862E; Thu, 30 Jun 2011 00:26: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xuF8YGmGH2vU; Thu, 30 Jun 2011 00:26:01 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 9F77E21F85AF; Thu, 30 Jun 2011 00:25:32 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9BCFF9C; Thu, 30 Jun 2011 09:25:29 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 99AEC9A; Thu, 30 Jun 2011 09:25:29 +0200 (CEST)
Date: Thu, 30 Jun 2011 09:25:29 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: [homegate] HOMENET working group proposal
In-Reply-To: <4E0C1CF8.7090601@gont.com.ar>
Message-ID: <alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar>
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-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:15 -0700
Cc: "homegate@ietf.org" <homegate@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 07:26:02 -0000

On Thu, 30 Jun 2011, Fernando Gont wrote:

> My point was that, except for the mechanism for PD, I don't see a 
> substantial difference here that would e.g. prevent this from being 
> developed for IPv4 (in addition to IPv6). -- Yes, I know we need to 
> deploy IPv6... but I don't think you can expect people to get rid of 
> their *working* IPv4 devices... (i.e., not sure why any of this 
> functionality should be v6-only)

Chaining NAT boxes already work. I also feel that we shouldn't put in a 
lot of work to develop IPv4 further, that focus should be put on IPv6.

> I think this deserves a problem statement that clearly describes what we 
> expect to be able to do (but currently can't), etc. And, if this is 
> meant to be v6-only, state why v4 is excluded -- unless we're happy to 
> have people connect their IPv4-devices, and see that they cannot 
> communicate anymore.

IPv4 should be excluded because it's a dead end, and we all know it. We're 
just disagreeing when it's going to die and how.

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

From mark@townsley.net  Thu Jun 30 02:57:12 2011
Return-Path: <mark@townsley.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AC6721F8765; Thu, 30 Jun 2011 02:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMCF1xRJkbPN; Thu, 30 Jun 2011 02:57:12 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 667EF21F8718; Thu, 30 Jun 2011 02:57:11 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1629381wyj.31 for <multiple recipients>; Thu, 30 Jun 2011 02:57:10 -0700 (PDT)
Received: by 10.227.195.13 with SMTP id ea13mr1680580wbb.0.1309427830425; Thu, 30 Jun 2011 02:57:10 -0700 (PDT)
Received: from ams-townsley-8714.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id ex2sm1506729wbb.14.2011.06.30.02.57.07 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 30 Jun 2011 02:57:08 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [homegate] HOMENET working group proposal
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se>
Date: Thu, 30 Jun 2011 11:57:06 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar> <alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se>
To: homegate@ietf.org, IETF Discussion <ietf@ietf.org>, fun@ietf.org
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:15 -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, 30 Jun 2011 09:57:12 -0000

I think the consensus we had in the past BoFs and discussion in and =
around this topic can be summed up as stating that homenet deliverables =
will:

- coexist with (existing) IPv4 protocols, devices, applications, etc.
- operate in a (future) IPv6-only home network in the absence of IPv4
- be IP-agnostic whenever possible

In other words, anything we do for the IPv6 homenet cannot actively =
break what's already running on IPv4. Also, trying to define what the =
IPv4 home network should be has long reached a point of diminishing =
returns given the effort in doing so coupled with our ability to =
significantly affect what's already deployed. There's still hope we can =
help direct IPv6, as such that is homenet's primary focus.  However, =
when we can define something that is needed for IPv6 in a way that is =
also useful for IPv4 without making significant concessions, we should =
go ahead and do so.=20

- Mark



On Jun 30, 2011, at 9:25 AM, Mikael Abrahamsson wrote:

> On Thu, 30 Jun 2011, Fernando Gont wrote:
>=20
>> My point was that, except for the mechanism for PD, I don't see a =
substantial difference here that would e.g. prevent this from being =
developed for IPv4 (in addition to IPv6). -- Yes, I know we need to =
deploy IPv6... but I don't think you can expect people to get rid of =
their *working* IPv4 devices... (i.e., not sure why any of this =
functionality should be v6-only)
>=20
> Chaining NAT boxes already work. I also feel that we shouldn't put in =
a lot of work to develop IPv4 further, that focus should be put on IPv6.
>=20
>> I think this deserves a problem statement that clearly describes what =
we expect to be able to do (but currently can't), etc. And, if this is =
meant to be v6-only, state why v4 is excluded -- unless we're happy to =
have people connect their IPv4-devices, and see that they cannot =
communicate anymore.
>=20
> IPv4 should be excluded because it's a dead end, and we all know it. =
We're just disagreeing when it's going to die and how.
>=20
> --=20
> Mikael Abrahamsson    email: swmike@swm.pp.se
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate


From pthubert@cisco.com  Thu Jun 30 03:53:48 2011
Return-Path: <pthubert@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 8D73621F86E2; Thu, 30 Jun 2011 03:53:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.599
X-Spam-Level: 
X-Spam-Status: No, score=-11.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qcl0Dhglk7ft; Thu, 30 Jun 2011 03:53:48 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 86A8D21F86AC; Thu, 30 Jun 2011 03:53:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pthubert@cisco.com; l=959; q=dns/txt; s=iport; t=1309431227; x=1310640827; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=F1G4sF0wTufITEnXncVNRIs8Nzlus7JcCeMeWVCvqOw=; b=LHgBC/7ERD835oFC+atOlaWe7KSmIqSX1d3/1kR6W+IVJNJKrZnwv6hy A4mfSbPab/ePmCh209G6rmQ4mE0ZIFewQqWy/sXz8kg0L5UocfV0QUzUe +cFOY/ohfH0N98INqnNNWBRJmKJKSYco+JPcx9rmEqf+QxWo4xFDZde4N E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAP9UDE6Q/khL/2dsb2JhbABSp1N3iHiga54WhjEEly6LMQ
X-IronPort-AV: E=Sophos;i="4.65,449,1304294400"; d="scan'208";a="39998362"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 30 Jun 2011 10:53:33 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5UArUSi008338; Thu, 30 Jun 2011 10:53:30 GMT
Received: from xmb-ams-107.cisco.com ([144.254.74.82]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 30 Jun 2011 12:53:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [fun] [homegate] HOMENET working group proposal
Date: Thu, 30 Jun 2011 12:53:25 +0200
Message-ID: <6A2A459175DABE4BB11DE2026AA50A5D04FAE6D4@XMB-AMS-107.cisco.com>
In-Reply-To: <4E0C49CD.30505@piuha.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [fun] [homegate] HOMENET working group proposal
Thread-Index: Acw3DOnOo1pL3PujS8ii/5j3somAQQABec+w
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar><alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se><4E0C1CF8.7090601@gont.com.ar> <4E0C4417.90804@piuha.net><4E0C4631.3010409@gont.com.ar> <4E0C49CD.30505@piuha.net>
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Jari Arkko" <jari.arkko@piuha.net>, "Fernando Gont" <fernando@gont.com.ar>
X-OriginalArrivalTime: 30 Jun 2011 10:53:31.0099 (UTC) FILETIME=[F332A2B0:01CC3713]
X-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:14 -0700
Cc: IETF Discussion <ietf@ietf.org>, fun@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 10:53:48 -0000

> That is the plan. And when I say "differently", I mean differences
such as
>=20
> * prefix delegation
> * global addresses and firewalls instead of private addresses and NATs
> * across-subnet communication internally in the home can be routed,
not
> NATted
>=20

[Pascal] I'd add to that multiple virtual topologies, and heterogeneous
subnets where even the link layer is not consistent across the subnet.

Automation and command/control already uses wireless technologies that
are non WIFI; ISA100.15 already works on backhaul technologies; the IETF
is missing a clear model to explain them how we isolate flows and merge
heterogeneous links into one subnet.=20

I think there is a lot this group can do to pursue / extend what was
done at 6LoWPAN (ND, backbone router) so that the work there connects to
the rest of the home, and by extension, the rest of other networks such
as building and industrial plants.

Cheers,

Pascal

From iljitsch@muada.com  Thu Jun 30 06:45:31 2011
Return-Path: <iljitsch@muada.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC79E11E80CC; Thu, 30 Jun 2011 06:45:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.328
X-Spam-Level: 
X-Spam-Status: No, score=-102.328 tagged_above=-999 required=5 tests=[AWL=0.272, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xT2NW0q2OXmF; Thu, 30 Jun 2011 06:45:31 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD5511E80BF; Thu, 30 Jun 2011 06:45:30 -0700 (PDT)
Received: from [IPv6:2001:720:410:100f:223:32ff:fec4:ba94] ([IPv6:2001:720:410:100f:223:32ff:fec4:ba94]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p5UDjq4O011921 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 30 Jun 2011 15:45:53 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: [BEHAVE] FW: Last Call: <draft-ietf-behave-ftp64-10.txt> (An FTP ALG for IPv6-to-IPv4 translation) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <817780D4-1CF0-4A5A-90A8-E8BF98A2274F@muada.com>
Date: Thu, 30 Jun 2011 15:45:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <44C34387-A958-41E9-9363-D8DB7EBBCEF0@muada.com>
References: <04C1AFDBEA554F3FA5FDD978C1682D6E@davidPC> <817780D4-1CF0-4A5A-90A8-E8BF98A2274F@muada.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:15 -0700
Cc: draft-ietf-behave-ftp64@tools.ietf.org, fgont@acm.org, "behave@ietf.orgWG WG" <behave@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>, Daniel Stenberg <daniel@haxx.se>, ftpext@ietf.org, TSV Area <tsv-area@ietf.org>, "behave-chairs@tools.ietf.org Chairs" <behave-chairs@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, draft-ietf-behave-ftp64.all@tools.ietf.org, David Harrington <ietfdbh@comcast.net>, Pekka Savola <pekkas@netcore.fi>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 13:45:31 -0000

[Please note that this message is going to many mailing lists, please =
trim as appropriate when responding.]

I submitted a new version of the draft which addresses most, if not all =
comments.

The most notable change, which I would like to ask previous reviewers to =
look at again, is the handling of the AUTH command, which is now made =
much less prominent as a way to make the ALG transparent (clients should =
use ALGS for this) so text specifying interaction of multiple ALGs could =
be removed.

The draft:

http://tools.ietf.org/html/draft-ietf-behave-ftp64-11

The diff with -10:

=
http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&url2=3Ddraft-ietf-behave=
-ftp64-11.txt

Thanks everyone for reviewing.=

From erik.taraldsen@telenor.com  Thu Jun 30 06:51:36 2011
Return-Path: <erik.taraldsen@telenor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E730811E8071; Thu, 30 Jun 2011 06:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.288
X-Spam-Level: 
X-Spam-Status: No, score=-2.288 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ww3vXRkces1; Thu, 30 Jun 2011 06:51:36 -0700 (PDT)
Received: from sv04.e.nsc.no (vip1scan.telenor.net [148.123.15.75]) by ietfa.amsl.com (Postfix) with ESMTP id 2A99A21F85AD; Thu, 30 Jun 2011 06:51:35 -0700 (PDT)
Received: from tns-fbu-22-248.corp.telenor.no ([134.47.162.18] [134.47.162.18]) by sv04.nsc.no with ESMTPS id BT-MMP-729675; Thu, 30 Jun 2011 15:51:33 +0200
Received: from TNS-FBU-2E-016.corp.telenor.no ([134.47.163.219]) by tns-fbu-22-248.corp.telenor.no ([134.47.162.18]) with mapi; Thu, 30 Jun 2011 15:51:32 +0200
From: <erik.taraldsen@telenor.com>
To: <swmike@swm.pp.se>, <fernando@gont.com.ar>
Date: Thu, 30 Jun 2011 15:51:30 +0200
Subject: RE: [homegate] HOMENET working group proposal
Thread-Topic: [homegate] HOMENET working group proposal
Thread-Index: Acw25FkjU7sz+zclSF65n2H2+JtplAAR9c+Q
Message-ID: <6A141C5EC2D26E47B3128814D5F69592156010B7D9@TNS-FBU-2E-016.corp.telenor.no>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se>
Accept-Language: nb-NO
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: nb-NO
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:15 -0700
Cc: homegate@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 Jun 2011 13:51:37 -0000

-----Original Message-----
From: homegate-bounces@ietf.org [mailto:homegate-bounces@ietf.org] On Behal=
f Of Mikael Abrahamsson
Sent: 30. juni 2011 07:12
To: Fernando Gont
Cc: homegate@ietf.org; IETF Discussion
Subject: Re: [homegate] HOMENET working group proposal

On Wed, 29 Jun 2011, Fernando Gont wrote:

> This is exactly why the whole "system" needs to work, including uPNP like=
=20
> functionality for nodes to talk to the firewall(s).

UPnP like can indeed be UPnP.  The UPnP Forum has defined IPv6 firewall con=
trol as a part of UPnP now.
http://upnp.org/specs/gw/UPnP-gw-WANIPv6FirewallControl-v1-Service.pdf

Telenor, which I work for, is going to ask for this as a part of the IPv6 o=
ffering from our CPE vendors.


-Erik Taraldsen

From palm@broadcom.com  Thu Jun 30 07:41:40 2011
Return-Path: <palm@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 B388B11E8091; Thu, 30 Jun 2011 07:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1DwscrhRJezS; Thu, 30 Jun 2011 07:41:39 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5964C22800E; Thu, 30 Jun 2011 07:41:39 -0700 (PDT)
Received: from [10.9.200.131] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 30 Jun 2011 07:46:16 -0700
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from mail-irva-13.broadcom.com (10.11.16.103) by IRVEXCHHUB01.corp.ad.broadcom.com (10.9.200.131) with Microsoft SMTP Server id 8.2.247.2; Thu, 30 Jun 2011 07:41:22 -0700
Received: from [10.9.254.251] (unknown [10.9.254.251]) by mail-irva-13.broadcom.com (Postfix) with ESMTP id D982B74D04; Thu, 30 Jun 2011 07:41:21 -0700 (PDT)
Message-ID: <4E0C8B11.3070609@broadcom.com>
Date: Thu, 30 Jun 2011 07:41:21 -0700
From: "Stephen [kiwin] PALM" <palm@broadcom.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: "Fernando Gont" <fernando@gont.com.ar>
Subject: Re: [homegate] HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar>
In-Reply-To: <4E0C1CF8.7090601@gont.com.ar>
X-WSS-ID: 621253B23B411813245-01-01
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:15 -0700
Cc: IETF Discussion <ietf@ietf.org>, fun@ietf.org, "homegate@ietf.org" <homegate@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 14:41:40 -0000

Agreed. I would phrase it this way:
How to do IPv6 in an IPv4 world.

Some points from the Description:
  > o Service providers are deploying IPv6, and support for IPv6 is
  > increasingly available in home gateway devices.

This is only *part* of the story.  *Users* have lots of IPv4
devices in their home.

  > o service discovery
This is already well handled by UPnP/DLNA

  > o managing routing

There were several snippets regarding routing/subnets/heterogeneous networking
technologies.  There is already work proceeding in IEEE P1905.1
to address issues related to multiple network technologies
via a MAC/PHY Abstraction Layer.  Also there are applications today
that expect a single subnet, so new architectures should not preclude
existing applications.

regards, kiwin

On 6/29/2011 11:51 PM, Fernando Gont wrote:
> On 06/30/2011 02:12 AM, Mikael Abrahamsson wrote:
>>> My high level comment/question is: the proposed charter seems to
>>> stress that IPv6 is the driver behind this potential wg effort...
>>> however, I think that this deserves more discussion -- it's not clear
>>> to me why/how typical IPv6 home networks would be much different from
>>> their IPv4 counterparts.
>>
>> In my mind, I see the possibility of /56 PD enabling different subnets
>> for different kinds of devices with different security and functional
>> needs, and also chaining of L3 devices. This definitely warrants a group
>> to look at that.
>
> My point was that, except for the mechanism for PD, I don't see a
> substantial difference here that would e.g. prevent this from being
> developed for IPv4 (in addition to IPv6). -- Yes, I know we need to
> deploy IPv6... but I don't think you can expect people to get rid of
> their *working* IPv4 devices... (i.e., not sure why any of this
> functionality should be v6-only)
>
>
>>> One would hope/expect that the former will be gone with IPv6. However,
>>> I don't think the latter will. As a result, even when you could
>>> "address" nodes that belong to the "home network", you probably won't
>>> be able to get your packets to them, unless those nodes initiated the
>>> communication instance.
>>
>> This is exactly why the whole "system" needs to work, including uPNP
>> like functionality for nodes to talk to the firewall(s).
>
> I think this deserves a problem statement that clearly describes what we
> expect to be able to do (but currently can't), etc. And, if this is
> meant to be v6-only, state why v4 is excluded -- unless we're happy to
> have people connect their IPv4-devices, and see that they cannot
> communicate anymore.
>
> Thanks,

-- 
Stephen [kiwin] Palm   Ph.D.                          E:  palm@kiwin.com
Senior Technical Director                             T: +1-949-926-PALM
Broadcom Broadband Communications Group               F: +1-949-926-7256
Irvine, California                               W: http://www.kiwin.com
Secondary email accounts:  stephenpalm@alumni.uci.edu  palm@broadcom.com
s.palm@ieee.org  palm@itu.ch  spalm@cs.cmu.edu  palm@ics.t.u-tokyo.ac.jp


From palm@broadcom.com  Thu Jun 30 07:56:27 2011
Return-Path: <palm@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 A55C322800E; Thu, 30 Jun 2011 07:56: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TRH1SOEuSv4l; Thu, 30 Jun 2011 07:56:26 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id A543D22800D; Thu, 30 Jun 2011 07:56:26 -0700 (PDT)
Received: from [10.9.200.131] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 30 Jun 2011 08:00:35 -0700
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from mail-irva-13.broadcom.com (10.11.16.103) by IRVEXCHHUB01.corp.ad.broadcom.com (10.9.200.131) with Microsoft SMTP Server id 8.2.247.2; Thu, 30 Jun 2011 07:55:40 -0700
Received: from [10.9.254.251] (unknown [10.9.254.251]) by mail-irva-13.broadcom.com (Postfix) with ESMTP id A19F174D04; Thu, 30 Jun 2011 07:55:40 -0700 (PDT)
Message-ID: <4E0C8E6C.3020205@broadcom.com>
Date: Thu, 30 Jun 2011 07:55:40 -0700
From: "Stephen [kiwin] PALM" <palm@broadcom.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: "Mark Townsley" <mark@townsley.net>
Subject: Re: [homegate] HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar> <alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se> <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net>
In-Reply-To: <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net>
X-WSS-ID: 621250193B411821620-01-01
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:15 -0700
Cc: "fun@ietf.org" <fun@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 14:56:27 -0000

Thanks Mark for stating that.
It would really be helpful if this type of text is included in the description/charter.
The lack of of this information in the recently distributed material caused
several immediate allergic reactions...

regards, kiwin

On 6/30/2011 2:57 AM, Mark Townsley wrote:
>
> I think the consensus we had in the past BoFs and discussion in and around this topic can be summed up as stating that homenet deliverables will:
>
> - coexist with (existing) IPv4 protocols, devices, applications, etc.
> - operate in a (future) IPv6-only home network in the absence of IPv4
> - be IP-agnostic whenever possible
>
> In other words, anything we do for the IPv6 homenet cannot actively break what's already running on IPv4. Also, trying to define what the IPv4 home network should be has long reached a point of diminishing returns given the effort in doing so coupled with our ability to significantly affect what's already deployed. There's still hope we can help direct IPv6, as such that is homenet's primary focus.  However, when we can define something that is needed for IPv6 in a way that is also useful for IPv4 without making significant concessions, we should go ahead and do so.
>
> - Mark
>
>
>
> On Jun 30, 2011, at 9:25 AM, Mikael Abrahamsson wrote:
>
>> On Thu, 30 Jun 2011, Fernando Gont wrote:
>>
>>> My point was that, except for the mechanism for PD, I don't see a substantial difference here that would e.g. prevent this from being developed for IPv4 (in addition to IPv6). -- Yes, I know we need to deploy IPv6... but I don't think you can expect people to get rid of their *working* IPv4 devices... (i.e., not sure why any of this functionality should be v6-only)
>>
>> Chaining NAT boxes already work. I also feel that we shouldn't put in a lot of work to develop IPv4 further, that focus should be put on IPv6.
>>
>>> I think this deserves a problem statement that clearly describes what we expect to be able to do (but currently can't), etc. And, if this is meant to be v6-only, state why v4 is excluded -- unless we're happy to have people connect their IPv4-devices, and see that they cannot communicate anymore.
>>
>> IPv4 should be excluded because it's a dead end, and we all know it. We're just disagreeing when it's going to die and how.
>>
>> --
>> Mikael Abrahamsson    email: swmike@swm.pp.se
>> _______________________________________________
>> homegate mailing list
>> homegate@ietf.org
>> https://www.ietf.org/mailman/listinfo/homegate
>
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate
>

-- 
Stephen [kiwin] Palm   Ph.D.                          E:  palm@kiwin.com
Senior Technical Director                             T: +1-949-926-PALM
Broadcom Broadband Communications Group               F: +1-949-926-7256
Irvine, California                               W: http://www.kiwin.com
Secondary email accounts:  stephenpalm@alumni.uci.edu  palm@broadcom.com
s.palm@ieee.org  palm@itu.ch  spalm@cs.cmu.edu  palm@ics.t.u-tokyo.ac.jp


From jason.weil@twcable.com  Thu Jun 30 08:06:21 2011
Return-Path: <jason.weil@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFD8011E8166; Thu, 30 Jun 2011 08:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.163
X-Spam-Level: 
X-Spam-Status: No, score=-0.163 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jDn6cAje65Fk; Thu, 30 Jun 2011 08:06:21 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id B844A11E8165; Thu, 30 Jun 2011 08:06:20 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.65,450,1304308800"; d="scan'208";a="244401990"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 30 Jun 2011 11:05:13 -0400
Received: from PRVPEXVS04.corp.twcable.com ([10.136.163.28]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Thu, 30 Jun 2011 11:06:20 -0400
From: "Weil, Jason" <jason.weil@twcable.com>
To: Mark Townsley <mark@townsley.net>, "homegate@ietf.org" <homegate@ietf.org>, IETF Discussion <ietf@ietf.org>, "fun@ietf.org" <fun@ietf.org>
Date: Thu, 30 Jun 2011 11:06:18 -0400
Subject: Re: [fun] [homegate] HOMENET working group proposal
Thread-Topic: [fun] [homegate] HOMENET working group proposal
Thread-Index: Acw3N0QENp1awgw7QgCuxWlYWR/P2g==
Message-ID: <CA31FD28.4B0C%jason.weil@twcable.com>
In-Reply-To: <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.0.0.100825
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:15 -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, 30 Jun 2011 15:06:21 -0000

Mark,

100% in agreement with this stance.

Just to echo what Fernando has already stated, you can't completely ignore
IPv4 in the home network especially when you are talking about a
multi-segmented network. For example RFC6204 calls for a separate /64 on
each LAN interface per the L-2 requirement. In IPv4 these interfaces
nearly always operate in bridged mode. Supporting bridged IPv4 and routed
IPv6 on the same physical interface could pose a challenge.

Overall I like the concept of not breaking core IPv4 functionality while
focussing all new functionality to IPv6.

Jason


On 6/30/11 5:57 AM, "Mark Townsley" <mark@townsley.net> wrote:

>
>I think the consensus we had in the past BoFs and discussion in and
>around this topic can be summed up as stating that homenet deliverables
>will:
>
>- coexist with (existing) IPv4 protocols, devices, applications, etc.
>- operate in a (future) IPv6-only home network in the absence of IPv4
>- be IP-agnostic whenever possible
>
>In other words, anything we do for the IPv6 homenet cannot actively break
>what's already running on IPv4. Also, trying to define what the IPv4 home
>network should be has long reached a point of diminishing returns given
>the effort in doing so coupled with our ability to significantly affect
>what's already deployed. There's still hope we can help direct IPv6, as
>such that is homenet's primary focus.  However, when we can define
>something that is needed for IPv6 in a way that is also useful for IPv4
>without making significant concessions, we should go ahead and do so.
>
>- Mark
>
>
>
>On Jun 30, 2011, at 9:25 AM, Mikael Abrahamsson wrote:
>
>> On Thu, 30 Jun 2011, Fernando Gont wrote:
>>
>>> My point was that, except for the mechanism for PD, I don't see a
>>>substantial difference here that would e.g. prevent this from being
>>>developed for IPv4 (in addition to IPv6). -- Yes, I know we need to
>>>deploy IPv6... but I don't think you can expect people to get rid of
>>>their *working* IPv4 devices... (i.e., not sure why any of this
>>>functionality should be v6-only)
>>
>> Chaining NAT boxes already work. I also feel that we shouldn't put in a
>>lot of work to develop IPv4 further, that focus should be put on IPv6.
>>
>>> I think this deserves a problem statement that clearly describes what
>>>we expect to be able to do (but currently can't), etc. And, if this is
>>>meant to be v6-only, state why v4 is excluded -- unless we're happy to
>>>have people connect their IPv4-devices, and see that they cannot
>>>communicate anymore.
>>
>> IPv4 should be excluded because it's a dead end, and we all know it.
>>We're just disagreeing when it's going to die and how.
>>
>> --
>> Mikael Abrahamsson    email: swmike@swm.pp.se
>> _______________________________________________
>> homegate mailing list
>> homegate@ietf.org
>> https://www.ietf.org/mailman/listinfo/homegate
>
>_______________________________________________
>fun mailing list
>fun@ietf.org
>https://www.ietf.org/mailman/listinfo/fun


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From palm@broadcom.com  Thu Jun 30 08:10:34 2011
Return-Path: <palm@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 03A6E11E818C; Thu, 30 Jun 2011 08:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R5aEPfsfx2Wo; Thu, 30 Jun 2011 08:10:32 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id 73DE411E8185; Thu, 30 Jun 2011 08:10:08 -0700 (PDT)
Received: from [10.9.200.131] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Thu, 30 Jun 2011 08:14:46 -0700
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from mail-irva-13.broadcom.com (10.11.16.103) by IRVEXCHHUB01.corp.ad.broadcom.com (10.9.200.131) with Microsoft SMTP Server id 8.2.247.2; Thu, 30 Jun 2011 08:09:51 -0700
Received: from [10.9.254.251] (unknown [10.9.254.251]) by mail-irva-13.broadcom.com (Postfix) with ESMTP id 3AF2B74D04; Thu, 30 Jun 2011 08:09:51 -0700 (PDT)
Message-ID: <4E0C91BE.6050807@broadcom.com>
Date: Thu, 30 Jun 2011 08:09:50 -0700
From: "Stephen [kiwin] PALM" <palm@broadcom.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: "Weil, Jason" <jason.weil@twcable.com>
Subject: Re: [fun] [homegate] HOMENET working group proposal
References: <CA31FD28.4B0C%jason.weil@twcable.com>
In-Reply-To: <CA31FD28.4B0C%jason.weil@twcable.com>
X-WSS-ID: 62124D6C3B411829987-01-01
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:15 -0700
Cc: "fun@ietf.org" <fun@ietf.org>, Mark Townsley <mark@townsley.net>, "homegate@ietf.org" <homegate@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 15:10:34 -0000

On 6/30/2011 8:06 AM, Weil, Jason wrote:

> Overall I like the concept of not breaking core IPv4 functionality while
> focussing all new functionality to IPv6.

It is more than just IPv4 functionality... it is all the deployed
applications and devices that utilize IPv4.... and for whatever
reason, cannot be "upgraded" to IPv6. 8-)

regards, kiwin

> On 6/30/11 5:57 AM, "Mark Townsley"<mark@townsley.net>  wrote:
>
>>
>> I think the consensus we had in the past BoFs and discussion in and
>> around this topic can be summed up as stating that homenet deliverables
>> will:
>>
>> - coexist with (existing) IPv4 protocols, devices, applications, etc.
>> - operate in a (future) IPv6-only home network in the absence of IPv4
>> - be IP-agnostic whenever possible
>>
>> In other words, anything we do for the IPv6 homenet cannot actively break
>> what's already running on IPv4. Also, trying to define what the IPv4 home
>> network should be has long reached a point of diminishing returns given
>> the effort in doing so coupled with our ability to significantly affect
>> what's already deployed. There's still hope we can help direct IPv6, as
>> such that is homenet's primary focus.  However, when we can define
>> something that is needed for IPv6 in a way that is also useful for IPv4
>> without making significant concessions, we should go ahead and do so.
>>
>> - Mark
>>
>>
>>
>> On Jun 30, 2011, at 9:25 AM, Mikael Abrahamsson wrote:
>>
>>> On Thu, 30 Jun 2011, Fernando Gont wrote:
>>>
>>>> My point was that, except for the mechanism for PD, I don't see a
>>>> substantial difference here that would e.g. prevent this from being
>>>> developed for IPv4 (in addition to IPv6). -- Yes, I know we need to
>>>> deploy IPv6... but I don't think you can expect people to get rid of
>>>> their *working* IPv4 devices... (i.e., not sure why any of this
>>>> functionality should be v6-only)
>>>
>>> Chaining NAT boxes already work. I also feel that we shouldn't put in a
>>> lot of work to develop IPv4 further, that focus should be put on IPv6.
>>>
>>>> I think this deserves a problem statement that clearly describes what
>>>> we expect to be able to do (but currently can't), etc. And, if this is
>>>> meant to be v6-only, state why v4 is excluded -- unless we're happy to
>>>> have people connect their IPv4-devices, and see that they cannot
>>>> communicate anymore.
>>>
>>> IPv4 should be excluded because it's a dead end, and we all know it.
>>> We're just disagreeing when it's going to die and how.
>>>
>>> --
>>> Mikael Abrahamsson    email: swmike@swm.pp.se
>>> _______________________________________________
>>> homegate mailing list
>>> homegate@ietf.org
>>> https://www.ietf.org/mailman/listinfo/homegate
>>
>> _______________________________________________
>> fun mailing list
>> fun@ietf.org
>> https://www.ietf.org/mailman/listinfo/fun
>
>
> This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
> _______________________________________________
> fun mailing list
> fun@ietf.org
> https://www.ietf.org/mailman/listinfo/fun
>

-- 
Stephen [kiwin] Palm   Ph.D.                          E:  palm@kiwin.com
Senior Technical Director                             T: +1-949-926-PALM
Broadcom Broadband Communications Group               F: +1-949-926-7256
Irvine, California                               W: http://www.kiwin.com
Secondary email accounts:  stephenpalm@alumni.uci.edu  palm@broadcom.com
s.palm@ieee.org  palm@itu.ch  spalm@cs.cmu.edu  palm@ics.t.u-tokyo.ac.jp


From mark@townsley.net  Thu Jun 30 08:14:06 2011
Return-Path: <mark@townsley.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A91BF11E818C; Thu, 30 Jun 2011 08:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u2MeOSs9cQ5Q; Thu, 30 Jun 2011 08:14:04 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7C7F011E8189; Thu, 30 Jun 2011 08:14:03 -0700 (PDT)
Received: by wyj26 with SMTP id 26so1856711wyj.31 for <multiple recipients>; Thu, 30 Jun 2011 08:14:02 -0700 (PDT)
Received: by 10.216.69.77 with SMTP id m55mr1905462wed.11.1309446842569; Thu, 30 Jun 2011 08:14:02 -0700 (PDT)
Received: from ams-townsley-8714.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id k84sm1187097weq.46.2011.06.30.08.14.00 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 30 Jun 2011 08:14:01 -0700 (PDT)
Subject: Re: [homegate] HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <4E0C8E6C.3020205@broadcom.com>
Date: Thu, 30 Jun 2011 17:13:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <518785F9-1FB4-456F-B4B4-26A97F9BC2F1@townsley.net>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar> <alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se> <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net> <4E0C8E6C.3020205@broadcom.com>
To: "Stephen [kiwin] PALM" <palm@broadcom.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Thu, 30 Jun 2011 08:14:15 -0700
Cc: IETF Discussion <ietf@ietf.org>, "fun@ietf.org" <fun@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 15:14:06 -0000

On Jun 30, 2011, at 4:55 PM, Stephen [kiwin] PALM wrote:

> Thanks Mark for stating that.
> It would really be helpful if this type of text is included in the =
description/charter.
> The lack of of this information in the recently distributed material =
caused
> several immediate allergic reactions...

I'm happy to include it in the next rev.

- Mark

>=20
> regards, kiwin
>=20
> On 6/30/2011 2:57 AM, Mark Townsley wrote:
>>=20
>> I think the consensus we had in the past BoFs and discussion in and =
around this topic can be summed up as stating that homenet deliverables =
will:
>>=20
>> - coexist with (existing) IPv4 protocols, devices, applications, etc.
>> - operate in a (future) IPv6-only home network in the absence of IPv4
>> - be IP-agnostic whenever possible
>>=20
>> In other words, anything we do for the IPv6 homenet cannot actively =
break what's already running on IPv4. Also, trying to define what the =
IPv4 home network should be has long reached a point of diminishing =
returns given the effort in doing so coupled with our ability to =
significantly affect what's already deployed. There's still hope we can =
help direct IPv6, as such that is homenet's primary focus.  However, =
when we can define something that is needed for IPv6 in a way that is =
also useful for IPv4 without making significant concessions, we should =
go ahead and do so.
>>=20
>> - Mark
>>=20
>>=20
>>=20
>> On Jun 30, 2011, at 9:25 AM, Mikael Abrahamsson wrote:
>>=20
>>> On Thu, 30 Jun 2011, Fernando Gont wrote:
>>>=20
>>>> My point was that, except for the mechanism for PD, I don't see a =
substantial difference here that would e.g. prevent this from being =
developed for IPv4 (in addition to IPv6). -- Yes, I know we need to =
deploy IPv6... but I don't think you can expect people to get rid of =
their *working* IPv4 devices... (i.e., not sure why any of this =
functionality should be v6-only)
>>>=20
>>> Chaining NAT boxes already work. I also feel that we shouldn't put =
in a lot of work to develop IPv4 further, that focus should be put on =
IPv6.
>>>=20
>>>> I think this deserves a problem statement that clearly describes =
what we expect to be able to do (but currently can't), etc. And, if this =
is meant to be v6-only, state why v4 is excluded -- unless we're happy =
to have people connect their IPv4-devices, and see that they cannot =
communicate anymore.
>>>=20
>>> IPv4 should be excluded because it's a dead end, and we all know it. =
We're just disagreeing when it's going to die and how.
>>>=20
>>> --
>>> Mikael Abrahamsson    email: swmike@swm.pp.se
>>> _______________________________________________
>>> homegate mailing list
>>> homegate@ietf.org
>>> https://www.ietf.org/mailman/listinfo/homegate
>>=20
>> _______________________________________________
>> homegate mailing list
>> homegate@ietf.org
>> https://www.ietf.org/mailman/listinfo/homegate
>>=20
>=20
> --=20
> Stephen [kiwin] Palm   Ph.D.                          E:  =
palm@kiwin.com
> Senior Technical Director                             T: =
+1-949-926-PALM
> Broadcom Broadband Communications Group               F: =
+1-949-926-7256
> Irvine, California                               W: =
http://www.kiwin.com
> Secondary email accounts:  stephenpalm@alumni.uci.edu  =
palm@broadcom.com
> s.palm@ieee.org  palm@itu.ch  spalm@cs.cmu.edu  =
palm@ics.t.u-tokyo.ac.jp
>=20
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate


From moore@network-heretics.com  Thu Jun 30 08:46:50 2011
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 2F45C11E8177; Thu, 30 Jun 2011 08:46:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.539
X-Spam-Level: 
X-Spam-Status: No, score=-3.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JLLNMY-h24aN; Thu, 30 Jun 2011 08:46:49 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id AFEB211E8181; Thu, 30 Jun 2011 08:46:49 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 50A9020941; Thu, 30 Jun 2011 11:46:49 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Thu, 30 Jun 2011 11:46:49 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=+8MO4cKZL1+XzoKUx/GM7OkLYEA=; b=ugUmrrMIg9UoVAXKG+QeaSDsGmfyKNYczHldeMrL6XhliNQ5nLuV1htPi5a/XssmQJ2PubGuPSaIlGtzPGiLF+Wwzxlet94qz10WHIkgW5MXV6kdINuchSGn/w+cvYJ5SCiqMvdsccw/v6/7Nsb4LBVGOrVRLwvf7oFOdcCG0AY=
X-Sasl-enc: UXiQAhwqbCvOK/+zWoOs9kiiTeDIgy8y/n3DbtmuTcLN 1309448808
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 6E82140829D; Thu, 30 Jun 2011 11:46:48 -0400 (EDT)
Subject: Re: [homegate] HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net>
Date: Thu, 30 Jun 2011 11:46:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F995E91-9853-4018-91F0-0699E1A7A06F@network-heretics.com>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar> <alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se> <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1084)
Cc: fun@ietf.org, homegate@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 15:46:50 -0000

On Jun 30, 2011, at 5:57 AM, Mark Townsley wrote:

>=20
> I think the consensus we had in the past BoFs and discussion in and =
around this topic can be summed up as stating that homenet deliverables =
will:
>=20
> - coexist with (existing) IPv4 protocols, devices, applications, etc.
> - operate in a (future) IPv6-only home network in the absence of IPv4
> - be IP-agnostic whenever possible

I'd like for this group to relax the "wherever possible" bit, so as to =
not preclude solutions where IPv6 can do a better job than IPv4.

IPv4 is a dinosaur gasping for its last breaths.

Keith



From fernando.gont.netbook.win@gmail.com  Thu Jun 30 08:59:26 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF12D11E8188; Thu, 30 Jun 2011 08:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.447
X-Spam-Level: 
X-Spam-Status: No, score=-3.447 tagged_above=-999 required=5 tests=[AWL=0.152,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQgsYRWH+3a0; Thu, 30 Jun 2011 08:59:26 -0700 (PDT)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3959011E807E; Thu, 30 Jun 2011 08:59:26 -0700 (PDT)
Received: by yie30 with SMTP id 30so1193451yie.31 for <multiple recipients>; Thu, 30 Jun 2011 08:59:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=YOO3Wuijr9NTfgIPEUoKX6tKNH9WXm6nIFmX6b2ENPY=; b=NInN7EMNRhlt3Rf5rcqSHrWptf36C+2p1Ca39Y470ixkc8Jx8M3sGD86a/JjU/XEn0 uuMF+DLPHSiMQ/sHpD4aLqodYcQpTNbqc5VCKfN10D0dF/+Lw4oCUSbDxZDg8zgVP9Xd x8UevZOThQqUGj36hxKuhPzdEEjmTtEbV92Qs=
Received: by 10.101.202.7 with SMTP id e7mr1923410anq.88.1309449565636; Thu, 30 Jun 2011 08:59:25 -0700 (PDT)
Received: from [192.168.123.103] ([190.48.255.131]) by mx.google.com with ESMTPS id c19sm2093868anm.15.2011.06.30.08.59.22 (version=SSLv3 cipher=OTHER); Thu, 30 Jun 2011 08:59:24 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4E0C9D58.30002@gont.com.ar>
Date: Thu, 30 Jun 2011 12:59:20 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: [fun] [homegate] HOMENET working group proposal
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar>	<alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se>	<4E0C1CF8.7090601@gont.com.ar>	<alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se>	<558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net> <0F995E91-9853-4018-91F0-0699E1A7A06F@network-heretics.com>
In-Reply-To: <0F995E91-9853-4018-91F0-0699E1A7A06F@network-heretics.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>, Mark Townsley <mark@townsley.net>, fun@ietf.org, homegate@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 15:59:27 -0000

On 06/30/2011 12:46 PM, Keith Moore wrote:
> I'd like for this group to relax the "wherever possible" bit, so as to not preclude solutions where IPv6 can do a better job than IPv4.
> 
> IPv4 is a dinosaur gasping for its last breaths.

Just curious: when you expect IPv4 to be gone? (including "gone" from
home and enterprise networks)

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From moore@network-heretics.com  Thu Jun 30 09:05:46 2011
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 4B34311E81C2; Thu, 30 Jun 2011 09:05:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.549
X-Spam-Level: 
X-Spam-Status: No, score=-3.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IDfl0bUwbLtv; Thu, 30 Jun 2011 09:05:45 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 6C94C11E8081; Thu, 30 Jun 2011 09:05:45 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 1E1DF20C58; Thu, 30 Jun 2011 12:05:45 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Thu, 30 Jun 2011 12:05:45 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=PLp8jPGs7cs5EmdUYPKcAQjl09Q=; b=MNUxzU7kN8q6IksZtStRL71GVwJPSlTuoMAJ9oWPttHFGUtuSV740///+kyOQdHnULCcZddiinwSSeXWOBWKMhQqyVDFAw+a2BghFSw0ujm0UJ20BiPC1KRzAPGRo9TgbgcGxBjE61KDekDglAUd/lsGGBg20kIcaULTVBHTLz4=
X-Sasl-enc: +uAHtUdj3Hecqrj0fdhwwlPHbLKo5rTPiCZGBuCiSm+i 1309449944
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id F21B540923A; Thu, 30 Jun 2011 12:05:43 -0400 (EDT)
Subject: Re: [fun] [homegate] HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4E0C9D58.30002@gont.com.ar>
Date: Thu, 30 Jun 2011 12:05:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE4CFDCA-9EFD-4A86-95CA-75F83F9C9917@network-heretics.com>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar>	<alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se>	<4E0C1CF8.7090601@gont.com.ar>	<alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se>	<558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net> <0F995E91-9853-4018-91F0-0699E1A7A06F@network-heretics.com> <4E0C9D58.30002@gont.com.ar>
To: Fernando Gont <fernando@gont.com.ar>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>, Mark Townsley <mark@townsley.net>, fun@ietf.org, homegate@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 16:05:46 -0000

On Jun 30, 2011, at 11:59 AM, Fernando Gont wrote:

> On 06/30/2011 12:46 PM, Keith Moore wrote:
>> I'd like for this group to relax the "wherever possible" bit, so as =
to not preclude solutions where IPv6 can do a better job than IPv4.
>>=20
>> IPv4 is a dinosaur gasping for its last breaths.
>=20
> Just curious: when you expect IPv4 to be gone? (including "gone" from
> home and enterprise networks)

I think it will be used for email and the web for at least ten years.
I think there will be a need to talk to legacy IPv4-only devices for =
about that long, perhaps a bit longer.
But IPv4 is already difficult to use for a great many applications, and =
it will only get worse with the imposition of LSN.  A home network that =
only supports IPv4, or which makes IPv6 as crippled as IPv4, is not a =
desirable goal.

Keith


From mrex@sap.com  Thu Jun 30 09:14:33 2011
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 77BC111E821D for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 09:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.199
X-Spam-Level: 
X-Spam-Status: No, score=-10.199 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2E5F4-s5s1ze for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 09:14:32 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id D2C0311E8221 for <ietf@ietf.org>; Thu, 30 Jun 2011 09:14:31 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p5UGEJtZ005459 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 30 Jun 2011 18:14:24 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201106301614.p5UGEImf009011@fs4113.wdf.sap.corp>
Subject: Re: HOMENET working group proposal
To: moore@network-heretics.com (Keith Moore)
Date: Thu, 30 Jun 2011 18:14:18 +0200 (MEST)
In-Reply-To: <F01354D1-3624-48D5-A6D2-81D4A2C51BE2@network-heretics.com> from "Keith Moore" at Jun 30, 11 08:16:53 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: 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, 30 Jun 2011 16:14:33 -0000

Keith Moore wrote:
> 
> Perimeter security of some kind is probably appropriate.

Not just appropriate, it is an indispensible prerequisite.

>
> That doesn't mean that it has to look like firewalls do today.

Not necessarily.  But any sensible security requirements and
primarily the requirement of the smallest possible attack surface
amount to it.  If it has to walk like a duck and quack like a duck,
just use a duck instead of trying to retrain a goat.


>
> For one thing, users shouldn't have to muck with the details of
> which ports to allow.

_Unless_ they want to make a service accessible to the internet
with software produced by folks or companys which prioritize
features and merchantability far over security, quality and robustness
-- which is to say 99.999% of the available software.


>
> And the idea that every application server on a home network needs
> to negotiate access through some application-specific external server
> (as is generally the case with NATs today) is also ridiculous.

No, it is a simple technical problem that can be solved with a few
lines of extra code for those few applications where it acutally matters.


Just as democracy is the worst form of government except all the
others that have been tried (attributed to Winston Churchill).


Home networks should ALWAYS be NATed to the internet, so that it is
not possible to provide a simple policy switch to make everything on
the home network fully accessible from the internet, because any
such switch will inevitably be abused much more often by the bad,
poor novices and ignorant than sensibly employed by the needy and
security conscious.

 
Black-listing doesn't provide security, it always amounts to
obscurity and security theater.

Anything else than whitelisting is irresponsible security-wise.
And dynamic whitelisting (the motivation behind NAT-PMP) is even better.


Privacy is another issue.  The current custom here in Germany is that
the external IP-Address on your home gateway is dynamically assigned,
it changes on every new assignment, i.e. when the DSL connection
is reestablished after a carrier loss or cable disconnect,
whenever you ask your DSL router for it, and at least once
every 24 hours.

While this does not provide perfect privacy protection, it is a
good start.  For many internet usage scenarios, the use of a
longterm static IP-Address for home users would be completely
irresponsible with respect to data privacy, and would likely make
any logging of client IP-Addresses on servers unconditionally
illegal in European countries.


With respect to privacy, anything besides striclty voluntary,
well-informed opt-in and anytime easy opt-out again, is a non-starter.


No application, unless it absolutely, positively and unavoidably needs
to should use a fixed/static address without the affected folks
having provided conscious and clear consent.


-Martin

From moore@network-heretics.com  Thu Jun 30 09:34:17 2011
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 AFC1211E8244 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 09:34:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.556
X-Spam-Level: 
X-Spam-Status: No, score=-3.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nF0IbR20xuZc for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 09:34:16 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id BB84811E8085 for <ietf@ietf.org>; Thu, 30 Jun 2011 09:34:16 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 68CC1208DE; Thu, 30 Jun 2011 12:34:16 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute3.internal (MEProxy); Thu, 30 Jun 2011 12:34:16 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=b12MJMDo62isi+Gr0aH92F1clgg=; b=RI0W8CuZ2IPAiOI7DeTDBarLYq83tbQCFiM0j8sAnSOEtRMpHNCgBq1u7ozPo0Db2iS0tnxZzB5OqWUNxL7PnWB0UAUyKK2kPnQccNW0HjfkXCeG8mxVTtihKpDZqqWCJuONS2sKOLOmEx3YNIdxzNhZmeSL5e6DQSCywUKbj2k=
X-Sasl-enc: w50J6I4cJCesPFSHZkdsli8SLsqNknqgDIVscPn7/tOf 1309451655
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 3054240978C; Thu, 30 Jun 2011 12:34:15 -0400 (EDT)
Subject: Re: HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <201106301614.p5UGEImf009011@fs4113.wdf.sap.corp>
Date: Thu, 30 Jun 2011 12:33:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E525ABC3-F450-43D4-BD2A-0F798FE66F19@network-heretics.com>
References: <201106301614.p5UGEImf009011@fs4113.wdf.sap.corp>
To: mrex@sap.com
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 16:34:17 -0000

On Jun 30, 2011, at 12:14 PM, Martin Rex wrote:

> Keith Moore wrote:
>>=20
>> Perimeter security of some kind is probably appropriate.
>=20
> Not just appropriate, it is an indispensible prerequisite.

I could take some issue with the indispensable part, because I also =
think that PCs are dinosaurs.  For a sufficiently small home network, =
there's a point where a firewall could provide very little marginal gain =
in exchange for the complexity and fragility that come with it. =20

I do think that some sort of perimeter security should be part of a home =
network architecture, but I'd strongly object to the idea that hosts and =
appliances don't need to be secure because they can expect a firewall to =
provide their security for them.

>> That doesn't mean that it has to look like firewalls do today.
>=20
> Not necessarily.  But any sensible security requirements and
> primarily the requirement of the smallest possible attack surface
> amount to it.=20

The mostly commonly kinds of firewalls used today do anything but that.

>> For one thing, users shouldn't have to muck with the details of
>> which ports to allow.
>=20
> _Unless_ they want to make a service accessible to the internet
> with software produced by folks or companys which prioritize
> features and merchantability far over security, quality and robustness
> -- which is to say 99.999% of the available software.

a.  Maybe part of what HOMENET should do is establish security =
expectations for appliances and applications intended to provide =
services from such an environment.
b.  Get out of the habit of thinking that using IP addresses and port =
numbers as authentication tokens is in any way sane or secure.

>> And the idea that every application server on a home network needs
>> to negotiate access through some application-specific external server
>> (as is generally the case with NATs today) is also ridiculous.
>=20
> No, it is a simple technical problem that can be solved with a few
> lines of extra code for those few applications where it acutally =
matters.

That's a completely incorrect and ridiculous statement.

> Home networks should ALWAYS be NATed to the internet, so that it is
> not possible to provide a simple policy switch to make everything on
> the home network fully accessible from the internet, because any
> such switch will inevitably be abused much more often by the bad,
> poor novices and ignorant than sensibly employed by the needy and
> security conscious.

Another completely ridiculous statement.  You're trying to cripple home =
networks.  More generally, you're arguing for the perpetuation of hacks =
that never did work very well, instead of leaving room for better =
mechanisms to be developed.

> Anything else than whitelisting is irresponsible security-wise.
> And dynamic whitelisting (the motivation behind NAT-PMP) is even =
better.

Whitelisting might be fine.  Basing that whitelist on port numbers and =
IP addresses is insane.  And users need better ways to manage the =
whitelist than typing in arcane information that they don't understand =
anyway for each service that they want to permit.

> Privacy is another issue.  The current custom here in Germany is that
> the external IP-Address on your home gateway is dynamically assigned,
> it changes on every new assignment, i.e. when the DSL connection
> is reestablished after a carrier loss or cable disconnect,
> whenever you ask your DSL router for it, and at least once
> every 24 hours.
>=20
> While this does not provide perfect privacy protection, it is a
> good start.  For many internet usage scenarios, the use of a
> longterm static IP-Address for home users would be completely
> irresponsible with respect to data privacy, and would likely make
> any logging of client IP-Addresses on servers unconditionally
> illegal in European countries.

Dynamically assigned addresses don't provide any privacy protection if =
there's some service (like Dynamic DNS) that always points to the =
current address.  Again, you're trying to perpetuate brain damage.

> With respect to privacy, anything besides striclty voluntary,
> well-informed opt-in and anytime easy opt-out again, is a non-starter.

That much I agree with.  We disagree about the mechanisms.

> No application, unless it absolutely, positively and unavoidably needs
> to should use a fixed/static address without the affected folks
> having provided conscious and clear consent.

Ridiculous.

Keith


From moore@network-heretics.com  Thu Jun 30 09:36:58 2011
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 1D12511E8255; Thu, 30 Jun 2011 09:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.561
X-Spam-Level: 
X-Spam-Status: No, score=-3.561 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RLizpg-a-mYA; Thu, 30 Jun 2011 09:36:57 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id C2D5111E8247; Thu, 30 Jun 2011 09:36:55 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.messagingengine.com (Postfix) with ESMTP id 70064206A8; Thu, 30 Jun 2011 12:36:55 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute5.internal (MEProxy); Thu, 30 Jun 2011 12:36:55 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=tTBwDGnemCORVN38Co+zkkB4Ezs=; b=Vh03ebhwSaCkchOF/nVJaQTrgwflglwy4jZkQ20PXqMEHRqTXFbDu+/Zc0UzK+1lUEFCYOJHQJldFpwMv4nP4B6Jcp1C1hpr8GxFxVx0QdVW2wuoUhmaM3/8CRnX04LFT643mG9kJrR7EH+3acdYDpn4fDl/8tanIlzHyYiAy6g=
X-Sasl-enc: 8/SypNtsIltWK8Y/YUYnihNlVq1/HhCoEnJWvsho6SS4 1309451814
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 61B16409DFC; Thu, 30 Jun 2011 12:36:54 -0400 (EDT)
Subject: Re: [homegate] HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <780C3063-AD82-46F3-874A-C4E1E61EE508@townsley.net>
Date: Thu, 30 Jun 2011 12:36:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC5C1553-38E9-4853-9AEA-61FC34FC5EC8@network-heretics.com>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar> <alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se> <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net> <0F995E91-9853-4018-91F0-0699E1A7A06F@network-heretics.com> <780C3063-AD82-46F3-874A-C4E1E61EE508@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>, fun@ietf.org, homegate@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 Jun 2011 16:36:58 -0000

On Jun 30, 2011, at 12:33 PM, Mark Townsley wrote:
>>>=20
>>> I think the consensus we had in the past BoFs and discussion in and =
around this topic can be summed up as stating that homenet deliverables =
will:
>>>=20
>>> - coexist with (existing) IPv4 protocols, devices, applications, =
etc.
>>> - operate in a (future) IPv6-only home network in the absence of =
IPv4
>>> - be IP-agnostic whenever possible
>>=20
>> I'd like for this group to relax the "wherever possible" bit, so as =
to not preclude solutions where IPv6 can do a better job than IPv4.
>=20
> Yes, and I think that IPv6 should naturally do a better job than IPv4 =
in the cases where it can.=20
>=20
> My original mail had this restatement of the above, which I think gets =
closer to what you want:
>=20
>>> However, when we can define something that is needed for IPv6 in a =
way that is also useful for IPv4 without making significant concessions, =
we should go ahead and do so.

when the group can define something that is useful in IPv6, it shouldn't =
matter whether it's also useful for IPv4.

please don't constrain home networks to work only within the confines of =
IPv4 brain damage.

Keith


From touch@isi.edu  Thu Jun 30 10:24:50 2011
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 B1CEB11E8285; Thu, 30 Jun 2011 10:24:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.099
X-Spam-Level: 
X-Spam-Status: No, score=-105.099 tagged_above=-999 required=5 tests=[AWL=1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BWZpac55vfda; Thu, 30 Jun 2011 10:24:49 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id B1B6611E8284; Thu, 30 Jun 2011 10:24:40 -0700 (PDT)
Received: from [75.217.203.236] (236.sub-75-217-203.myvzw.com [75.217.203.236]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p5UHNlGa006404 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 30 Jun 2011 10:23:57 -0700 (PDT)
Message-ID: <4E0CB121.1050004@isi.edu>
Date: Thu, 30 Jun 2011 10:23:45 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, IETF discussion list <ietf@ietf.org>, karp@ietf.org, draft-ietf-karp-design-guide@tools.ietf.org
Subject: TSVDIR review of draft-ietf-karp-design-guide
References: <4E0C0FB3.8080602@isi.edu>
In-Reply-To: <4E0C0FB3.8080602@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 17:24:50 -0000

(resending cc'd to the KARP WG rather than SIDR; please respond to this 
post instead)

Hi, all,

I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the
document's authors for their information and to allow them to address
any issues raised. The authors should consider this review together with
any other last-call comments they receive. Please always CC
tsv-dir@ietf.org if you reply to or forward this review.

The document discusses design issues for protecting routing protocols.

The most problematic issue is the term "on the wire" which is used in
various contexts to imply physical, link, network, or transport protocol
layers. This needs to be clarified.

Transport protection appears to be a potential focus of the design
guide, but is inconsistently discussed. In some cases, transport issues
are raised (TCP issues for BGP); in other cases, the relevant transport
isn't even noted (e.g., RIP over UDP). This should be corrected throughout.

It is important for this document to be more clear on what layers were
in scope for the design guide, and what guidelines are being given with
respect to those layers, even in a general sense.

Further information on these issues is provided below. There is
additional feedback provided below ("other notes") as a suggestion.

I hope this feedback will be useful to the authors, and will be glad to
provide further assistance either on- or off-list as useful.

Joe

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

>please note that some of these comments apply to the
draft-ietf-karp-threats-reqs-03 as well; further, there is duplicate
text that is not needed in both these docs. FWIW, the threats-reqs doc
has many issues as well which are not addressed here.

Of the four issues noted in the intro, the last uses the ambiguous term
"on the wire". This is confusing in both this and the threats doc, and
many times both docs us the term 'wire' or 'bits', all of which would
typically indicate either the link layer or the physical media or both.
There is no rationale for this focus in either document.

The threats document should more clearly indicate *why* protection
beyond the routing messages (the SIDR work) is needed, and what the
expected threats are. These appear to be:
- routing protocols often rely on information in the
link, transport or network packets
- routing protocols often rely on properties of transport
connections to infer reachability, e.g., if a TCP connection
cannot stay up, then the endpoint's routes should not be
considered reachable
(if there are other reasons, please clarify) The threats then appear to be:
- spoofing link/network addresses
- spoofing transport ports
- disrupting the TCP connection (where TCP is used)
Note that falsification (as noted in the threats doc) is not in this
list since it is (IMO) clearly the purvue of the SIDR work. Also out of
scope should have been any of the interference issues, unless the
*performance* of the TCP connection needs protection.

This doc then may need to protect the link or network protocol ID and/or
transport protocol from interference. This should be more clearly stated
in the threats doc, IMO, and the term "on the wire" should be avoided.

The discussion of multicast should note that multicast can be
implemented by broadcast, true multicast, or serial unicast; these may
have different security requirements.

The document should more clearly indicate the underlying protocol used
as a key property of a routing protocol, especially because (as above)
this document appears to focus on guidelines for link, network, and/or
transport protocols. E.g., the discussion on OSPF, RIP, and ISIS should
more clearly indicate that, e.g., RIP runs over UDP, OSPF runs over IP
directly, and IS-IS runs natively over L2. Similar info would be useful
for BFD, RSVP, etc.

The document is unclear on its overall advice, other than a somewhat
general description of "do good stuff". E.g., it notes:

Not all routing protocol authentication mechanisms provide
support for replay attacks, and the design teams should
identify such authentication mechanisms and work on them so
that this can get fixed. The design teams must look at the
protocols that they are working on and see if packets captured
from the previous/stale sessions can be replayed.

More specific advice would be, e.g.:

Not all routing protocol authentication mechanisms provide
protection from replay attacks. Such deficiencies should
be addressed at that layer, rather than having design
teams conclude that such systems thus require lower layer
(transport, network, or link) protection from replays.

----
Other notes:

Overall, this document would benefit from a revision focused on
clarification, where the focus of each section and advice were made more
clear.

The abstract is excessively detailed and doesn't get to the point until
"This document...". Everything preceding that should be removed, and the
result should be appended with a few sentences summarizing the
recommendations.

The intro refers in a lot of detail to the motivation for the doc (some
of which may be historically important but is not relevant to the doc
itself), but only briefly notes the KARP threats document. This
document's observations should be motivated by addressing those threats,
so it would be important to summarize them in this doc in the intro as
context.

The summary of RFC 4984 discusses four tightening steps as if they were
indicated by that RFC; that RFC only suggests tightening itself. This
doc should more clearly indicate that "The WG identified four...".

-----








From jhw@apple.com  Thu Jun 30 11:21:21 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F33F09E800D; Thu, 30 Jun 2011 11:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wfIedxz3ddvX; Thu, 30 Jun 2011 11:21:20 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6993E9E801B; Thu, 30 Jun 2011 11:21:20 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LNM00JDQ8AP3EW0@mail-out.apple.com>; Thu, 30 Jun 2011 11:21:14 -0700 (PDT)
X-AuditID: 1180711d-b7c5fae000001427-ef-4e0cbe816c23
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id 3D.87.05159.18EBC0E4; Thu, 30 Jun 2011 11:20:49 -0700 (PDT)
Received: from [17.193.13.64] (unknown [17.193.13.64]) by cardamom.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LNM00K208BDZS70@cardamom.apple.com>; Thu, 30 Jun 2011 11:21:13 -0700 (PDT)
Subject: Re: [homegate] HOMENET working group proposal
From: james woodyatt <jhw@apple.com>
In-reply-to: <DC5C1553-38E9-4853-9AEA-61FC34FC5EC8@network-heretics.com>
Date: Thu, 30 Jun 2011 11:21:13 -0700
Message-id: <5C263F1C-A180-4EFC-A44F-3E867C6CF4DC@apple.com>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar> <alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se> <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net> <0F995E91-9853-4018-91F0-0699E1A7A06F@network-heretics.com> <780C3063-AD82-46F3-874A-C4E1E61EE508@townsley.net> <DC5C1553-38E9-4853-9AEA-61FC34FC5EC8@network-heretics.com>
To: fun@ietf.org
X-Mailer: Apple Mail (2.1244.3)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNLMWRmVeSWpSXmKPExsUiON1OVbdxH4+fwc85KhaPD8xit3i2cT6L A5PHkiU/mQIYo7hsUlJzMstSi/TtErgyzl49yV7QwlEx6c0O5gbGfWxdjJwcEgImEtdevWCC sMUkLtxbDxTn4hASaGWSaOh6xAiS4BUQlPgx+R5LFyMHB7OAvMTB87IgYWYBLYnvj1pZIOrb mSS29J9mAUkIC5hJdF39wQxiswmoSHy7fBdsAaeAh8TKpp/sIDaLgKrEisYONohByhJvzvxn gthlI7Fx6kt2iKGHmCVuP+gGaxAREJDYOe0OO8Sl8hKLWz4zTmAUmIXkvlkI981Cct8CRuZV jIJFqTmJlYbGeokFBTmpesn5uZsYQUHYUCi7g3H/T/5DjAIcjEo8vCcn8vgJsSaWFVfmHmKU 4GBWEuFdVQ0U4k1JrKxKLcqPLyrNSS0+xCjNwaIkzhuTye0nJJCeWJKanZpakFoEk2Xi4JRq YAxNOas+x2J2TMyEP7P/Hzh32Y3h3sfWY5I7l1V5twaJeK7ccuWAUZL3EvaMhNWWu5Vqv8+q eG89V0fI8cmm8om7bX1OJj5XUOI1mXnt9pne7yJrTz67y6sWOXdL/x3LBpbQC0fLp/AUnhaN 9K96FsOimH57lQyzxMl3W6K3Pfr0fN3Nde6x134rsRRnJBpqMRcVJwIAlMclgj4CAAA=
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, 30 Jun 2011 18:21:21 -0000

On Jun 30, 2011, at 09:36 , Keith Moore wrote:
> 
> when the group can define something that is useful in IPv6, it shouldn't matter whether it's also useful for IPv4.
> please don't constrain home networks to work only within the confines of IPv4 brain damage.

I suspect what Mr. Townsley and Mr. Arkko are aiming at here is that if FUN can come up with a scheme to make routed home subnetworks work with delegated IPv6 prefixes, then it is probably not too far-fetched that the same scheme could be trivially extended for assigning IPv4 subnets from the RFC 1918 private realm to support dual-stack routed home subnetworks.

I'm not expecting home networks to be able to run IPv6-only with the IPv4 Internet mapped to 64:ff9b::/96 through NAT64 for several more years yet.  There's a whole crapload of legacy IPv4-only devices in the average home theater system today that nobody wants to cut off from the Internet just yet.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From mohta@necom830.hpcl.titech.ac.jp  Thu Jun 30 14:32:50 2011
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 2318E11E82EC for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 14:32:50 -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=[AWL=-0.000,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9pGA-YQ3rN59 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 14:32:49 -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 CC2E411E82EB for <ietf@ietf.org>; Thu, 30 Jun 2011 14:32:48 -0700 (PDT)
Received: (qmail 71075 invoked from network); 30 Jun 2011 21:45:00 -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; 30 Jun 2011 21:45:00 -0000
Message-ID: <4E0CEB49.70506@necom830.hpcl.titech.ac.jp>
Date: Fri, 01 Jul 2011 06:31:53 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [fun] [homegate] HOMENET working group proposal
References: <CA31FD28.4B0C%jason.weil@twcable.com>
In-Reply-To: <CA31FD28.4B0C%jason.weil@twcable.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: Thu, 30 Jun 2011 21:32:50 -0000

Weil, Jason wrote:

> Overall I like the concept of not breaking core IPv4 functionality while
> focussing all new functionality to IPv6.

Remember that IPv6 became unusably complex by impossible attempts
to add new functionality not available with IPv4, which implies
that there is no such thing as new functionality of IPv6.

E.g. DHCPv4 is better than not-really-stateless configuration
by ND.

Fernando Gont wrote:

> Just curious: when you expect IPv4 to be gone? (including "gone" from
> home and enterprise networks)

It will be long after IPv6 gone (excluding "gone" from home and
enterprise networks, because it is not really there).

						Masataka Ohta

From marka@isc.org  Thu Jun 30 16:20:49 2011
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 77D3411E8122; Thu, 30 Jun 2011 16:20:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.685
X-Spam-Level: 
X-Spam-Status: No, score=-2.685 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1egcnvQxQK0F; Thu, 30 Jun 2011 16:20:48 -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 5BFC111E810E; Thu, 30 Jun 2011 16:20:48 -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 "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 5DF44C94CF; Thu, 30 Jun 2011 23:20:39 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (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 E8617216C82; Thu, 30 Jun 2011 23:20:38 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 860E911532DE; Fri,  1 Jul 2011 09:20:35 +1000 (EST)
To: james woodyatt <jhw@apple.com>
From: Mark Andrews <marka@isc.org>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar> <alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se> <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net> <0F995E91-9853-4018-91F0-0699E1A7A06F@network-heretics.com> <780C3063-AD82-46F3-874A-C4E1E61EE508@townsley.net> <DC5C1553-38E9-4853-9AEA-61FC34FC5EC8@network-heretics.com> <5C263F1C-A180-4EFC-A44F-3E867C6CF4DC@apple.com>
Subject: Re: [fun] [homegate] HOMENET working group proposal
In-reply-to: Your message of "Thu, 30 Jun 2011 11:21:13 MST." <5C263F1C-A180-4EFC-A44F-3E867C6CF4DC@apple.com>
Date: Fri, 01 Jul 2011 09:20:35 +1000
Message-Id: <20110630232035.860E911532DE@drugs.dv.isc.org>
Cc: fun@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2011 23:20:49 -0000

In message <5C263F1C-A180-4EFC-A44F-3E867C6CF4DC@apple.com>, james woodyatt wri
tes:
> On Jun 30, 2011, at 09:36 , Keith Moore wrote:
> > 
> > when the group can define something that is useful in IPv6, it shouldn't ma
> tter whether it's also useful for IPv4.
> > please don't constrain home networks to work only within the confines of IP
> v4 brain damage.
> 
> I suspect what Mr. Townsley and Mr. Arkko are aiming at here is that if FUN c
> an come up with a scheme to make routed home subnetworks work with delegated 
> IPv6 prefixes, then it is probably not too far-fetched that the same scheme c
> ould be trivially extended for assigning IPv4 subnets from the RFC 1918 priva
> te realm to support dual-stack routed home subnetworks.
> 
> I'm not expecting home networks to be able to run IPv6-only with the IPv4 Int
> ernet mapped to 64:ff9b::/96 through NAT64 for several more years yet.  There
> 's a whole crapload of legacy IPv4-only devices in the average home theater s
> ystem today that nobody wants to cut off from the Internet just yet.

I'm expecting home nets to be dual stacked for 10+ years after IPv6
is common to the home (2-5) years.  If the home gateway has DS-Lite
support then that provides a better solution than NAT 444.  It also
continues to work when the home net goes IPv6 only with the home
gateway passing on the DS-Lite parameters from the ISP.

Consumer electronics lasts 10+ years.  I'm still using my DOCSIS
1.0 modem 8+ years.  My router hardware is 13+ years old, the
software is newer and is the 6in4 tunnel end point.  I've got TV's
of similar vintage.

> --
> james woodyatt <jhw@apple.com>
> member of technical staff, core os networking
> 
> 
> 
> _______________________________________________
> fun mailing list
> fun@ietf.org
> https://www.ietf.org/mailman/listinfo/fun
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From mrex@sap.com  Thu Jun 30 16:46:15 2011
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 6AF0211E82EC for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 16:46:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.669
X-Spam-Level: 
X-Spam-Status: No, score=-9.669 tagged_above=-999 required=5 tests=[AWL=-0.412, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wwWHsS3KJ3ch for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 16:46:14 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 74ADE11E80BF for <ietf@ietf.org>; Thu, 30 Jun 2011 16:46:14 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p5UNkCVi024896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 1 Jul 2011 01:46:12 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201106302346.p5UNkCgp005000@fs4113.wdf.sap.corp>
Subject: Re: HOMENET working group proposal
To: moore@network-heretics.com (Keith Moore)
Date: Fri, 1 Jul 2011 01:46:12 +2600 (MEST)
In-Reply-To: <3597BE26-F405-4D02-AE22-461635453FCF@network-heretics.com> from "Keith Moore" at Jun 30, 11 01:26:17 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: 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, 30 Jun 2011 23:46:15 -0000

Keith Moore wrote:
> 
> On Jun 30, 2011, at 1:09 AM, Martin Rex wrote:
> 
> (a bunch of stuff in defense of NAT)
> 
> Rather than having another of an endless series of discussions about
> the merits of NAT or lack thereof, can we just agree that it should
> not be pre-ordained that this WG should assume NAT as a solution?

You absolutely want to have fairly fixed addresses within
your home network, and you absolutely want to have a short-lived
ephemeral IP-Address assigned on your internet side of your
home gateway for the purpose of privacy.

Otherwise the number of very unpleasant surprises, including
stuff like this:

   http://www.theregister.co.uk/2011/06/30/xbox_swat_police_rait/

is going to become quite popular.  And that is really among the
mild unpleasant things if every bit that floats in and out
your internet gatway has your name stamped on it visibly
to everyone.


-Martin

From jhw@apple.com  Thu Jun 30 17:09:43 2011
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC6B21F88B8 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 17:09:43 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7w6c9L470E-d for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 17:09:42 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id C9A8021F8827 for <ietf@ietf.org>; Thu, 30 Jun 2011 17:09:41 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay16.apple.com ([17.128.113.55]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTP id <0LNM00FI8OEB0O71@mail-out.apple.com> for ietf@ietf.org; Thu, 30 Jun 2011 17:09:41 -0700 (PDT)
X-AuditID: 11807137-b7c4bae0000013e5-25-4e0d1080f347
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay16.apple.com (Apple SCV relay) with SMTP id 81.8D.05093.0801D0E4; Thu, 30 Jun 2011 17:10:40 -0700 (PDT)
Received: from [17.193.13.64] (unknown [17.193.13.64]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LNM006DLOG4S150@koseret.apple.com> for ietf@ietf.org; Thu, 30 Jun 2011 17:09:41 -0700 (PDT)
Subject: Re: HOMENET working group proposal
From: james woodyatt <jhw@apple.com>
In-reply-to: <201106302346.p5UNkCgp005000@fs4113.wdf.sap.corp>
Date: Thu, 30 Jun 2011 17:09:40 -0700
Message-id: <2EDF9C8B-FBDA-411E-840C-2AE0831AEF21@apple.com>
References: <201106302346.p5UNkCgp005000@fs4113.wdf.sap.corp>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1244.3)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCLMWRmVeSWpSXmKPExsUiON1OXbdBgNfPoOeTkcWzjfNZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVsfYGT8EWlorbl5wbGI8wdzFycEgImEg8WJjaxcgJZIpJXLi3 nq2LkYtDSKCTSeLYvA2MIAleAUGJH5PvsYDUMwvISxw8LwsSZhbQkvj+qJUFon46k8TMSZOY QBLCAtoS+75dYgax2QRUJL5dvgsW5xSwk9ixYAMTyBwWAVWJG7vLQUxeARuJ+f8cQSqEBGwl HjbcYwexRQSUJR5NPc8GcZq8xOKWz4wTGPlnITloFsJBs5ActICReRWjYFFqTmKloZleYkFB Tqpecn7uJkZQWDUUmu9g3P5X7hCjAAejEg9vYT+PnxBrYllxZe4hRgkOZiUR3lXVQCHelMTK qtSi/Pii0pzU4kOM0hwsSuK8qzO5/YQE0hNLUrNTUwtSi2CyTBycUg2MG6Q+/dApOPXq+Z8N S/5Nat49iXPplLwoR645jM2VBfZek6xmybPYlEtMEmv3Xqxx7kLhTfXy0gW1rV3ve/k52Sb4 iV/r8TzbsKNXYJ2jXnma0O/TxUvP9xzvWdLmd2dr/povF+8V33rwqPK9VkKWidnUMKVA6TWi D3btqNvjs3Z7r0LqVIc4JZbijERDLeai4kQAGL7V7CcCAAA=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 00:09:43 -0000

On Jun 30, 2011, at 18:46 , Martin Rex wrote:
> 
> And that [false police report incident] is really among the mild unpleasant things...

It's also not even remotely relevant.  Under the regime where that incident happened, it's not even news anymore when the police do that without any provocation at all.  There is nothing about NAT or dynamic subscriber IP assignment that provides any mitigation whatsoever of the risks entailed by living in a regime like that.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From moore@network-heretics.com  Thu Jun 30 18:11:31 2011
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 6C3EA21F867D for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 18:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.566
X-Spam-Level: 
X-Spam-Status: No, score=-3.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Z-Td1DNp14N for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 18:11:30 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 9039821F85FE for <ietf@ietf.org>; Thu, 30 Jun 2011 18:11:30 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id E5F7420500; Thu, 30 Jun 2011 21:11:29 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Thu, 30 Jun 2011 21:11:29 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=WWYTxDBA7+u1JvVAdOzl5nJnM6o=; b=Ynjt8JnWeB4iz2iE7UUfxbIrkSvnW/2KAaxp4L35Cm1X/5xeN1FtlORmiQ2G+M2FB/Ek/hlb/qYHe8nnC/saiou0Z0bzn1pA4pbMKdJIJd+NW9ufVsQU6ouA+BzXvkaM8sFnloTdPphn3EqPyXM+5GJ7Ph8iyMea5mbV/TWSLRc=
X-Sasl-enc: R3hysEXZEZj6VA+b2QgXGwlAbiavzeZ0xcj4Fc1xtPuI 1309482689
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 1081840282E; Thu, 30 Jun 2011 21:11:28 -0400 (EDT)
Subject: Re: HOMENET working group proposal
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <201106302346.p5UNkCgp005000@fs4113.wdf.sap.corp>
Date: Thu, 30 Jun 2011 21:11:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E037C767-8E97-480B-A106-D712CBA2063B@network-heretics.com>
References: <201106302346.p5UNkCgp005000@fs4113.wdf.sap.corp>
To: mrex@sap.com
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 01:11:31 -0000

On Jun 30, 2011, at 9:46 PM, Martin Rex wrote:

> Keith Moore wrote:
>>=20
>> On Jun 30, 2011, at 1:09 AM, Martin Rex wrote:
>>=20
>> (a bunch of stuff in defense of NAT)
>>=20
>> Rather than having another of an endless series of discussions about
>> the merits of NAT or lack thereof, can we just agree that it should
>> not be pre-ordained that this WG should assume NAT as a solution?
>=20
> You absolutely want to have fairly fixed addresses within
> your home network, and you absolutely want to have a short-lived
> ephemeral IP-Address assigned on your internet side of your
> home gateway for the purpose of privacy.

No, *you* want these things.  I do not, and imposing them is not in the =
interests of users in general.

> Otherwise the number of very unpleasant surprises, including
> stuff like this:
>=20
>   http://www.theregister.co.uk/2011/06/30/xbox_swat_police_rait/

Nowhere in this article does it say that the user had a static IP =
address.  And as I indicated earlier, even with a dynamic IP address, =
there are frequently other ways to find a host's IP address.  If you =
force all hosts on a home network to have dynamic IP addresses, you =
break applications that need stable addresses.  If you don't force all =
hosts on a home network to have dynamic IP addresses, those that don't =
need stable addresses can still get ephemeral addresses via privacy =
addresses, DHCP, or other means.

You keep arguing for the perpetuation of bad hacks because of accidental =
properties of those hacks.  I'd rather have well-designed mechanisms =
that are tailor made to suit particular purposes. =20

Keith


From narten@us.ibm.com  Thu Jun 30 21:55:26 2011
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 0DD2E11E80A1 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 21:55:26 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bD3QKPMPmOmR for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 21:55:25 -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 5FF2011E8072 for <ietf@ietf.org>; Thu, 30 Jun 2011 21:55:25 -0700 (PDT)
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by e39.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p614cZe8010160 for <ietf@ietf.org>; Thu, 30 Jun 2011 22:38:35 -0600
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p614r316173322 for <ietf@ietf.org>; Thu, 30 Jun 2011 22:53:03 -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 p614wRqK000797 for <ietf@ietf.org>; Thu, 30 Jun 2011 22:58:27 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.176.22]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p614wRKF000792 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 30 Jun 2011 22:58:27 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p614r2vw011422 for <ietf@ietf.org>; Fri, 1 Jul 2011 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p614r2XS011410 for ietf@ietf.org; Fri, 1 Jul 2011 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201107010453.p614r2XS011410@rotala.raleigh.ibm.com>
Date: Fri, 01 Jul 2011 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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 04:55:26 -0000

Total of 170 messages in the last 7 days.
 
script run at: Fri Jul  1 00:53:01 EDT 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 15.88% |   27 | 13.35% |   185247 | moore@network-heretics.com
  1.76% |    3 | 15.97% |   221649 | robmcm@microsoft.com
  5.29% |    9 |  3.78% |    52401 | fernando@gont.com.ar
  4.12% |    7 |  2.92% |    40484 | mrex@sap.com
  2.35% |    4 |  3.95% |    54801 | touch@isi.edu
  3.53% |    6 |  2.73% |    37874 | sm@resistor.net
  3.53% |    6 |  2.32% |    32150 | joelja@bogus.com
  3.53% |    6 |  2.04% |    28247 | jnc@mercury.lcs.mit.edu
  2.35% |    4 |  2.31% |    32121 | evnikita2@gmail.com
  2.35% |    4 |  2.30% |    31862 | jari.arkko@piuha.net
  2.35% |    4 |  2.12% |    29459 | john-ietf@jck.com
  2.94% |    5 |  1.52% |    21087 | mohta@necom830.hpcl.titech.ac.jp
  2.35% |    4 |  1.93% |    26749 | jhw@apple.com
  2.35% |    4 |  1.89% |    26243 | marka@isc.org
  2.35% |    4 |  1.74% |    24161 | dougb@dougbarton.us
  1.76% |    3 |  1.63% |    22668 | palm@broadcom.com
  1.18% |    2 |  2.15% |    29769 | jmh@joelhalpern.com
  1.76% |    3 |  1.38% |    19193 | d3e3e3@gmail.com
  1.76% |    3 |  1.37% |    19036 | john@jlc.net
  1.76% |    3 |  1.18% |    16442 | paul.hoffman@vpnc.org
  1.76% |    3 |  1.10% |    15256 | julian.reschke@gmx.de
  1.18% |    2 |  1.23% |    16999 | cb.list6@gmail.com
  0.59% |    1 |  1.72% |    23914 | paulfordh@uk.ibm.com
  1.18% |    2 |  1.08% |    14965 | kathleen.moriarty@emc.com
  1.18% |    2 |  0.99% |    13707 | mark@townsley.net
  1.18% |    2 |  0.94% |    13020 | rja.lists@gmail.com
  0.59% |    1 |  1.50% |    20759 | otuenehoj@gmail.com
  1.18% |    2 |  0.90% |    12430 | stephen.farrell@cs.tcd.ie
  1.18% |    2 |  0.86% |    11912 | scott.rose@nist.gov
  1.18% |    2 |  0.85% |    11737 | msk@cloudmark.com
  0.59% |    1 |  1.42% |    19684 | osa.peter@gmail.com
  1.18% |    2 |  0.83% |    11519 | brian.e.carpenter@gmail.com
  1.18% |    2 |  0.82% |    11352 | barryleiba@computer.org
  1.18% |    2 |  0.76% |    10612 | swmike@swm.pp.se
  1.18% |    2 |  0.75% |    10373 | melinda.shore@gmail.com
  0.59% |    1 |  1.00% |    13821 | ron.even.tlv@gmail.com
  0.59% |    1 |  0.90% |    12512 | eburger@standardstrack.com
  0.59% |    1 |  0.86% |    11990 | marshall.eubanks@gmail.com
  0.59% |    1 |  0.72% |     9943 | even.roni@huawei.com
  0.59% |    1 |  0.69% |     9534 | narten@us.ibm.com
  0.59% |    1 |  0.63% |     8699 | suresh.krishnan@ericsson.com
  0.59% |    1 |  0.60% |     8370 | fluffy@cisco.com
  0.59% |    1 |  0.59% |     8207 | daedulus@btconnect.com
  0.59% |    1 |  0.56% |     7745 | jason.weil@twcable.com
  0.59% |    1 |  0.55% |     7681 | ycsijes@gmail.com
  0.59% |    1 |  0.55% |     7601 | r.e.sonneveld@sonnection.nl
  0.59% |    1 |  0.49% |     6802 | presnick@qualcomm.com
  0.59% |    1 |  0.46% |     6451 | dwhite@olp.net
  0.59% |    1 |  0.46% |     6441 | aiverson@spamresource.com
  0.59% |    1 |  0.45% |     6268 | tjc@ecs.soton.ac.uk
  0.59% |    1 |  0.44% |     6131 | warren@kumari.net
  0.59% |    1 |  0.44% |     6098 | ice@cisco.com
  0.59% |    1 |  0.43% |     6033 | dotis@mail-abuse.org
  0.59% |    1 |  0.43% |     5978 | ben@nostrum.com
  0.59% |    1 |  0.43% |     5943 | pthubert@cisco.com
  0.59% |    1 |  0.42% |     5768 | scott@kitterman.com
  0.59% |    1 |  0.40% |     5557 | rdroms.ietf@gmail.com
  0.59% |    1 |  0.38% |     5307 | otroan@employees.org
  0.59% |    1 |  0.37% |     5131 | dhc2@dcrocker.net
  0.59% |    1 |  0.37% |     5096 | randy@qualcomm.com
  0.59% |    1 |  0.36% |     5033 | petithug@acm.org
  0.59% |    1 |  0.36% |     5033 | iljitsch@muada.com
  0.59% |    1 |  0.35% |     4844 | ajs@anvilwalrusden.com
  0.59% |    1 |  0.35% |     4810 | huitema@microsoft.com
  0.59% |    1 |  0.33% |     4646 | erik.taraldsen@telenor.com
  0.59% |    1 |  0.31% |     4289 | john@jck.com
--------+------+--------+----------+------------------------
100.00% |  170 |100.00% |  1387644 | Total

From jvasseur@cisco.com  Thu Jun 30 22:30:19 2011
Return-Path: <jvasseur@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 4215B21F869B; Thu, 30 Jun 2011 22:30:19 -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.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WunDwdCTiGS3; Thu, 30 Jun 2011 22:30:15 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id 821B821F86BD; Thu, 30 Jun 2011 22:30:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jvasseur@cisco.com; l=1903; q=dns/txt; s=iport; t=1309498215; x=1310707815; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:from:to:cc; bh=+Ltjwy5EJJwOl/+/MsYUAqAvJQKr07MYx1z2X1K3YIs=; b=OPq3j1dfSq9dNWtgpMoC5wcSUFY/59NzjbQNhSDeZIi+gTpQQ0rS/60J An7wVsEBPX+i6HrL0/3qt97nIHTdob9ke93ZrIjBuOIZwZMmu1McK9j+I wgLqmnFcJDvVwXRHJXLKU1g8Dmd5mWtM5j+93W66w0X21vxY2DjtntBXF I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvIAAKRaDU6tJV2a/2dsb2JhbABSmCuPMneIeaIlnXKGMgSHPo9xi08
X-IronPort-AV: E=Sophos;i="4.65,456,1304294400"; d="scan'208";a="725212169"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by sj-iport-6.cisco.com with ESMTP; 01 Jul 2011 05:30:14 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p615UEZJ019423;  Fri, 1 Jul 2011 05:30:14 GMT
Received: from xmb-rcd-203.cisco.com ([72.163.62.210]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 1 Jul 2011 00:30:14 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [fun] [homegate] HOMENET working group proposal
Date: Fri, 1 Jul 2011 00:30:14 -0500
Message-ID: <E104C094D4487643BB93F43875CBCBCF032BD3CF@XMB-RCD-203.cisco.com>
In-Reply-To: <780C3063-AD82-46F3-874A-C4E1E61EE508@townsley.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [fun] [homegate] HOMENET working group proposal
Thread-Index: Acw3RGDhWzyvVlXSTKCZLwtsLh7yEgAa5NF6
From: "JP Vasseur (jvasseur)" <jvasseur@cisco.com>
To: <mark@townsley.net>, <moore@network-heretics.com>
X-OriginalArrivalTime: 01 Jul 2011 05:30:14.0580 (UTC) FILETIME=[F4627740:01CC37AF]
Cc: ietf@ietf.org, homegate@ietf.org, fun@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 05:30:19 -0000

I'd like to second the relaxation of "wherever possible", which may lead =
to a suboptimal solution for several components.

JP Vasseur
Cisco Fellow

Sent from Blackberry

----- Original Message -----
From: Mark Townsley [mailto:mark@townsley.net]
Sent: Thursday, June 30, 2011 11:33 AM
To: Keith Moore <moore@network-heretics.com>
Cc: IETF Discussion <ietf@ietf.org>; fun@ietf.org <fun@ietf.org>; =
homegate@ietf.org <homegate@ietf.org>
Subject: Re: [fun] [homegate] HOMENET working group proposal



On Jun 30, 2011, at 5:46 PM, Keith Moore wrote:

>=20
> On Jun 30, 2011, at 5:57 AM, Mark Townsley wrote:
>=20
>>=20
>> I think the consensus we had in the past BoFs and discussion in and =
around this topic can be summed up as stating that homenet deliverables =
will:
>>=20
>> - coexist with (existing) IPv4 protocols, devices, applications, etc.
>> - operate in a (future) IPv6-only home network in the absence of IPv4
>> - be IP-agnostic whenever possible
>=20
> I'd like for this group to relax the "wherever possible" bit, so as to =
not preclude solutions where IPv6 can do a better job than IPv4.

Yes, and I think that IPv6 should naturally do a better job than IPv4 in =
the cases where it can.=20

My original mail had this restatement of the above, which I think gets =
closer to what you want:

>> However, when we can define something that is needed for IPv6 in a =
way that is also useful for IPv4 without making significant concessions, =
we should go ahead and do so.


- Mark

>=20
> IPv4 is a dinosaur gasping for its last breaths.
>=20
> Keith
>=20
>=20
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate

_______________________________________________
fun mailing list
fun@ietf.org
https://www.ietf.org/mailman/listinfo/fun

From shimshamshimmy@gmail.com  Thu Jun 30 22:34:21 2011
Return-Path: <shimshamshimmy@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D9DC11E80F9 for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 22:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q7XoOinCgzJd for <ietf@ietfa.amsl.com>; Thu, 30 Jun 2011 22:34:20 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4889211E80F7 for <ietf@ietf.org>; Thu, 30 Jun 2011 22:34:20 -0700 (PDT)
Received: by vws12 with SMTP id 12so2616019vws.31 for <ietf@ietf.org>; Thu, 30 Jun 2011 22:34:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=Dl1LgUBti1MqyePwRBFhJgR+aRjCvMglSxiRawrT3+k=; b=TO6ZXhDoCjYM+1n94z5S13L6nLMOEHXJl+aycZal5iIVrIlXMoMvagb4aVQrrNbeKV HCZai/QcdjZ4nTa2J3CIwBvYtKF4lcKU2pOverAW1QtzjTPBcl6tAZVhuivcwKga7h6W IYaqb5M58+gmDKEV9lXTzKwxA8wViKCyXp/FI=
Received: by 10.52.27.103 with SMTP id s7mr314755vdg.96.1309498459135; Thu, 30 Jun 2011 22:34:19 -0700 (PDT)
MIME-Version: 1.0
Sender: shimshamshimmy@gmail.com
Received: by 10.52.160.233 with HTTP; Thu, 30 Jun 2011 22:33:59 -0700 (PDT)
From: Jun Murai <jun@wide.ad.jp>
Date: Fri, 1 Jul 2011 14:33:59 +0900
X-Google-Sender-Auth: vWzUlEb8skkaDKKfNXmPCzIIhIM
Message-ID: <BANLkTi=PYOqUK7ZApNG8aoWK7wWPFDdurw@mail.gmail.com>
Subject: reminder: Itojun Service Award 2011 nomination
To: "ietf@ietf. org" <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2011 05:34:21 -0000

Dear IETFers,
Let me remind you for the nomination of  the Itojun Service Award.
The deadline is July 15.
Thanks,
Jun Murai
===
ANNOUNCING: CALL FOR CANDIDATES FOR ITOJUN SERVICE AWARD

The Itojun Service Award is presented every year to an individual or a
group who has made outstanding contributions in service to the IPv6
community.   The deadline for nominations for this year's award is 15
July 2011.  The award will be presented at the 82nd meeting of the
IETF to be held in November 2011 in Taipei, Taiwan.

About the Award

The Itojun Service Award was established by the friends of Itojun and
administered by the Internet Society (ISOC), recognises and
commemorates the extraordinary dedication exercised by Itojun over the
course of IPv6 development.  The award includes a presentation
crystal, a US$3,000 honorarium, and a travel grant.

The award is focused on pragmatic technical contributions, especially
through development or operation, with the spirit of servicing the
Internet.  With respect to the spirit, the selection committee seeks
contributors to the Internet as a whole; open source developers are a
common example of such contributors, although this is not a
requirement for expected nominees.  While the committee primarily
consider practical contributions such as software development or
network operation, higher level efforts that help those direct
contributions will also be appreciated in this regard.  The
contribution should be substantial, but could be immature or ongoing;
this award aims to encourage the contributor to keep their efforts,
rather than just recognizing well established work.  Finally,
contributions of a group of individuals will be accepted as deployment
work is often done by a large project, not just a single outstanding
individual.

The award is named after Dr. Jun-ichiro "Itojun" Hagino, who passed
away in 2007, aged just 37.  Itojun worked as a Senior Researcher at
Internet Initiative Japan Inc. (IIJ), was a member of the board of the
Widely Integrated Distributed Environment (WIDE) project, and from
1998 to 2006 served on the groundbreaking KAME project in Japan as the
"IPv6 samurai". He was also a member of the Internet Architecture
Board (IAB) from 2003 to 2005.

For additional information on the award, please visit
http://www.isoc.org/awards/itojun/

Award Nomination Procedure

Neither the nominee nor nominator needs to be a member of ISOC.
Nominate via email to <itojun-award at elists.isoc.org> and include the
following details:
1. Name and Email address of nominee (in case of a group nominee,
 names and Email addresses of representative persons of that group)
2. CV/Bio of nominee (in case of a group nominee, a summary of the
 group's achievements)
3. Statement of recommendation including specific acts, works,
 contributions, and other criteria that would show the nominee to
 fit the standard set by Itojun.  Please include corroborating
 references with their name, email address, and telephone
 number. Conclude with your affiliation, postal address, and
 telephone number as well as the postal address, telephone and fax
 number of the nominee.

Thank you in advance for your support,

Jun Murai
Itojun Service Award Selection Committee
